LOB import considerations

Since the import utility restricts the size of a single column value to 32 KB, extra considerations need to be taken when importing LOBs.

The import utility, by default, treats data in the input file as data to load into the column. However, when large object (LOB) data is stored in the main input data file, the size of the data is limited to 32 KB. Therefore, to prevent loss of data, LOB data should be stored separate from the main datafile and the lobsinfile file type modifier should be specified when importing LOBs.

The LOBS FROM clause implicitly activates lobsinfile. The LOBS FROM clause conveys to the import utility the list of paths to search for the LOB files while importing the data. If LOBS FROM option is not specified, the LOB files to import are assumed to reside in the same path as the input relational data file.

Indicating where LOB data is stored
The LOB Location Specifier (LLS) can be used to store multiple LOBs in a single file when importing the LOB information. The export utility generates and stores it in the export output file when lobsinfile is specified, and it indicates where LOB data can be found. When data with the modified by lobsinfile option specified is being imported, the database will expect an LLS for each of the corresponding LOB columns. If something other than an LLS is encountered for a LOB column, the database will treat it as a LOB file and will load the entire file as the LOB.

For an import in CREATE mode, you can specify that the LOB data be created and stored in a separate table space by using the LONG IN clause.

IMPORT FROM inputfile.del OF DEL 
	LOBS FROM /tmp/data 
	MODIFIED BY lobsinfile
	INSERT INTO newtable