OGG-00456
Object that is not replicated. The object "{0}" was renamed to "{1}" even though DDLOPTIONS NOCROSSRENAME is in effect. This may result in new (renamed) objects not processed correctly.
Cause
The DDLOPTIONS parameter includes NOCROSSRENAME, and the table was renamed to one that is included in a TABLE statement (probably because of a wildcard). This can cause the object to be replicated incorrectly, depending on whether a target exists and how it is defined. This might also cause data to be replicated that you do not want to be replicated.
Action
Ensure that the source and target tables match, for both the original and renamed tables. If you cannot resolve the problem, contact Oracle Support.
OGG-00456
Object that is not replicated. The object "{0}" was renamed to "{1}" even though DDLOPTIONS NOCROSSRENAME is in effect. This may result in new (renamed) objects not processed correctly.
Cause
The DDLOPTIONS parameter includes NOCROSSRENAME, and the table was renamed to one that is included in a TABLE statement (probably because of a wildcard). This can cause the object to be replicated incorrectly, depending on whether a target exists and how it is defined. This might also cause data to be replicated that you do not want to be replicated.
Action
Ensure that the source and target tables match, for both the original and renamed tables. If you cannot resolve the problem, contact Oracle Support.
OGG-00456
Object that is not replicated "{0}" was renamed into object that is "{1}" even though DDLOPTIONS NOCROSSRENAME is in effect. This may result in new (renamed) objects not processed correctly.
Cause
The DDLOPTIONS parameter includes NOCROSSRENAME, and the table was renamed to one that is included in a TABLE statement (probably because of a wildcard). This can cause the object to be replicated incorrectly, depending on whether a target exists and how it is defined. This might also cause data to be replicated that you do not want to be replicated.
Action
Ensure that the source and target tables match, for both the original and renamed tables. If you cannot resolve the problem, contact Oracle Support.
