Troubleshooting DDL Replication Failure in Replication Agent for UDB

Troubleshoot errors when Replication Agent for UDB fails to replicate DDL commands for a newly created table.

If you create a new table, and if pdb_automark_tables is true, you must manually set the value of the table DATA CAPTURE option to DATA CAPTURE CHANGES in the same transaction. Otherwise, Replication Agent for UDB logs an error message in its system log, an exclusive NOCDCERRORTRC trace log for this event, and the name of the newly created table. To handle this situation, follow these steps to successfully replicate the new table:

Mark the table identified in the NOCDCERRORTRC trace log in Replication Agent for UDB:
```
pdb_setreptable ownername.tablename, mark, owner
```
Create a table level replication definition in Replication Agent for UDB:
```
rs_create_repdef ownername.tablename
```

Create a table level subscription in the Replication Server with direct load materialization:

create subscription subscription_name
for repdef_name
with replicate at replicateDS.replicateDB
without holdlock
direct_load
user RAU_admin_username password RAU_admin_password

Add the table to the database replication definition inclusion list in Replication Server:

alter database replication definition database_repdef_name 
with primary at primaryDS.primaryDB 
add tables in files (ownername.tablename)

After the table level subscription is validated in the Replication Server, drop the table level subscription in the Replication Server:
```
drop subscription subscription_name 
for repdef_name 
with replicate at replicateDS.replicateDB 
without purge
```
Drop the table level replication definition in Replication Agent for UDB:
```
rs_drop_repdef ownername.tablename
```