ASM database not starting automatically after server reboot

As we all know that in unix, we have different runlevels and every runlevel have certain demons to be started and stopped. We can check the demons in each runlevel by going to directory /etc/rc.d/rc[0-6] or /etc/init.d (or some platform specific location).

Typical runlevels are
0 Halt, 6 reboot 
3 Multi-User mode, 5 Multi-User mode with X11

Here we’ll see two types of scripts. Scripts starting with K(kill scripts) and S(Start scripts)

When the system is enters a specific run level, the K scripts in rc[0-6].d are run, then the S scripts are run. The idea is that the K scripts stop anything which might be running but which should not be running, followed by the S scripts start anything which should be running.

In case of database deployments on ASM, we should have ASM started first (ocssd.bin) & then database. 

Typically in rc2/3.d which is the mostly used runlevel, we should have a S script for cssd/ohsad start and then followed by database startup script.

If we have ohsad/cssd startup script as S01ohasd/S02init.cssd, then the database startup script should be something like S96oradb (i.e. with higher number than 01/02). If this is not in place correctly, database will try to start before ASM diskgroups are mounted & fail to start.

cssd/ohsad also write to syslog in Linux. Syslog demon is started using a start script like S06syslog. If this demon is not started, cssd demon start may fail. So it is good to have dependency between syslog & cssd.

Advertisements
This entry was posted in Oracle Automatic Storage Management, Oracle Cluster Ready Services and tagged . Bookmark the permalink.

4 Responses to ASM database not starting automatically after server reboot

  1. Cluster callouts are scripts or programs that Oracle Clusterware will run whenever a cluster event like starting or stopping an instance occurs. There you will find a small zip archive that has a couple of perl scripts and a short readme file explaining how to install and use them.

  2. Startup Shutdown Apps In our next topic in learning Oracle Apps DBA this post covers startup shutdown of Oracle Application DBAAs you are aware by now there is Database Tier Database DB Listener and Application Tier WebServer Forms Reports Concurrent Manager Discoverer Apps Listener OnetoOne Fullfillment Server Order of StartUp of Services Should be First DB Listener Database then Application Tier ServicesOrder of ShutDown of Services Should beFirst Application Tier Services then Database DB ListenerDatabase Startup Shutdown ScriptsDepending on your AD Version these will be in ORACLE HOME appsutil scripts SID hostnameaddbctl.sh database startup shutdown scriptaddlnctl.sh database listener Script Where AD is for Application DBADB is for databaseDLN is database listenerCTL is controlIsnt this easy to remeber Thanks to Oracle for naming convention —–Application Tier Startup Shutdown ScriptsDepending on your AD Version these will be inOAD TOP admin scripts SID hostnameadalnctl.sh Apps Listener Control Scriptadapcctl.sh Apache Web Server Control Scriptadcmctl.sh Concurrent Manager Control Scriptaddisctl.sh Discoverer Control Scriptadfrmctl.sh Forms server Control Scriptadrepctl.sh Report Server Control Scriptadstpall.sh Stop All Middle Application Tieradstrtall.sh Start All Middle Application TierWhere AD CTL you already know now isnt itadl stand for Apps Listenerapc stand for Apachecm Concurrent Managerdis Discovererfrm formsrep reportDo you know whats Use of Apps Listener ?

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