OID 11g Fails to Start After Patching from 11.1.1.6.0 to 11.1.1.7.0 -- Oidmon log shows: OIDMON_STOP: WARNING: Connected to incorrect OID base schema version, (version=OID 10.1.2.1.0). WARNING: OID (version 11.1.1.7.0) is now operating in read_only mode (Doc ID 1900337.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Internet Directory - Version 11.1.1.7.0 to 11.1.1.7.0 [Release 11g]
Information in this document applies to any platform.

Symptoms

Existing three High Available (HA) Oracle Internet Directory (OID) 11g 11.1.1.6's (not an upgrade from 10g) which had been working fine.

Attempting to patchset to 11.1.1.7, and apply Apr CPU 2014 patch on top.

Started by updating WebLogic Server (WLS) from 10.3.6.0.7 to 10.3.6.0.8 first.

Next applied Patchset 6 11.1.1.7.

Afterwards, did not start or test any process or service, nor did any checking after the upgrade; just went on and applied the April 2014 CPU right on top.

Ran the PatchSet Assistant (PSA) supplying "sys as sysdba" for connection as instructed.  The PSA .log and .out files returned a successful upgrade and no errors.

Note: The upgrade post-patching did not prompt to run "oidRoot.sh" as noted in the documentation, and it only requested to run "oracleRoot.sh" once.


Now OID will not start.  The oidmon log file shows:

[2014-05-05T15:04:39-04:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: myoidhost.mycompany.com] [pid: 13669] [tid: 0] OIDMON_STOP: WARNING: Connected to incorrect OID base schema version, (version=OID 10.1.2.1.0).
WARNING: OID (version  11.1.1.7.0) is now operating in read_only mode

 


The ODS schema version shows the correct 11.1.1.7 in schema_version_registry, however, the following sql returns the older version:

But there is no orclcompatibleversion=11.1.1.7 (neither from the sql query nor in the oiddiag report).

 

The issue is similar to <Document 1569628.1>, and <Document 1545286.1> which is upgrading to 11.1.1.6.  The supported/preferred method to correct upgrade problems is as in <Document 1376706.1> (i.e., to re-run all upgrade tasks and ensure there are no failures of any sort in any logs), however this has not worked in this case.


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