| ETERNUS SF AdvancedCopy Manager Message Guide 13.0 -Microsoft(R) Windows(R) 2000/Microsoft(R) Windows Sever(TM) 2003-, -Solaris-, -HP-UX-, -Linux-, -AIX- |
|
Contents
Index
|
This chapter describes error codes that are inserted as parameters into the messages.
In use, it may become the error of communication service or repository access by the abnormalities of cluster Transactions in a cluster environment. In this case, also carry out the check of operation of cluster Transactions.
The error codes for communication service/communication daemon are listed below.
|
Error code |
Description |
Action |
|---|---|---|
|
1 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
2 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
3 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
4 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
5 |
A memory shortage occurred. |
Check the memory operating condition at the request source server. If a memory shortage is actually caused, increase the size of memory. |
|
6 |
A memory shortage occurred. |
Check the memory operating condition at the request source server. If a memory shortage is actually caused, increase the size of memory. |
|
7 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
8 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
9 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
11 |
An error occurred during communication environment creation. |
Check whether the request send destination server is running or check the conditions of communication service/communication demon. If no abnormality is found as a result of this check, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
12 |
An error occurred during communication environment creation. |
Check whether the request send destination server is running or check the conditions of communication service/communication demon. If no abnormality is found as a result of this check, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
21 |
An error occurred during data transmission or reception. |
Check the conditions of the request send destination server and communication service/communication daemon. If no abnormality is found as a result of this check, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
22 |
An error occurred during data transmission or reception. |
Check the conditions of the request send destination server and communication service/communication daemon. If no abnormality is found as a result of this check, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
31 |
An error occurred during data transmission or reception. |
Check the conditions of the request send destination server and communication service/communication daemon. If no abnormality is found as a result of this check, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
32 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
33 |
A memory shortage occurred. |
Check the memory operating condition at the request source server. If a memory shortage is actually caused, increase the size of memory. |
|
41 |
An error occurred during data transmission or reception. |
Verify that the request send destination server does not fail. |
|
42 |
An error occurred during data transmission or reception. |
Verify that the request send destination server does not fail. Check also the condition of the communication service/communication daemon of the request send destination server. |
|
43 |
An error occurred during data transmission or reception. |
Verify that the request send destination server does not fail. Verify also that no problem occurs in the network. |
|
51 |
A file-open-error occurred on the requesting server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
52 |
A file-read-error occurred on the requesting server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
53 |
A file-write-error occurred on the requesting server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
61 |
The AdvancedCopy Manager registry cannot be read. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
62 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
101 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
102 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
103 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
105 |
A memory shortage occurred. |
Check the memory operating condition at the request send destination server. If a memory shortage is actually caused, increase the size of memory. |
|
106 |
A memory shortage occurred. |
Check the memory operating condition at the request send destination server. If a memory shortage is actually caused, increase the size of memory. |
|
107 |
An error occurred when a processing request was received from the request source server. |
Re-execute processing several minutes later. If an error still occurs, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
151 |
The request send destination server failed in opening a file. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
152 |
A file-read-error occurred on the request destination server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
153 |
A file-write-error occurred on the request destination server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
154 |
A file-close-error occurred on the request destination server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
155 |
An error occurred while processing a request on the request destination server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
162 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
165 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
172 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
175 |
The function definition of the repository driver cannot be found. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
176 |
The libraries of the general-purpose functions cannot be found. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
177 |
The handling process aborted. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
178 |
An internal conflict occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
179 |
The code conversion failed. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
181 |
An error occurred while processing requests on the request destination server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
182 |
An error occurred while processing requests on the request destination server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
183 |
An error occurred while processing requests on the request destination server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
184 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
185 |
An error occurred while processing requests on the request destination server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
302 |
An error occurred during volume lock processing in a Windows version. |
Collect the data necessary for troubleshooting from the server where the error occurred, and contact a Fujitsu systems engineer (SE). (*1) |
(*1): Refer to the following manual, collect the data necessary to solve the error.
"Collecting maintenance information", in the ETERNUS SF AdvancedCopy Manager Operator's Guide
|
Error code |
Description |
Action |
|---|---|---|
|
1 |
An invalid parameter was specified. |
Check the specified parameter. If the parameter is valid, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
2 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
3 |
A memory shortage occurred at the request send source server. |
|
|
4 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
5 |
Inconsistent repository data. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
102 |
A registry access error occurred. |
Check whether /env/swstg.ini and |
|
199 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
201 |
Insufficient memory on the Storage management server side. |
Check the memory operating condition. If a memory shortage is actually caused, increase the size of memory. |
|
202 |
A communication error occurred. |
Make sure that the storage management server and the communication service/communication daemon of the Storage management server are active. |
|
203 |
A timeout occurred during communication processing. |
Make sure that the storage management server and the communication service/communication daemon of the Storage management server are active. |
|
204 |
The Storage management server failed. |
Make sure that the storage management server and the communication service/communication daemon of the Storage management server are active. |
|
205 |
The IP address of the storage management server could not be obtained. |
If the command is executed in cluster operation, check whether environment variable SWSTGNODE is set, and re-execute the command. If the error recurs, check whether swnode.ini exist. |
|
299 |
An internal error occurred. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
399 |
An internal discrepancy was detected on the Storage management server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
401 |
An internal discrepancy was detected on the Storage management server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
402 |
Repository access failed. |
Check whether the repository is active. If it is active, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
403 |
The maximum allowable number of connections to the repository was exceeded. |
The maximum allowable number of concurrent connections to the repository was exceeded. Re-execute processing later. If the same error recurs, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
404 |
Repository access failed. |
Check whether the repository is active. If it is active, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
405 |
Repository access failed. |
Check whether the repository is active. If it is active, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
406 |
Repository access failed. |
Check whether the repository is active. If it is active, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
407 |
Repository access failed. |
Check whether the repository is active. If it is active, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
408 |
Repository access failed. |
Check whether the repository is active. If it is active, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
409 |
An internal discrepancy was detected on the Storage management server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
499 |
An internal conflict was detected on the Storage management server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
504 |
There is no server or device registered that meets the specified conditions. |
Check whether the specified parameter is correct. |
|
505 |
The repository cannot be accessed. |
Check whether the repository is active. If it is active, collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
506 |
Insufficient memory on the Storage management server side. |
Check the memory operating condition. If a memory shortage is actually caused, increase the size of memory. |
|
510 |
An internal conflict was detected on the Storage management server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
|
599 |
An internal conflict was detected on the Storage management server. |
Collect the information required for troubleshooting, then contact a Fujitsu systems engineer. (*1) |
(*1): Refer to the following manual, collect the data necessary to solve the error.
"Collecting maintenance information", in the ETERNUS SF AdvancedCopy Manager Operator's Guide
(*2): A logic node name is the value specified by the cluster setup.
The error codes of repository access is described below.
|
Error code |
Explanation |
Response |
|---|---|---|
|
101 |
A memory shortage occurred. |
Investigate the memory usage state and if a memory shortage actually occurred, expand memory. |
|
102 |
Communication with the communication daemon/service of the storage management server failed. |
Use the following method that corresponds to the operating system type of the Storage management server to check whether the communication daemon/service of the Storage management server is active. [UNIX system] Check whether there is an active process in the execution result of the ps -ef | grep stgxfws | grep logical node name when the Storage management server is in cluster operation (*1). Check whether there is an active process in the ps -ef | grep stgxfws execution result when the Storage management server is not in cluster operation. [Windows] Check whether service display name "AdvancedCopy Manager COM Service" for a logical node name (SafeCLUSTER AdvancedCopy COM_logic node name) is active when the Storage management server is in cluster operation (*1). Check whether service display name "AdvancedCopy Manager COM Service" is active when the Storage management server is not in cluster operation. If the name is inactive, refer to the following manuals and start the communication demon/service: "Starting and Stopping a Daemon", in the ETERNUS SF AdvancedCopy Manager Operator's Guide (Solaris/Linux version) "Starting and Stopping a Service", in the ETERNUS SF AdvancedCopy Manager Operator's Guide (Windows version) |
|
103 |
||
|
104 |
||
|
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 the error recurs, check whether swnode.ini and swstg.ini exist in the following directories: [UNIX system] /etc/opt/swstorage/logical-node-name for cluster operation (*1) /etc/opt/swstorage for other than cluster operation [Windows version] Shared drive \etc\opt\swstorage\etc for cluster operation Environment setting directory \etc for other than cluster operation If environment variable setting is not the cause, collect the information required to solve the problem, and call a Fujitsu system engineer. (*2) |
|
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 the problem recurs, 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 |
|
304 |
Access 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 |
|
305 |
||
|
306 |
||
|
307 |
||
|
308 |
||
|
Except the above |
An error other than that described above occurred. |
Collect the information required to solve the problem, and call a Fujitsu system engineer. (*2) |
(*1) The logical node name is the value specified during cluster setup.
(*2) Refer to the manual given below for details on collecting the data required to solve the problem.
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
Error codes of the volume lock function in the Windows version are described below.
|
Error code |
Explanation |
Action to be taken |
|---|---|---|
|
1 |
A memory shortage occurred. |
Check the available space in memory. If memory is actually insufficient, increase the amount of memory. |
|
2 |
Internal inconsistency occurred. |
Collect the data necessary for troubleshooting, and contact a Fujitsu systems engineer (SE). (*1) |
|
3 |
Internal inconsistency occurred. |
Collect the data necessary for troubleshooting, and contact a Fujitsu systems engineer (SE). (*1) |
|
4 |
A memory shortage occurred. |
Check the available space in memory. If memory is actually insufficient, increase the amount of memory. |
|
5 |
An error occurred during volume lock processing. |
Collect the data necessary for troubleshooting, and contact a Fujitsu systems engineer (SE). (*1) |
|
6 |
Releasing volume lock failed. |
Collect the data necessary for troubleshooting, and contact a Fujitsu systems engineer (SE). (*1) |
|
8 |
Unmounting a volume failed. |
Collect the data necessary for troubleshooting, and contact a Fujitsu systems engineer (SE). (*1) |
|
10 |
Internal inconsistency occurred. |
Collect the data necessary for troubleshooting, and contact a Fujitsu systems engineer (SE). (*1) |
|
15 |
An error occurred during volume lock processing. |
Collect the data necessary for troubleshooting, and contact a Fujitsu systems engineer (SE). (*1) |
|
16 |
Obtaining a port number failed. |
In cluster operation, confirm that the SWSTGNODE environment variable is set correctly at the time of command execution, and reexecute processing. If the error occurs again, collect the data necessary for troubleshooting, and contact a Fujitsu systems engineer (SE). (*1) |
|
17 |
An error occurred during volume lock processing. |
Collect the data necessary for troubleshooting, and contact a Fujitsu systems engineer (SE). (*1) |
|
18 |
An error occurred during volume lock processing. |
Collect the data necessary for troubleshooting, and contact a Fujitsu systems engineer (SE). (*1) |
*1 For how to collect the data necessary for troubleshooting, refer to the following manual.
[Windows version]
"Collecting Maintenance Data" in the AdvancedCopy Manager Operator's Guide
The table below lists the error codes of the preprocessing script and postprocessing script.
|
Error code |
Message |
Explanation |
Cause and response |
|---|---|---|---|
|
1 |
System error |
A system error occurred. |
A system error occurred in the preprocessing or postprocessing script. Possible causes of this error are as follows: The preprocessing or postprocessing script does not have the execution privilege. A syntax error exists in the preprocessing or postprocessing script. Check if the script file privilege is correct. Also check if a syntax error exists in the preprocessing or postprocessing script. |
|
2 |
Parameter error |
A parameter error occurred. |
The parameter to be passed to the preprocessing or postprocessing script is invalid. Check if the customization of the preprocessing or postprocessing script is correct. |
|
3 |
Script file not found |
The script file was not found. |
The preprocessing or postprocessing script file was not found. Stop all operations and then reinstall AdvancedCopy Manager. |
|
4 |
Unknown exception |
An unknown exception occurred. |
The script terminated abnormally because an unknown exception occurred. Check if script customization is correct. |
|
10 |
umount error |
An attempt to unmount the volume has failed. |
An attempt to unmount the volume has failed. The volume that you attempted to unmount may be being used. (*1) The output from the fuser command and ps command when the volume unmount failed is saved to the following files: Check if a user was accessing the volume that you attempted to unmount by referencing these files. Backup management: Replication management: The error messages of the umount command are also saved to the following files, so check the contents of these files and then take appropriate action: Backup management: Replication management: |
|
11 |
mount error |
An attempt to mount the volume has failed. |
An attempt to mount the volume has failed. Check if the mount point exists and also if the mount point is already being used. If the copy source volume is the RAW device and the copy destination volume is already mounted, an error occurs in the copy destination volume. In this case, unmount the copy destination volume first. The error messages of the mount command are saved to the following files, so check the contents of these files and then take appropriate action: Backup management: Replication management: |
|
12 |
fsck error |
fsck failed. |
An error was detected during the file system check. An error may have occurred in the file system on the copy source volume. Check the status of the file system on the copy source volume. The error messages of the fsck command are saved to the following files, so check the contents of these files and then take appropriate action: Backup management: Replication management: |
|
13 |
Illegal mount type |
The mount type of the target disk is stack mount or bind mount. |
The mount type of the target disk is stack mount or bind mount. These mount formats are not supported. If the mount type is stack mount, unmount the copy source volume or unmount all the other volumes mounted on the mount point of the copy source volume, and then rerun. If the mount type is bind mount, unmount all the directories mounted by the mount command with the --bind option on the copy source volume and then rerun the command. |
|
30 |
VG configuration file not fount error |
The volume group configuration information file was not found. |
The volume group configuration information file was not found. |
|
31 |
vgcfgrestore error |
vgcfgrestore failed. |
An attempt to restore the volume group configuration information has failed. The error messages of the vgcfgrestore command are saved to the following files, so check the contents of these files and then take appropriate action: Backup management: Replication management: |
|
50 |
varyoffvg error |
varyoffvg failed. |
An attempt to deactivate the volume group has failed. Check if the volume group is being used. The error messages of the varyoffvg command are saved to the following files, so check the contents of these files and then take appropriate action: Backup management: Replication management: |
|
51 |
varyonvg error |
varyonvg failed. |
An attempt to activate the volume group has failed. The error messages of the varyonvg command are saved to the following files, so check the contents of these files and then take appropriate action: Backup management: Replication management: |
|
52 |
chfs error |
chfs failed. |
An attempt to change a logical volume mount point has failed. Check if the preprocessing and postprocessing scripts are correctly customized. The error messages of the chfs command are saved to the following files, so check the contents of these files and then take appropriate action: Backup management: Replication management: |
|
53 |
chdev error |
chdev failed. |
An attempt to clear PVID has failed. Check if the preprocessing and postprocessing scripts are correctly customized. The error messages of the chdev command are saved to the following files, so check the contents of these files and then take appropriate action: Backup management: Replication management: |
|
54 |
exportvg error |
exportvg failed. |
An attempt to temporarily remove the volume group has failed. Check if the preprocessing and postprocessing scripts are correctly customized. The destination volume may be active. Usually, this active status does not occur because the preprocessing script of the replication deactivate the destination volume. Check if the destination volume is manually activated. The error messages of the exportvg command are saved to the following files, so check the contents of these files and then take appropriate action: Backup management: Replication management: |
|
56 |
recreatevg error |
recreatevg failed. |
An attempt to recreate a volume group has failed. Check if the preprocessing and postprocessing scripts are correctly customized. The error messages of the recreatevg command are saved to the following files, so check the contents of these files and then take appropriate action: Backup management: Replication management: |
|
99 |
Script not customize |
The preprocessing and postprocessing scripts are not customized. |
The preprocessing and postprocessing scripts are not yet customized. Customize these scripts according to "Preprocessing and Postprocessing of Backup and Restoration" and "Preprocessing and Postprocessing of replication" in the Operations Guide, and then rerun. |
|
Others |
Other error |
Some other error occurred. |
An error other than the above errors occurred. Check if the customized part is correct. |
*1 If an error occurs when the volume is being unmounted
[Solaris versions/Linux versions/HP-UX versions/AIX versions]
Check that the target volume can be unmounted.
To suppress data access to guarantee data integrity, preprocessing unmounts the copy source volume. For this reason, if the target volume is being used when copy is run, an error occurs because the volume cannot be unmounted. Note the following points when the volume cannot be unmounted:
No other application is using the transaction volume. If any other application is using the transaction volume, temporarily exit the application.
No user is using the transaction volume. A user who is currently using the transaction volume must temporarily stop using it.
No other volume is mounted on the transaction volume. If any other volume is mounted, temporarily unmount it.
The transaction volume is not shared by NFS. If the transaction volume is shared by NFS, temporarily unshare it.
You may be able to investigate if a volume is in use by using the following commands. For details on these commands, see the OS manuals.
[Solaris] mount, fuser, pfiles, share
[Linux/HP-UX/AIX] mount, fuser
|
Contents
Index
|