Change Diagwait FINAL

You might also like

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 3

To change the diagwait setting:

1. Log in as root, and run the following command on all nodes, where CRS_home is
the home directory of the Oracle Clusterware installation:

# CRS_home/bin/crsctl stop crs

Note: Proper shutdown of the CRS can check below as how to shutdown and
startup of RAC cluster database.

2. Enter the following command, where CRS_home is the Oracle Clusterware home:

# CRS_home/bin/oprocd stop

Repeat this command on all nodes.

3. Ensure that Clusterware stack is down on all nodes by executing

# ps -ef |egrep "crsd.bin|ocssd.bin|evmd.bin|oprocd"

This should return no processes. If there are clusterware processes running


and you proceed to the next step, you will corrupt your OCR. Do not continue until
the clusterware processes are down on all the nodes of the cluster.

4. From one node of the cluster, change the value of the diagwait parameter to 13
seconds by issuing the following command as root:

# CRS_home/bin/crsctl set css diagwait 13 –force

5. Check if diagwait is set successfully by executing. the following command. The


command should return 16. If diagwait is not set, the following message will be
returned "Configuration parameter diagwait is not defined"

#crsctl get css diagwait

6. Restart the Oracle Clusterware by running the following command on all nodes:

# CRS_home/bin/crsctl start crs

7. Run the following command to ensure that Oracle Clusterware is functioning


properly:

# CRS_home/bin/crsctl check crs


Steps to shutdown the RAC database

Node1:

1. $ Oracle_home\BIN\srvctl stop emctl

2. $ Oracle_home\BIN\isqlplusctl stop

3. Connect to all the instances(databases) using sqlplus and shutdown them.


Now Run the below .

$ Oracle_home\BIN\ srvctl stop instance -d gcprod -i gcprod1

4. $ Oracle_home\bin\srvctl stop asm -n cmsprod1

5. $ Oracle_home\bin\srvctl stop nodeapps -n cmsprod1

6. # CRS_home\bin\crsctl stop crs (as root user)

Node2:

1. $ Oracle_home\BIN\srvctl stop emctl

2. $ Oracle_home\BIN\isqlplusctl stop

3. $ Oracle_home\BIN\ srvctl stop instance -d gcprod -i gcprod2

4. $ Oracle_home\bin\srvctl stop asm -n cmsprod2

5. $ Oracle_home\bin\srvctl stop nodeapps -n cmsprod2

6. # CRS_home\bin\crsctl stop crs (as root user)


Steps to startup the RAC database

Node1:

1. # CRS_home\bin\crsctl start crs (as root user)

2. $ Oracle_home\bin\srvctl start nodeapps -n cmsprod1

3. $ Oracle_home\bin\srvctl start asm -n cmsprod1

4. $ Oracle_home\BIN\ srvctl start instance -d gcprod -i gcprod1

5. $ Oracle_home\BIN\isqlplusctl start

6. $ Oracle_home\BIN\srvctl start emctl

Node2:

1. # CRS_home\bin\crsctl start crs (as root user)

2. $ Oracle_home\bin\srvctl start nodeapps -n cmsprod2

3. $ Oracle_home\bin\srvctl start asm -n cmsprod2

4. $ Oracle_home\BIN\ srvctl start instance -d gcprod -i gcprod2

5. $ Oracle_home\BIN\isqlplusctl start

6. $ Oracle_home\BIN\srvctl start emctl

Unsetting/Removing diagwait

Customers should not unset diagwait without fixing the OS scheduling issues as that
can lead to node evictions via reboot. Diagwait delays the node eviction (and
reconfiguration) by diagwait (13) seconds and as such setting diagwait does not
affect most customers.In case there is a need to remove diagwait, the above
mentioned steps need to be followed except step 3 needs to be replaced by the
following command

#crsctl unset css diagwait

You might also like