RC/Migrator is not generating DDL for LOB objects in a Migration Strategy

Document ID : KB000071714
Last Modified Date : 23/02/2018
Show Technical Document Details
Issue:
In a Quick Migration strategy, even though the LOB Tablespace has been explicitly specified in the PARMFILE and the LOBTOO Analysis option has been specified, RC/Migrator is not generating the DDL for the LOB objects.

//PARMFILE DD *
STRTSSID ssid
CREATOR creator
QUICKM
TABLESPACE dname tsname <- base Tablespace
EXPLODE TABLE
EXPLODE INDEX
TABLESPACE dbname tsname <- LOB Tablespace
EXPLODE TABLE
EXPLODE INDEX
QUICKEND
TRGSSID ssid
AUXIMP Y
MQTIMP N
REFMQT N
LOBTOO
SEQIMP
RTNIMP
RTNIIO N
PREFIX userid
MODEL4 model_name
MODEL4C model_creator

Only the DDL for the base Tablespace, Table and Indices is generated.
Cause:
If these LOB objects (LOB Tablespace, auxiliary table and index) were created implicitly by DB2 then RC/Migrator will not generate the DDL. RC/Migrator, by design, does not generate DDL for implicitly generated objects. DB2 will implicitly create the LOB objects when the base objects are created. So the generated DDL is correct.
 
Resolution:
When the CREATE statements for the base objects are executed, DB2 will implicitly create the LOB objects.
Additional Information:
Based on the LOBTOO Analysis option, RC/Migrator will only generate the DDL for LOB objects when they have been created explicitly.