Oracle GoldenGate Best Practices: Extracting Object ID’s for ALTID Table Mapping (Doc ID 1959140.1)

Last updated on JANUARY 12, 2015

Applies to:

Oracle GoldenGate - Version 10.0.0.14 and later
Information in this document applies to any platform.

Goal

 

In some cases it may be necessary to use the object ID's to extract table data.  This document covers the steps necessary to convert a list of tables into a list of object ID's that can be used in an extract process as ALTID's.   ALTID's can be used in the case where a source table was dropped and you have the original object ID and you want to extract historical data from archive log files.   ALTID's  can also be used to extract data from archive log files in ALO mode where you do not have a connection to or a copy of the original database, but you must extract the object ID's from the original database. You can use ALTID’s to extract a single partition of a partitioned table. One word of caution, if the Object ID changes in the source database, the new ID will be skipped using this method.

In order to process archive log files from another system you will need the following items

»   Supplemental logging enable on the tables to be extracted.

»   DDL for tables to be extracted, if not connecting to the source database.

»   Object ID’s for tables and partitions from the source database.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms