My Oracle Support Banner

Instance Does not Start After 11gR2 Grid Infrastructure Restart or Node Reboot (Doc ID 1149003.1)

Last updated on OCTOBER 15, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.

Symptoms


Some database instances of 11gR2 databases does not come up automatically after Grid Infrastructure(GI) restarts or node reboots.

In example below, database <DB_NAME> is enabled with MANAGEMENT_POLICY=AUTOMATIC, AUTO_START=restore(by default) and a service <DB_NAME>s(preferred instance1), and has one instance on each node:

$GRID_HOME/bin/crsctl stat res ora.<DB_NAME>.db -t
ora.<DB_NAME>.db
     1        ONLINE  ONLINE       <HOSTNAME_1>                    Open              
     2        ONLINE  ONLINE       <HOSTNAME_2>                    Open


$GRID_HOME/bin/crsctl stat res ora.<DB_NAME>.<DB_NAME>s.svc -t
ora.<DB_NAME>.<DB_NAME>s.svc
     1        ONLINE  ONLINE       <HOSTNAME_1>



$GRID_HOME/bin/crsctl stat res ora.<DB_NAME>.db -p
NAME=ora.<DB_NAME>.db
..
AUTO_START=restore
..
ENABLED=1
..
MANAGEMENT_POLICY=AUTOMATIC
..



$GRID_HOME/bin/srvctl config service -d <DB_NAME> -s <DB_NAME>s
Service name: <DB_NAME>s
..
Preferred instances: <DB_NAME>1
Available instances:

If the database is stopped with srvctl before restart of GI, once GI comes back up, both instances stay down.
But if the database is stopped with sqlplus, once GI comes back up, instance 1 starts automatically but instance 2 stays down.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.