2.5 Handling abnormal termination of the adbarchivechunk command
If the adbarchivechunk command terminates abnormally, check if the following messages have been output:
-
KFAA50225-E
-
KFAA96606-E
If either of these messages has been output, there is an error in the specified command options or archive chunk options. Correct the error in the command options or archive chunk options, and then re-execute the adbarchivechunk command.
For details about invalid -c option specifications, see (3) Errors that can be caused by the -c option in 2.2.1 Explanation of the specification format and options.
Also, for details about invalid -r option specifications, see the following resources for each type of range specification.
-
Date range specification
See Table 2‒5: Message IDs that are displayed when the specified date range is invalid, and possible errors in (a) Specifying ranges of dates in (4) Explanation of the -r option (range specification) in 2.2.1 Explanation of the specification format and options.
-
Time range specification
See Table 2‒7: Message IDs that are displayed when the specified time range is invalid, and possible errors in (b) Specifying ranges of times in (4) Explanation of the -r option (range specification) in 2.2.1 Explanation of the specification format and options.
-
Time stamp range specification
See Table 2‒9: Message IDs that are displayed when the specified time stamp range is invalid, and possible errors in (c) Specifying ranges of time stamps in (4) Explanation of the -r option (range specification) in 2.2.1 Explanation of the specification format and options.
-
Fixed-length character string range specification
See Table 2‒10: Message IDs that are displayed when the specified fixed-length character string range is invalid, and possible errors in (d) Specifying ranges of fixed-length character strings in (4) Explanation of the -r option (range specification) in 2.2.1 Explanation of the specification format and options.
-
Decimal range specification
See Table 2‒11: Message IDs that are displayed when the specified decimal range is invalid, and possible errors in (e) Specifying ranges of decimal numbers in (4) Explanation of the -r option (range specification) in 2.2.1 Explanation of the specification format and options.
-
Integer range specification
See Table 2‒12: Message IDs that are displayed when the specified integer range is invalid, and possible errors in (f) Specifying ranges of integers in (4) Explanation of the -r option (range specification) in 2.2.1 Explanation of the specification format and options.
-
Floating point range specification
See Table 2‒13: Message IDs that are displayed when the specified floating point range is invalid, and possible errors in (g) Specifying ranges of floating point numbers in (4) Explanation of the -r option (range specification) in 2.2.1 Explanation of the specification format and options.
Note that if you had specified multiple chunks for a adbarchivechunk command that terminated abnormally, only chunks that were processed before the abnormality occurred are archived. In this case, after eliminating the cause of the command terminating abnormally, re-execute the adbarchivechunk command by using the same specifications as when the command terminated abnormally. Chunk archive processing will be executed for the remaining chunks.
If none of the preceding messages was output, eliminate the cause of the command terminating abnormally, and re-execute the adbarchivechunk command.
Note that the adbarchivechunk command does not change the contents of tables or indexes. Therefore, there is no need to restore tables or indexes if the adbarchivechunk command terminates abnormally.