HP-UX WBEM SAS Provider release notes (5900-2519, March 2013)

Table 8 Defects fixed in the HP-UX 11i v3 OS (continued)
DescriptionDefect ID
WARNING! Started processing old osel log files. Old events may get reported.
You can safely ignore this message.
Defects fixed in version B.11.31.1209.08.02
When the first node of the hostname is changed to a name that has more than 8
characters, the SASProvider fails to report the events.
QXCR1001221295
This issue is fixed in this release. The events get generated even after changing the
first node of system name to more than 8 characters.
The event suppression in HPUXSASNativeIndicationProvider is not getting
reset after the system reboot.
QXCR1001230102
This issue is fixed in this release.
Defects fixed in version B.11.31.1303.05.01
During the unconfiguration of SASProvider, the native library gets deleted. Therefore,
configuring of SASProvider fails.
QXCR1001232692
This issue is fixed in this release.
The following error message is logged in SASProvider log:QXCR1001228957
SFM: ERROR: invalid input syntax for type timestamp with time zone: ""
This issue is fixed in this release.
Known problems, workarounds, and limitations
The following known problem is for the current release:
• Problem: The events are lost when diagnostic products are upgraded on a DRD cloned disk.
Description: Prior to September 2012 release version of 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 diagnostics products are upgraded
from prior to September 2012 release to September 2012 web release and later, the postgres
data need 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 and error records 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.
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.
Following is the limitation of the SAS provider:
• SAS is a read-only provider and hence does not allow users to modify, create, or delete
instances.
• When SAS provider B.11.31.1106 or later is installed on legacy Integrity systems,
dm_sas_adapter is never launched regardless of the diag mode.
HPUXSASNativeIndicationProviderModule always monitors natively the hardware and generates
10 HP-UX WBEM SAS provider release notes