The table below describes the database status and recovery method in the event of an error during a LOB data reload operation.

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

-l option	Status/Recovery method		Message output immediately before error occurred
			None	721	712 and 732	714 and 734
a or p	Status	Table or index	Status before execution	Reorganization of LOB column structure base table completed	Reorganization of LOB column structure base table completed	Table reorganization completed
		LOB column	Status before execution	Null	Null	LOB column reorganization completed
	Recovery	Table or index	Unnecessary	Unnecessary	Unnecessary	Unnecessary
		LOB column	Re-execute reloading of LOB column only	Re-execute reloading of LOB column only	Re-execute reloading of LOB column only	Unnecessary
n	Status	Table or index	No-log shutdown	No-log shutdown	No-log shutdown	Table reorganization completed
		LOB column	Not guaranteed	Not guaranteed	Not guaranteed	LOB column reorganization completed
	Recovery	Table or index	Re-execute after recovering database#	Re-execute after recovering database#	Re-execute after recovering database#	Unnecessary
		LOB column	Re-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.