When tables are created or dropped in the source database where the active config file is using wildcard, the following messages appear in the event log (shown here for both scenarios):
When table is dropped:
Notice 2016-09-27 16:26:30.859912 13424 1 Capture: Table OWNER.TABLE1 is dropped from replication. (capturing from source_SID) [module oct]
When table is created:
Info 2016-09-27 16:26:57.370809 13424 1 Table OWNER.TABLE2 (object id 204368) has been added to replication (capturing from source_SID)
This article explains how SharePlex deals with CREATE/DROP of tables that conform to the wildcard specification in an active config file.
The messages informing the addition or dropping of a table in replication appear only in a wildcard environment. The messages are logged whenever a table that conforms to the wildcard specification is created or dropped in the source database and is consequently added or dropped from replication. When wildcards are used in config file and the SP_OCT_AUTOADD_ENABLE is set to 1, then creation or dropping of the tables can inadvertently bring them into replication or drop them from replication. The above messages are logged so that users can validate such changes by viewing the event log. In fact the event log is the only file where such actions are logged. The activation logs *oconf01.log and *log.rep do not log such adding or dropping of objects in an AUTO ADD environment.
This is different for the non-wildcard objects. When such objects are dropped from replication or brought into replication, the *oconf01.log specifically logs such modifications though the event log shows the complete list of objects brought into replication and does not delve on what was added or dropped.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center