The database user name included in LTL for replicating DDL commands to the standby database. This user must have permission to execute all replicated DDL commands at the standby database.
This parameter is available only for Oracle and Microsoft
SQL Server.
<not_configured>
A valid user name in the standby database.
The value for the ddl_username must not be the same as the value of the maintenance user defined in Replication Server for the standby connection. Failure to provide different names results in a Replication Server error.
The value of the ddl_username parameter is sent in the LTL for all replicated DDL statements.
The value of the ddl_password parameter is the password for the database user name specified in the ddl_username parameter.
When DDL is replicated, Replication Server will connect to the replicate database using the ddl_username and ddl_password.
For Oracle, Replication Server issues the following message:
ALTER SESSION SET CURRENT_SCHEMA=user
where user is the user ID that generated the DDL operation at the primary database. The actual DDL command is then executed against the replicate database. If the ddl_username does not have permission to issue ALTER SESSION SET CURRENT_SCHEMA or to execute the DDL command against the user schema, the command fails.
For Microsoft SQL Server, Replication Agent will send:
execute as login = user
where user is the user ID that generated the DDL operation at the primary database. The actual DDL command is then executed against the replicate database. If the ddl_username does not have permission to issue execute as login or to execute the DDL command against the user schema, the command fails.
