parameter with the NOMAPDERIVED option. See page 408.
Setting DDL processing options
Use the DDLOPTIONS parameter to configure aspects of DDL processing other than filtering and string substitution. You can use multiple DDLOPTIONS statements, but using one is recommended. If using multiple DDLOPTIONS statements, make each of them unique so that one does not override the other. Multiple DDLOPTIONS statements are executed in the order listed. Note Before you create a DDLOPTIONS parameter statement, it might help to review “How DDL is evaluated for processing” on page 411.
Syntax DDLOPTIONS
[, ADDTRANDATA]
[, DEFAULTUSERPASSWORDPASSWORD
[, REMOVECOMMENTS {BEFORE | AFTER}]
[, REPLICATEPASSWORD | NOREPLICATEPASSWORD] [, REPORT | NOREPORT]
Syntax
ADDTRANDATA
This option is valid for Extract. Use ADDTRANDATA to: ??enable supplemental logging automatically for new tables created with a
CREATE TABLE.
??update supplemental logging for tables affected by an ALTER TABLE to add or
drop columns. ??update supplemental logging for tables that are renamed. ??update supplemental logging for tables where unique or primary keys are added or dropped.
By default, the ALTER TABLE that adds the supplemental logging is not replicated to the target unless the GETREPLICATES parameter is in use.
For new tables created with CREATE TABLE, ADDTRANDATA produces the same results as the default ADD TRANDATA command in GGSCI by issuing the Oracle ALTER TABLE command with the ADD SUPPLEMENTAL LOG GROUP option. GoldenGate executes this command when the CREATE TABLE or ALTER TABLE is captured on the source. If you have special requirements for the supplemental logging, use the ADD
TRANDATA command, not DBOPTIONS ADDTRANDATA. For more information about the ADD TRANDATA command, see the GoldenGate for Windows and UNIX Reference Guide.
For renamed tables, ADDTRANDATA deletes the supplemental log group for the old table and creates it for the new one. If you do not use ADDTRANDATA and tables
will be renamed, do the following to create the log group before doing the rename.
To create a log group without ADDTRANDATA
1. Drop the supplemental log group from the database interface or by using the DELETE TRANDATA command in GGSCI. 2. Rename the table.
3. Create the new supplemental log group from the database interface or by using the ADD TRANDATA command in GGSCI.
There might be a lag between the time when an original DDL operation occurs and when the ADD TRANDATA takes effect. During this time, do not allow DML operations (insert, update, delete) on the affected table if the data is to be replicated; otherwise, it will not be captured.
To determine when DML can be resumed after ADDTRANDATA 1. Run GGSCI.
2. Open the Extract parameter file.
EDIT PARAMS
3. If the DDLOPTIONS parameter does not include the REPORT option, add it to the parameter statement, and then save and close the file.
DDLOPTIONS [, other DDLOPTIONS options], REPORT
4. Stop and start Extract to make the parameter change effective.
STOP EXTRACT
5. View the Extract process report.
VIEW REPORT
6. Look for the ALTER TABLE operation that added the supplemental log group to the table. It looks similar to the following:
2007-03-20 15:11:42 GGS INFO 2100 Successfully added TRAN DATA for table with the key, table [QATEST1.MYTABLE], operation [ALTER TABLE \
\].
7. Based on the report, make a note of the time that the ADD TRANDATA took effect.
8. Permit DML operations on the new table.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DEFAULTUSERPASSWORD
This option is valid for Replicat. Use DEFAULTUSERPASSWORD for a replicated
{CREATE | ALTER} USER
You can provide a clear-text or encrypted password. Replicat will replace the
placeholder that Extract writes to the trail with the specified password. Options are as follows: ??DDLOPTIONS DEFAULTUSERPASSWORD
??DDLOPTIONS DEFAULTUSERPASSWORD
Specifies a password that was encrypted with a user-defined method and specifies a lookup key in an ENCKEYS file on the target system.
??DDLOPTIONS DEFAULTUSERPASSWORD
DEFAULT:
Specifies a password that was encrypted by using a random key generated by GoldenGate. On the target, the password is decrypted automatically without requiring an ENCKEYS file. Examples:
DDLOPTIONS DEFAULTUSERPASSWORD ocean
DDLOPTIONS DEFAULTUSERPASSWORD AACAAAAAAAAAAADADESGTFTATAOEEIKB ENCRYPTKEY superkey1
DDLOPTIONS DEFAULTUSERPASSWORD AACAAAAAAAAAAADALHSFYDIEWDEIEIHC ENCRYPTKEY DEFAULT
When using DEFAULTUSERPASSWORD, use the DDLOPTIONS parameter with the NOREPLICATEPASSWORD option in the Extract parameter file.
For more information about how to use these encryption options, see page 291.
GETAPPLOPS | IGNOREAPPLOPS
This option is valid for Extract. It controls whether or not DDL operations produced by local applications except Replicat are included in the content that Extract writes to a trail or file. For more information, see Chapter 15 on page 273.
GETREPLICATES | IGNOREREPICATES
This option is valid for Extract. It controls whether or not DDL operations produced by Replicat are included in the content that Extract writes to a trail or file. For more information, see Chapter 15 on page 273.
MAPDERIVED | NOMAPDERIVED
This option is valid for Replicat. Use MAPDERIVED and NOMAPDERIVED to control whether or not Replicat converts the name of a derived object according to a TARGET clause of a MAP statement that includes it. ??MAPDERIVED: Allows mapping of derived object names according to the rules stated in “How GoldenGate handles derived object names” on page 397. MAPDERIVED is the default. ??NOMAPDERIVED: Prevents name mapping. NOMAPDERIVED overrides any explicit MAP statements that contain the name of the base or derived object. Source DDL that contains derived objects is replicated with the same owner and object names on the target.
Table 42 shows the results of MAPDERIVED compared to NOMAPDERIVED, based on whether there is a MAP statement just for the base object, just for the derived
object, or for both.