HP-UX ProviderSvcsBase (PSB) Release Notes (766968-001, March 2014)

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, 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
pg_dumpall and restore in 8.4.8 version using the psql operations. Both of these operations
require 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.
Product structure
Following are the commands, you must use to obtain the bundle, product, sub-product, and the
fileset information about ProviderSvcsBase (PSB) products in ProviderSvcsBase (PSB)
Depot. The below examples are generated for Integrity systems.
Integrity Systems
Bundle
# swlist -l bundle <ProviderSvcsBase Depot Location>
Provider Services BaseC.14.00.06.01ProviderSvcsBase
Product(s)
# swlist -l product <ProviderSvcsBase Depot Location>
Provider Services BaseC.14.00.06.01# ProviderSvcsBase
Provider Services CoreC.14.00.06ProviderSvcsBase.ProviderSvcsCore
10 ProviderSvcsBase (PSB) release notes for March 2014 release