HP XP7 Storage - Manual (Page 138)

Troubleshooting the Export Tool
The following table explains possible problems with the Export Tool and probable solutions to the
problems.
Probable causes and recommended action Possible problems
The path to the Java Virtual Machine (Java.exe) might not be defined in the PATH
environment variable. If this is true, you must add that path to the PATH environment You cannot run the batch file.
variable. For information about how to add a path to the environment variable, see
the documentation for your operating system.
An incorrect version of Java Runtime Environment (JRE) might be installed on your
computer. To check the JRE version, enter the following command at the Windows
command prompt or the UNIX console window:Java -versionIf the version is
incorrect, install the correct version of JRE.
The Export Tool stops and the
processing does not continue. •
The command prompt window might be in pause mode. The command prompt
window will be in pause mode if you click the command prompt window when
the Export Tool is running. To cancel pause mode, activate the command prompt
The command prompt window
was displaying progress of the
window and then press the key. If a timeout of RMI occurs during pause
mode, the login will be canceled and an error will occur when you cancel pause
mode after the timeout. The error message ID will be (0001 4011).
export processing, but the
window stopped displaying
•
If a memory size is not specified in a batch file, the Out Of Memory Error occurs
in JRE, the Export Tool might stop and the processing might not continue. Confirm
whether the specified memory size is correct or not. progress before the processing
stopped. The progress
information does not seem to be
updated anymore.
If the error message ID is (0001 4011), the user is forcibly logged off and the
processing stops because the Export Tool did not issue any request to SVP within the An error occurs and the
processing stops.
timeout period specified by the -Dmd.rmitimeout parameter of the Java command
(default: 20 minutes). The computer running the Export Tool could be slow. Confirm
whether you are using a computer that is not supported, or whether the computer is
slow. To continue running the export tool, first increase the value of the
-Dmd.rmitimeout parameter (maximum: 1,440 minutes (24 hours), and then run the
export tool. For details about -Dmd.rmitimeout, see the Operands table for the Java
command in
“Operands” . If the error persists, contact the HP Technical Support.
If the error message ID is (0002 5510), probable error causes and solutions are:
• An internal processing is being performed in the disk array. Alternatively, another
user is changing configurations. Wait for a while and then run the Export Tool
again.
•
Maintenance operations are being performed on the disk array. Wait until the
maintenance operations finish and then run the Export Tool again.
If the error message ID is none of the above, see “Messages issued by the Export
tool” (page 139) .
For details on invalid monitoring data, see “Causes of Invalid Monitoring Data”
(page 137) .
The monitoring data in the CSV
file includes (-1).
It might be unsuitable combination of DKCMAIN/SVP program version and Export
Tool version. Confirm whether versions of these programs are correct. •
When the Export Tool
terminated abnormally due
to error, the row of Check
License is shown as
UnmarshalException in the
log file.
•
The Export Tool terminated
abnormally because the
processing did not continue.
version unmatched is shown
in the log file.
138 Exporting Performance Monitor data