Home > TroubleShooting > RAC instance resources don’t start automatically after rebooting cluster nodes

RAC instance resources don’t start automatically after rebooting cluster nodes

Symptoms

  1. Can start database instances normally after registering databases into oracle cluster registry.
  2. Reboot a cluster node, the database instance can’t start automatically
  3. Got the following massages in the cluster registry service daemon log ($CRS_HOME/log/wvpdb09/crsd/crsd.log)

2009-11-26 09:52:13.988: [  CRSAPP][54] StartResource error for ora.sgcmspro.sgcmspro1.inst error code = 1
2009-11-26 09:52:13.988: [  CRSAPP][55] StartResource error for ora.sgdmpro.sgdmpro1.inst error code = 1
2009-11-26 09:52:13.988: [  CRSAPP][56] StartResource error for ora.sgptpro.sgptpro1.inst error code = 1
2009-11-26 09:52:14.083: [  CRSAPP][57] StartResource error for ora.vstbpro.vstbpro1.inst error code = 1
2009-11-26 09:52:15.225: [  CRSRES][53] Start of `ora.wvpdb09.LISTENER_WVPDB09.lsnr` on member `wvpdb09` succeeded.
2009-11-26 09:52:15.693: [  CRSRES][121] CRS-1002: Resource ‘ora.wvpdb09.LISTENER_WVPDB09.lsnr’ is already running on member ‘wvpdb09’
2009-11-26 09:52:15.933: [  CRSRES][56] Start of `ora.sgptpro.sgptpro1.inst` on member `wvpdb09` failed.
2009-11-26 09:52:15.936: [  CRSRES][54] Start of `ora.sgcmspro.sgcmspro1.inst` on member `wvpdb09` failed.
2009-11-26 09:52:15.939: [  CRSRES][55] Start of `ora.sgdmpro.sgdmpro1.inst` on member `wvpdb09` failed.
2009-11-26 09:52:15.944: [  CRSRES][57] Start of `ora.vstbpro.vstbpro1.inst` on member `wvpdb09` failed.
2009-11-26 09:52:19.019: [  CRSRES][139] startRunnable: setting CLI values
2009-11-26 09:52:19.030: [  CRSRES][139] Attempting to start `ora.wvpdb09.ons` on member `wvpdb09`
2009-11-26 09:52:20.843: [  CRSRES][139] Start of `ora.wvpdb09.ons` on member `wvpdb09` succeeded.
2009-11-26 09:52:20.870: [  CRSRES][58] Start of `ora.wvpdb09.ASM1.asm` on member `wvpdb09` succeeded.
2009-11-26 09:52:20.872: [  CRSRES][141] Skip online resource: ora.wvpdb09.ons

Caused

The database instance resource started before the ASM instance
Solution

Add the dependency between database instance resource and ASM instance by the following command

# srvctl modify instance -d ORASID -i ORASID1 -s +ASM1
# srvctl modify instance -d ORASID -i ORASID2 -s +ASM2


Advertisements
Categories: TroubleShooting
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: