Not valid for MySQL.
DUMPDDL command to view the data in the Oracle
GoldenGate DDL history table if the trigger-based DDL capture is in use. This
information is the same information that is used by the Extract process. It is
stored in proprietary format, but can be exported in human-readable form to the
screen or to a series of SQL tables that can be queried by using regular SQL.
DUMPDDL always dumps all of the records in the DDL
history table. Use SQL queries or search redirected standard output to view
information about particular objects and the operations you are interested in.
Because the history table contains large amounts of data, only the first 4000 bytes
(approximately) of a DDL statement are displayed in order to maintain efficient
performance. The format of the metadata is string based. It is fully escaped and
supports table and column names in their native character set.
Because the information is historical data that is provided by the DDL
before trigger, it reflects the state of an object before a DDL change.
Consequently, there will not be any data for
Note:The default name of the before trigger is
DUMPDDL, log into the database as the owner
of the history table by using the
DUMPDDL command outputs metadata to the
Table 4-2 DUMPDDL Tables
Information about the objects for which DDL operations
are being synchronized.
Information about the columns of the objects involved in DDL synchronization.
Information about the supplemental log groups involved in DDL synchronization.
Information about the partitions for objects involved in DDL synchronization.
Information about the primary keys of the objects involved in DDL synchronization.
SEQNO column is the DDL sequence number that is
listed in the Extract and Replicat report files. It also can be obtained by querying
the DDL history table (default name is
All of these tables are owned by the schema that was designated as the
Oracle GoldenGate DDL schema during the installation of the DDL objects. To view the
structure of these tables, use the
DESC command in SQL*Plus.