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
HP-UX Workload Manager Toolkits User's Guide: Version A.01.10.01 > Chapter 2 HP-UX WLM Oracle Database Toolkit: Providing Database Metrics to WLM

Troubleshooting

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

This section explains how to view error and informational messages. In addition, it discusses debugging techniques, as well as common errors and how to fix them.

Error and informational messages

Messages are provided on stderr and through syslog.

  • stderr

    You can redirect stderr with the wlmoradc option --stderrfile file

    Alternatively, you can use the coll_stderr keyword in your WLM configuration. This keyword allows you to capture stderr for all data collectors in your configuration, not just wlmoradc. You can send stderr to syslog or another file of your choosing.

  • syslog

    Typically, syslog is at /var/adm/syslog/syslog.log; if not, see /etc/syslog.conf for a pointer to syslog on your system.

Also, WLM has a message log at:

/var/opt/wlm/msglog

Debugging suggestions

Following are some pointers when you are debugging:

  1. Check syslog for indication of any problems.

  2. Use the wlmoradc option --debug 1 to check that wlmoradc settings match expected values.

Common errors and their solutions

Following are some of the more common problems you may encounter. The error messages below are not exactly the output you will see, but rather are indicative of a general class of errors that may occur. Solutions are also provided.

smooth: nonnumeric value ...

Run the tool with the option --debug to see what values are being fed into it by the data collector (either wlmoradc or a user-supplied collector). Then fix wlmoradc or the user-supplied collector feeding the invalid input to smooth.

wlmoradc: can’t connect to instance

Confirm the --home, --instance, and --username values (or their $opt_name equivalents in the wlmoradc configuration file) by setting the associated environment variables and running SQL*Plus manually, as in the following POSIX shell example:

  1. Set the ORACLE_HOME env variable to the --home value:

    # export ORACLE_HOME=/oracle/app/oracle/product/8.1.5

  2. Set the ORACLE_SID env variable to the --instance value:

    # export ORACLE_SID=myinstance

  3. Use the --username/--password values with SQL*Plus to confirm that the instance can be connected to:

    # $ORACLE_HOME/bin/sqlplus scott/tiger

    SQL*Plus: Release 8.1.5.0.0 - Production on Thu Jan 18 19:48:40 2001

    (c) Copyright 1999 Oracle Corporation. All rights reserved.

    Connected to:
    Oracle8i Enterprise Edition Release 8.1.5.0.0 - Production
    With the Partitioning and Java options
    PL/SQL Release 8.1.5.0.0 - Production

    SQL> exit
    Disconnected from Oracle8i Enterprise Edition Release 8.1.5.0.0 - Production
    With the Partitioning and Java options
    PL/SQL Release 8.1.5.0.0 - Production
wlmoradc: bad perl code in configfile

Use perl -c to check the syntax of the configuration file, then run wlmoradc by hand.

wlmoradc: bad SQL code in sqlfile or sqlstring

Use SQL*Plus manually to check syntax and functionality, then use the file or string with wlmoradc.

wlmoradc: missing environment variables

Run wlmoradc using wlmd, but include the options --debug 2 --stderrfile /tmp/test to see the complete environment. Make sure the wlmoradc command line has the correct options, including -h oracle_home (--home oracle_home).

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