HP-UX ProviderSvcsBase Release Notes (5900-2526, March 2013)

Table 3 Disk space requirement
Disk spaceProduct
85 MBProviderSvcsBase products with the Health
Test sub-product.
15 MBHealth Test sub-product only
Known problems, workarounds, 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
is a limitation that no service can be run on the cloned disk when products are either installed
or upgraded. This limits diagnostics product upgrade steps from taking the backup of the
postgres 7.4.2 data. As a result, the data such as events, error records, and subscriptions
(created using Evweb) is lost during such circumstances.
Workaround: You can select any of the following two alternatives:
1. To install the product on the DRD cloned disk as a normal upgrade scenario. The scenario
will be same as fresh installation and user may refer to event.log for historical event data.
Also, the user has to recreate the user defined subscriptions (created using Evweb) at the
end of the installation.
2. To have a seamless migration of the data from postgres 7.4.2 version. In this case, the
user is required to perform the manual steps listed in the Installation scenarios of Postgres
8.4.8 guide at www.hp.com/go/hpux-diagnostics-sfm-docs.
6 HP-UX ProviderSvcsBase release notes