Occasionally it may be convenient to add a table to the Capture Agent Configuration (.cab) file before it is present in the Oracle Catalog. This scenario might occur when a new Oracle Business application is being implemented. The tables will have been created in the test environment for the new application and because a downstream application will requires that data to be captured, the capture configuration in the test environment has also been updated so the downstream application can also be tested.
While the normal capture configuration maintenance process supports adding tables and marking them Inactive and then subsequently changing them to Active, they must be in the Oracle Catalog even when they are marked Inactive. Because the scale of implementation is large it would be desirable to create or more likely update the production capture configuration in advance. That can be accomplished by adding the table with a Pending status (--pending) rather than Inactive, which would cause the capture to immediately fail because the production catalog did not yet contain those tables.
The SQDCONF Utility will be used to add the Pending tables and later to modify the configuration when it is time for them to be activated.
sqdconf add <cab_file_name>
--schema=<name> --table=<name> | --key=<name>
--datastore=<url>
[--pending]Finally, when it is time to begin to capture the new tables, use the modify command to change the status of the tables from Pending to Active (or Inactive).
sqdconf modify <cab_file_name>
--schema=<name> --table=<name> | --key=<name>
[--active | --inactive]- The sqdconf modify command only needs to be run once for each Pending table regardless of the number of datastores (Engines) subscribed.
- Like all modifications to the Capture Agent Configuration (.cab) file the must be activated, see Applying the Configuration File changes.