The Applier task can apply the following DDL operations to Greenplum targets:
ALTER TABLE
table_name
ADD
column_name
datatype
[NULL]
ALTER TABLE
table_name
ADD CONSTRAINT
constraint_name
PRIMARY KEY (
column_name
)
ALTER TABLE
table_name
ALTER COLUMN
column_name
SET NOT NULL
ALTER TABLE
table_name
ALTER COLUMN
column_name
TYPE
datatype
ALTER TABLE
table_name
DROP COLUMN
column_name
CASCADE
ALTER TABLE
table_name
DROP CONSTRAINT
constraint_name
CASCADE
ALTER TABLE
table_name
RENAME COLUMN
old_column_name
TO
new_column_name
(Oracle sources only)
CREATE INDEX
index_name
ON
table_name
(
column_name
)
CREATE TABLE
table_name
(
column_name
datatype
[NULL|NOT NULL]) DISTRIBUTED RANDOMLY
DROP INDEX
index_name
CASCADE
DROP TABLE
table_name
TRUNCATE TABLE
table_name
For Oracle sources, Data Replication, by default, cannot replicate DROP CONSTRAINT operations that drop a primary key. When extracting these DDL operations, the Extractor sets the NULL option on the primary key columns. However, Greenplum does not support altering primary key columns.
If you execute DROP CONSTRAINT operations that drop a primary key on the source, set the
apply.skip_alter_column_failed_ddl
runtime parameter to 1. This setting causes the Applier to not set the NULL option for the primary key columns on the target. You can then set the NULL option for these columns manually.
To replicate CREATE TABLE, ADD COLUMN, and RENAME COLUMN operations to Greenplum targets in Audit Apply and Merge Apply modes, you must specify table and column names in all lowercase on the source. If you use uppercase, the Applier cannot replicate subsequent DML operations for the new table or column.