pdb_skip_op

Description

This command is available only for Oracle.

Maintains a list of record identifiers. Log records matching these identifiers will not be processed. The format of the identifier is database-specific.

Syntax

pdb_skip_op [ {add, id} | { remove, { all | id } } ]

Parameters

add: The add keyword adds a specified ID to the list of identifiers of records to skip.

remove: The remove keyword removes a specified ID from the list of identifiers to skip.

id: The identifier of the record that you want to add or remove from the list of identifiers to skip.

all: The all keyword allows you to add or remove all IDs in the list of identifiers to skip.

Examples

Example 1

pdb_skip_op

This command with no parameters returns a list of the identifiers for the records you want to skip.

Example 2

pdb_skip_op add, id

This command adds an ID to the list of identifiers you want to skip.

Example 3

pdb_skip_op remove, id

To remove an ID to the list of identifiers you want to skip:

Example 4

pdb_skip_op remove, all

This command removes all the IDs on the list of identifiers you want to skip.

Usage

The pdb_skip_op command allows you to skip problem records, thereby avoid having to reinitialize the Sybase Replication Agent.
Skipped records are written to the system log as a warning message.
The pdb_skip_op command is valid when the Sybase Replication Agent is in Admin state.
For Oracle, the format of the identifier is a rollback address (RBA). An RBA has the following form:
```
LSN.BLKNUM.BLKOFFSET
```
where:
- LSN is the log sequence number.
- BLKNUM is the block number.
- BLKOFFSET is the offset into the block where this record resides.
The three values must be specified in the pdb_skip_op command together, enclosed in quotes, each item separated by a period.

For example:
```
‘0012.0000444.0000123’
```
An RBA value can be described as a hexadecimal by prefixing the identifier with an ‘0x’ as follows:
```
‘0x000c.00001bc.000007b’
```