Automatically Restarting ONS

scrap by http://www.idevelopment.info/

Automatically Restarting ONS

by Jeff Hunter, Sr. Database Administrator

---

Contents

1. Overview
2. Solution

---

Overview

For Oracle Database 10g release 1 (both 10.1.0.2 and 10.1.0.3) installations, the Oracle Notification Service (ONS) AUTO_START parameter is set to 0 on each node of the cluster. This bug seems to exist for all UNIX platforms (Solaris, Linux, etc.) For this reason, CRS does not automatically start the ONS component when the node is restarted. This issue is documented and being tracked with Oracle bug 4011834.

You can verify this using the following command in UNIX:

$ $ORA_CRS_HOME/bin/crs_stat
...
NAME=ora.vmlinux1.ons
TYPE=application
TARGET=OFFLINE
STATE=OFFLINE
...
NAME=ora.vmlinux2.ons
TYPE=application
TARGET=OFFLINE
STATE=OFFLINE

---

Solution

To work around this issue, perform the following steps as the CRS owner (the user account that installed CRS and in UNIX is usually the oracle user account) for each ONS resource. For the purpose of this article, I will also be giving the commands I ran on one of the nodes in my cluster, vmlinux1:

1. Change directory to the crs_home/crs/public directory.

   cd $ORA_CRS_HOME/crs/public

2. Use the following command to create a text file containing the profile resources:

   crs_home/bin/crs_stat -p ora.nodename.ons > ora.nodename.ons.cap

   For example,

   $ORA_CRS_HOME/bin/crs_stat -p ora.vmlinux1.ons > ora.vmlinux1.ons.cap

3. Enter the following command to change the AUTO_START parameter value to 1 in the ora.nodename.ons.cap file:

   crs_home/bin/crs_profile -update ora.nodename.ons -o as=1

   For example,

   $ORA_CRS_HOME/bin/crs_profile -update ora.vmlinux1.ons -o as=1

4. Enter the following command to update the resource profile:

   crs_home/bin/crs_register -u ora.nodename.ons

   For example,

   $ORA_CRS_HOME/bin/crs_register -u ora.vmlinux1.ons