HP-UX Workload Manager Toolkits A.01.08 Release Notes for HP-UX 11i V1 and HP-UX 11i V2
Table Of Contents
- HP-UX Workload Manager Toolkits A.01.08 Release Notes for HP-UX 11i v1 and HP-UX 11i v2
- Contents
- 1 HP-UX WLM Toolkits (WLMTK) Release Notes
- Announcement
- What’s in this version
- Known problems and workarounds
- Compatibility information and installation requirements
- Patches and fixes in this version
- Software availability in native languages
- What manuals are available
- Toolkit updates
- Providing feedback
- Training
The new features of these toolkits are described in the next section.
What’s in this version
WLMTK Version A.01.08 provides the toolkits ApacheTK, DMTK, ODBTK, PPUTK, SASTK, SNMPTK,
and WebLogicTK. The new functionality of the individual toolkits is described below.
• Terminology change: The Instant Capacity on Demand (iCOD) product is now known as Instant
Capacity, or iCAP. Given WLM’s integration with this product, Instant Capacity is mentioned
in a number of places in the WLM product and documentation.
• Pay Per Use Toolkit being deprecated
The toolkit, including its utilitydc command, are being deprecated. Support for the
command will be removed in a future release. In the meantime, for documentation, see the
utilitydc(1M) man page.
The utilitydc command does not work with any version of Instant Capacity after version
6.
Please begin upgrading to the simpler and more robust solution provided by wlmpard and
the new keyword utilitypri. For information on the new solution and keyword, see the
wlmpard(1M) and wlmparconf(4) man pages.
Known problems and workarounds
This section discusses problems and workarounds.
ODBTK: No control of instance on start-up
Issue Assume a database instance is managed by HP-UX WLM. If WLM starts before that instance,
it sets the CPU allocation for the instance’s workload group based on the mincpu and maxcpu
values in the WLM configuration file. The instance’s workload group remains at that initial
CPU allocation until the instance starts, allowing wlmoradc to gather metrics on it and pass
the metrics to WLM.
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
nl
Mar 26
22:57:16 mytestmachine WLMTK: wlmoradc[p8686] ERROR bad oracle home
passed to -h or --home argument
nl
Mar 26 22:57:16 mytestmachine
WLMTK: wlmoradc[p8686] INFO ending wlmoradc
nl
Mar 26
22:57:16 mytestmachine WLMTK: wlmoradc[p8686] DEBUG clean_exit with
exit value:Not a typewriter
6 HP-UX WLM Toolkits (WLMTK) Release Notes