Triggers generated in wrong order using RC/Migrator
search cancel

Triggers generated in wrong order using RC/Migrator


Article ID: 137457


Updated On:


RC/Migrator for DB2 for z/OS RC/Merger for DB2 for z/OS RC/Update for DB2 for z/OS RC Compare for DB2 for z/OS Database Management for DB2 for z/OS - Administration Suite


What order are Triggers created in using RC/Migrator for Db2 for z/OS (RCM)?  Expecting the CREATE DDL to be generated in alphabetical order but this is not the case.
In addition, in the "Implode/Explode Analysis General format:" report, the order of these triggers is the same as the generated create statements.

Why are these statements not generated in alphabetical order?


The firing sequence of the triggers is determined by the order in which they were created. Since the firing sequence needs to be maintained,
RC/Migrator recreates the triggers in timestamp order. We use the catalog timestamp if the trigger exists in the subsystem.