Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1569678.1
Update Date:2013-07-24
Keywords:

Solution Type  Problem Resolution Sure

Solution  1569678.1 :   OKM 2.5.2: Replication Lag Size Stuck Around 480k Size After Activating 2.5.2 OKM Version  


Related Items
  • Oracle Key Manager
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Backup Software-Filesystems>SN-TP: Encryption
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Created from <SR 3-7540243401>

Applies to:

Oracle Key Manager - Version 2.3 to 2.5.2 [Release 2.0]
Information in this document applies to any platform.

Symptoms

Customer upgrading his KMA's from 2.3.1 to 2.5.2 customer noticed "not responding" on the service network and lag size seems to be stuck at 480.

Changes

 Recently upgraded OKM software from 2.3.1 to 2.5.2

Cause

Upgrade of the OKM software.
 

Solution

The status of "Not Responding" for the service network is normal if all the KMA's are not on the same subnet.

Noticed on two KMA's that were activated on 2.5.2, the lag size appears to be stuck at 480, this is also normal until all the KMA's have been activated and the replication levels are the same, level 14 for OKM 2.5.2.

References

<NOTE:1447111.2> - Information Center: Oracle Key Manager (KMS/OKM) Overview Advisor

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback