Marking a stored procedure for replication

When you mark a stored procedure for replication, Replication Agent creates the transaction log objects that capture the stored procedure invocation in the transaction log.

NoteFor Oracle, DDL replication must be disabled during the marking of stored procedures. Because marking of a stored procedure modifies that stored procedure, you must first disable DDL replication to prevent the marking modifications from replicating to the standby site. See “Disabling replication for DDL”.

StepsTo mark a stored procedure for replication

  1. Log in to the Replication Agent instance with the administrator login.

  2. Use the pdb_setrepproc command to determine if the stored procedure is already marked in the primary database:

    pdb_setrepproc pdb_proc
    

    where pdb_proc is the name of the stored procedure in the primary database that you want to mark for replication.

  3. Use the pdb_setrepproc command to mark the stored procedure for replication.

    The pdb_setrepproc command allows you to mark the primary stored procedure to be replicated and specify a different stored procedure name to use in the replicate database (as specified in a function replication definition).

  4. Use the pdb_setrepproc command to enable replication for the marked stored procedure:

    pdb_setrepproc pdb_proc, enable
    

    where pdb_proc is the name of the marked stored procedure for which you want to enable replication.

    After replication is enabled for the stored procedure, you can begin replicating invocations of that stored procedure in the primary database.

    NoteIf your stored procedure is in Oracle and you disabled DDL replication during stored procedure marking, remember to re-enable DDL replication. Because marking a stored procedure modifies it, you must first disable DDL replication to prevent the marking modifications from replicating to the standby site. See “Enabling replication for DDL”.