OID 11g Fails to Start After Metadata Repository (MR) Database (DB) Upgrade. Oidmon Log Errors: ORA-1034, ORA-01034: ORACLE not available | ORA-27101: shared memory realm does not exist | Error: 2: No such file or directory (Doc ID 2076825.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Internet Directory - Version 11.1.1 and later
Information in this document applies to any platform.

Symptoms

Oracle Internet Directory (OID) instance had been working.

After upgrading the OID repository database, e.g., to 12c, OID fails to start with oidmon-0001.log error:

[2015-11-11T13:17:28.885306-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: myoidhost.mycompany.com] [pid: 14657] [tid: 0] Guardian: [oidmon]: Unable to connect to database,
  will retry again after 10 sec

[2015-11-11T13:17:38.16684-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: myoidhost.mycompany.com] [pid: 15664] [tid: 0] OIDMON_STOP: Thread started

[2015-11-11T13:17:38.17245-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: myoidhost.mycompany.com] [pid: 15664] [tid: 0] OIDMON_STOP: Connecting to database, connect string is oiddb

[2015-11-11T13:17:38.895325-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: myoidhost.mycompany.com] [pid: 14657] [tid: 0] Guardian: Connecting to database, connect string is oiddb

[2015-11-11T13:18:08.137937-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: myoidhost.mycompany.com] [pid: 15664] [tid: 0] OIDMON_STOP: Could not login to the database after 10 attempts

[2015-11-11T13:18:08.138039-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: myoidhost.mycompany.com] [pid: 15664] [tid: 0] OIDMON_STOP: [gsdsiConnect] ORA-1034, ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory

[2015-11-11T13:18:08.138156-06:00] [OID] [NOTIFICATION:16] [] [OIDMON] [host: myoidhost.mycompany.com] [pid: 15664] [tid: 0] OIDMON_STOP: [oidmon]: Unable to connect to database,
  will retry again after 10 sec


The issue can be reproduced at will with the following steps:
1. Shutdown OID instance
2. Stop SqlNet listener
3. Upgrade the repository database and register with 12c listener (no port change)
4. Bring up the OID instance back again
5. OID will not start with errors mentioned above

 

A sqlplus connection attempt from the OID home fails with:

 

Changes

OID DB was upgraded.

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