HP Serviceguard Toolkit for Oracle on Linux User Guide Version A.12.00.00

Run the cmcheckconf –P command to perform the package verification irrespective of the state
of the package in the cluster.
The following are the steps to initiate the package verification by using the cmcheckconf –P
command:
1. While the package is running, retrieve the current package configuration values using the
cmgetconf command.
For example: # cmgetconf -p <package_name> <package_name.conf>
2. Run the cmcheckconf command to verify the package configuration file.
For example: # cmcheckconf –P <package_name.conf>
Use the cluster verification feature for the Oracle toolkit to:
• Verify the presence of sqlplus, and opatch commands. If the command does not exist, the
console displays the following error messages:
ERROR: The Oracle command "$ORACLE_ORACLE_HOME/bin/sqlplus" is
missing. ERROR: The Oracle command
"$ORACLE_ORACLE_HOME/OPatch/opatch" is missing.
Reason: The Oracle command the sqlplus does not exist in the ${ORACLE_HOME}/bin/
and opatch command does not exist in the $ORACLE_ORACLE_HOME/OPatch/opatch
directories.
Solution: You must ensure that Oracle database software installation has been done properly.
If it is not installed, reinstall the same.
• Verify for the consistency of package attributes.
If the LISTENER attribute is set to no and if the oracle_listener_service is not
commented. Then, the console displays the following error message:
ERROR: The LISTENER parameter has been set to "no" but the
service_cmd has still the listener service
◦
"oracle_listener_service". Comment out the
"oracle_listener_service" service.
Solution: Comment the oracle_listener_service.
◦ If the LISTENER attribute is set to yes, then, existence of listener.ora is checked.
If the configuration file does not exist, the console displays the following error message:
ERROR: Listener file
"$ORACLE_ORACLE_HOME/network/admin/listener.ora" is missing.
Solution: Create a listener.ora file in $ORACLE_ORACLE_HOME/network/admin
folder along with the required values or copy the configuration file from another node
where the listener is in running condition.
• Verify if the PFILE/SPFILE files exist on all the nodes.
If both these files do not exist, the console displays the following error message:
ERROR: PFILE "${ORACLE_ORACLE_HOME}/dbs/init${sid_name}.ora" and
SPFILE "${ORACLE_ORACLE_HOME}/dbs/spfile${sid_name}.ora" are missing.
Solution: Create these files by using Oracle command or copy from the package node where
the Oracle database is in running condition.
• Verify if the ORACLE and ASM users exist on all the nodes.
If both these users do not exist, the console displays the following error messages:
ERROR: Oracle user "$ORACLE_ORACLE_ADMIN" doesn't exist.
34 Oracle toolkit features