Valid For

Extract and Replicat


Use the GETTRUNCATES and IGNORETRUNCATES parameters to control whether or not Oracle GoldenGate processes table truncate operations. By default, truncate operations are not captured from the source or replicated to the target.

GETTRUNCATES and IGNORETRUNCATES are table-specific. One parameter remains in effect for all subsequent TABLE or MAP statements, until the other parameter is encountered.

In a coordinated Replicat configuration, truncates are always processed by the thread that is responsible for barrier transactions.

Supported Databases

  • GETTRUNCATES and IGNORETRUNCATES are not supported for Teradata.

  • GETTRUNCATES and IGNORETRUNCATES are supported by Extract for Oracle Database, MySQL, DB2 LUW, and DB2 for i.

  • GETTRUNCATES and IGNORETRUNCATES are supported by Extract and Replicat for DB2 for i.

  • GETTRUNCATES and IGNORETRUNCATES are supported by Replicat for Oracle Database, SQL Server, DB2 LUW, DB2 z/OS, MySQL, and other ODBC targets that support the TRUNCATE command.

  • GETTRUNCATES and IGNORETRUNCATES are supported by Extract for Sybase. However, if the same table name is present in the include list for two schemas then it is abended and an error occurs, stating " Found the same table name in multiple schemas and the table name could not be resolved to process truncate operation."

  • Sybase AES 16 is supported from Oracle GoldenGate


It is not possible to ignore TRUNCATEs during capture from a DB2 z/OS database. By default, TRUNCATEs are always captured from a DB2 z/OS source, but they can be ignored by Replicat if IGNORETRUNCATES is used in the Replicat parameter file.

DB2 LUW Limitations

  • DB2 LUW does not support a TRUNCATE command, so Replicat replicates a truncate operation by performing an IMPORT REPLACE from a NULL (blank) file.

Oracle Limitations

  • Oracle GoldenGate supports the Oracle TRUNCATE TABLE command, but not TRUNCATE PARTITION. You can replicate TRUNCATE PARTITION as part of the full Oracle GoldenGate DDL replication support.

  • The database does not log truncates against an empty table, so those operations are not captured by Oracle GoldenGate. The DDL support of Oracle GoldenGate can be used for this purpose.

  • The database does not log truncates for empty partitions, so Oracle GoldenGate cannot reliably process TRUNCATE TABLE when the table contains any empty partitions. Do not use GETTRUNCATES on any partitioned table. Oracle GoldenGate DDL support can be used to capture truncates on tables that might include empty partitions.