One of the reason of why cluster won’t start is DIAGNOSTIC_DEST folder is missing. Here it is what I got today in of the nodes of the RAC environment:

db-bash: crs_stat -t

HA Resource Target State
———– —— —–
error connecting to CRSD at [(ADDRESS=(PROTOCOL=IPC)(KEY=ora_crsqs))] clsccon 184

While checking alert log file of the clusterware ($GRID_HOME/log/node1/alertnode1.log

[/home/oracle/11.2.0/grid_1124/bin/oraagent.bin(4745)]CRS-5011:Check of resource “+ASM” failed: details at “(:CLSN00006:)” in “/home/oracle/11.2.0/grid_1124/log/node01/agent/ohasd/oraagent_oracle/oraagent_oracle.log”

ASM instance failed to start. I connected to ASM instance and tried to start it manually:

db-bash-$ asm

SQL*Plus: Release 11.2.0.4.0 Production on Mon Mar 3 10:32:24 2014

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

Connected to an idle instance.

ASM> startup

ORA-48108: invalid value given for the diagnostic_dest init.ora parameter

ORA-48140: the specified ADR Base directory does not exist [/home/oracle/11.2.0/dbhome]

ORA-48187: specified directory does not exist

HPUX-ia64 Error: 2: No such file or directory

Additional information: 1

ASM>

ADR Base Directory is missing. After creating it, I successfully started the CRS and got the happiest message :

db-bash-$ crsctl check crs
CRS-4638: Oracle High Availability Services is online
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
db-bash-$

After migrating 10gR2 single instance to 11gR2 RAC db, the next step should be configuring Enterprise Manager (if you don’t use centralized Grid Control)

It can be done by a simple command. But as usual (at least for me) it didn’t go smooth and I got some errors :). In this article I will show you solutions for some of them.

The command should be run is as follows:

emca -config dbcontrol db -repos create –cluster

It will ask you to provide the following information:

db-bash-$ emca -config dbcontrol db -repos create -cluster

STARTED EMCA at Mar 2, 2014 3:03:19 PM

EM Configuration Assistant, Version 11.2.0.3.0 Production

Copyright (c) 2003, 2011, Oracle.  All rights reserved.

Enter the following information:

Database unique name:

Service name:

Listener port number:

Listener ORACLE_HOME

Password for SYS user:

Password for DBSNMP user:

Password for SYSMAN user:

Cluster name:

Email address for notifications (optional):

Outgoing Mail (SMTP) server for notifications (optional):

ASM ORACLE_HOME :

ASM port :

ASM username [ ASMSNMP ]:

ASM user password:

–          Get Database unique name from db_unique_name parameter from the database

SQL> show parameter db_unique_name

–          To provide a service name, get the SCAN listener name from the host (ps –ef | grep tns), get the status of SCAN listener by running lsnrctl status LISTENER_SCAN1 command from $GRID_HOME and get the service name from the output

Service “RACDB.MYCOMP.COM” has 3 instance(s).
     Instance “RACDB1”, status READY, has 1 handler(s) for this service…
     Instance “RACDB2”, status READY, has 1 handler(s) for this service…
     Instance “RACDB3”, status READY, has 1 handler(s) for this service…

–          Make sure all password files at all nodes – orapwNODE1[2-3] – are same. If not, create a password file at each node and provide the same password

–          As a Cluster Name, provide the name of the cluster. To get the cluster name, use the following command:

cd $GRID_HOME/bin

./cemutlo –n

–          Make sure you’ve ASMSNMP user created at ASM instance and SYSDBA privilege is granted. Do it in the first node, then copy ora+ASM1 to the different nodes under $GRID_HOME/dbs/+ASM[1-2]

Hope above mentioned notes will help you to create EM db control successfully for your RAC environment.

To get more information from metalink, use the following MOS:

How to manage DB Control 11.x for RAC Database with emca (Doc ID 578011.1)