HP-UX Workload Manager Toolkits A.01.07.01 Release Notes for HP-UX 11.0, HP-UX 11i V1, and HP-UX 11i V2

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, and/or

the time_url_fetch tool to ensure you are really getting a page fetch.

ApacheTK: Errors with the pig.pl workload in the white paper

Issue In the “Using HP-UX Workload Manager with Apache” white paper, in section

13.4.0.7, the step using pig.pl to generate load, namely:

Then visit (several

times, if necessary)

http://mymachine:8090/cgi-bin/pig.pl

while watching the output of wlminfo

group.

may produce error messages and not generate the desired load. The errors in

/opt/hpws/apache/logs/error_log or /opt/hpws/apache/logs/error_log2 are

of the form:

[Sun Dec 14 16:03:08 2003]

[error] 13441: ModPerl::Registry: No

comma allowed

after filehandle at /opt/hpws/apache/cgi-bin/pig.pl

line 26.

or possibly:

Known problems and workarounds 7