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

Last updated on OCTOBER 24, 2012

Applies to:

Oracle Server - 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 b2n is enabled with MANAGEMENT_POLICY=AUTOMATIC, AUTO_START=restore(by default) and a service b2ns(preferred instance1), and has one instance on each node:

$GRID_HOME/bin/crsctl stat res ora.b2n.db -t
ora.b2n.db
     1        ONLINE  ONLINE       racnode1                    Open              
     2        ONLINE  ONLINE       racnode2                    Open


$GRID_HOME/bin/crsctl stat res ora.b2n.b2ns.svc -t
ora.b2n.b2ns.svc
     1        ONLINE  ONLINE       racnode1



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



$GRID_HOME/bin/srvctl config service -d b2n -s b2ns
Service name: b2ns
..
Preferred instances: b2n1
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.

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