8.13.6 Error when reloading LOB data

Table 8-43 describes the database status and recovery method in the event of an error during a LOB data reload operation.

Table 8-43 Database status and recovery method in the event of an error during LOB data reload operation

-l optionStatus/Recovery methodMessage output immediately before error occurred
None721712 and 732714 and 734
a or pStatusTable or indexStatus before executionReorganization of LOB column structure base table completedReorganization of LOB column structure base table completedTable reorganization completed
LOB columnStatus before executionNullNullLOB column reorganization completed
RecoveryTable or indexUnnecessaryUnnecessaryUnnecessaryUnnecessary
LOB columnRe-execute reloading of LOB column onlyRe-execute reloading of LOB column onlyRe-execute reloading of LOB column onlyUnnecessary
nStatusTable or indexNo-log shutdownNo-log shutdownNo-log shutdownTable reorganization completed
LOB columnNot guaranteedNot guaranteedNot guaranteedLOB column reorganization completed
RecoveryTable or indexRe-execute after recovering database*Re-execute after recovering database*Re-execute after recovering database*Unnecessary
LOB columnRe-execute after recovering database*Re-execute after recovering database*Re-execute after recovering database*Unnecessary
Legend:
721: LOB data deleted
712 and 732: Reloading of LOB data started
714 and 734: Reloading of LOB data completed
Note 1
Messages are abbreviated. For example, 712 means KFPL00712-I and 732 means KFPL00732-I.
Note 2
When both the LOB column structure base table and the LOB column are reorganized without the -j option specified, the unload and lobunld statements are both used. In the event of an error during the unload or reload operation on the LOB column, you must delete the unload statement and re-execute the processing with only the lobunld statement specified, because reorganization of the LOB column structure base table has been completed. In the event of abnormal termination of the unload operation, you can re-execute -k rorg as is; however, in the event of abnormal termination of the reload operation, you must change it to -k reld.

* If the reload operation on a LOB column terminates abnormally in the no-log mode, you must recover the table (LOB column structure base table, LOB column, columns of an abstract data type with the LOB attributes, and indexes) from its backup and then re-execute table reorganization.