Troubleshooting granular data collection error codes

Ops Center Analyzer User Guide

Version

11.0.x

Audience

anonymous

Part Number

MK-99ANA002-06

If an error occurs during granular data collection, determine the cause of the error using one of the following methods.

Check the message display on the Events tab in Ops Center Analyzer.
If data collection does not start because the script corresponding to an action does not exist, the message returns a code that indicates the cause of the error.
Example:
```
 Command finished. (action name, command return code: return code
```
Refer to the following table to identify the cause of the error and the solution.
Check the result in the log file.
If the return code 0 is displayed on the Events tab, check the log file to see the results of the granular data collection.
```
 KNAQ03626-I command finished. (exit code: exit code)
```
Note: The message ID related to granular data collection is KNAQ03626-I.

If an action ends successfully, the message displays exit code 0. If an exit code other than 0 is displayed, refer to the following table to identify the cause of the error and the solution.

Return code	Root cause and solutions
10-21	An invalid value is specified for an option. Refer to the log and specify an appropriate value for the option that caused the error.
22-23	The value specified for the -startTime or -timezone option is invalid. Specify appropriate values for these options.
24	The date and time specified for the -startTime option is earlier than the current date and time. Specify an appropriate value for this option.
28	The target Agent host could not be identified. Make sure that the file `storage_agent_map.txt` exists in the same directory as this command. Confirm that the lines corresponding to the model and serial numbers specified in the -model and -serialNumber options are coded in the file `storage_agent_map.txt`.
29	The port number defined in the file `storage_agent_map.txt` is invalid. Make sure that a numeric value is defined for the port number.
30	A connection to the Agent host could not be established. Make sure that the IP address of the Agent host specified in the file `storage_agent_map.txt` is correct. Make sure that Agent host is running. Confirm that communication can be established between the Ops Center Analyzer server and the Agent host. Make sure that the initial settings for this command are completed.
40-44	An internal error occurred. Make sure that IP address of the Agent host specified in the file `storage_agent_map.txt` is correct. Make sure that the Agent host is running. Confirm that communication can be established between the Ops Center Analyzer server and the Agent host. Make sure that the initial settings of this command are completed.
45	The storage information could not be obtained. Make sure that the Tuning Manager Web service is running on the Agent host. Make sure that the port number of the Agent host specified in the file `storage_agent_map.txt` matches the port number used by the Tuning Manager Web service.
46	The Agent instance that is to monitor the target storage system does not exist. Make sure that the storage system specified by the -model and -serialNumber options is set to be monitored on the corresponding Agent host. Check that the PD records have been already collected on the instance that is to monitor the specified storage system.
50	The directory that stores the collection results exists as a file. Refer to the log file and delete or rename the file whose path is shown for the RESULT_DIR parameter. Alternatively, change the path name specified for the -pathLabel option.
51	The directory that stores the execution results exists as a file. Refer to the log file and delete or rename the file `model-name_serial-number` whose path is shown for the RESULT_DIR parameter. Alternatively, change the path name specified for the -pathLabel option.
52	The directory that stores the execution results could not be created. Refer to the log file and check the permissions for the directory shown for the RESULT_DIR parameter.
53-54	An internal error occurred. A temporary file could not be created or deleted. Refer to the log file and check the permissions for the directory shown for the RESULT_DIR parameter.
60-62	An internal error occurred. An operation could not be performed for a file or directory on the Agent host. Delete the file in the following directory on the Agent host: /opt/jplpc/agtd/agent/`instance-name`/raidperf_ldevlist/hiaa.conf /opt/jplpc/agtd/agent/`instance-name`/secdata_rm For `instance-name`, specify the name of the instance that monitors the specified storage system.
70-72	An internal error occurred. The RAID Agent command could not be executed normally on the Agent host. Make sure that the Agent host is running and that communication is available between the Ops Center Analyzer server and the Agent host. Make sure that the Agent version is 8.5.1 or later. Part of the pre-transfer execution result might remain in the following directory on the Agent host. Because this directory is initialized the next time the command is run, obtain the file beforehand if necessary: /opt/jplpc/agtd/agent/`instance-name`/secdata_rm For `instance-name`, specify the name of the instance that monitors the specified storage system.
73	The execution result file could not be transferred from the Agent host. Part of the pre-transfer execution result might remain in the following directory on the Agent host. Because this directory is initialized the next time the command is run, obtain the file beforehand, if necessary.
80	An internal error occurred. Make sure that Agent host is running and that communication is available between the Ops Center Analyzer server and the Agent host. /opt/jplpc/agtd/agent/`instance-name`/secdata_rm For `instance-name`, specify the name of the instance that monitors the specified storage system.
81	The data collection processing is being executed for the same storage by the same command. After the data collection processing is finished, run the command again. If this error occurs but no data collection processing is running, delete the following file on the Agent host: /opt/jplpc/agtd/agent/instance-name/raidperf_ldevlist_hiaa.conf For `instance-name`, specify the name of the instance that monitors the specified storage system.
90	The installation path of Ops Center Analyzer was not found. Check the status of the installation.
91	The schedule could not be set according to the time specified in the -startTime option. Check the specification for this option. Make sure that the `atd` service is running on the Ops Center Analyzer server.
92	The command required for specifying the start of the collection time (the -startTime option) was not found. Install the `at` command on the Ops Center Analyzer server.