OID Does Not Automatically Restart / Reconnect to DB After Extended DB Shutdown, Restart or Reboot. How to Stop and Start / Restart OID Remotely from Its Database Server? oidmon Log Shows: Guardian: Shutting down / Guardian: Exiting with status 0
(Doc ID 1543866.1)
Last updated on DECEMBER 15, 2020
Applies to:Oracle Internet Directory - Version 11.1.1 and later
Information in this document applies to any platform.
Oracle Internet Directory (OID) 11g, 12c or higher.
OID does not reconnect automatically to the Database (DB) when it comes back up from an outage, planned outage, or DB server reboot.
OID keeps shutting down whenever its DB repository is being shutdown for an extended period of time for maintenance or other purposes.
Whenever the oid component goes down after the database shutdown, oidmon process does not stay alive and goes down as well. Once the DB goes down and restarts, the oid component never comes back up.
Example 12c oidmon log error:
[2019-07-31T00:05:02.161166-04:00] [OID] [NOTIFICATION:16]  [OIDMON] [host: <HOSTNAME>] [pid: <PID>] [tid: 0] Guardian: Shutting down
[2019-07-31T00:07:07.168037-04:00] [OID] [NOTIFICATION:16]  [OIDMON] [host: <HOSTNAME>] [pid: <PID>] [tid: 0] Guardian: Exiting with status 0
However, the documentation:
Oracle® Fusion Middleware Administering Oracle Internet Directory 12c (188.8.131.52.0)
Chapter Troubleshooting Oracle Internet Directory
Section Oracle Database Server Connection is Down
"OIDMON automatically detects that the database is up and restarts OIDLDAPD servers."
How to have OID restart automatically after DB shutdown?
In addition, how to shutdown the OID processes from the remote DB server side whenever the database is comes down, i.e., have the database tier remotely shut down OID and application services before shutting down the database, then start up the OID services again after the database comes back up?
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