HP StorageWorks XP Performance Advisor Software v4.6 User and Troubleshooting Guide (T1789-96094, June 2010)

CLUI command gives Java error
If CLUI (Command Line User Interface) commands fail with the error: "Exception in thread "main"
java.lang.OutOfMemoryError: Java heap space", you need to increase the Java size by adding new
java options -xms & -xmx for the failed command. To increase the Java heap size for a batch file:
1. Open the batch file from: <install directory>:\Program Files\Hewlett-Packard\Performance Ad-
visor\clui\<file.bat>
2. Replace the following line:
%javacmd% -Djava.cmd=%javacmd% -Dinstall.dir="%installdir%" -cp
%classpath% com.hp.xpsl.clui.XpPaCli %COMMAND% %*
with
%javacmd% -Djava.cmd=%javacmd% -Dinstall.dir="%installdir%" -Xms256m
-Xmx1024m -cp %classpath% com.hp.xpsl.clui.XpPaCli %COMMAND% %*
Daylight savings time error
The following message appears in the application event log:
Database Warning - Primary Key Unique Constraint Violation: This may be
due to a change of time on a host (i.e. daylight savings)
This warning occurs when the time on the host agent has changed either because of daylight savings
time or a manual change was made. The error should stop occurring as soon as the amount of time
that changed, such as one hour for daylight savings time, has passed.
Delays in alarm dispatch and email notification generation
If you detect delays in alarm dispatches and the generation of email notifications, ensure that the XP
Perf Advisor management station and the host are in the same time zone and have the same time
settings. You must also verify that the Oracle service is running. However, if there are reports scheduled
at the same time as the alarm email notification, then the notification through email may get delayed.
This is because XP Perf Advisor uses the same mechanism to send both alarm email notifications and
reports to users.
Entries in the event log during database size modification
The alarm dispatcher failure exceptions, XML exception, document messages, and report dispatcher
thread exceptions may occur and be logged in the Event log file, when the Oracle database size is
being modified. These exceptions can be ignored safely.
Event log not updating
If events are not updated in the event log as soon as an operation is done, then check the time
difference between the machine from where the XP Perf Advisor application is launched using the
web browser and management station where XP Perf Advisor is installed. If there is a time difference
between the management station and the machine from where the XP Perf Advisor application is
launched you must include the management station time in the Event Log screen. To add the
management station time:
Troubleshooting XP Perf Advisor304