Determines whether Replication Agent automatically runs scripts (for transaction log creation and removal, and object marking and unmarking) at the primary database.
true – Replication Agent automatically runs scripts.
false – Replication Agent generates and saves the scripts, but it does not automatically run them at the primary database.
(IBM DB2 UBD only) If the pdb_auto_run_scripts parameter is true, Replication Agent automatically runs scripts and the script files are not saved when marking and unmarking a table. Otherwise, when marking a table, all generated SQL files are stored in the mark directory. When unmarking a table, all generated SQL files are stored in the unmark directory.
When the pdb_xlog command is invoked to create or remove the transaction log, Replication Agent generates a script to create or remove the Replication Agent system objects.
When the pdb_setrepproc command is invoked to mark or unmark an object in the primary database, Replication Agent generates a script to create or remove the transaction log objects necessary for object marking.
Replication Agent always saves the scripts in a file. Log creation and removal scripts are saved in files named partinit.sql and partdeinit.sql. Object marking and unmarking scripts are saved in files named partmark.sql and unmark.sql.
When the pdb_auto_run_scripts parameter is set to false, the scripts are created but no action is taken. This allows you to review the scripts to see what action will be taken before execution. You cannot execute the scripts. You must set pdb_auto_run_scripts parameter back to true and re-execute the command to have the desired action take place.
As described above for the pdb_xlog and pdb_setrepproc commands, Oracle and Microsoft SQL Server create the partinit, partdeinit, partmark, and partunmark scripts. For Oracle and Microsoft SQL Server, these scripts cannot be executed (since they do not update the RASD) and are for informational purposes only.
This parameter must be set to true for initialization to occur.