The staging tables used by CDM Streaming, CDM Multi-Stream, and CDM for CREATE TABLE AS (CTAS) are managed by Teradata Business Continuity Manager. The staging tables are automatically created in the current user default database and are automatically dropped when Business Continuity Manager completes the transaction.
_U<sid>_<tid>_<dbqlid>_<stmtno>_<orderno>_<oid>_ISTG_<tablename>
Where:
Parameter | Description |
---|---|
sid | Primary session ID for the original request |
tid | Primary transaction ID for the original request |
dbqlid | DBQL Query ID from the source system for the original request |
stmtno | Statement number from the source system for the original request |
orderno | Step order number within each statement from the source system for the original request |
oid | Dictionary ID of the base table for which this staging table is used. |
ISTG, DSTG, or TMP | Staging table types |
tablename | Name of the base table for which this staging table is used |
If Business Continuity Manager is shut down improperly while CDM staging tables are in use, some staging tables can remain after the Business Continuity Manager restart. You can identify these staging tables by the naming convention, and the associated session has moved past the associated transaction. If that is the case, you can drop the orphaned staging table through Business Continuity Manager. This should only be done if you are certain that the staging table is orphaned. Dropping a staging table that is still in use causes the change data replication to fail on the target system.