HP-UX Workload Manager Toolkits A.01.10.xx Release Notes for HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3

HP-UX WLM Toolkits (WLMTK) Release Notes
Known problems and workarounds
Chapter 110
Workaround
Try to minimize the time between WLM start-up and instance start-up.
ODBTK: Problematic SQL statements
Issue wlmoradc provides minimal checking of the SQL it passes to SQL*Plus. If
SQL*Plus finds problems with the SQL statements, messages are sent to
syslog or stderr. In some cases, SQL*Plus cannot execute the statements,
resulting in a warning and a reported execution time (walltime) of 0
seconds.
Workaround To avoid such events, always verify your SQL by hand before finalizing your
WLM and wlmoradc configuration files.
ODBTK: Debug clean_exit code is not useful
Issue If wlmoradc detects a command-line error and debugging is enabled, the
code reported by clean_exit may not be useful. For example:
Mar 26 22:57:16 mytestmachine WLMTK: wlmoradc[p8686] INFO starting
wlmoradc
Mar 26 22:57:16 mytestmachine WLMTK: wlmoradc[p8686] ERROR bad oracle home
passed to -h or --home argument
Mar 26 22:57:16 mytestmachine WLMTK: wlmoradc[p8686] INFO ending wlmoradc
Mar 26 22:57:16 mytestmachine WLMTK: wlmoradc[p8686] DEBUG clean_exit
with exit value:Not a typewriter
Workaround If the ERROR message and the DEBUG message disagree, ignore the
DEBUG message.
ApacheTK: Elapsed time reported may not be for a successful page
fetch
Issue If you use the ApacheTK tool time_url_fetch with a URL that Apache
cannot serve (such as http://mytestmachine/misspelllllled_url.htm) the ab
tool and time_url_fetch report the elapsed time for Apache to serve up a
“Not found” msg. Neither tool considers this an error, although an individual
trying to access this URL might.
Workaround Always check your target URL by hand with your browser, the ab tool, or the
time_url_fetch tool to ensure you are really getting a page fetch.