When comparing schemas on different Oracle servers, some incompatibilities can occur in schema objects. For example, when comparing schemas on Oracle 9i and 12c. Schema on Oracle 12c > can have such objects as COMPOUND TRIGGER, PROCEDURE WRAPPED that are not supported on 9i server. This topic describes how dbForge Schema Compare for Oracle treats such incompatibilities.
If source schema contains objects that are not supported on the target Oracle server, they are not displayed in the Schema Comparison document and are not affected by synchronization.
If target schema contains objects that are not supported on the source Oracle server, they are displayed in the document. Their default operation is None, and they will not be affected by synchronization. You may change their operation to Drop, and the object will be dropped from the target schema.
Sometimes there are some incompatibilities even if the type of the database object is supported on both source and target databases. For example, tables are supported by both Oracle 11g and Oracle 21c, but a table on one server may have a column of a type that is not supported on the other one.
When an object is supported on the source server but is not supported on the target server, it will have Inconsistent status and cannot participate in synchronization. When there is an object in the target that is not supported in the source, but source objects are supported on the target server, target schema can be synchronized and incompatible database objects have Different status.
Here are some examples of such incompatibilities:
Partitioning is treated in another way than other incompatibilities. Let us examine several situations:
If target schema supports partitioning, partitioned tables are included into schema comparison results, otherwise they are ignored.
In cases when equal schema objects have syntax differences, because they are placed on different server versions, the object DDL is generated according to target object DDL.