Oracle Key Manager (OKM) - Tapes Not Able to Load on Encrypted Drive Because of FSC 6146

Asset ID:	1-72-1949893.1
Update Date:	2018-03-20
Keywords:

Solution Type Problem Resolution Sure

Solution 1949893.1 : Oracle Key Manager (OKM) - Tapes Not Able to Load on Encrypted Drive Because of FSC 6146

Applies to:

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

Symptoms

Tape stuck on drive T10K.

Load failed resultcode = 6406

Receiving the following error in the host application log:

@SLS6684I RTD RTD507F1 on VTSS VTAPE5 Returned ECAM error CC=5 RC=108
@SLS6625E RTD RTD507F1 reported Unsolicited sense: 004820000000002001000000000000000000000000000000CE0E502039870000

Receiving the following errors in the library log:
Error from device Code: 603 - Drive cartridge is present, drive 1,4,1,1,4: load FAILED resultCode = 6440, (driveType = T10000b-Enc, driveFirmware = 1.50.203-5.30, sn = 572004003987)
Error from device Code: 604 - Drive is not functional, drive 1,4,1,1,4: load FAILED resultCode = 6406, (driveType = T10000b-Enc, driveFirmware = 1.50.203-5.30, sn = 572004003987)

OKM shows KMA1 not able to provide keys and may have to be rebooted:

F7F2188B1AE1B0290000000001B6B736 F7F2188B1AE1B029 rchasekma2 Cluster Client Communication Medium Term Retention Request Peer Replication Service SOAP Error Warni
ng 000088000025 2014-11-20 14:17:50.789342+00 rchasekma1 xx.xx.xx.xx Peer KMA ID = 54E398F5FE9415C4, Anti-Entropy Push = FALSE, Function Name = PushUpdates, SOAP Fault Code = SOAP-ENV:Client, SOAP Fault String = Timeout, SOAP Fault Detail = connect failed in tcp_connect(), Error Code = 28 If the peer KMA is currently applying initial updates after joining the Cluster, then wait until it completes applying these updates. Otherwise, check the management network connection on the KMA reporting the issue as well as the peer KMA. If this condition persists, then one of these KMAs might need to be rebooted.

Changes

No known change but one KMA is showing hung processes and SOAP errors

Cause

The KMA that provides keys to the drive is not functional

Solution

Reboot the KMA.

If rebooting is not possible, and another KMA can provide keys to this drive, delete the drive agent from the KMA server agent list and then re-create the agent and enroll in the other KMA.

Attachments

This solution has no attachment