Oracle Key Manager: AFTER UPGRADING VERSION 2.5.2 SYSTEM DID NOT REBOOT- SYSTEM DOWN (Doc ID 1587186.1)

Last updated on SEPTEMBER 30, 2013

Applies to:

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

Symptoms

When resetting the KMA to Factory Defaults on all 6 KMA's that I have upgraded to OKM 2.5.2, the following are the messages on the eLOM Console:

OKM: Console unavailable during reset

OKM: services stopped. Re-creating LiveUpgrade inactive partition. Do NOT interrupt…

OKM: Inactivate partition re-created
OKM: wiping the other partitions…

OKM: resetting the system configuration …

svc.startd The system is coming down. Please wait…
svc.startd 65 system services are now being stopped.

OKM: stopping services…

OKM: services stopped. Re-creating LiveUpgrade inactive partition. Do NOT interrupt…

OKM: Inactivate partition re-created
OKM: wiping the other partitions…

OKM: resetting the system configuration …

svc.startd The system is coming down. Please wait…
svc.startd 65 system services are now being stopped.

OKM: stopping services…

OKM: services stopped. Re-creating LiveUpgrade inactive partition. Do NOT interrupt…

OKM: Inactivate partition re-created
OKM: wiping the other partitions…

OKM: resetting the system configuration …

svc.startd The system is coming down. Please wait…
svc.startd 65 system services are now being stopped.


The KMA starts up successfully after the reset process. However, both inactive and active partitions now show OKM 2.5.2.
It used to be that the old OKM version is kept in the inactive partition.

Changes

Upgraded KMA to OKM 2.5.2 and the KMA firmware to version 3d16.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms