HP-UX WBEM ProviderSvcsBase (PSB) Release Notes (September 2013)
Table 2 ProviderSvcsBase (PSB) software requirements
Product versionProduct
B.11.31Event Manager (EVM)
C.07.06.03 March 2012 web release or laterSysFaultMgmt
A.05.00.09.01, March 2011 release or laterSysMgmtPlus
A.02.09.02.00 or laterWBEM Services
NOTE: On legacy Integrity systems running HP-UX 11i v3, both dialogd and oserrlogd
co-exist from March 2009. The OnlineDiag product, if installed, must be March 2009 or later
version.
Disk space requirement
Table 3 (page 7) lists the amount of disk space required to install the ProviderSvcsBase
bundle products:
Table 3 Disk space requirement
Disk spaceProduct
85 MBProviderSvcsBase products with the Health
Test sub-product.
15 MBHealth Test sub-product only
Known problems, workaround, and limitations
Following known problems are applicable for the current release:
• Problem: If the permission for /tmp and /var/tmp directories are changed during HP-UX
installation phase, the sfmdb user cannot write temporary files related to WBEM events and
postgres database. As a result, WBEM events are not logged at the following locations:
EventArchive, syslog, email and /var/opt/sfm/log/event.log. The user would
experience installation failure during the configure phase of the SysFaultMgmt and the following
message is logged in the /var/opt/sfm/log/install.log file:
/var/tmp/createtable.XXX.sh[70]: /var/tmp/shYYY.13: Cannot create
the specified file.
Workaround: To enable logging of WBEM events and to create the intermediate postgres
database files, the directory permission and ownership for /tmp and /var/tmp must be
reset to the values 1777 and root:root respectively.
• Limitation in the health test for disk drive
The health test for disk drive will not be available for the disks which are configured under
Hardware RAID (Logical volumes).
• Problem: The events and user defined subscriptions (created using Evweb) are lost when
diagnostic products are upgraded on a DRD cloned disk.
Description: Prior to September 2012 release version of the diagnostics product, the postgres
7.4.2 version was supported. However version 8.4.8 is shipped from September 2012 release.
Due to the missing data compatibility between PostgreSQL version 7.4.2 (prior to September
2012) and 8.4.8 (September 2012 release or later), when the diagnostics products are
upgraded from prior to September 2012 release to September 2012 web release and later,
the postgres data needs to be migrated to 8.4.8 format. Data migration involves backup in
7.4.2 version using the pg_dumpall and restore in 8.4.8 version using the psql operations.
Both of these operations requires a running postgres service. But in the DRD environment there
Known problems, workaround, and limitations 7