Use the show_last_posted command to view the PostgreSQL LSN of the last transaction that a Post process applied to the target. The command shows all of the last LSNs when using multiple post queues.
sp_ctrl (sysB)>show last_posted
$> show_last_posted r.dbname1
For resume replication from r.dbname1
On source activate to pglsn=<LSN in hexadecimal format>
reconcile queue sp01 for r.dbname1-r.dbname1 pglsn <LSN1 in hexadecimal format>
reconcile queue sp02 for r.dbname1-r.dbname1 pglsn <LSN2 in hexadecimal format>
reconcile queue sp03 for r.dbname1-r.dbname1 pglsn <LSN3 in hexadecimal format>
NOTE: This command stops all Post processes in order to obtain the LSN information.
Usage
| Supported source: |
PostgreSQL (on-prem), Amazon RDS for PostgreSQL, Amazon Aurora for PostgreSQL, Azure Database for PostgreSQL Flexible Server, and Google Cloud SQL for PostgreSQL |
| Supported targets: |
PostgreSQL, Oracle, SQL Server, Kafka, Amazon RDS for PostgreSQL, Amazon Aurora for PostgreSQL, Azure Database for PostgreSQL Flexible Server, and Google Cloud SQL for PostgreSQL |
| Authorization level: |
Viewer (3) |
| Issued for: |
target system |
| Related commands: |
activate config |
Syntax
This section describes the user-configurable SharePlex parameters. Parameters not documented in this chapter are internal parameters that should only be modified under guidance of a Quest developer or Technical Support representative.
Parameters are grouped as follows:
Configuration activation parameters
These parameters are used by the SharePlex activation process. They take effect at the time that you activate a configuration file.
SP_OCF_HASH_BY_BLOCK
This parameter controls whether the hash algorithm used in horizontally partitioned replication is based on the rowid or on the block where the row resides. The default is 0, which uses the hash based on rowid. Using a hash based on the block may improve the performance of the Post process when processing tables that are using horizontally partitioned replication. To enable a hash based on the block, set this parameter to 1 and then reactivate the configuration file.
Default: 0 (disabled)
Range of valid values: 0 or 1 (enabled block-based hash)
Takes effect: for the next activation
SP_OCF_LOCK_WAIT_TIME
This parameter tells SharePlex how long to wait before failing activation on a particular table. Since the table must be locked for activation, the logic is to retry the lock for a designated period of time, and this designated period of time is controlled by the SP_OCF_LOCK_WAIT_TIME parameter.
Default: 5 minutes
Range of valid values: Any positive integer
Takes effect: Immediately
SP_OCF_THREAD_COUNT
This parameter controls the default number of threads that SharePlex generates during configuration activation. It might be necessary to experiment with the number of threads to determine the optimal performance level. As an example, for a 32-CPU machine with a large disk array, 10 or more threads could show improved performance. The value for the thread count is independent of the number of tables to be analyzed.
Default: 3 threads
Range of valid values: 1 to 32
Takes effect: Immediately
