SharePlex 9.2.7 - Installation and Setup for Oracle Source

Configure named export queues

A named export queue is an optional, user-defined export queue that is attached to its own Export process. SharePlex creates each named Export queue and associated Export process in addition to the default export queue-process pair. When SharePlex creates a named export queue-process pair, it also creates a dedicated Import process, post queue, and Post process on the target to contain that data stream.

You direct SharePlex to create one or more named export queues when you create your configuration file. Any data that is not configured for processing through a named export queue is processed through the default export queue.

Supported sources

Oracle

Supported targets

All

Benefits of named export queues

Use named export queues to isolate the replication of:

• Individual configurations: By default, SharePlex sends data from all active configurations through one export queue-process pair per target system, but the use of named Export queues enables you to separate each of those replication streams into its own export queue and Export process. In this way, you ensure that purge config or abort config commands that are issued for one configuration do not affect any of the others.
• Selected database objects: You can use a named export queue to isolate certain objects such as tables that contain LOBs. Because each named export queue has its own Import process, post queue, and Post process on the target, you are able to isolate the data the entire way from source to target. For more information about the benefits of named post queues, see Configure named post queues.

Additional benefits:

• You can stop the Export or Import process for one data stream, while allowing the others to continue processing.
• You can set SharePlex parameters to different settings for each export queue-process pair. This enables you to tune the performance of the Export processes based on the objects replicating through each one.

Considerations when using named export queues

• Make certain that each queue name is unique.

• You can combine named export queues with default export queues. Tables in the configuration with a standard routing map (targetsys@database_spec without a named queue specification) are replicated through a default export queue.

• All tables with referential integrity to one another must be in the same export queue.
• SharePlex has a maximum number of allowed queues. For more information, see Routing specifications in a configuration file.

Note: If Post returns the error message "shs_SEMERR: an error occurred with the semaphore" on a Windows system, the number of semaphores may need to be increased to accommodate the queues that you created. For more information, see Post stopped .

Configure a named export queue

Use the following syntax to define a routing map that includes a named export queue.

source_host:export_queuename*target_host[@database]

Configuration with named export queue in routing map

NoteS:

• Allow no spaces between any components in the syntax of the routing map.
• For more information about the components of a configuration file, see Configure data replication.

Examples

The following configuration files show two different datasources that are being replicated to two different databases on the same target system. Each datasource is routed through a named export queue.

The following shows how to separate a table that contains LOBs from the rest of the tables by using named export queues.

Alternatively, you could simply define a named export queue for the LOB table and allow the remaining tables to be processed through the default export queue.

How to identify named export queues

You can view named export queues through sp_ctrl:

• Use the qstatus command to view all queues on a system.
• Use the show command to view all Export processes with their queues.

See the SharePlex Reference Guide for more infomation about theses commands.