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.
Using object ID's to extract table data is fairly easy. All you need from the source system is the structure of the table and the object ID's you are scanning for. If you are not connecting to the source database to extract the metadata you will need to gather the DDL for the tables from the source system. If not using the source system for the metadata, the structure of the table must be identical to the source including the PK/UK on the table. GoldenGate will use the structure in the database you are connecting too for the metadata on the table and use the Object ID in the parameter file to extract the data.
The complete document can now be found on the Oracle Support site -