Oracle Key Manager (OKM) - Import Key Fails With "Key Already Exists But Is Destroyed Or Not Activated"
(Doc ID 2379929.1)
Last updated on SEPTEMBER 09, 2021
Applies to:
Sun StorageTek Crypto Key Management System - Version All Versions to All Versions [Release All Releases]Information in this document applies to any platform.
Symptoms
A KMA cluster with four node was separated and are now operating independently.
A key assigned to a tape written recently in the cluster before they were separated needed to be imported to the other cluster to retrieve data from the tape.
There was a problem where the customer could not import the key into that cluster because of a relic duplicate Key ID.
So the key is active in one cluster and inactive in the other, but the that tape needs the encryption key is in the wrong cluster. A straight import across Transfer Partners fails.
Changes
A four node cluster was separated to become two independent clusters.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |