Returns, adds to, or removes operations from a list of operations to skip during processing. The format of the record locator is database-specific.
pdb_skip_op [ { add , { locator | { scn, thread, rba | lsn } } | remove, { all | locator | { scn, thread, rba | lsn } } } ]
pdb_skip_op
This command with no parameters returns a list of the identifiers for the records you want to skip.
pdb_skip_op add, id
This command adds an ID to the list of identifiers you want to skip.
pdb_skip_op remove, id
This command removes an ID from the list of identifiers you want to skip.
pdb_skip_op remove, all
This command removes all the IDs on the list of identifiers you want to skip.
pdb_skip_op add, locator
This command adds an operation, referred to by its location, to the list of identifiers that you want to skip.
The pdb_skip_op command allows you to skip problem records, thereby avoiding having to reinitialize Replication Agent.
Skipped records are written to the system log as a warning message.
The pdb_skip_op command is valid when Replication Agent is in Admin or Replication Down state.
wrap.base.sub, thread, lsn.blknum.blkoffset
The values must be specified in the pdb_skip_op command together, as shown above, enclosed in quotes, with each item separated by a period.
For example:
‘0000.012345678.00’, ’1’, ’0012.0000444.0000123’
All values can be described as hexadecimal by prefixing the identifier with an “0x” as follows:
‘0x000c.00001bc.000007b’
‘0x000.00BC614E’