Contents

• Arithmetic overflow may occur
• Cluster is not indexed
• Columns dropped
• Column precision or data loss
• Column renamed
• Column data loss
• Data type cannot be converted
• Data will be truncated
• Default value will be added
• Dependency Violation 
• Encrypted column data loss
• Ensure data is in the correct format
• Ensure edition exists in target
• Ensure encryption password is set for encrypted column
• Ensure object exists in remote server
• Ensure proper LBAC credentials
• Ensure security policy exists in target
• Ensure type object can be deployed
• Grants on missing grantees
• Grants for missing group
• Grants for missing role
• Grants for missing user
• No value specified for a NOT NULL column
• No value specified for a NOT NULL column
• Non-standard filegroup does not exist in target
• Non-standard segment does not exist in target
• Non-standard tablespace does not exist in target
• Partitioning will change
• Possible data truncation
• Schema does not exists in the target database
• Sequence current value will be lost
• System partitioning cannot be changed
• Table dropped
• Table rebuild
• Transfer Ownership permissions will be lost
• Unsupported data type 
• Unsupported clause
• Unsupported cluster definition
• Unsupported cluster modification
• Unsupported keyword
• Unsupported object modification
• Unsupported STATISTICS object
• Unsupported storage parameter
• Unsupported storage parameter in target

Arithmetic overflow may occur

Severity: High

When Will You See This Warning? An issue occurs when the data type range or the data type precision of the target column exceeds the source column. To resolve that issue, Schema Synchronization generates a data conversion function in the Configure Script tab. However, if you choose the Ignore issue option, Schema Synchronization generates the Arithmetic overflow will occur warning.

Impact on the Script: The deployment script might fail.

Cluster is not indexed

Severity: High

When Will You See This Warning? When index is not created on the cluster. 

Impact on the Script: The deployment script might fail because Schema Synchronization will not alter object using the cluster.

Columns dropped

Severity: High

When Will You See This Warning? When a column in the target table will be dropped.

Impact on the Script: Schema Synchronization will drop a column from the target table and data in that target column will be lost.

Column precision or data loss

Severity: High

When Will You See This Warning? When the data type range or the data type precision of the target column exceeds the source column.

Impact on the Script: The deployment script might fail, or data in the target column might be lost.

Column renamed

Severity: Medium

When Will You See This Warning? When the target column name does not match the source column name.

Impact on the Script: Schema Synchronization will rename the target column to the source column.

Column data loss

Severity: High

When Will You See This Warning? When the data type of the target column cannot be converted to the data type of the source column and the source table contains a NOT NULL column.

Impact on the Script: Data in the target column will be lost.

Data type cannot be converted

Severity: High

When Will You See This Warning? When the data type of the target column is not compatible with the data type of the source column.

Impact on the Script: Data in the target column will be lost.

Data will be truncated

Severity: High

When Will You See This Warning? An issue occurs when the data type length of the target column exceeds the source column. To resolve that issue, Schema Synchronization generates a data conversion function in the Configure Script tab. However, if you choose the Ignore issue option, Schema Synchronization generates the Data will be truncated warning.

Impact on the Script: Data in the target column might be lost.

Default value will be added

Severity: Low

When Will You See This Warning? When you specify a custom value for a NOT NULL column in the Configure Script tab.

Impact on the Script: Schema Synchronization will add the specified custom value in the deployment script and consider it as the default value for a NOT NULL column.

Dependency Violation 

Severity: High

When Will You See This Warning? When the target server version does not support the referred object.

Impact on the Script: The deployment script will fail.

Encrypted column data loss

Severity: High

When Will You See This Warning? When the Table Rebuild process ignores the encrypted column.

Impact on the Script: Data from the target column will be lost.

Ensure data is in the correct format

Severity: Medium

When Will You See This Warning? When data in the target column is not compatible with the data type of the source column.

Impact on the Script: The deployment script might fail.

Ensure edition exists in target

Severity: Low

When Will You See This Warning? When users must ensure the edition existing on the source server also exists on the target server.

Impact on the Script: If the edition does not exist on the target server, the deployment script will fail.

Ensure encryption password is set for encrypted column

Severity: High

When Will You See This Warning? When the target table contains an encrypted column which cannot be altered by the Alter Statement as the encryption password is not set.

Impact on the Script: The deployment script will fail.

Ensure object exists in remote server

Severity: High

When Will You See This Warning? When users must ensure a remote object on the source server also exists at the location provided on the target server.

Impact on the Script: If the remote object does not exist on the target server, the deployment script will fail.

