5.13 Database status in the event of an error and recovery methods

Table 5-59 Database status and recovery method (in the event of an error during data loading) (1/3) through Table 5-61 Database status and recovery method (in the event of an error during data loading) (3/3) describe the database statuses and recovery methods in the event of an error during data loading; Table 5-62 Database status and recovery method (in the event of an error during data loading on LOB columns) describes the database statuses and recovery methods in the event of an error during data loading on LOB columns, and Table 5-63 Database status and recovery method (in the event of an input data error) describes the database statuses and recovery methods in the event of an input data error.

In the Classification column of the tables, Status means the status of the database when the error occurred and Recovery means the recovery method.

Table 5-59 Database status and recovery method (in the event of an error during data loading) (1/3)

OptionClassificationMessage output immediately before error
-l-i1.2.3.
None (excluding control statement errors)KFPL00721-I
Row data deleted
KFPL00702-I
Data loading started
a or psStatusStatus before executionNullNull
RecoveryRe-executeRe-executeRe-execute
cStatusStatus before executionNullNull
RecoveryRe-executeRe-executeRe-execute
nStatusStatus before executionNullNull
RecoveryRe-executeRe-executeRe-execute
xStatusStatus before executionNullNull
RecoveryRe-executeRe-executeRe-execute
nsStatusNot guaranteedNot guaranteedNot guaranteed
RecoveryRe-execute after recovering databaseRe-execute after recovering databaseRe-execute after recovering database
cStatusNot guaranteedNot guaranteedNot guaranteed
RecoveryRe-execute after recovering databaseRe-execute after recovering databaseRe-execute after recovering database
nStatusNot guaranteedNot guaranteedNot guaranteed
RecoveryRe-execute after recovering databaseRe-execute after recovering databaseRe-execute after recovering database
xStatusNot guaranteedNot guaranteedNot guaranteed
RecoveryRe-execute after recovering databaseRe-execute after recovering databaseRe-execute after recovering database

Table 5-60 Database status and recovery method (in the event of an error during data loading) (2/3)

OptionClassificationMessage output immediately before error
-l-i4.5.6.
KFPL00800-I
Notification of synchronization point
KFPL15225-E
Rollback
KFPL24510-E
Detection of invalid data
a or psStatusData was stored through the row displayed in KFPL00800-IStatus of 3 or 4Status of 5 if KFPL15225-E has been displayed.
If not, data was stored through the row displayed in KFPL24509-E.
RecoveryRe-executeRe-executeIf it is in the status of 5, re-execute.
If some of the rows have been stored, specify the -r option and then re-execute.
cStatusData was stored through the row displayed in KFPL00800-IStatus of 3 or 4Status of 5 if KFPL15225-E has been displayed.
If not, data was stored through the row displayed in KFPL24509-E.
RecoveryRe-executeRe-executeIf it is in the status of 5, re-execute.
If some of the rows have been stored, specify the -r option and then re-execute.#
nStatusData was stored through the row displayed in KFPL00800-IStatus of 3 or 4Status of 5 if KFPL15225-E has been displayed.
If not, data was stored through the row displayed in KFPL24509-E.
RecoveryRe-executeRe-executeIf it is in the status of 5, re-execute.
If some of the rows have been stored, specify the -r option and then re-execute.#
xStatusData was stored through the row displayed in KFPL00800-IStatus of 3 or 4Status of 5 if KFPL15225-E has been displayed.
If not, data was stored through the row displayed in KFPL24509-E.
RecoveryRe-executeRe-executeIf it is in the status of 5, re-execute.
If some of the rows have been stored, specify the -r option and then re-execute.#
nsStatusN/ANot guaranteedStatus of 5 if KFPL15225-E has been displayed.
If not, data was stored through the row displayed in KFPL24509-E.
RecoveryN/ARe-execute after recovering databaseIf it is in the status of 5, re-execute.
If some of the rows have been stored, specify the -r option and then re-execute.#
cStatusN/ANot guaranteedStatus of 5 if KFPL15225-E has been displayed.
If not, data was stored through the row displayed in KFPL24509-E.
RecoveryN/ARe-execute after recovering databaseIf it is in the status of 5, re-execute.
If some of the rows have been stored, specify the -r option and then re-execute.#
nStatusN/ANot guaranteedStatus of 5 if KFPL15225-E has been displayed.
If not, data was stored through the row displayed in KFPL24509-E.
RecoveryN/ARe-execute after recovering databaseIf it is in the status of 5, re-execute.
If some of the rows have been stored, specify the -r option and then re-execute.#
xStatusN/ANot guaranteedStatus of 5 if KFPL15225-E has been displayed.
If not, data was stored through the row displayed in KFPL24509-E.
RecoveryN/ARe-execute after recovering databaseIf it is in the status of 5, re-execute.
If some of the rows have been stored, specify the -r option and then re-execute.#
Legend:
N/A: If the applicable option is specified, the corresponding message is not displayed.
#: If you are re-executing the utility with the -r option specified, do not specify the -d option.

Table 5-61 Database status and recovery method (in the event of an error during data loading) (3/3)

