Valid For
Extract
Description
Use the MAP parameter for Extract when Extract is operating in classic capture mode and you need to use the ALTID component of this parameter to map an object ID to an object name. ALTID specifies the correct object ID if Extract is capturing from Oracle transaction logs that were generated by a database other than the one to which Extract is connected. This configuration is required when Extract is not permitted to connect directly to the production (source) database to capture production transactions.
When Extract cannot connect directly to a source database, it connects to a live standby or other facsimile database, but it reads transaction logs that are sent from the source database. By querying the catalog of the alternate database, Extract can get the metadata that it needs to expand the transaction data into valid SQL statements, but it cannot use the object ID from this query. The local object ID for a table is different from the object ID of that table in the source database (and, thus, in the transaction log). You must manually map each table name to the source object ID by using a MAP statement with ALTID.
To Use MAP with ALTID
Create one MAP statement with ALTID for each table that you want to capture. Wildcarded table names are not allowed for a MAP parameter that contains ALTID.
To specify other processing for the same table (or tables), such as data filtering or manipulation, you must also create a TABLE statement for each of those tables. Wildcarding can be used to specify multiple tables with one TABLE statement, if appropriate.
Use a regular Replicat MAP statement in the Replicat parameter file, as usual. MAP for Extract does not substitute for MAP for Replicat, which is required to map source tables to target tables.
DDL capture and replication is not supported when using ALTID.
Default
None
Syntax
MAP [container.]schema.table, ALTID object_ID [, object_ID]