How does activation process react if an unsupported object type is found to be a part of the config file?
If there are other objects in the config file which are supported, the activation process will simply list out such unsupported object by raising exception and move on to the next object to try to bring it into the fold of replication as the following sample entry shows:
Warning 2012-05-07 19:49:02.961935 29718 1 Activation: Indexed-Organized table with overflow segment on Oracle 9i is not supported. Skipping (OWNER.TABLENAME) (activating sid SID_name) [module ocf]
If the problem object is the only one forming part of the config file, then the activation will fail with:
Error 2012-05-07 15:49:39.733198 27288 1 Compile of "<config file name>" for sid o.SourceSID failed: No valid tables were found in the config.
