The following messages show up in oconf log and event_log and similar messages can also show up in “verify config”, “activate config” and the like:
oconf 2018-01-26 16:54:14.435061 4383 1 Processing the configuration entries
oconf 2018-01-26 16:54:14.441616 4383 1 Cannot replicate SecureFile LOB with NOLOGGING. Skipping ("OWNER"."SOURCE_TABLE")
SharePlex is a log based replication hence any object or column in an object that is NOLOGGING will fail to replicate.
There are two options available to deal with the above:
A. If wishing to bring the table into replication, carry out the following steps:
1. Issue ALTER TABLE with LOGGING clause to make it logging. (see Oracle documentation for details)
2. Make a copy of the currently active config file.
3. Activate the copy so as to bring the table into replication.
4. Resync the table at a convenient time.
B. If not interested in replicating the table, ignore the messages about “cannot replicate..” or if the messages are too much of annoyance, take the table out of the config file as:
1. Make a copy of the currently active config file.
2. Edit the copy to remove the entry for the table.
3. Activate the copy. Henceforth these messages about “cannot replicate..” will not show up anymore.
