Schema Compare for Oracle - 2.0

Schema Compare for Oracle

Warnings - Schema Compare for Oracle

On the Review script page of the Synchronization Wizard, you can click the Warnings tab to view information about inefficiencies in the synchronization script, or reasons the script may fail.

When warnings are displayed, you are strongly recommended to review the synchronization script and make any required changes before running it on your target database.

The most common warnings that Schema Compare for Oracle may display are listed below.

Table will be rebuilt

Synchronization will rebuild a table. The table is rebuilt in four steps:

  1. A new table is created.
  2. Data from the original table is copied into the new table.
  3. The original table is dropped.
  4. The new table is renamed as the original table.

A table is rebuilt when synchronization requires making changes that cannot be specified in an ALTER TABLE statement.

Columns will be dropped

When a table is rebuilt, if a column in the target table does not have a matching column in the source table, synchronization will drop the target column. Data in the target column will be lost.

Data will be truncated

Synchronization will reduce the width of a column in a table. If there is data in the column, the synchronization script will fail.

No value specified for NOT NULL column

If no default value is specified for a NOT NULL column in a table, the synchronization script will fail.

To specify a default value:

  1. Click Back to display the Configure script page.
  2. In the Value column for the issue, enter the value you require.

Default value will be added

Synchronization will set a value specified on the Configure script page as the new default for a column.

To specify a different default value:

  1. Click Back to display the Configure script page.
  2. In the Value column for the issue, enter the value you require.

Data type cannot be converted

Synchronization requires that a data type is converted to an incompatible data type. For example, Schema Compare for Oracle cannot convert a BFILE data type to a NUMBER data type. If you run the synchronization script, data in the target column will be lost.

Type object cannot be synchronized

Synchronizing type objects is not supported. If the type object is not referenced by another object, it will not be synchronized. If the type object you want to synchronize is referenced by another object, the synchronization script will fail.

Sequence current value will be lost

The current value of the target sequence will be lost because it is not within the MINVALUE and MAXVALUE limits of the source sequence. The current value will be reset to a default value.

Partitioning will change

Synchronization will make changes to the partitioning of a table. The table will be rebuilt.

You are strongly recommended to review and make any changes to the table rebuild section of the synchronization script before running it on your target database.

System partitioning cannot be changed

Making changes to the partitioning of a system partitioned table is not supported. If you run the synchronization script, the table will not be synchronized.

REF constraints cannot be synchronized

Synchronizing REF constraints is not supported. If you run the synchronization script without making any changes, it may produce unexpected results.

See also

Using the Synchronization wizard

Setting project options

Was this article helpful?

Search support
Forums