The Applier task can apply the following DDL operations to Oracle targets:
ALTER TABLE
table_name
ADD (
column_name
datatype
[CONSTRAINT
constraint_name
{NOT NULL|UNIQUE}]
ALTER TABLE
table_name
ADD CONSTRAINT
constraint_name
ALTER TABLE
table_name
DROP (
column_name
)
ALTER TABLE
table_name
DROP CONSTRAINT
constraint_name
ALTER TABLE
table_name
DROP {UNIQUE (
column_name
)|PRIMARY KEY}
ALTER TABLE
table_name
MODIFY (
column_name
datatype
ALTER TABLE
table_name
RENAME COLUMN
column_name
TO
new_column_name
CREATE INDEX
index_name
ON
table_name
CREATE TABLE
table_name
(
column_name
datatype
[CONSTRAINT
constraint_name
{NOT NULL|UNIQUE}]
CREATE TABLE
table_name
AS SELECT
statement
DROP INDEX
index_name
DROP TABLE
table_name
TRUNCATE TABLE
table_name
When replicating DDL changes from Microsoft SQL Server sources to Oracle targets, Data Replication does not replicate ALTER COLUMN operations that change a column datatype from VARCHAR(
n
) to VARCHAR(MAX). Data Replication maps the SQL Server VARCHAR(MAX) datatype to the Oracle CLOB datatype, but Oracle does not support an ALTER COLUMN operation that changes a VARCHAR column to a CLOB column.
To replicate CREATE TABLE and ADD COLUMN operations to Oracle targets in Audit Apply and Merge Apply modes, you must specify table and column names in all uppercase on the source. If you use lowercase, the Applier cannot replicate subsequent DML operations for the new table or column.