B.3 Error Codes for Repository Access

The error codes relating to repository access problems are described below.

Table B.3 Error Codes for Repository Access
Error Code	Explanation	Corrective action
101	A memory shortage occurred.	Investigate the memory usage state and if a memory shortage has occurred, expand the memory.
102 103 104	Communication with the communication daemon or service of the Storage Management Server has failed.	Use the following method that corresponds to the operating system type of the Storage Management Server to check whether the communication daemon or service of the Storage Management Server is active. [UNIX system] For cluster system: Check whether there is an active process in the execution result of the "ps -ef \| grep stgxfws \| grep logical node name". (NOTE1) For non cluster system: Check whether there is an active process in the "ps -ef \| grep stgxfws" execution result. [Windows] For cluster system: Check whether the service display name "AdvancedCopy Manager COM Service for logical node name" (The case of SafeCLUSTER is "AdvancedCopy COM_logic node name") is active. (NOTE1) For non cluster system: Check whether service the display name "AdvancedCopy Manager COM Service" is active. If the name is inactive, refer to the following manuals and start the communication daemon/service: [Solaris and Linux versions] "Starting and Stopping Daemons" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" [Windows] "Starting and Stopping a Service" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide"
105	A registry access error occurred.	If the command is executed in cluster operation, check whether environment variable SWSTGNODE is set, and re-execute the command. If this fails to solve the problem, check whether swnode.ini and swstg.ini exist in the following directories: [UNIX system] For cluster system: /etc/opt/swstorage/"logical node name" (NOTE1) For non cluster system: /etc/opt/swstorage [Windows version] For cluster system: "Shared drive"\etc\opt\swstorage\etc For non cluster system: "Environment setting directory"\etc If environment variable setting is not the cause, collect the information required for troubleshooting, and then contact a Fujitsu system engineer. (NOTE2)
302	Connection to the repository database failed.	Refer to the following manuals that correspond to the operating system type of the Storage Management Server, and take the corrective action. "Troubleshooting for a failure in access to a repository database" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide"
303	The maximum number of connections to the repository database is exceeded.	Wait a while and re-execute the processing. If this fails to solve the problem, refer to the following manual that corresponds to the operating system type of the Storage Management Server, and take the corrective action. "Troubleshooting for a failure in access to a repository database" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide"
304 305 306 307 308	Access to the repository database failed.	Refer to the following manual that corresponds to the operating system type of the Storage Management Server, and take the corrective action. "Troubleshooting for a failure in access to a repository database" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide"
Except the above	An error has occurred that is not described above.	Collect the information required for troubleshooting, and then contact a Fujitsu system engineer. (NOTE2)

NOTE1:: The "logical node name" is the value specified during cluster setup.

NOTE2:: Refer to the manual given below for details on collecting the information required for troubleshooting. Collect the information on the server where the error occurred and on the Storage Management Server.
"Collecting maintenance information" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide".