OBIEE, OBI Apps, ODI, Informatica, Essbase, BI Publisher...you name it. The OBI suite entails them all and more.
I will talk mainly about its technical aspects, interesting findings and noteworthy solutions, but will definitely throw in some random weirdness.

Friday, March 23, 2012

OBIEE 11g in-place upgrade issue with configuration lock

In-place upgrade within OBIEE 11 versions (from .3 to .5 o r .6 or from .5 to .6) can be a whole lot quicker than out-of-place ones but are also more interesting in terms of potential issues arising. After two uneventful in-place upgrades from 11.1.1.5 to 11.1.1.6 I had a more challenging third upgrade with some unexpected errors.

Looking into the provision.log (situated in MW_HOME/instances/myinstance/diagnostics/logs/OPMN/opmn) read as follows:

[Deployer:149163]The domain edit lock is owned by another session in non-exclusive mode - this deployment operation requires exclusive access to the edit lock and hence cannot proceed. If you are using "Automatically Aquire Lock and Activate Changes" in the console, then the lock will expire shortly so retry this operation.

I ran the upgradenonj2eeapp.sh a second time to see what it would do:

SEVERE: Command failed:oracle.as.config.ProvisionException: Exception while unregistering the instance at oracle.as.config.impl.OracleASInstanceImpl.unregister(OracleASInstanceImpl.java:290) at oracle.as.config.impl.OracleASInstanceImpl.unregister(OracleASInstanceImpl.java:250) at oracle.as.config.provisioner.commands.UnregisterInstanceCommand.execute(UnregisterInstanceCommand.java:34) at oracle.as.config.provisioner.InstallerCmdLine.run(InstallerCmdLine.java:146) at oracle.as.config.provisioner.InstallerCmdLine.main(InstallerCmdLine.java:46)Caused by: oracle.as.config.impl.SimpleProvisionException: Failed to unregister instance instance1. It does not exist on the adminserver.

So, a real no-go situation. Luckily, the OBIEE EMG already had a post which contained part of the solution. Root cause of the initial error was that there was a lock on the configuration I hadn't seen:

"Release Configuration" removed the immediate error source. Next step was re-running upgradenonj2eeapp.sh again to see what would happen and obviously the error "Failed to unregister instance instance1. It does not exist on the adminserver." still persisted since initially the first half of the script had run through and un-registered my instance. So off to some opmnctl commands to undo the damage.