OKM - "Key not found" errors in the OKM audit log

Asset ID:	1-72-1540231.1
Update Date:	2014-09-04
Keywords:

Solution Type Problem Resolution Sure

Solution 1540231.1 : OKM - "Key not found" errors in the OKM audit log

Applies to:

Oracle Key Manager - Version 2.0.2 to 2.5.2 [Release 2.0]
Sun StorageTek 9840D Tape Drive - Version Not Applicable to Not Applicable [Release N/A]
ORACLE Server for UNIX System V/386

Symptoms

9840D tape drives are hanging or timeing out waiting for encryption keys to be sent to them from KMA servers.

Repeated errors in the OKM Audit log:
F497C25F6A8FFF4F00000000013F4F96        F497C25F6A80E54F        mxzkmmbm09      Data Unit Agent Operations
Medium Term Retention   Retrieve Data Unit Keys Key not found   Error   000208000140
2013-03-23 00:43:05.952617+00   469C    172.18.21.25    Data Unit ID = 09A38BT24598970F821B0C5AAC80D296,
External Unique ID = (null), External Tag = Z89280, Page Size = 31, Page Offset = 0,
Key ID = 000000000000000000000000000000000000000000000000000000000000     Retry using different input

Changes

none

Cause

There is a key ID cache issue in 9840D drives running code version 1.45.703 and below. This issue generates a "Key not found" error
during OKM data unit key retrieval process, typically when a KMA is busy with multiple key requests.

Solution

Apply 9840D special build code RL.46.703 This special build code fixes the key ID cache issue.
GA code 1.46.703 should not be installed as it has a 10 second key timeout value that can cause the drive
to fail to get a key and failover.

Attachments

This solution has no attachment