pdb_skip_op

Description

This command is available only for Oracle and Microsoft SQL Server.

Returns, adds to, or removes operations from a list of operations to skip during processing. The format of the record locator is database-specific.

Syntax

pdb_skip_op [add | remove], [locator | scn, thread, rba] | [remove, all]

Parameters

add: Adds a specified ID to the list of identifiers of records to skip.

remove: Removes a specified ID from the list of identifiers to skip.

locator: The locator keyword from the list of LTM locators to identify the operations to skip.

scn: (For Oracle) The system change number (SCN) keyword identifies a specified log record to skip.

thread: (For Oracle) The thread keyword of the redo log thread of the operation to skip.

rba: (For Oracle) The record byte address (RBA) keyword of the log record to skip.

all: 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.

Example 5

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.

Usage

The pdb_skip_op command allows you to skip problem records, thereby avoiding having to reinitialize the Replication Agent.
Skipped records are written to the system log as a warning message.
The pdb_skip_op command is valid when the Replication Agent is in Admin state.
The format of the identifier is database specific:
- For Microsoft SQL Server, the identifier is the RBA and it has the following form:
```
virtualfileseqno:pageid:operationsseqno
```
  where:
  - virtualfileseqno is the virtual log sequence number (LSN).
  - pageid is the page number.
  - operationsseqno is the sequence number of the operation.
  You can get the LSN using the Microsoft SQL Server DBCC command, or you can parse it from the locator. For example:
  - LSN in decimal format:
```
489:112:27
```
  - LSN in hexadecimal format:
```
0x00000489:00000112:0027
```
```
0012.0000444.0000123
```
  An RBA value can be described as a hexadecimal by prefixing the identifier with an “0x” as follows:
```
0x00c.00001bc.000007b
```
- For Oracle, the identifier contains the system change number (SCN), redo log thread, and record byte address (RBA). It has the following form:
```
wrap.base.sub, thread, lsn.blknum.blkoffset
```
  where:
  - wrap is the SCN wrap number.
  - base is the SCN base number.
  - sub is the SCN subindex.
  - thread is the redo log thread number that the operation occurred on.
  - lsn is the RBA log sequence number.
  - blknum is the RBA block number.
  - blkoffset is the RBA offset into the block where this record resides.
  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’
```
  or:
```
‘0x000.00BC614E’
```