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

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

book

Article ID: 71714

calendar_today

Updated On:

Products

RC/Migrator for DB2 for z/OS RC Compare for DB2 for z/OS

Issue/Introduction

In a RC/Migrator for Db2 for z/OS (RCM) 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.