OptionClassificationMessage output immediately before error
-l-i7.8.9.
KFPL00703-I
Data loading completed
KFPL00715-I
Index creation started
KFPL00716-I
Index creation completed
a or psStatusCreation of table and index completedN/AN/A
RecoveryUnnecessary#1N/AN/A
cStatusTable creation completedTable creation completedCreation of table and index completed
RecoveryBatch creation of index was executed by pdrorg -k ixmkBatch creation of index was executed by pdrorg -k ixmk#2Unnecessary#1, #2
nStatusTable creation completedN/AN/A
RecoveryBatch creation of index was executed by pdrorg -k ixmk#1N/AN/A
xStatusTable creation completedN/AN/A
RecoveryBatch creation of index was executed by pdrorg -k ixmk#1N/AN/A
nsStatusTable creation completedN/AN/A
RecoveryBatch creation of index was executed by pdrorg -k ixmk#1N/AN/A
cStatusTable creation completedTable creation completedCreation of table and index completed
RecoveryRe-execute after recovering database#3Re-execute after recovering database#3Unnecessary#1
nStatusTable creation completedN/AN/A
RecoveryBatch creation of index was executed by pdrorg -k ixmk#1N/AN/A
xStatusTable creation completedN/AN/A
RecoveryBatch creation of index was executed by pdrorg -k ixmk#1N/AN/A
Legend:
N/A: If the applicable option is specified, the corresponding message is not displayed.
#1: If you are executing data loading with an option other than -k d, also see Table 5-62 Database status and recovery method (in the event of an error during data loading on LOB columns).
#2: If there are multiple index storage RDAREAs, the indexes for which the KFPL00716-I message was issued have been created, but no other indexes have been created. Execute batch creation of indexes for the indexes that have not been created.
#3: If the table storage RDAREA differs from the index storage RDAREA, you can release the table storage RDAREA from the no-log shutdown status, re-initialize the index storage RDAREA, and then execute pdrorg -k ixrc.

Table 5-62 Database status and recovery method (in the event of an error during data loading on LOB columns)

Control statement-l optionClassificationMessage output immediately before error
KFPL00707-I
Data loading on LOB column started
KFPL00708-I
Data loading on LOB column completed
When executing data loading on both LOB column structure base table and LOB columns:
source statement
lobmid statement
lobdata statement
a or pStatusUSERCreation of LOB column structure base table and index completedTable creation completed
ULOBNull if the -d option is specified. Status before execution if the option is not specified.Creation of LOB column created
RecoveryUSERUnnecessaryUnnecessary
ULOBData loaded only on LOB columns#2Unnecessary#2
nStatusUSERNo-log shutdownTable creation completed
ULOBNot guaranteedCreation of LOB column created
RecoveryUSERRe-execute after recovering database#1Unnecessary
ULOBRe-execute after recovering database#1Unnecessary
When executing data loading only on LOB columns:
lobmid statement
lobdata statement
a or pStatusUSERN/AN/A
ULOBStatus before execution (-d option is ignored)Creation of LOB column created
RecoveryUSERN/AN/A
ULOBRe-executeUnnecessary
nStatusUSERN/AN/A
ULOBNot guaranteedCreation of LOB column created
RecoveryUSERN/AN/A
ULOBRe-execute after recovering databaseUnnecessary
Legend:
N/A: If the applicable option is specified, the corresponding message is not displayed.
USER: User RDAREA
ULOB: User LOB RDAREA
#1: In the no-log mode, you must re-execute data loading on the LOB column structure base table and LOB columns after recovering the table (LOB column structure base table, LOB columns, abstract data type columns with the LOB attribute, and indexes) even when data loading on LOB columns terminated abnormally.
#2: If there are multiple index storage RDAREAs, the indexes for which the KFPL00708-I message was issued have been created, but no other LOB columns have been created. Execute data loading on the LOB columns that have not been created.

Table 5-63 Database status and recovery method (in the event of an input data error)

-e optionerrdata operand in source statementClassificationError that does not require rollback (termination with return code 4)Error that requires rollback (termination with return code 8)
Not specifiedNot specifiedStatusAll rows have been stored in the database except those that were output to the error information file.If -l n was not specified, the status before pdload was executed.
If -l n was specified, there is no guarantee.
RecoveryCreate a file containing the applicable data in the input data file, correct them, then re-execute data loading.If -l n was not specified, correct the input data and then re-execute data loading.
If -l n was specified, recover the database, correct the input data, and then re-execute data loading.
SpecifiedStatusAll rows have been stored in the database except those that were output to the error information file.If -l n was not specified, the status before pdload was executed.
If -l n was specified, there is no guarantee.
RecoveryCorrect the data that was output to the error data file and then re-execute data loading.If -l n was not specified, correct the input data and then re-execute data loading.
If -l n was specified, recover the database, correct the input data, and then re-execute data loading.
SpecifiedNot applicableStatusStored in the database up to the row displayed in KFPL24509-E.If -l n was not specified, the status before pdload was executed.
If -l n was specified, there is no guarantee.
RecoveryCorrect the row displayed in KFPL24509-E and then re-execute data loading with the -r option specified.If -l n was not specified, correct the input data and then re-execute data loading.
If -l n was specified, recover the database, correct the input data, and then re-execute data loading.
Note
Errors that require rollback include LOB column storage data errors and negative-value errors on the length of variable-length character string and on the number of elements for repetition columns.
A key value duplication error in a mode other than the index update mode (-i s) results in a database corruption error where the table and indexes do not match. To recover the error, restore the database to its status before pdload was executed, correct the input data, and then re-execute data loading.