You can use wildcard characters to specify multiple objects of a schema in one entry of the configuration file. SharePlex replicates any objects that satisfy the wildcard, except those that you explicitly exclude.
Note: Only object names can be wildcarded. Owner names cannot be wildcarded.
Wildcards are not allowed anywhere in a configuration entry that includes the following:
The tables that use these features must be specified in the configuration file separately.
SharePlex supports the following SQL wildcards
Use this template for help when specifying a wildcarded name in the configuration file.
| datasource_specification | ||
| expand src_owner.wildcard_name [not (list)] |
tgt_owner.wildcard_name |
routing_map |
| Component | Description |
|---|---|
| expand |
Indicates that the specification contains wildcard characters that must be expanded. When SharePlex detects the expand keyword, it queries the database for all objects that match the criteria in the wildcard specification. Without this required keyword, the wildcard characters are assumed to be part of an explicit object name, and no wildcard expansion is performed. Note: Leave a space between expand and the start of the source object specification. |
| src_owner.wildcard_name |
Rules: Oracle: The names of the target objects must be identical to those of the source objects, but the objects may belong to different owners. |
| not (list) |
An exclusion list that defines objects to omit from the wildcard expansion. Use this option to exclude objects that you do not want to be replicated. Note: This not keyword does not have the same meaning as the SQL wildcard NOT operator.
Leave a space before and after the not keyword. A space is allowed after each comma in the list. Note: If an object that satisfies a wildcard is listed elsewhere in the configuration file, that entry overrides the processing or routing specified in the wildcarded entry. In this case, a not clause is not needed. See the Examples. |
| tgt_owner.wildcard_name |
The target specification must be in the form of owner.%. Partially expanded target wildcarded names are not supported, such as owner.tab%. |
| routing_map | Any valid routing map. For more information, see Routing specifications in a configuration file |
To confirm that a wildcard specification will produce the specific list of tables that you want to replicate, issue the verify config command in sp_ctrl before you activate the configuration. This command produces a list of the objects that SharePlex will capture and replicate, as well as any problems that occurred. For more information about this command, see the SharePlex Reference Guide.
Example 1: The following wildcard specification directs SharePlex to activate all tables owned by scott, where the table name is like prod% except if the table name is like %temp%. All tables that match this description are replicated to tables of the same names on the target in the hal schema. Note that SharePlex automatically upshifts the names, so that it actually activates all tables where the table name is like 'PROD%' but not like '%TEMP%'.
Datasource:o.sidA expand scott.prod% not (%temp%) hal.% sysa@o.sidB
Example 2: The following example shows how you can specify special handling for one of the tables in a wildcarded specification, in this case the photo table. All tables but photo are routed through the default post queue. The separate entry for the photo table overrides the wildcarded entry and processes the photo table through a named post queue. For more information, see Configure named post queues.
Datasource:o.sidA cust.% cust.% hostB@o.oraB cust.photo cust.photo hostB:lobQ@o.oraB
The following are additional examples of valid wildcard specifications
Datasource:o.sidA expand scott.%test% scott.% sysa@o.sidB
Datasource:o.sidA expand scott.%t__t% fred.% sysa@o.sidB
Datasource:o.sidA expand scott.% not (spo%, gen%, prodct) scott.% sysa@o.sidB
Datasource:o.sidA expand scott.prod% not (%temp%) hal.% sysa@o.sidB
The following example contains a wildcarded schema, which is not permitted.
Datasource:o.sidA expand rob%.%test% scott.% sysa@o.sidB
The following example contains a partially wildcarded target object name, which is not permitted.
Datasource:o.sidA expand scott.%test% scott.%obj% sysa@o.sidB
© ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center
