STEPS
Customer uses to DROP and create "EXISTING_TABLE" "
1.CREATE NEW_TABLE
2.COPY EXISTING_TABLE to NEW_TABLE
3.DROP the EXISTING_TABLE
4.RENAME THE NEW_TABLE to EXISTING_TABLE NAME
5. CONTINUE COLLECTING CHANGES for "EXISTIG_TABLE"
===========================================================
- Their default is to IGNORE DROP
- Logstream and replication tasks DB2 LUW( SAP)
- TABLE SELECTION = %.% ( they do not select the name of the table having the DROP issue)
===================================
1) When they do the drop of the EXISTING_TABLE:
At this point, the drop table is recorded in Replicate log for Logstream task.
Note that DROP table statement isn't thrown as Error but as Warning in Child/Replication task if "When source table is dropped:"
Expected Behavior:
1. Throw the warning message as Error so that we could catch it.