| Asset ID: |
1-72-1549068.1 |
| Update Date: | 2017-12-13 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1549068.1
:
OKM - Unable To Join a New KMA To an existing KMA Cluster
| Related Categories |
- PLA-Support>Sun Systems>TAPE>Backup Software-Filesystems>SN-TP: Encryption
|
In this Document
Created from <SR 3-6918705811>
Applies to:
Oracle Key Manager - Version 2.0.0 to 2.5.2 [Release 2.0]
Information in this document applies to any platform.
Symptoms
Unable to add a new KMA to the cluster
Error messages in the KMA audit log:
----
F497C25F6A80E54F00000000014393ED F497C25F6A80E54F tx2kmmfm02 System Messages Medium Term Retention Database Command Invalid result set size Error 000004000013 2013-04-14 07:02:38.421+00 Table Name = ReplicationLog (KeyPoolSize), Number of Rows = 0 Contact Customer Support and gather a system dump if possible
B35ACB8EB892F680000000000120AB46 B35ACB8EB892F680 tx2kmmfm01 System Messages Medium Term Retention Database Command Invalid result set size Error 000004000013 2013-04-14 07:20:50.611+00 Table Name = ReplicationLog (KeyPoolSize), Number of Rows = 0 Contact Customer Support and gather a system dump if possible
Tried joining the new KMA to the 2 existing KMAs in the cluster and saw the same outcome.
Changes
Add a third KMA to an existing KMA cluster
Cause
The " Invalid result set size Error" messages referred to the "Table Name = ReplicationLog (KeyPoolSize)" attribute.
The customer increased the key pool size and this resolved the problem.
Solution
1. Increase the Key Pool Size parameter
- On the OKM GUI, login as security officer.
- Bring up the KMA List window and modify the Key Pool Size parameter using the "Modify Key Pool Size ..." option.
2. Join the new KMA to one of the existing KMAs in the cluster.
Attachments
This solution has no attachment