Ensure proper LBAC credentials

Severity: High

When Will You See This Warning? When users must ensure they have LBAC credentials to use security label with the column in the target table. 

Ensure security policy exists in target

Grants on missing grantees

Grants for missing group

Grants for missing role

Grants for missing user

No value specified for a NOT NULL column  

No value specified for a NOT NULL column

Severity: High

When Will You See This Warning? When the DEFAULT object is bound to a NOT NULL column in the source table and the column in the target table is NULLABLE.

Impact on the Script: The deployment script might fail if the target column contains NULL value.

Non-standard filegroup does not exist in target

Severity: High

When Will You See This Warning? When a non-standard filegroup in a table or index exists on the source server but not on the target server.

Impact on the Script: The deployment script will fail. 

Non-standard segment does not exist in target

Severity: High

When Will You See This Warning? When a non-standard segment in a table exists on the source server but not on the target server.

Impact on the Script: The deployment script will fail

Non-standard tablespace does not exist in target

Severity: High

When Will You See This Warning? When a non-standard tablespace in a table exists on the source server but not on the target server.

Impact on the Script: The deployment script will fail. 

Partitioning will change

Severity: High

When Will You See This Warning? When partitioning differs for both the target and the source schemas.

Impact on the Script: The deployment script will change the partition of the target table and rebuild the table.

Possible data truncation

Schema does not exists in the target database

Sequence current value will be lost

System partitioning cannot be changed

Severity: High

When Will You See This Warning? When system partitioning is included in synchronization but the Oracle Server does not allow to change the system partitioning.

Warning Description and Impact:

• Description: If the source schema is SYSTEM partitioned and the target schema is NONSYSTEM partitioned, for example, HASH, RANGE, and LIST.
  Impact: The script will rebuild the target table and retain the existing partition. We recommend reviewing the target table rebuild script before executing it.
• Description: If tables are SYSTEM partitioned and existed in both the source and target schemas, but the TABLESPACE is different for both schemas.
  Impact: The script will not rebuild the table but retain the existing partition. If the partition levels are different, then deployment will rebuild the target table and remove the partition.

Table dropped

Table rebuild

Severity: Medium

1. A new temporary table similar to the source table will be created.
2. Data from the target table will be inserted into the temporary table.
3. The target table will be dropped. 
4. The temporary table will be altered and renamed as per the source table.

Transfer Ownership permissions will be lost

Unsupported data type 

Severity: High

When Will You See This Warning? You will see this warning in these scenarios:

• Data type used in the user-defined data type on the source server version is not supported on the target server version.
• Data type in a column on the source server version is not supported on the target server version.
• Data type of a parameter on the source server version is not supported on the target server version.
• Data type of the return type on the source server version is not supported on the target server version.

Impact on the Script: The deployment script will fail.

Unsupported clause

Severity: High

When Will You See This Warning? When the clause of an object type is supported on the source server version but not on the target server version.

Impact on the Script:

• If the clause is not present in the deployment script, then the script will be executed without deploying the clause.
• If the clause is present in the deployment script, then the script will fail.

Unsupported cluster definition

Severity: High

When Will You See This Warning? When a clustered table is present in the source schema and an unclustered table in the target schema.

Schema Synchronization does not support cluster modification.

Impact on the Script: The script might fail. We recommend reviewing the script before executing it.

Unsupported cluster modification

Severity: High

When Will You See This Warning?

• A clustered table is present in the source schema and an unclustered table in the target schema.
• Both the source and the target schemas contain a clustered table, but the definitions are different.

Schema Synchronization does not support cluster modification.

Impact on both scenarios: The script might fail. We recommend reviewing the script before executing it.

Unsupported keyword

Severity: High

When Will You See This Warning? When keywords are supported on the source server version but not on the target server version.

Impact on the Script:

• If the keyword is not present in the deployment script, then the script will be executed without deploying the keyword.
• If the keyword is present in the deployment script, then the script will fail.

Unsupported object modification

Severity: High

When Will You See This Warning? When the definition of the cluster object for both the source and target schemas is different.

Schema Synchronization does not support cluster modification.

Impact on the Script: The script might fail. We recommend reviewing the script before executing it.

Unsupported STATISTICS object

Severity: High

When Will You See This Warning? Aqua Data Studio does not support STATISTICS object, but the tables or views included for synchronization contain this object.

Impact on the Script: The DDL script will not be generated for the STATISTICS object.

Unsupported storage parameter

Unsupported storage parameter in target