KMS/OKM - Downgrade Issue From 2.3.x to 2.2.x Fails to Boot

Asset ID:	1-72-1339736.1
Update Date:	2011-07-21
Keywords:

Solution Type Problem Resolution Sure

Solution 1339736.1 : KMS/OKM - Downgrade Issue From 2.3.x to 2.2.x Fails to Boot

Applies to:

Oracle Key Manager - Version: 2.2 and later [Release: 2.0 and later ]
Information in this document applies to any platform.

Symptoms

Downgrade issue from 2.3.x to 2.2.x fails to boot.
Receives error:
/opt/SUNWkms2/bin/changeDatabasePasswords.sh: notifyDatabaseConfigChange: not found
psql: FATAL: password authtication failed for user "postgres"

Changes

Downgrading microcode on KMS.

Cause

The problem is caused by the process of uploading and applying a software upgrade. That process extracts a tar file which contains a new /opt/SUNWkms2/bin/kms-common.sh script. This new kms-common.sh script no longer contains the function notifyDatabaseChangeConfig(). That function has been moved to the script postgresql-common.sh. If the active OS does not have the postgresql-common.sh script in /opt/SUNWkms2/bin (which was added in 2.3), then factory reset (and possibly other functionality which changes the database password) will fail at the KMA console.

Solution

Recommend not to downgrade from 2.3.x to 2.2.x if possible.

Workaround is to logon to customer system via webex and vi common.sh

CR7060009

Sometimes resetting the KMA from the ILOM will help the boot process continue otherwise do not factory reset.

Another workaround is to enable the technical support and primary administrator account and then manually edit the script /opt/SUNWkms2/bin/kms-common.sh and append the following lines:

# Send a HUP signal to PostgreSQL or reload to tell it that one of its
# config files has changed

notifyDatabaseConfigChange()
{
pgBinPath=$1
if [ -z "${pgBinPath}" ]; then
pgBinPath=${PGSQL_BINPATH}
fi

pidFile=${pgDataDir}/postmaster.pid
pgPid=`head -1 ${pidFile} 2>/dev/null`
if [ -n "${pgPid}" ]; then
kill -HUP ${pgPid}
else
su - postgres -c "${pgBinPath}/pg_ctl reload -D ${pgDataDir}"
fi
}

This should only be done on a 2.2.x KMA and only if the kms-common.sh script does not contain the notifyDatabaseConfigChange() function. Also, this should be done after the new software has been uploaded, but before the 2.2.x KMA has been factory reset.

Provided by Stephen Patching.

Attachments

This solution has no attachment