HP-UX WBEM RAIDSA Provider Release Notes (September 2013)

Table 8 Defects fixed in the HP-UX 11i v3 OS (continued)
During the unconfiguration of RAIDSAProvider, the native library gets deleted.
Therefore, configuring of RAIDSAProvider fails.
QXCR1001232692
This issue is fixed in this release.
The following error message is logged in RAIDSAProvider log:QXCR1001228957
SFM: ERROR: invalid input syntax for type timestamp with time zone: ""
This issue is fixed in this release.
Known problems, workaround, and limitations
Following is the known problem tabulated from the current release.
Problem: After the installation of RAIDSA Provider, couple of initial events are not generated.
Workaround: After installation run /opt/raidsaprovider/bin/RAID_Provider_Test
-a twice.
The following known problems are tabulated from the previous release.
• When RAIDSA provider B.11.31.1106 or later is installed on legacy Integrity systems,
dm_raid_adapter is never launched regardless of the diag mode.
HPUXRAIDSAIndicationProviderModule always monitors natively the hardware and generates
WBEM events. The reverse wrapper, RAID_WbemWrapperMonitor, may be launched
depending on the connected hardware. These reverse wrappers convert the WBEM event to
the corresponding EMS event.
The introduction of this native support adds to support the following EMS resource path:
/adapters/events/raid_wbem_wrapper
On the other hand, as the process for dm_raid_adapter is never launched, the corresponding
EMS resource path is not monitored:
/adapters/events/raid_adapter
• 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.
Known problems, workaround, and limitations 13