DDL_Flags
The parameter DDL_Flags defines how DDL changes (i.e. structural changes in the source database) are processed. A DDL change could be, for example, adding a column to a table, changing the column data type, dropping a table, etc.
The parameter value is numeric. The following values are defined and can be specified in combination:
- DDL_ACTIVATED (hex value 0x0001)
- The DDL processing is activated.
- DDL_PROTOCOL (hex value 0x0002)
-
Turn on protocoling of the DDL events. A DDL protocol file is created under the same naming rules as the trace or info files; its name ends with '-ddl.txt'.
Note: DDL protocoling is only available on workstations. - DDL_FORMAT_TXT (hex value 0x0004)
- DDL events are protocoled in TXT format.
- DDL_FORMAT_JSON_COMPACT (hex value 0x0008)
- Protocol DDL events in JSON format; each DDL event is represented by a one-line JSON string in a compressed, non human-friendly format.
- DDL_FORMAT_JSON_FORMATTED (hex value 0x0010)
- Protocol DDL events in JSON format; DDL events are represented by pretty-printed, human-readable text.
- DDL_FORWARD (hex value 0x0040)
-
SQL statements for DDL events will be generated and forwarded to the target.
Note:- If the target is set to REPOSITORY (i.e.
Output_Type is 'REPOSITORY'), this flag is ignored and DDL forwarding is controlled via target settings. - This feature is only available on workstations.
- If the target is set to REPOSITORY (i.e.
Example:
DDL_Flags = DDL_ACTIVATED + DDL_PROTOCOL + DDL_FORMAT_JSON_FORMATTED