Configures Replication Agent to automatically create replication definitions at Replication Server when a table or procedure is marked for replication, after initialization. To improve performance, pdb_auto_create_repdefs is ignored during initialization.
This parameter is available only for Oracle and Microsoft
SQL Server.
The pdb_xlog create command
no longer checks the setting of pdb_auto_create_repdefs
during initialization. To create replication definitions for
all marked tables after executing pdb_xlog create,
execute command rs_create_repdef all.
false
true – Replication Agent automatically creates replication definitions at the Replication Server when tables or procedures are marked after initialization.
false – no replication definitions are created when tables or procedures are marked.
Replication Agent always assumes that a database replication
definition exists for the primary database.
The table and procedure replication definitions that Replication Agent creates assume that a database level replication definition for the primary database already exists at Replication Server.All replication definitions created by this command include the send standby clause, which means the replication definition will only be used by Replication Server if there is a database level replication definition or the primary Replication Server connection is for a warm standby configuration. The replication definition created by rs_create_repdef can not be individually subscribed to. If you do not wish to have a database level replication definition, or warm standby configuration, you must use a different tool, or create replication definitions manually, and not use rs_create_repdef.
Replication definitions created by rs_create_repdef will always define the datatypes using available user defined datatypes that are installed in Replication Server. This means that customers using rs_create_repdef should not set Replication Agent configuration parameter pdb_convert_datetime to true, as doing so converts date and timestamp datatypes to Sybase format, instead of UDD format.
If this parameter is set to true and when pdb_setrepproc is invoked to mark a procedure or procedures, a replication definition is created at Replication Server for each procedure that gets marked for replication.
If this parameter is set to true and when pdb_setreptable is invoked to mark a table or tables, a replication definition is created at Replication Server for each table that gets marked for replication.
If this parameter is set to true and when pdb_setreptable is invoked to unmark a table or tables, the replication definition is dropped at Replication Server for each table that gets unmarked for replication.
If this parameter is set to true and when pdb_setrepproc is invoked to unmark a procedure or procedures, a replication definition is dropped at Replication Server for each procedure that gets unmarked for replication if this parameter is set to true.
The following applies to replication definition table and procedure names:
All non-alphanumeric characters and spaces are removed and are not part of the table or procedure name.
Underscores are kept as part of the name even though they are non-alphanumeric characters.
Periods are replaced with underscores.
Replication definition names for tables always begin with the prefix “ra$,” followed by a unique alphanumeric identifier (maximum of 8 characters), and ending with a table or object name. For example, for a replicate name of “My Table,” the resulting replication definition name is “ra$0x7952_mytable.” For an especially long replicate name of “mytable89012345678901234567890” (30 characters), the resulting replication definition name is “ra$0x7952_mytable8901234567890” (30 or 255 characters maximum, depending on whether or not the pdb_support_large_identifier configuration parameter is set).
Replication definition names for procedures are the same name as the procedure.
