OGG-00457
Object {0} was renamed even though it's marked excluded with NORENAME. Renamed object (if included) may or may not be picked up (you should not rename objects marked with NORENAME)
Cause
The object is specified in a TABLEEXCLUDE parameter that has the NORENAME option enabled, 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-00457
Object {0} was renamed even though it's marked excluded with NORENAME. Renamed object (if included) may or may not be picked up (you should not rename objects marked with NORENAME)
Cause
The object is specified in a TABLEEXCLUDE parameter that has the NORENAME option enabled, 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-00457
Object {0} was renamed even though it's marked excluded with NORENAME. Renamed object (if included) may or may not be picked up (you should not rename objects marked with NORENAME)
Cause
The object is specified in a TABLEEXCLUDE parameter that has the NORENAME option enabled, 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.
