Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Using High Availability Monitors > Appendix B Troubleshooting HA Monitors

Database Monitor Troubleshooting for Oracle

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

For Oracle MIB monitors, review the following troubleshooting hints.

  • If MIB resource classes under rdbms continue to be unavailable, there might be a problem with the Oracle SNMP daemons. For Oracle, these are ora_naaagt, master_peer, dbsnmp, or tnslsnr. Try using the following commands to stop and restart Oracle SNMP:

    su oracle -c "cd $ORACLE_HOME/bin; ./lsnrctl stop"
    (cd $ORACLE_HOME/bin; ./lsnrctl dbsnmp_stop)
    (cd $ORACLE_HOME/network/snmp/peer; ./start_peer -k -a)
    su oracle -c "cd $ORACLE_HOME/bin; ./lsnrctl start"
    (cd $ORACLE_HOME/bin; ./lsnrctl dbsnmp_start)

    You might have to wait up to 60 seconds before trying to access rdbms resources again.

  • If rdbms resource classes continue to be unavailable, be sure that one of the get-community and set-community names in /etc/SnmpAgent.d/snmpd.conf match the -c option on each of the MONITOR statements in the mibmond.dict and rdbmsmond.dict files under /etc/opt/resmon/dictionary.

    If changes are needed to dictionary files, stop any MIB monitors that are already running.

    If changes are needed to snmpd.conf, stop and restart HP SNMP, following the procedure above.

    NOTE: The -c option is not required if public is one of the get-community or set-community names.
  • If rdbms resource classes continue to be unavailable, be sure that the HP_NAA_GET_COMMUNITY name in the start_peer script matches the COMMUNITY name in the CONFIG.master file. Both files are under $ORACLE_HOME/network/snmp/peer.

    If any changes are needed, it will be necessary to stop and restart Oracle SNMP, following the procedure above.

  • The HA Database Monitor relies on the proper installation and configuration of the Oracle Net8 product and processes (ora_naaagt, master_peer, dbsnmp, and tnslsnr). If you are able to connect to the database using the Oracle sqlplus utility, then the HA Database Monitor should also work. To verify Oracle Net8 connectivity, run the Oracle sqlplus utility from a client system that uses the same tnsnames.ora file as the one on the server. Type:

    	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 		 	 	 sqlplus username/password@service_name 

    where:

    • username/password is for the target database

    • service_name is the alias name in the tnsnames.ora file for the database server that you are trying to access.

  • If you are attempting to use the HA Database Monitor with ServiceGuard, ensure that your version of ServiceGuard supports DEFERRED resource processing. Otherwise, your packages will not be able to start successfully. Verify all configuration settings as described in Chapter 3 “Monitoring Database Resources” of this manual and in the related ServiceGuard documentation for this feature. Also, ensure that you have the Oracle SNMP running on the primary and any failover node(s), before attempting to configure your ServiceGuard package(s).

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1997, 2003 Hewlett-Packard Development Company, L.P.