ETERNUS SF XL-DATA/MV V13 User's Guide
Contents Index PreviousNext
Appendix A : Return Information from the XL-DATA/MV

A.1 Return Information of the XL-DATA/MV on the UNIX/IA Server

This clause explains the return information of the XL-DATA/MV on the UNIX/IA server.

Return information consists of the following information.

Caution

Detail Codes

Detail Code
Decimals
(Hexadecimals)		 Definition
[ Object Request name ]		 User Process
1
(0001)		 A parameter error was detected. Contact a Fujitsu system engineer (SE).
2
(0002)		 A disk that cannot be used for the data transfer has been specified.
When initializing the disk, the system name, device name, physical drive name, or device type specified in the initialization configuration file may not match any of the existing names.		 Check to see if the disk was initialized using mftfdvini (for the UNIX/IA server) of the XL-DATA/MV.
Check to see if the system name, device name, physical drive name, or device type specified in the initialization configuration file actually exists.
3
(0003)		 An error occurred in the status check of the device. Track the cause of the error from the error number or system message displayed in the log or messages of the XL-DATA/MV of the corresponding system. This often occurs in the following situation:
  • The specified device does not exist.
4
(0004)		 The open process of the data transfer volume failed. Track the cause of the error from the error number or system message displayed in the log or messages of the XL-DATA/MV of the corresponding system. This often occurs in the following situations:
  • The specified device does not exist.
  • Access to the specified device is not authorized.
    (If this occurs when using the transfer command, the user did not log in as the system administrator).
  • An I/O error occurred in the specified device.
  • Label is not in the specified device (For Solaris).
  • The specified device is not bound by the raw command (For Linux).
5
(0005)		 The seek process of the data transfer volume failed. Track the cause of the error from the error number or system message displayed in the log or messages of the XL-DATA/MV of the corresponding system. This often occurs in the following situations:
  • An I/O error occurred in the specified device.
  • The specified device has not been initialized properly.
6
(0006)		 The read process of the data transfer volume failed. Track the cause of the error from the error number or system message displayed in the log or messages of the XL-DATA/MV of the corresponding system. This often occurs in the following situation:
  • An I/O error occurred in the specified device.
  • The logical volume of LVM (Logical Volume Manager) form is used for the data transfer volume (For HP-UX).
  • The data transfer volume is offline (For IA server).
7
(0007)		 The write process to the data transfer volume failed.
8
(0008)		 Insufficient memory available for the process. Track the cause of the error from the error number or system message displayed in the log or messages of the XL-DATA/MV of the corresponding system.
9
(0009)		 An error in the time interval for issuing the request (i.e., over 6 minutes) occurred in the system. The load on its system or on the volume where the data transfer source file or target file exists is too high. Reduce the load (multiprocessing level) on the system or volume.
10
(000A)		 An error in the time interval for issuing the request (i.e., over 6 minutes) occurred in the other system. The following things can be considered as a cause of the other system.
  • The system stopped.
  • The XL-DATA/MV daemon or the XL-DATA/MV service stopped.
  • The data transfer process(transfer command) was canceled.
  • The volume (volume in which the source file or target file of data transfer exists) is a high loading state.
  • CPU is a high loading state.
Please contact the system administrator and perform one of the following processes.
  • Please start the system.
  • Please start the XL-DATA/MV daemon or the XL-DATA/MV service.
  • Please rerun The data transfer process (transfer command).
  • When the load of volume is high, please reduce the load (multiprocessing level) of the volume.
  • Please lower the load of CPU.
11
(000B)		 The process time of the request exceeded the standard time limit.
12
(000C)		 Cannot output the data because the environment that inputs the data is closed. Other errors may be occurring in the XL-DATA/MV. Check for other messages and resolve the problem accordingly.
13
(000D)		 [For kjuwrite or kjuread]
Insufficient free space in the slice to store the data (for data output).
No data to get from the slice (for data input).
[For kjuwtcom]
Unable to write the data because the read process of the previous communication data is not complete.
14
(000E)		 A conflict was detected in the slice control.
15
(000F)		 Insufficient free space in the slice used for the data transfer. Wait for the other data transfer processes to complete, then try executing the data transfer again.
16
(0010)		 The other system is not open. Track the cause of the error from the error number or system message displayed in the log or messages of the XL-DATA/MV of the corresponding system. This often occurs in the following situations:
  • An invalid device information was specified in the initialization command (mftfdvadd,mftfdvalt) of the UNIX server.
  • The data transfer volume was initialized during a data transfer.
17
(0011)		 Failed to get the lock. Reduce the multiprocessing level of the data transfer process.
18
(0012)		 Unable to open the lock file. Track the cause of the error from the error number or system message displayed in the log or messages of the XL-DATA/MV of the corresponding system. This often occurs in the following situations:
  • The XL-DATA/MV is not installed properly.
  • An I/O error occurred in the specified device.
19
(0013)		 Unable to change the status of the lock file. Track the cause of the error from the error number or system message displayed in the log or messages of the XL-DATA/MV of the corresponding system. This often occurs in the following situations:
  • The data transfer process of execution exists.
  • The XL-DATA/MV is not installed properly.
  • An I/O error occurred in the specified device.
This may also occur if the XL-DATA/MV of the other system shuts down or terminates abnormally. If this is the case, stop the XL-DATA/MV of the system, then restart it. Check to see if the other system is running properly, then try executing the data transfer again.
20
(0014)		 The seek process of the lock file failed. Track the cause of the error from the error number or system message displayed in the log or messages of the XL-DATA/MV of the corresponding system. This often occurs in the following situations:
  • The XL-DATA/MV is not installed properly.
  • An I/O error occurred in the specified device.
21
(0015)		 Unable to write to the lock file.
22
(0016)		 The data transfer volume has not been initialized with a 1:1 relationship between the client and server. An error in the initialization of the data transfer volume. Initialize correctly.
23
(0017)		 An error notification was issued by the other system. Other errors may be occurring in the XL-DATA/MV. Check for other messages and resolve the problem accordingly.
24
(0018)		 An error in the issue sequence of the request. Contact a Fujitsu system engineer (SE).
27
(001B)		 The other system closed. Other errors may have occurred in the XL-DATA/MV, or it may have been initialized during the transfer. Check for other messages and resolve the problem accordingly.
Contents Index PreviousNext
All Rights Reserved, Copyright(C) FUJITSU LIMITED 2011