Troubleshooting Export Tool for Performance Monitor

The following table explains possible problems with Export Tool and probable solutions to the problems.

Possible problems

Probable causes and recommended action

You cannot run the batch file.

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 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 -version

If the version is incorrect, install the correct version of JRE.

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 Export Tool is running. To cancel pause mode, activate the command prompt window and then press the <ESC> 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).
  • If a memory size is not specified in a batch file, the Out Of Memory Error occurs in JRE, Export Tool might stop and the processing might not continue. Confirm whether the specified memory size is correct or not.

The command prompt window was displaying progress of the export processing, but the window stopped displaying progress before the processing stopped. The progress information does not seem to be updated anymore.

An error occurs and the processing stops.

If the error message ID is (0001 4011), the user is forcibly logged off and the processing stops because Export Tool did not issue any request to SVP within the timeout period specified by the -Dmd.rmitimeout parameter of the Java command (default: 20 minutes). The computer running 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 Export Tool, first increase the value of the -Dmd.rmitimeout parameter (maximum: 1,440 minutes (24 hours), and then run Export Tool. For details about -Dmd.rmitimeout, see the Operands table for the Java command in Operands. If the error persists, contact the Hitachi Solution Support Center.

If the error message ID is (0002 5510), probable error causes and solutions are:

  • An internal processing is being performed in the storage system. Alternatively, another user is changing configurations. Wait for a while and then run Export Tool again.
  • Maintenance operations are being performed on the storage system. Wait until the maintenance operations finish and then run Export Tool again.

If the error message ID is none of the above, see Messages issued by Export Tool.

The monitoring data in the CSV file includes (-1).

For details on invalid monitoring data, see Causes of invalid monitoring data.

  • When Export Tool terminated abnormally due to error, the row of Check License is shown as Unmarshal Exception in the log file.
  • Export Tool terminated abnormally because the processing did not continue. version unmatched is shown in the log file.

It might be an unsuitable combination of the DKCMAIN firmware version, the Device Manager - Storage Navigator software version, and the Export Tool version. Confirm whether versions of these programs are correct.

Export Tool terminated abnormally. NoSuchObjectException is shown in the log file.

The computer workload might be high. Perform potential fixes to lower the workload as shown below. Then execute Export Tool again.

  • Reduce the number of Export Tool applications running concurrently.
  • Execute Export Tool while virus scan is not being performed by anti-virus software.

When a CSV file is opened, the parity group ID and volume ID appear as follows:

  • The parity group IDs appear as dates.
  • The volume IDs appear with a decimal point.

To display a CSV file correctly, you need to perform the following operations:

1. Start Microsoft Excel.

2. On the menu bar, select Data, Import External Data, and Import Text File, and specify a CSV file to import. The Text Import.zip - Step 1 of 3 dialog box is displayed.

3. In the Text Import.zip - Step 1 of 3 dialog box, click Next. Text Import.zip - Step 2 of 3 dialog box is displayed.

4. In the Text Import.zip - Step 2 of 3 dialog box, check only Comma in the Delimiter area, and click Next. The Text Import.zip - Step 3 of 3 dialog box is displayed.

5. In the Text Import.zip - Step 3 of 3 dialog box, select all columns of Date preview, and check Text in the Column data format area on the upper right of this dialog box.

6. Click Finish. The imported CSV file is displayed.

When you run Export Tool with many volumes specified, Export Tool terminated abnormally while collecting monitoring data.

Because too many volumes are specified, a timeout error might have occurred due to a heavy workload imposed on the computer where Export Tool was running. The error message ID is (0001 4011). Specify fewer volumes. It is recommended that the number of volumes to be specified is 16,384 or less.

"404 Not found." or other errors appear when you run Export Tool.

This error occurred because the Export Tool execution has failed. Possible causes are as follows:

  • The svpip value is wrong.
  • The SVP version you are using is old.

"Specified "ip" is wrong." appears when you run Export Tool.

This error occurred because the network connection with the SVP could not established. Possible causes are as follows:

  • The IP address or host name specified by the ip subcommand is incorrect.
  • The connection port number (default is 1099) specified by the ip subcommand is incorrect.*
  • The connection port number (default is 1099) for RMI connection used by the SVP is changed or used by other applications.*
  • The SVP is not working correctly or does not have a network connection.

* For the connection port number, see the hardware reference guide for your model.