OID 11g Fails to Start After Patching / a Patchset -- Oidmon log shows: OIDMON_STOP: WARNING: Connected to incorrect OID base schema version, (version=OID <lower 11g or 10g patchset>). WARNING: OID (version <...>) is now operating in read_only mode
(Doc ID 1900337.1)
Last updated on JANUARY 29, 2021
Applies to:Oracle Internet Directory - Version 11.1.1 to 188.8.131.52.0 [Release 11g]
Information in this document applies to any platform.
Oracle Internet Directory (OID) 11g, for example, 184.108.40.206's (not an upgrade from 10g), which had been working fine.
Applied a newer patchset, e.g. 220.127.116.11 or 18.104.22.168.
Afterwards, did not start or test any process or service, nor did any checking after the upgrade; just went on and applied a CPU patch 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, for example:
WARNING: OID (version 22.214.171.124.0) is now operating in read_only mode
The ODS schema version shows the correct 126.96.36.199 in schema_version_registry, however, the following sql returns an older 11g or 10g version, for example:
But there is no orclcompatibleversion=188.8.131.52 (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 184.108.40.206. 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.
This issue is not be reproducible on a different environment (env).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document