Topics indicate symptoms and likely procedures required for a solution.
Check the permissions of the file /etc/llttab
. Oracle must be allowed to read it.
If the VCSMM driver (the membership module) is not configured, an error displays on starting the Oracle instance that resembles:
ORA-29702: error occurred in Cluster Group Operation
The command included in the /etc/vcsmmtab
file enables the VCSMM driver to be started at system boot.
The Oracle log files may show that a shutdown was called even when not shutdown manually.
The Oracle enterprise agent calls shutdown if monitoring of the Oracle/Netlsnr resources fails for some reason. On all cluster nodes, look at the following VCS and Oracle agent log files for any errors or status:
Verify that the hostname
-i
command returns the public IP address of the current node. This command is used by the installer and the output is stored in the OCR. If hostname
-i
returns 127.0.0.1, it causes the DBCA to fail.
Verify that the correct private IP address is configured on the private link using the PrivNIC
agent. Check the CSS log files to learn more.
If the CRS fails to start up after boot up, check for the occurrence of the following strings in the /var/log/
messages file:
"Oracle CSSD failure. Rebooting for cluster integrity"
"Waiting for file system containing"
The CRS installation is on a shared disk and the init
script is waiting for that file system to be made available.
"Oracle Cluster Ready Services disabled by corrupt install"
The following file is not available or has corrupt entries: /etc/oracle/scls_scr/
hostname
/root/crsstart
.
"OCR initialization failed accessing OCR device"
The shared file system containing the OCR is not available and CRS is waiting for it to become available.
Use the following procedure to remove Oracle CRS.
rootdelete.sh
script:
inittab.orig
back to the name and remove other init
files:
ora*
files from the /etc
directory:
$CRS_HOME
and Oracle Inventory:
If OCR and Voting disk storage are on raw volumes, use command resembling:
# dd if=/dev/zero of=/dev/vx/rdsk/ocrvotedg/ocrvol bs=8192 \
# dd if=/dev/zero of=/dev/vx/rdsk/ocrvotedg/votvol bs=8192 \
When encountering issues with the VIP configuration, you can use the following commands and files:
/etc/ifconfig
-a
command on all nodes to check for network problems.
/usr/bin/nslookup
virtual_host_name
to make sure the virtual host name is registered with the DNS server.
/etc/hosts
file on each node.
$CRS_HOME/bin/crs_stat
.
start
nodeapps
-n
node_name.
This command works only if the virtual IP address is plumbed.
Verify that the permissions are set appropriately as given in the Oracle installation guide. If these files are present from a previous configuration, remove them. See CRS fails after restart.