Previous Next JavaScript must be enabled to correctly display this content

## F Zero Downtime Migration Logical Migration Response File Parameters Reference

Zero Downtime Migration response file parameters supported for logical migrations.

### F.1 DATA_TRANSFER_MEDIUM

Specifies how data will be transferred from the source database system to the target database system.

See also Configuring the Transfer Medium and Specifying Transfer Nodes

Property | Description
--- | ---
Syntax | `DATA_TRANSFER_MEDIUM = {OSS | NFS | DBLINK | COPY | AMAZON3}`
Default value | `OSS`
Range of values | `OSS` - Object Storage Service `NFS` - Network File System `DBLINK` - Direct transfer of data over a database link. `COPY` - secure copy (for co-managed and user managed targets) `MANUAL_COPY` - This option is valid only for no-ssh case which means that you have not specified the -`targetnode` or the -`sourcenode` info in the zdmcli migrate command. Specifying this option skips copying the dump files by ZDM. Copy the dumps to the import directory in the target node. Use the -`pauseafter` method with value `ZDM_DATAPUMP_EXPORT_SRC` in the zdmcli migrate command so that the migrations pauses post Export and then you can copy the dump files to the target node's import directory. After this, you can resume the migration. ZDM uses the dumps in the import directory and continues with the migration. If you do not use `pauseafter`, ZDM fails in the IMPORT phase and displays the error that the required dump files are not present in the target import directory. You can then copy the dumps and resume the migration. `AMAZON3` - Amazon Simple Storage Service (Amazon S3) bucket (only supported when `SOURCEDATABASE_ENVIRONMENT_NAME=AMAZON`
Required | Yes
Modifiable on Resume | No

### F.2 DATAPUMPSETTINGS_CREATEAUTHTOKEN

Indicates whether to create a new OCI Auth Token.

Note:

This parameter is applicable only when the source database is Oracle Autonomous Database on Shared Exadata Infrastructure or Oracle Autonomous Database on Dedicated Exadata Infrastructure.
If you are not using a network database link for Data Pump Import, an OCI Auth Token is created for the specified OCI user to import Data Pump dump files from the Object Storage into an Autonomous Database.

To reuse an existing Auth Token, set this property to `FALSE`.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_CREATEAUTHTOKEN ={TRUE | FALSE}`
Default value | `FALSE`
Range of values | `TRUE` - Creates an OCI Auth Token for the specified OCI user `FALSE` - Does not create an OCI Auth Token.
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_TGT` phase is `COMPLETED`.

### F.3 DATAPUMPSETTINGS_DATABASELINKDETAILS_NAME

Specifies the name of the database link from the OCI database to the on-premise database.

Zero Downtime Migration creates the database link if the link does not already exist.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

The `DATAPUMPSETTINGS_DATABASELINKDETAILS_*` parameters are optional details for creating a network database link from OCI database to the on-premise database.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATABASELINKDETAILS_NAME = db_link_name`
Default value | There is no default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_DATAPUMP_SETTINGS_TGT` phase is `COMPLETED`.

### F.4 DATAPUMPSETTINGS_DATABASELINKDETAILS_WALLETBUCKET_BUCKETNAME

Specifies the OCI Object Storage bucket.

The `DATAPUMPSETTINGS_DATABASELINKDETAILS_WALLETBUCKET_*` parameters are used with Autonomous Database migration targets. These parameters settings specify the OCI Object Storage details used to store the wallet containing the certificate for on-premise database to create a database link from the Autonomous Database to the on-premise database using TLS.

Not required for a TCP connection from Autonomous Database to the on-premise database.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATABASELINKDETAILS_WALLETBUCKET_BUCKETNAME = Object Storage bucket name`
Default value | There is no default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_TGT` phase is `COMPLETED`.

### F.5 DATAPUMPSETTINGS_DATABASELINKDETAILS_WALLETBUCKET_NAMESPACENAME

Specifies the Object Storage namespace.

The `DATAPUMPSETTINGS_DATABASELINKDETAILS_WALLETBUCKET_*` parameters are used with Autonomous Database migration targets. These parameters settings specify the OCI Object Storage details used to store the wallet containing the certificate for on-premise database to create a database link from the Autonomous Database to the on-premise database using TLS.

Not required for a TCP connection from Autonomous Database to the on-premise database.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATABASELINKDETAILS_WALLETBUCKET_NAMESPACENAME = Object Storage bucket namespace`
Default value | There is no default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_TGT` phase is `COMPLETED`.

### F.6 DATAPUMPSETTINGS_DATABUCKET_BUCKETNAME

In lieu of a network database link, the OCI Object Storage bucket specified in `DATAPUMPSETTINGS_DATABUCKET_BUCKETNAME` is used to store Data Pump dump files for migrating to an Autonomous Database.

`DATAPUMPSETTINGS_DATABUCKET_BUCKETNAME` is one of the optional settings for logical migrations using Data Pump.

Use with `DATAPUMPSETTINGS_DATABUCKET_NAMESPACENAME`

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATABUCKET_BUCKETNAME = Name of the Object Storage bucket`
Default value | There is no default value
Range of values | Enter the storage bucket name
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_DATAPUMP_SETTINGS_SRC` phase is `COMPLETED`.

### F.7 DATAPUMPSETTINGS_DATABUCKET_NAMESPACENAME

In lieu of a network database link, the OCI Object Storage bucket specified with `DATAPUMPSETTINGS_DATABUCKET_NAMESPACENAME` is used to store Data Pump dump files for migrating to an Autonomous Database.

`DATAPUMPSETTINGS_DATABUCKET_NAMESPACENAME` is one of the optional settings for logical migrations using Data Pump.

Use with `DATAPUMPSETTINGS_DATABUCKET_BUCKETNAME`

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATABUCKET_NAMESPACENAME = Object Storage namespace`
Default value | There is no default value
Range of values | Enter the storage bucket namespace
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_DATAPUMP_SETTINGS_SRC` phase is `COMPLETED`.

### F.8 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_ESTIMATEBYSTATISTICS

Specifies the STATISTICS method for Data Pump dump size estimation.

Zero Downtime Migration estimates the Data Pump dump size using the BLOCKS or STATISTICS methods. You are expected to apply discretion in arriving at the FILESYSTEM space required for the dump path, considering other factors that affect the actual dump size expected. The estimated dump size and actual size varies based on the data compression applied on the data in the database.

- If data is compressed, then it would be the same as that of the reported ESTIMATE
- If data is uncompressed, then Zero Downtime Migration exports with COMPRESSION set as MEDIUM and the resulting dump would be ~50% of estimate
- There is deviation in dump size expected between data having HCC vs. Advanced compression modes

Note that by default, Zero Downtime Migration performs estimation using the BLOCKS method as part of the precheck and as part of the actual migration part of phase `ZDM_DATAPUMP_ESTIMATE_SRC`.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

`DATAPUMPSETTINGS_DATAPUMPPARAMETERS_*` are optional parameters for Data Pump Export and Import. See SET_PARAMETER Procedures for more information.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_ESTIMATEBYSTATISTICS = [TRUE | FALSE]`
Default value | `FALSE`
Valid values | `TRUE` enables this parameter `FALSE` disables this parameter
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_ESTIMATE_SRC` phase is `COMPLETED`.

### F.9 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_TABLEEXISTSACTION

Specifies the action to be performed when data is loaded into a preexisting table.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

`DATAPUMPSETTINGS_DATAPUMPPARAMETERS_*` are optional parameters for Data Pump Export and Import. See SET_PARAMETER Procedures for more information.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_TABLEEXISTSACTION = [SKIP | TRUNCATE | REPLACE | APPEND]`
Default value | `SKIP`
Range of values | `SKIP` - the preexisting table is left unchanged. `TRUNCATE` - rows are removed from a preexisting table before inserting rows from the Import. Note that if `TRUNCATE` is specified on tables referenced by foreign key constraints, the `TRUNCATE` will be modified into a `REPLACE`. `REPLACE` - preexisting tables are replaced with new definitions. Before creating the new table, the old table is dropped. `APPEND` - new rows are added to the existing rows in the table See `TABLE_EXISTS_ACTION` entry in Table 48-25 "Valid Options for the name Parameter in the SET_PARAMETER Procedure" in SET_PARAMETER Procedures
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_IMPORT_TGT` phase is `COMPLETED`.

### F.10 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_USERMETADATA

For EXPORT and Network IMPORT, if set to a nonzero value for schema-mode operations, specifies that the metadata to re-create the user's schemas should also be part of the operation.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

`DATAPUMPSETTINGS_DATAPUMPPARAMETER_*` are optional parameters for Data Pump Export and Import. See SET_PARAMETER Procedures for more information.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_USERMETADATA = integer`
Default value | There is no default value
Valid values | An integer value is expected
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_EXPORT_SRC` is `COMPLETED`, or until `ZDM_DATAPUMP_IMPORT_TGT` phase when using `DATA_TRANSFER_MEDIUM=DBLINK`.

### F.11 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_IMPORTPARALLELISMDEGREE

Specifies the maximum number of worker processes that can be used for a Data Pump Import job.

For migration to an Autonomous Database target, Zero Downtime Migration automatically queries its CPU core count and sets this parameter.

Note:

While the value is calculated automatically, if you have already set this parameter, then the value is not calculated and ZDM will consider the value that you set.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

`DATAPUMPSETTINGS_DATAPUMPPARAMETERS_*` are optional parameters for Data Pump Export and Import. See SET_PARAMETER Procedures for more information.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_IMPORTPARALLELISMDEGREE = integer`
Default value | There is no default value
Valid values | An integer value is expected
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_IMPORT_TGT` phase is `COMPLETED`.

### F.12 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_EXPORTPARALLELISMDEGREE

Specifies the maximum number of worker processes that can be used for a Data Pump Import job.

For migration to an Autonomous Database target, Zero Downtime Migration automatically queries its CPU core count and sets this parameter.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

`DATAPUMPSETTINGS_DATAPUMPPARAMETERS_*` are optional parameters for Data Pump Export and Import. See SET_PARAMETER Procedures for more information.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_EXPORTPARALLELISMDEGREE = integer`
Default value | There is no default value
Valid values | An integer value is expected
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_EXPORT_SRC` phase is `COMPLETED`.

### F.13 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_DISABLESTATSGATHERING

Enable this parameter to minimize the resource impact of statistics gathering during the Data Pump job execution.

Set the DATAPUMPSETTINGS_DATAPUMPPARAMETERS_DISABLESTATSGATHERING parameter to `TRUE` in the Data Pump job procedure. This helps to minimize the resource impact of statistics gathering during the Data Pump job execution.

Note:

This parameter disables the statistics gathering only during the Data Pump import, not during export.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

`DATAPUMPSETTINGS_DATAPUMPPARAMETERS_*` are optional parameters for Data Pump Export and Import. See SET_PARAMETER Procedures for more information.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_DISABLESTATSGATHERING = {TRUE | FALSE}`
Default value | `FALSE`
Valid values | Following are the supported values: `TRUE`: Disable the DataPump job statistics gathering `FALSE`: Enable the DataPump job statistics gathering
Required | No
Modifiable on Resume | No

### F.14 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_ENCRYPTION

Specifies what should be encrypted in the dump file set.

Parameter Relationships

Note:

Oracle Database Standard Edition 2 does not have dump encryption support and set DATAPUMPSETTINGS_DATAPUMPPARAMETERS_ENCRYPTION=NONE for migration to proceed with data being exported using Data Pump without encryption.

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

`DATAPUMPSETTINGS_DATAPUMPPARAMETERS_*` are optional parameters for Data Pump Export and Import. See SET_PARAMETER Procedures for more information.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_ENCRYPTION = <encryptionValue>`
Default value | `ALL`
Valid values | Following are the supported values: `DATA_ONLY` `METADATA_ONLY` `ENCRYPTED_COLUMNS_ONLY` `ALL` `NONE`
Required | No
Modifiable on Resume | No

### F.15 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_EXCLUDETYPELIST

Specifies a comma separated list of object types to exclude.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

`DATAPUMPSETTINGS_DATAPUMPPARAMETERS_*` are optional parameters for Data Pump Export and Import. See SET_PARAMETER Procedures for more information.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_EXCLUDETYPELIST = object_type_list`
Default value | There is no default
Valid values | A comma separated list of object types
Required | No
Modifiable on Resume | No

Example

    DATAPUMPSETTINGS_DATAPUMPPARAMETERS_EXCLUDETYPELIST=cluster,dblink,comment

### F.16 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_FLASHBACKTIME

During export, specify the timestamp to determine a consistent point for reading your data. This parameter sets the FLASHBACK_TIME parameter for Data Pump Export.

Note:

The value for `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_FLASHBACKTIME` can be either `SYSTIMESTAMP` or a value that can start with `TO_TIMESTAMP`.

Online migration does not support `TO_TIMESTAMP`; use `SYSTIMESTAMP` instead.

Parameter Relationships

This parameter is applicable for both offline and online logical migration.

Note:

Do not specify this parameter when using Oracle GoldenGate for online migration.

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

`DATAPUMPSETTINGS_DATAPUMPPARAMETERS_*` are optional parameters for Data Pump Export and Import. See SET_PARAMETER Procedures for more information.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_FLASHBACKTIME = FLASHBACKTIME_string` For example: `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_FLASHBACKTIME= TO_TIMESTAMP('2025-07-30 17:45:00', 'YYYY-MM-DD HH24:MI:SS')`
Default value | There is no default value
Range of values | A string value is expected
Valid values | A comma separated list of object types
Required | No
Modifiable on Resume | No

### F.17 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_SKIPCURRENT

Specifies whether actions that were "in progress" on a previous execution of the job are skipped when the job restarts.

This mechanism allows you to skip actions that trigger fatal bugs and cause the premature termination of a job. Multiple actions can be skipped on a restart. The log file identifies which actions are skipped.

The skip is only honored for Import jobs.

If a domain index was being processed, all pieces of the domain index are skipped, even if the error only occurred in a sub-component of the domain index.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

`DATAPUMPSETTINGS_DATAPUMPPARAMETERS_*` are optional parameters for Data Pump Export and Import. See SET_PARAMETER Procedures for more information.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_SKIPCURRENT = [TRUE | FALSE]`
Default value | `FALSE`
Valid values | `TRUE` enables this parameter `FALSE` disables this parameter
Required | No
Modifiable in Resume | Until `ZDM_DATAPUMP_IMPORT_TGT` phase is `COMPLETED`.

### F.18 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_NOCLUSTER

Specifies whether all Data Pump workers are started on the current instance or on instances usable by the job.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

`DATAPUMPSETTINGS_DATAPUMPPARAMETERS_*` are optional parameters for Data Pump Export and Import. See SET_PARAMETER Procedures for more information.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_NOCLUSTER = [TRUE | FALSE]`
Default value | `FALSE`
Valid values | `TRUE` all Data Pump workers are started on the current instance `FALSE` Data Pump workers are started on instances usable by the job
Required | No
Modifiable on Resume | No

### F.19 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_RETAININDEX

Specifies whether to retain the index.

Parameter Relationships

While migrating to the Oracle Autonomous Database on Shared Exadata Infrastructure target database, the INDEXTYPE objects are excluded by default. Set the DATAPUMPSETTINGS_DATAPUMPPARAMETERS_RETAININDEX parameter to retain the INDEXTYPE objects from source to target Oracle Autonomous Database on Shared Exadata Infrastructure database.

Note:

This is not applicable for the other supported target databases as INDEXTYPE objects are always migrated.

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

`DATAPUMPSETTINGS_DATAPUMPPARAMETERS_*` are optional parameters for Data Pump Export and Import. See SET_PARAMETER Procedures for more information.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_RETAININDEX = [TRUE | FALSE]`
Default value | `FALSE`
Valid values | `TRUE` retains the index `FALSE` does not retain the index
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_EXPORT_SRC` phase is `COMPLETED`, or until `ZDM_DATAPUMP_IMPORT_TGT` phase when using `DATA_TRANSFER_MEDIUM=DBLINK`.

### F.20 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_PARTITIONOPTION

`DATAPUMPSETTINGS_DATAPUMPPARAMETERS_PARTITIONOPTION` specifies how partitioned tables should be handled during an import operation when the target database type is Oracle Autonomous Data Warehouse.

`DATAPUMPSETTINGS_DATAPUMPPARAMETERS` are optional parameters for Data Pump Export and Import. See SET_PARAMETER Procedures for more information.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DATAPUMPPARAMETERS_PARTITIONOPTION = [DEPARTITION | MERGE | NONE]`
Default value | `NONE`
Valid values | `DEPARTITION`, `MERGE`, `NONE`

### F.21 DATAPUMPSETTINGS_DELETEDUMPSINOSS

Indicates whether to retain dump files which are uploaded to Object Storage as part of the migration.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_DELETEDUMPSINOSS = {TRUE|FALSE}`
Default value | `TRUE`
Range of values | `TRUE` = delete dumps `FALSE` = retain dumps
Required | No
Modifiable on Resume | Until `ZDM_POST_DATAPUMP_TGT` phase is `COMPLETED`.

### F.22 DATAPUMPSETTINGS_ENABLETRACE

Allows users to disable the traces for Data Pump.

Set this property to `FALSE` to disable any traces and by default, the property is `TRUE`.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_ENABLETRACE = [TRUE | FALSE]`
Default value | `TRUE`
Valid values | `TRUE` `FALSE`
Required | No
Modifiable on Resume | No

### F.23 DATAPUMPSETTINGS_EXPORTDIRECTORYOBJECT_NAME

Specifies the object name of a directory on server file system of an on-premises database.

In lieu of a network database link, a directory on the server file system of an on-premises database, specified with the `DATAPUMPSETTINGS_EXPORTDIRECTORYOBJECT_*` properties is used to store Data Pump Export dump files.

Zero Downtime Migration creates this object if it does not already exist

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_EXPORTDIRECTORYOBJECT_NAME = Name`
Default value | There is no default value
Range of values | Name of directory object in the database.
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_DATAPUMP_SETTINGS_SRC` phase is `COMPLETED`.

### F.24 DATAPUMPSETTINGS_EXPORTDIRECTORYOBJECT_PATH

Specifies the object path of a directory on server file system of an on-premises database.

In lieu of a network database link, a directory on the server file system of an on-premises database, specified with the `DATAPUMPSETTINGS_EXPORTDIRECTORYOBJECT_*` properties is used to store Data Pump Export dump files.

Zero Downtime Migration creates this object if it does not already exist

Note:

For Oracle Database 19c and later releases, the `UTL_FILE_DIR` initialization parameter is desupported, which means symbolic links for Data Pump directories are not supported.

If you attempt to use an affected feature configured with symbolic links, then you encounter ORA-29283: invalid file operation: path traverses a symlink. Oracle recommends that you instead use directory objects in place of symbolic links.

See How Does Oracle Data Pump Move Data? for more information.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_EXPORTDIRECTORYOBJECT_PATH = Path`
Default value | There is no default value
Range of values | Absolute path of directory on database server
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_DATAPUMP_SETTINGS_SRC` phase is `COMPLETED`.

### F.25 DATAPUMPSETTINGS_EXPORTVERSION

Specifies the Data Pump job export version.

See Oracle Data Pump documentation for Data Pump Export Version.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_EXPORTVERSION = ["COMPATIBLE","12","LATEST"]`
Default value | `COMPATIBLE`, if the target database is of same or higher version than that of source database, and specific version, if the target database is a lower version than that of source database.
Required | No

### F.26 DATAPUMPSETTINGS_FIXINVALIDOBJECTS

Specifies whether invalid objects are recompiled in the database as part of the migration job.

Note:

Starting with Oracle Zero Downtime Migration 26 (26.1) release, the `DATAPUMPSETTINGS_FIXINVALIDOBJECTS` parameter is deprecated and will be desupported in a future release. It is replaced by the following parameters:

- `FIXINVALIDS_ENABLED`
- `FIXINVALIDS_BYSCHEMA`
- `FIXINVALIDS_PARALLELCOUNT`
- `FIXINVALIDS_RETRYCOUNT`

Migration can result in invalid schema objects. Typically, invalid objects fix themselves as they are accessed or run. However, Oracle recommends that invalid objects are recompiled in the database as part of the Zero Downtime Migration migration job so that issues with invalid objects, and any required dependencies, are resolved before users encounter these invalid objects.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_FIXINVALIDOBJECTS = {TRUE | FALSE}`
Default value | `FALSE`
Range of values | `TRUE` = fix invalid objects `FALSE` = do not fix invalid objects
Required | No
Modifiable on Resume | Until `ZDM_POST_DATAPUMP_TGT` phase is `COMPLETED`.

### F.27 DATAPUMPSETTINGS_IGNOREERROR

Enables you to define and ignore specific sequences of ORA errors (Data Pump error blocks). You can configure multiple error blocks, such as `IGNOREERROR-1, IGNOREERROR-2`, and so on, to customize error handling during execution.

The `DATAPUMPSETTINGS_IGNOREERROR` parameter works by matching error strings using regular expressions. Each parameter is configured to match a specific sequence of ORA errors (error block) based on the error, messages generated during execution. Here’s how the matching works:

Group multiple error patterns into a single parameter, separated by commas and wildcard character `*` (preceded by period `.` for example, you can use `ORA-39083.*INDEX.*`) for matching.

Example: `DATAPUMPSETTINGS_IGNOREERROR-1="ORA-39083.*INDEX.*,ORA-02158,ORA-39082: Object type PACKAGE BODY.*"`

The above example matches:

- Error for `ORA-39083` containing "INDEX" as error string.
- The exact error `ORA-02158` (only ORA-02158 string is matched).
- The error containing string `ORA-39082: Object type PACKAGE BODY`.

    Example 1:
    ORA-39083: Object type INDEX:"FUSION_SOCIAL"."XCO$TI_01" failed to create with error:ORA-02158: invalid CREATE INDEX option
    ORA-39082: Object type PACKAGE BODY:"FUSION_SOCIAL"."WAGGLE_CODE" created with compilation warnings

    Example 2:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-20000: some user-defined error message
    ORA-06512: at "CTXSYS.DRUE", line 123ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 456

Define each error block in the response file using an `IGNOREERROR` parameter as follows:

    DATAPUMPSETTINGS_IGNOREERROR-1="ORA-39083.*INDEX.*,ORA-02158,ORA-39082: Object type PACKAGE BODY.*"
    DATAPUMPSETTINGS_IGNOREERROR-2="ORA-29855.*ODCIINDEXCREATE.*,ORA-20000,ORA-06512.*CTXSYS.DRUE.*,ORA-06512.*CTXSYS.TEXTINDEXMETHODS.*"

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_IGNOREERROR =`
Default value | There is no default value
Range of values | Absolute path of directory on database server
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_DATAPUMP_SETTINGS_TGT` phase is `COMPLETED`.

### F.28 DATAPUMPSETTINGS_IMPORTDIRECTORYOBJECT_PATH

Specifies the absolute path of an import directory object.

In lieu of a network database link, a directory on the server file system of OCI database is used to store Data Pump dump files.

Zero Downtime Migration creates this object if it does not already exist.

For Autonomous Database migration targets, the `DATA_PUMP_DIR` object will already exist.

Note:

For Oracle Database 19c and later releases, the `UTL_FILE_DIR` initialization parameter is desupported, which means symbolic links for Data Pump directories are not supported.

If you attempt to use an affected feature configured with symbolic links, then you encounter ORA-29283: invalid file operation: path traverses a symlink. Oracle recommends that you instead use directory objects in place of symbolic links.

See How Does Oracle Data Pump Move Data? for more information.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_IMPORTDIRECTORYOBJECT_PATH = Path of the directory object`
Default value | There is no default value
Range of values | Absolute path of directory on database server
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_DATAPUMP_SETTINGS_TGT` phase is `COMPLETED`.

### F.29 DATAPUMPSETTINGS_IMPORTDIRECTORYOBJECT_NAME

Specifies the name of an import directory object.

In lieu of a network database link, a directory on the server file system of OCI database is used to store Data Pump dump files.

Zero Downtime Migration creates this object if it does not already exist.

For Autonomous Database migration targets, the `DATA_PUMP_DIR` object will already exist.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_IMPORTDIRECTORYOBJECT_NAME = Name of the directory object`
Default value | There is no default value
Range of values | Name of directory object in database
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_DATAPUMP_SETTINGS_TGT` phase is `COMPLETED`.

### F.30 DATAPUMPSETTINGS_JOBMODE

Specifies the Data Pump export mode.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Usage

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_JOBMODE = jobModeValue`
Default value | `SCHEMA`
Range of values | `FULL` performs a full database export. `SCHEMA` (default) lets you specify a set of schemas to export. Note: Ensure to not use `SCHEMA` with `GOLDENGATESETTINGS_USEMIGRATIONMODE=TRUE` However, you can set the value to `FULL` for migration mode. `TABLE` lets you specify a set of tables to export. In this mode, Zero Downtime Migration precreates the target schema before Data Pump import. `TABLESPACE` lets you specify a set of tablespaces to export. In this mode, Zero Downtime Migration precreates the target schema before Data Pump import. `TRANSPORTABLE` is not supported by Zero Downtime Migration. See Oracle Data Pump Export Modes for more information.
Required | No
Modifiable on Resume | No

### F.31 DATAPUMPSETTINGS_METADATAFILTERS-LIST_ELEMENT_NUMBER

Defines the name, the object type, and the value of the filter for the Data Pump `METADATA_FILTER` property.

To add multiple filters, increment the integer appended to the parameter name, as shown in the examples below.

    DATAPUMPSETTINGS_METADATAFILTERS-1=name:nameValue1st, objectType:objectTypeValue1st, value:valueValue1st
    DATAPUMPSETTINGS_METADATAFILTERS-2=name:nameValue2nd, objectType:objectTypeValue2nd, value:valueValue2nd

To exclude select `SCHEMA` Objects for `FULL` mode:

    DATAPUMPSETTINGS_METADATAFILTERS-1=name:NAME_EXPR,value:'NOT IN(' 'SYSMAN' ')',objectType:SCHEMA
    DATAPUMPSETTINGS_METADATAFILTERS-2=name:NAME_EXPR,value:'NOT IN(' 'SH' ')',objectType:SCHEMA

Note that the `SCHEMA` name `SYSMAN` is surrounded by two single quotes and not a double quote.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_METADATAFILTERS-LIST_ELEMENT_NUMBER = name:nameValue, objectType:objectTypeValue, value:valueValue`
Default value | There is no default value
Range of values | An entry specifying the name, type, and value is expected, as shown in the examples above.
Required | No
Modifiable on Resume | No

### F.32 DATAPUMPSETTINGS_METADATAREMAPS-LIST_ELEMENT_NUMBER

Defines remapping to be applied to objects as they are processed.

To add multiple remappings, increment the integer appended to the parameter name, as shown in the examples below.

    DATAPUMPSETTINGS_METADATAREMAPS-1=type:typeValue1st, oldValue:oldValueValue1st, newValue:newValueValue1st
    DATAPUMPSETTINGS_METADATAREMAPS-2=type:typeValue2nd, oldValue:oldValueValue2nd, newValue:newValueValue2nd

See METADATA_REMAP Procedure for more information.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_METADATAREMAPS-LIST_ELEMENT_NUMBER = type:typeValue, oldValue:oldValueValue, newValue:newValueValue` See Remaps Provided by the METADATA_REMAP Procedure for more information about the values that can be specified for `type`.
Default value | There is no default value
Range of values | An entry specifying the new value, old value and type is expected, as shown in the examples above.
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_EXPORT_SRC` phase is `COMPLETED`, or until `ZDM_DATAPUMP_IMPORT_TGT` phase when using `DATA_TRANSFER_MEDIUM=DBLINK`

### F.33 DATAPUMPSETTINGS_METADATATRANSFORMS-LIST_ELEMENT_NUMBER

Defines the name, the object type, and the value for the Data Pump `METADATA_TRANSFORM` property.

To add multiple filters, increment the integer appended to the parameter name, as shown in the examples below.

    DATAPUMPSETTINGS_METADATATRANSFORMS-1=name:nameValue1st, objectType:objectTypeValue1st, value:valueValue1st
    DATAPUMPSETTINGS_METADATATRANSFORMS-2=name:nameValue2nd, objectType:objectTypeValue2nd, value:valueValue2nd

See METADATA_TRANSFORM for more information.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_METADATATRANSFORMS-LIST_ELEMENT_NUMBER = name:nameValue, objectType:objectTypeValue, value:valueValue` Note: See METADATA_TRANSFORM for more information about the values that can be specified for `name`.
Default value | There is no default value
Range of values | An entry specifying the name, type, and value is expected, as shown in the examples above.
Required | No
Modifiable on Resume | No

Usage Notes

You can set `XMLTYPE_STORAGE_CLAUSE` to `'BINARY XML'`.`DATAPUMPSETTINGS_METADATATRANSFORMS-1=name:XMLTYPE_STORAGE_CLAUSE, value:'BINARY XML'` . With this enhancement all XML types can be converted as part of the migration.

In another example, you can set `DATAPUMPSETTINGS_METADATATRANSFORMS-2=name:TABLE_COMPRESSION_CLAUSE, value: 'NONE'`.

### F.34 DATAPUMPSETTINGS_METADATAFIRST

Specifies that Zero Downtime Migration will import METADATA and DATA as separate phases in the migration job work flow. Setting `DATAPUMPSETTINGS_METADATAFIRST` to `TRUE` will import the METADATA before DATA.

Migrating METADATA and DATA as separate phase in the migration job workflow provides these benefits:

- Allows you to quickly identify the migration issues that arise due to lockdown profiles in ADB.

- Allows quick completion of export/import operations of large databases and identify and rectify DDL import errors

- Allows you to intervene in the migration workflow with target custom actions that require the database objects to exist, namely USER Schema or TABLE or other associated OBJECT definitions

- Helps you identify potential import failure points in DDL processing

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Usage

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_METADATAFIRST = {TRUE | FALSE}`
Default value | `FALSE`
Range of values | `TRUE` = import METADATA before DATA as a separate migration job workflow phase `FALSE` = do not import METADATA and DATA in separate phases
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_SRC`

### F.35 DATAPUMPSETTINGS_MONITORINTERVALMINUTES

Specifies the Data Pump monitor interval in minutes. This setting is optional.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_MONITORINTERVALMINUTES = number`
Default value | 10
Range of values | An integer value is expected
Required | No
Modifiable on Resume | No

### F.36 DATAPUMPSETTINGS_OMITENCRYPTIONCLAUSE

Sets `TRANSFORM=OMIT_ENCRYPTION_CLAUSE`, which directs Data Pump to suppress any encryption clauses associated with objects using encrypted columns.

This parameter is valid for targets on Oracle Database 19c and later releases.

`OMIT_ENCRYPTION_CLAUSE` applies to materialized view, table, and tablespace objects, and enables objects which were using encrypted columns in the source to get created in a target database environment where encryption attributes are not supported.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_OMITENCRYPTIONCLAUSE = [TRUE | FALSE]`
Default value | `TRUE`
Valid values | `TRUE` enables this parameter `FALSE` disables this parameter
Required | No
Modifiable on Resume | No

### F.37 DATAPUMPPARAMETER_<PARAMETER_NAME>

Specifies the Data Pump parameter in the following format:

`DATAPUMPPARAMETER_<PARAMETER_NAME>=<PARAMETER_VALUE>,stage:<STAGE_NAME>`

`<PARAMETER_NAME>` : Oracle Data Pump parameter name to apply.

`<PARAMETER_VALUE>` : The value for the specified Data Pump parameter. If the value is a string, enclose it in single quotes.

`<STAGE_NAME>` : Stage in which Data Pump parameter will be applied. Enter one of the allowed values.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPPARAMETER_<PARAMETER_NAME>=<PARAMETER_VALUE>,stage:<STAGE_NAME>`
Default value | There is no default value
Valid values for <STAGE_NAME> | `INIT_EXPORT, INIT_IMPORT, ALL_EXPORT, ALL_IMPORT, RELOAD_EXPORT, RELOAD_IMPORT, ALL`
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_DATAPUMP_SETTINGS_TGT` phase is `COMPLETED`.

### F.38 DATAPUMPSETTINGS_RETAINDUMPS

Specifies if you want to clean the dumps in OSS or FSS.

If this parameter is set to `TRUE`, then export dumps are not cleaned as part of the post actions in the selected data transfer medium; OSS, NFS, or FSS.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_RETAINDUMPS = [TRUE | FALSE]`
Default value | `FALSE` For regular export/import job, the dumps are cleaned up in OSS or FSS.
Valid values | `TRUE` enables this parameter `FALSE` disables this parameter
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_DATAPUMP_SETTINGS_TGT` phase is `COMPLETED`.

### F.39 DATAPUMPSETTINGS_REUSE_DUMPPREFIX

(Optional) Specifies the dump prefix of the existing dump files from a previous job.

ZDM can reuse the existing DataPump dump files from the previous ZDM jobs. This is optional and can be done by specifying in this parameter the dump file prefix as `ZDM_<jobID>_DP_EXPORT_<#>_dmp`. ZDM auto detects the dump files in the indicated import directory object path and includes them for import. In this case, ZDM does not include the estimate, export, and transfer phase. If the specified dumps are not present, an error is thrown.

Note:

To retain the dumps in the ZDM job, set `DATAPUMPSETTINGS_RETAINDUMPS` to `TRUE`.
Specify the dump's prefix pattern for preexisting dumps that you want to re-import. Provide the prefix as `ZDM_<jobID>_DP_EXPORT_<#>_dmp`.

Note:

Setting `REUSE` and `DATAPUMPSETTINGS_METADATAFIRST` to `TRUE` is not currently supported in the Oracle Zero Downtime Migration 21c (21.5) release.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_REUSE_DUMPPREFIX = ZDM_<jobID>_DP_EXPORT_<#>_dmp`
Default value | None
Valid values | NA
Required | No
Modifiable on Resume | No

### F.40 DATAPUMPSETTINGS_SECUREFILELOB

Sets `TRANSFORM=LOB_STORAGE:SECUREFILE`, which directs Data Pump to transform basic LOBs into securefile LOBs during the Data Pump import.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_SECUREFILELOB = [TRUE | FALSE]`
Default value | `TRUE`
Valid values | `TRUE` enables this parameter `FALSE` disables this parameter
Required | No
Modifiable on Resume | No

### F.41 DATAPUMPSETTINGS_SCHEMABATCHCOUNT

Specifies the number of schemas to be processed in parallel as batches.

When `DATAPUMPSETTINGS_JOBMODE=SCHEMA` you can specify the number of schemas to be migrated in parallel. If this count is specified, then Zero Downtime Migration determines the set of schemas included in each batch from the list of user schemas identified from the database.

`DATAPUMPSETTINGS_SCHEMABATCHCOUNT` is mutually exclusive with the `DATAPUMPSETTINGS_SCHEMABATCH` parameter. `DATAPUMPSETTINGS_METADATAFIRST` is not supported along with the `DATAPUMPSETTINGS_SCHEMABATCHCOUNT` or `DATAPUMPSETTINGS_SCHEMABATCH` parameters.

Note:

Database initialization parameter `MAX_DATAPUMP_JOBS_PER_PDB` determines the maximum number of concurrent Oracle Data Pump jobs for each PDB.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_SCHEMABATCHCOUNT = integer`
Default value | There is no default value
Range of values | An integer equal to or less than database initialization parameter `MAX_DATAPUMP_JOBS_PER_PDB`
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_SRC` phase is `COMPLETED`

### F.42 DATAPUMPSETTINGS_SCHEMABATCH-LIST_ELEMENT_NUMBER

Specifies which schemas are batched together to be migrated in parallel.

When `DATAPUMPSETTINGS_JOBMODE=SCHEMA` you can specify which schemas are migrated together in parallel as a batch. Increment the -LIST_ELEMENT_NUMBER value to differentiate the batches.

In this example there are two batches, each containing two schemas that are migrated in parallel.

`DATAPUMPSETTINGS_SCHEMABATCH-1=n1,n2`

`DATAPUMPSETTINGS_SCHEMABATCH-2=n3,n4`

`DATAPUMPSETTINGS_SCHEMABATCH` is mutually exclusive with the `DATAPUMPSETTINGS_SCHEMABATCHCOUNT` parameter.

Note:

Database initialization parameter `MAX_DATAPUMP_JOBS_PER_PDB` determines the maximum number of concurrent Oracle Data Pump jobs for each PDB.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_SCHEMABATCH-LIST_ELEMENT_NUMBER = `list of schemas``
Default value | There is no default value.
Range of values | LIST_ELEMENT_NUMBER must be a unique integer value for each batch specified `list of schemas` must be a comma-separated list of schemas
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_SRC` phase is `COMPLETED`

### F.43 DATAPUMPSETTINGS_SKIPDEFAULTTRANSFORM

Skips default transform parameters.

Set this property to `TRUE` to avoid all internal Zero Downtime Migration transform defaults.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_SKIPDEFAULTTRANSFORM = [TRUE | FALSE]`
Default value | `FALSE`
Valid values | `TRUE` enables this parameter `FALSE` disables this parameter
Required | No
Modifiable on Resume | No

### F.44 DATAPUMPSETTINGS_TEXTINDEX_METHOD

Controls the population of TEXT INDEXes during the import process and improves the performance of the import operation.

Set this property to `NOPOPULATE` to not populate the `TEXT_INDEX`es during the Data Pump import.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_TEXTINDEX_METHOD = [NOPOPULATE]`
Default value | There is no default value
Valid values | `NOPOPULATE`
Required | No
Modifiable on Resume | No

### F.45 DATAPUMPSETTINGS_TRACELEVEL

Set any trace level for the Data Pump logging using this property.

By default, ZDM adds the tracing level of `1FF0300` (To trace all components). You can enable or disable any tracing by choosing the right tracing level. Refer to Export/Import DataPump Parameter TRACE - How to Diagnose Oracle Data Pumpdoc for the lists all the valid trace levels.

Parameter Relationships

The optional `DATAPUMPSETTINGS_*` parameters let you customize Oracle Data Pump Export and Import jobs.

Property | Description
--- | ---
Syntax | `DATAPUMPSETTINGS_TRACELEVEL = [1FF0300]`
Default value | `1FF0300`
Valid values | A trace level string which contains only hexadecimal characters
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_DATAPUMP_SETTINGS_SRC` phase is COMPLETED.

### F.46 DUMPTRANSFERDETAILS_PUBLICREAD

Specifies if the dump files on NFS are readable for others.

Parameter Relationships

This option allows target database user to read the dumps on the shared path when the dump files are allowed to be read by public.

This helps when the user accessing source database server is not allowed to change the group ownership on dumps on the shared path.

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_PUBLICREAD = {TRUE | FALSE}`
Default value | `FALSE`
Range of values | `TRUE`: Dump files on NFS are readable by public. `FALSE`: Dump files on NFS are not readable by public.
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.47 DUMPTRANSFERDETAILS_PARALLELCOUNT

Specifies the maximum number of Export dump files to transfer to Object Storage or remote node in parallel.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_PARALLELCOUNT = integer`
Default value | 3
Range of values | This parameter accepts integer values
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.48 DUMPTRANSFERDETAILS_RETRYCOUNT

Specifies the number of times to retry upload or transfer of dump failure.

Intermittent network failures observed during the transfer of Data Pump dumps can mitigated by setting the `DUMPTRANSFERDETAILS_RETRYCOUNT` parameter.

Parameter Relationships

The `DUMPTRANSFERDETAILS` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_RETRYCOUNT = integer`
Default value | 3
Range of values | This parameter accepts integer values
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.49 DUMPTRANSFERDETAILS_RSYNCAVAILABLE

Specifies that the transfer dump files are using the Linux rsync utility.

Ensure rsync is installed in both source and target servers. Oracle Exadata does not ship with rsync, refer to MOS Doc ID 1556257.1 for details. ZDM defaults to scp command for transfer.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_RSYNCAVAILABLE = {TRUE | FALSE`
Default value | `FALSE`
Range of values | `TRUE` - transfer dump files are using the Linux rsync utility `FALSE` - not using rsync
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.50 DUMPTRANSFERDETAILS_S3BUCKET_ACCESSKEY

Specifies the access key of the Amazon Simple Storage Service (Amazon S3) bucket.

When you set `DATA_TRANSFER_MEDIUM=AMAZON3` to migrate an Amazon Web Services RDS Oracle database to Oracle Autonomous AI Database using an S3 bucket, you must also set the `DUMPTRANSFERDETAILS_S3BUCKET_*` parameters.

See Migrating from Amazon Web Services RDS to Oracle Autonomous AI Database for details.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_S3BUCKET_ACCESSKEY = s3_bucket_access_key`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.51 DUMPTRANSFERDETAILS_S3BUCKET_NAME

Specifies the name of the Amazon Simple Storage Service (Amazon S3) bucket.

When you set `DATA_TRANSFER_MEDIUM=AMAZON3` to migrate an Amazon Web Services RDS Oracle database to Oracle Autonomous AI Database using an S3 bucket, you must also set the `DUMPTRANSFERDETAILS_S3BUCKET_*` parameters.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_S3BUCKET_NAME = s3_bucket_name`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.52 DUMPTRANSFERDETAILS_S3BUCKET_REGION

Specifies the region of the Amazon Simple Storage Service (Amazon S3) bucket.

When you set `DATA_TRANSFER_MEDIUM=AMAZON3` to migrate an Amazon Web Services RDS Oracle database to Oracle Autonomous AI Database using an S3 bucket, you must also set the `DUMPTRANSFERDETAILS_S3BUCKET_*` parameters.

See Migrating from Amazon Web Services RDS to Oracle Autonomous AI Database for details.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_S3BUCKET_REGION = s3_bucket_region`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.53 DUMPTRANSFERDETAILS_SHAREDSTORAGE_NAME

Specifies the name of the exported filesystem to be specified for mount in Autonomous Database.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SHAREDSTORAGE_NAME` `= name`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is COMPLETED

### F.54 DUMPTRANSFERDETAILS_SHAREDSTORAGE_HOST

Specifies the hostname to access shared path in the Autonomous Database.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SHAREDSTORAGE_HOST` `= name`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is COMPLETED

### F.55 DUMPTRANSFERDETAILS_SHAREDSTORAGE_PATH

Specifies the exported path to be mounted in the Autonomous Database.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SHAREDSTORAGE_PATH` `= name`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is COMPLETED

### F.56 DUMPTRANSFERDETAILS_SHAREDSTORAGE_DETACHFSSPOST

Enable this parameter if you want to retain FSS which is attached by the workflow.

Parameter Relationships

If File Storage Service (FSS) is used as DATA_TRANSFER_MEDIUM for migrating to ADB, then ZDM auto-mounts the FSS if it is not already mounted.

However, now ZDM unmounts the attached FSS mounted by ZDM and you have an option to retain the FSS attached in both target and source databases post migration.

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SHAREDSTORAGE_DETACHFSSPOST` `{TRUE | FALSE}`
Default value | `TRUE`
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is COMPLETED

### F.57 DUMPTRANSFERDETAILS_SOURCE_OCIHOME

Specifies the Oracle Cloud OCI-CLI Binary path.

Parameter Relationships

The `DUMPTRANSFERDETAILS_SOURCE_*` parameters specify details to upload the Dump files from source node Data Pump dump location to Oracle Cloud Object Storage.

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SOURCE_OCIHOME = path`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.58 DUMPTRANSFERDETAILS_SOURCE_PARTSIZEMB

Specifies the part size in MB for chunked transfer.

Parameter Relationships

The `DUMPTRANSFERDETAILS_SOURCE_*` parameters specify details to upload the Dump files from source node Data Pump dump location to Oracle Cloud Object Storage.

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SOURCE_PARTSIZEMB = integer`
Default value | `128`
Range of values | An integer value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.59 DUMPTRANSFERDETAILS_SOURCE_NOSSHUPLOADMETHOD

Specifies the method to use no-ssh upload.

Parameter Relationships

When value of this parameter is `HTTPS`, then `ociWalletLoc` is required to be a valid path.

For the default method, value of this parameter is `NONE`. Data is uploaded to OSS securely by using Curl or OCI CLI.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SOURCE_NOSSHUPLOADMETHOD = <Specify the method to use no-ssh upload details.>`
Default value | `NONE`
Required | No

### F.60 DUMPTRANSFERDETAILS_SOURCE_OCIWALLETLOC

Specifies the directory path of the OCI SSL wallet location on the source database server node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_SOURCE_OCIWALLETLOC` parameter specifies the OCI wallet location in the respective database servers.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SOURCE_OCIWALLETLOC = < Directory path for OCI SSL wallet location on the source database server node.>`
Default value | `None`
Required | No

### F.61 DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_DUMPDIRPATH

Specifies the absolute path of the directory to copy or upload dump files.

The `DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_*` parameters are configured when you use a standalone server as transfer server.

Transfer dump files using Oracle Cloud OCI-CLI or curl, or copy to or from a node other than the database server.

This option can be leveraged for cases where OCI CLI is installed and configured in a specific node per data center and the node has the Data Pump export or import directory path shared with it. This avoids the requirement of installing OCI CLI on the database node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node. Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

The `DUMPTRANSFERDETAILS_SOURCE_*` parameters specify details to upload the Dump files from source node Data Pump dump location to Oracle Cloud Object Storage.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_DUMPDIRPATH = path`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.62 DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_HOST

Specifies the dump transfer node host name.

The `DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_*` parameters are configured when you use a standalone server as transfer server.

Transfer dump files using Oracle Cloud OCI-CLI or curl, or copy to or from a node other than the database server.

This option can be leveraged for cases where OCI CLI is installed and configured in a specific node per data center and the node has the Data Pump export or import directory path shared with it. This avoids the requirement of installing OCI CLI on the database node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node. Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

The `DUMPTRANSFERDETAILS_SOURCE_*` parameters specify details to upload the Dump files from source node Data Pump dump location to Oracle Cloud Object Storage.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_HOST = host_name`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.63 DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_SUDOPATH

Specifies the Sudo path on the dump transfer node.

The `DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_*` parameters are configured when you use a standalone server as transfer server.

Transfer dump files using Oracle Cloud OCI-CLI or curl, or copy to or from a node other than the database server.

This option can be leveraged for cases where OCI CLI is installed and configured in a specific node per data center and the node has the Data Pump export or import directory path shared with it. This avoids the requirement of installing OCI CLI on the database node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node. Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

The `DUMPTRANSFERDETAILS_SOURCE_*` parameters specify details to upload the Dump files from source node Data Pump dump location to Oracle Cloud Object Storage.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_SUDOPATH = path`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.64 DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_USER

Specifies the user allowed to execute OCI CLI in the dump transfer node.

The `DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_*` parameters are configured when you use a standalone server as transfer server.

Transfer dump files using Oracle Cloud OCI-CLI or curl, or copy to or from a node other than the database server.

This option can be leveraged for cases where OCI CLI is installed and configured in a specific node per data center and the node has the Data Pump export or import directory path shared with it. This avoids the requirement of installing OCI CLI on the database node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

The `DUMPTRANSFERDETAILS_SOURCE_*` parameters specify details to upload the Dump files from source node Data Pump dump location to Oracle Cloud Object Storage.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_USER = user`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.65 DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_USERKEY

Specifies the user's authentication key.

The `DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_*` parameters are configured when you use a standalone server as transfer server.

Transfer dump files using Oracle Cloud OCI-CLI or curl, or copy to or from a node other than the database server.

This option can be leveraged for cases where OCI CLI is installed and configured in a specific node per data center and the node has the Data Pump export or import directory path shared with it. This avoids the requirement of installing OCI CLI on the database node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node. Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

The `DUMPTRANSFERDETAILS_SOURCE_*` parameters specify details to upload the Dump files from source node Data Pump dump location to Oracle Cloud Object Storage.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_USERKEY = user_auth_key`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.66 DUMPTRANSFERDETAILS_SOURCE_USEOCICLI

Indicates that transfer dump files use Oracle Cloud Infrastructure command line interface (CLI).

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

The `DUMPTRANSFERDETAILS_SOURCE_*` parameters specify details to upload the Dump files from source node Data Pump dump location to Oracle Cloud Object Storage.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SOURCE_USEOCICLI = {TRUE | FALSE}`
Default value | `FALSE`
Range of values | `TRUE` or `FALSE`
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.67 DUMPTRANSFERDETAILS_SRCPROXY_HOSTNAME

Specifies the proxy host name to be used on the source database server node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node. Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

Property | Description
--- | ---
Syntax | DUMPTRANSFERDETAILS_SRCPROXY_HOSTNAME `= hostname`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.68 DUMPTRANSFERDETAILS_SRCPROXY_PORT

Specifies the proxy port to be used on the source database server node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node. Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SRCPROXY_PORT` `= port number`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.69 DUMPTRANSFERDETAILS_SRCPROXY_PROTOCOL

Specifies whether `HTTP` or `HTTPS` proxy protocol is to be used on the source database server node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node. Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_SRCPROXY_PROTOCOL = `HTTP` or `HTTPS``
Default value | ``HTTP``
Required | No
Modifiable on Resume | Yes

### F.70 DUMPTRANSFERDETAILS_TARGET_OCIHOME

Specifies the Oracle Cloud Infrastructure command line interface (CLI) Binary path.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

The `DUMPTRANSFERDETAILS_TARGET_*` parameters specify details to download the Dump files to the target node Data Pump dump location from Oracle Cloud Object Storage.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TARGET_OCIHOME = path`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.71 DUMPTRANSFERDETAILS_TARGET_NOSSHUPLOADMETHOD

Specifies the method to use no-ssh upload. When HTTPS is used, `ociWalletLoc` is required to be a valid path.

Parameter Relationships

When value of the parameter is `HTTPS`, then `ociWalletLoc` is required to be a valid path. For default method, when value of the parameter is `NONE`, data is uploaded to OSS securely using Curl or OCI CLI.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TARGET_NOSSHUPLOADMETHOD = <Specify the method to use no-ssh upload details.>`
Default value | `NONE`
Required | No

### F.72 DUMPTRANSFERDETAILS_TARGET_OCIWALLETLOC

Specifies the directory path of the OCI SSL wallet location on the target database server node.

Parameter Relationships

Specifies the OCI wallet location in the respective database server.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TARGET_OCIWALLETLOC = < Directory path for OCI SSL wallet location on the target database server node.>`
Default value | `None`
Required | No

### F.73 DUMPTRANSFERDETAILS_TARGET_PARTSIZEMB

Specifies the part size in MB for chunked transfer.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

The `DUMPTRANSFERDETAILS_TARGET_*` parameters specify details to download the Dump files to the target node Data Pump dump location from Oracle Cloud Object Storage.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TARGET_PARTSIZEMB = integer`
Default value | `128`
Range of values | An integer value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.74 DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_DUMPDIRPATH

Specifies the absolute path of the directory to copy or upload dump files.

The `DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_*` parameters are configured when you use a standalone server as transfer server.

Transfer dump files using the OCI CLI or curl, or copy to or from a node other than the database server.

This option can be leveraged for cases where OCI CLI is installed and configured in a specific node per data center and the node has the Data Pump export or import directory path shared with it. This avoids the requirement of installing OCI CLI on the database node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through Oracle Cloud Infrastructure command line interface (CLI) or Curl.

The `DUMPTRANSFERDETAILS_TARGET_*` parameters specify details to download the Dump files to the target node Data Pump dump location from Oracle Cloud Object Storage.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_DUMPDIRPATH = path`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.75 DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_HOST

Specifies the dump transfer node host name.

The `DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_*` parameters are configured when you use a standalone server as transfer server.

Transfer dump files using OCI CLI or curl, or copy to or from a node other than the database server.

This option can be leveraged for cases where OCI CLI is installed and configured in a specific node per data center and the node has the Data Pump export or import directory path shared with it. This avoids the requirement of installing OCI CLI on the database node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through Oracle Cloud Infrastructure command line interface (CLI) or Curl.

The `DUMPTRANSFERDETAILS_TARGET_*` parameters specify details to download the Dump files to the target node Data Pump dump location from Oracle Cloud Object Storage.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_HOST = host_name`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.76 DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_SUDOPATH

Specifies the Sudo path on the dump transfer node.

The `DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_*` parameters are configured when you use a standalone server as transfer server.

Transfer dump files using OCI CLI or curl, or copy to or from a node other than the database server.

This option can be leveraged for cases where OCI CLI is installed and configured in a specific node per data center and the node has the Data Pump export or import directory path shared with it. This avoids the requirement of installing OCI CLI on the database node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through Oracle Cloud Infrastructure command line interface (CLI) or Curl.

The `DUMPTRANSFERDETAILS_TARGET_*` parameters specify details to download the Dump files to the target node Data Pump dump location from Oracle Cloud Object Storage.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_SUDOPATH = path`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.77 DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_USER

Specifies the user allowed to execute OCI CLI in the dump transfer node.

The `DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_*` parameters are configured when you use a standalone server as transfer server.

Transfer dump files using OCI CLI or curl, or copy to or from a node other than the database server.

This option can be leveraged for cases where OCI CLI is installed and configured in a specific node per data center and the node has the Data Pump export or import directory path shared with it. This avoids the requirement of installing OCI CLI on the database node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node. Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through Oracle Cloud Infrastructure command line interface (CLI) or Curl.

The `DUMPTRANSFERDETAILS_TARGET_*` parameters specify details to download the Dump files to the target node Data Pump dump location from Oracle Cloud Object Storage.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_USER = user`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.78 DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_USERKEY

Specifies the user's authentication key.

The `DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_*` parameters are configured when you use a standalone server as transfer server.

Transfer dump files using OCI CLI or curl, or copy to or from a node other than the database server.

This option can be leveraged for cases where OCI CLI is installed and configured in a specific node per data center and the node has the Data Pump export or import directory path shared with it. This avoids the requirement of installing OCI CLI on the database node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through Oracle Cloud Infrastructure command line interface (CLI) or Curl.

The `DUMPTRANSFERDETAILS_TARGET_*` parameters specify details to download the Dump files to the target node Data Pump dump location from Oracle Cloud Object Storage.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_USERKEY = user_auth_key`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.79 DUMPTRANSFERDETAILS_TARGET_USEOCICLI

Indicates that transfer dump files use Oracle Cloud Infrastructure command line interface (CLI).

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

The `DUMPTRANSFERDETAILS_TARGET_*` parameters specify details to download the Dump files to the target node Data Pump dump location from Oracle Cloud Object Storage.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TARGET_USEOCICLI = {TRUE | FALSE}`
Default value | `FALSE`
Range of values | `TRUE` or `FALSE`
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.80 DUMPTRANSFERDETAILS_TRANSFERTARGET_DUMPDIRPATH

Specifies the absolute path of the directory to copy or upload dump files.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

The `DUMPTRANSFERDETAILS_TRANSFERTARGET_*` parameters specify details for the target node to copy the Dump files from source node Data Pump dump location or transfer node directory path specified. Default target database host.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TRANSFERTARGET_DUMPDIRPATH = path`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.81 DUMPTRANSFERDETAILS_TRANSFERTARGET_HOST

`DUMPTRANSFERDETAILS_TRANSFERTARGET_HOST` specifies the dump transfer node host name.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

The `DUMPTRANSFERDETAILS_TRANSFERTARGET_*` parameters specify details for the target node to copy the Dump files from source node Data Pump dump location or transfer node directory path specified. Default target database host.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TRANSFERTARGET_HOST = host_name`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.82 DUMPTRANSFERDETAILS_TRANSFERTARGET_SUDOPATH

Specifies the Sudo path on the dump transfer node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

The `DUMPTRANSFERDETAILS_TRANSFERTARGET_*` parameters specify details for the target node to copy the Dump files from source node Data Pump dump location or transfer node directory path specified. Default target database host.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TRANSFERTARGET_SUDOPATH = path`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.83 DUMPTRANSFERDETAILS_TRANSFERTARGET_USER

Specifies the host user name that has write permission to the indicated dump storage path.

The user specified in `DUMPTRANSFERDETAILS_TRANSFERTARGET_USER` should be allowed to

- Execute OCI CLI in the specified host to download the dumps from the Object Storage bucket if `DATA_TRANSFER_MEDIUM=OSS`

- Copy the dump files from the source node to the target host specified if `DATA_TRANSFER_MEDIUM=COPY`.

See Configuring the Transfer Medium and Specifying Transfer Nodes for more information about configuring the dump transfer details parameters.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

The `DUMPTRANSFERDETAILS_TRANSFERTARGET_*` parameters specify details for the target node to copy the Dump files from source node Data Pump dump location or transfer node directory path specified. Default target database host.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TRANSFERTARGET_USER = host_username`
Default value | `There is no default value`
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.84 DUMPTRANSFERDETAILS_TRANSFERTARGET_USERKEY

Specifies the user's authentication key.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node.

Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

The `DUMPTRANSFERDETAILS_TRANSFERTARGET_*` parameters specify details for the target node to copy the Dump files from source node Data Pump dump location or transfer node directory path specified. Default target database host.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TRANSFERTARGET_USERKEY = user_auth_key`
Default value | No default value
Range of values | A string value is expected
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is `COMPLETED`

### F.85 DUMPTRANSFERDETAILS_TGTPROXY_HOSTNAME

Specifies the proxy host name to be used on the target database server node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node. Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TGTPROXY_HOSTNAME` `= hostname`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is COMPLETED

### F.86 DUMPTRANSFERDETAILS_TGTPROXY_PORT

Specifies proxy port number to be used on the target database server node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node. Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TGTPROXY_PORT` `=port number`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_TRANSFER_DUMPS_SRC` phase is COMPLETED

### F.87 DUMPTRANSFERDETAILS_TGTPROXY_PROTOCOL

Specifies whether `HTTP` or `HTTPS` proxy protocol is to be used on the target database server node.

Parameter Relationships

The `DUMPTRANSFERDETAILS_*` parameters specify details to transfer dumps from the source node to the target node. Supported modes of transfer are OSS and secure copy. Upload of dumps to OSS can be either through OCI CLI or Curl.

Property | Description
--- | ---
Syntax | `DUMPTRANSFERDETAILS_TGTPROXY_PROTOCOL = HTTP or `HTTPS``
Default value | `HTTP`
Required | No
Modifiable on Resume | Yes

### F.88 EXCLUDEOBJECTS-LIST_ELEMENT_NUMBER

Specifies database objects to exclude from migration.

To exclude multiple objects, increment the integer appended to the parameter name, as shown in the examples below.

`EXCLUDEOBJECTS-1=owner:ownerValue1, objectName:objectNameValue1, objectType:objectTypeValue1`

`EXCLUDEOBJECTS-2=owner:ownerValue2, objectName:objectNameValue2, objectType:objectTypeValue2`

See Selecting Objects for Migration for more information about using `EXCLUDEOBJECTS`.

Property | Description
--- | ---
Syntax | `EXCLUDEOBJECTS-LIST_ELEMENT_NUMBER = owner:ownerValue, objectName:objectNameValue, objectType:objectTypeValue`
Default value | There is no default value.
Range of values | An entry specifying the owner, object name, and object type is expected, as shown in the examples above.
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_EXPORT_SRC` phase is `COMPLETED`, or until `ZDM_DATAPUMP_IMPORT_TGT` phase when using `DATA_TRANSFER_MEDIUM=DBLINK`.

### F.89 FIXINVALIDS_ENABLED

Specifies if fixing invalid objects is enabled.

Enabling this feature allows ZDM to attempt to fix the invalids post a successful import. ZDM attempts to fix invalids twice and any invalids found after that are reported as warning for you to review and handle.

Note:

Ensure the database user specified to connect to the target database has execute permission on `SYS.UTL_RECOMP`.

Migration can result in invalid schema objects. Typically, invalid objects fix themselves as they are accessed or run. However, Oracle recommends that invalid objects are recompiled in the database as part of the Zero Downtime Migration migration job so that issues with invalid objects, and any required dependencies, are resolved before users encounter these invalid objects.

Parameter Relationships

The optional `FIXINVALIDS_*` parameters let you customize fixing invalids.

Property | Description
--- | ---
Syntax | `FIXINVALIDS_ENABLED = {TRUE | FALSE}`
Default value | `TRUE`
Range of values | `TRUE` = fix invalid objects `FALSE` = do not fix invalid objects
Required | No
Modifiable on Resume | Until `ZDM_POST_DATAPUMP_TGT` phase is `COMPLETED`.

### F.90 FIXINVALIDS_BYSCHEMA

Indicates fixing invalids to be performed at schema parallelism.

Parameter Relationships

The optional `FIXINVALIDS_*` parameters let you customize fixing invalids.

Property | Description
--- | ---
Syntax | `FIXINVALIDS_BYSCHEMA = {TRUE | FALSE}`
Default value | `TRUE`
Range of values | `TRUE` = fix invalid objects `FALSE` = do not fix invalid objects
Required | No
Modifiable on Resume | Until `ZDM_POST_DATAPUMP_TGT` phase is `COMPLETED`.

### F.91 FIXINVALIDS_PARALLELCOUNT

Indicates the minimum number of parallel counts for fixing invalids.

Defines number of recompile threads to run in parallel. Parallel recompilation can use multiple CPUs to reduce the time taken to recompile invalid objects. This uses the `RECOMP_PARALLEL` procedure.

Note:

The process of recompiling an invalid object writes a significant amount of data to system tables and is quite I/O intensive. A slow disk system may be a significant bottleneck and limit speedups available from a higher degree of parallelism.

Parameter Relationships

The optional `FIXINVALIDS_*` parameters let you customize fixing invalids.

Property | Description
--- | ---
Syntax | `FIXINVALIDS_PARALLELCOUNT = integer`
Default value | `Null`
Range of values |
Required | No
Modifiable on Resume | Until `ZDM_POST_DATAPUMP_TGT` phase is `COMPLETED`.

### F.92 FIXINVALIDS_RETRYCOUNT

Indicates the minimum number of retry attempts for fixing invalids.

Parameter Relationships

The optional `FIXINVALIDS_*` parameters let you customize fixing invalids.

Property | Description
--- | ---
Syntax | `FIXINVALIDS_RETRYCOUNT = integer`
Default value | `2`
Range of values |
Required | No
Modifiable on Resume | Until `ZDM_POST_DATAPUMP_TGT` phase is `COMPLETED`.

### F.93 GOLDENGATEHUB_ALLOWSELFSIGNEDCERTIFICATE

Indicates whether Oracle GoldenGate server's self-signed HTTPS certificate should be accepted to avoid the `sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target` error, similar to the `curl --insecure` command.

Parameter Relationships

For online logical migration, you must set the `GOLDENGATEHUB_*` parameters to provide Zero Downtime Migration with details about Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATEHUB_ALLOWSELFSIGNEDCERTIFICATE = {TRUE | FALSE}`
Default value | `FALSE`
Range of values | `TRUE` `FALSE`
Required | No
Modifiable on Resume | Yes

### F.94 GOLDENGATEHUB_ADMINUSERNAME

Specifies the Oracle GoldenGate deployment's administrator username.

Parameter Relationships

For an Oracle GoldenGate deployment provisioned using Oracle Cloud Marketplace image, retrieve the `oggadmin` username and password credentials in the `/home/opc/ogg-credentials.json` file on the Oracle Cloud compute instance where Oracle GoldenGate is running. For Oracle GoldenGate deployment running in a docker container, obtain the `oggadmin` username and password credentials as indicated at Administrative Account Password.

For online logical migration, you must set the `GOLDENGATEHUB_*` parameters to provide Zero Downtime Migration with details about Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATEHUB_ADMINUSERNAME = user_name`
Default value | There is no default value
Range of values | Oracle GoldenGate hub's administrator user name
Required | No* *Required for online logical migration
Modifiable on Resume | Until `ZDM_PREPARE_GG_HUB` phase is `COMPLETED`.

### F.95 GOLDENGATEHUB_COMPUTEID

Specifies the Oracle Cloud identifier of the VM.

Parameter Relationships

For online logical migration, you must set the `GOLDENGATEHUB_*` parameters to provide Zero Downtime Migration with details about Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATEHUB_COMPUTEID = vm_identifier`
Default value | There is no default value
Range of values | Oracle Cloud identifier of the VM
Required | No* *Required for online logical migration
Modifiable on Resume | Until `ZDM_PREPARE_GG_HUB` phase is `COMPLETED`.

### F.96 GOLDENGATEHUB_SOURCEDEPLOYMENTNAME

Specifies the name of the GoldenGate Microservices deployment to operate on the source database.

Parameter Relationships

For online logical migrations, you must set the `GOLDENGATEHUB` parameters to provide Zero Downtime Migration with details about Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATEHUB_SOURCEDEPLOYMENTNAME = GG_microservices_deployment_name`
Default value | There is no default value
Range of values | Name of the GoldenGate Microservices deployment to operate on the source database
Required | No* *Required for online logical migration
Modifiable on Resume | Until `ZDM_PREPARE_GG_HUB` phase is `COMPLETED`.

### F.97 GOLDENGATEHUB_TARGETDEPLOYMENTNAME

Specifies the name of the GoldenGate Microservices deployment to operate on the target database.

Parameter Relationships

For online logical migrations, you must set the `GOLDENGATEHUB` parameters to provide Zero Downtime Migration with details about Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATEHUB_TARGETDEPLOYMENTNAME = GG_microservices_deployment_name`
Default value | There is no default value
Range of values | Name of the GoldenGate Microservices deployment to operate on the target database
Required | No* *Required for online logical migration
Modifiable on Resume | Until `ZDM_PREPARE_GG_HUB` phase is `COMPLETED`.

### F.98 GOLDENGATEHUB_URL

Specifies the Oracle GoldenGate hub's REST endpoint.

Parameter Relationships

For example, `GOLDENGATEHUB_URL=https://<FQDN or IP address of server hosting GoldenGate deployment>`. For more information, see, Network.

For online logical migrations, you must set the `GOLDENGATEHUB` parameters to provide Zero Downtime Migration with details about Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATEHUB_URL = GG_hub_rest_endpoint`
Default value | There is no default value
Range of values | Oracle GoldenGate hub's REST endpoint
Required | No* *Required for online logical migration
Modifiable on Resume | Until `ZDM_PREPARE_GG_HUB` phase is `COMPLETED`.

### F.99 GOLDENGATESETTINGS_ACCEPTABLELAG

Specifies GoldenGate end-to-end latency lag time

Zero Downtime Migration monitors GoldenGate end-to-end latency until the lag time is lower than the value (in seconds) specified in `GOLDENGATESETTINGS_ACCEPTABLELAG`.

Parameter Relationships

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_ACCEPTABLELAG = seconds`
Default value | 30 seconds
Required | No
Required | No
Modifiable on Resume | Until `ZDM_MONITOR_GG_LAG` phase is `COMPLETED`.

### F.100 GOLDENGATESETTINGS_EXTRACT_PERFORMANCEPROFILE

Tunes Oracle GoldenGate Integrated Capture.

Use this setting to automatically configure relevant parameters to achieve the desired throughput and latency.

Parameter Relationships

The `GOLDENGATESETTINGS_EXTRACT_*` parameters define settings for the Integrated Extract process.

Only one Extract can be configured.

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_EXTRACT_PERFORMANCEPROFILE = [HIGH | MEDIUM | LOW_RES]`
Default value | `HIGH`
Valid values | `HIGH`, `MEDIUM`, `LOW_RES`
Required | No
Modifiable on Resume | Until `ZDM_CREATE_GG_EXTRACT_SRC` phase is `COMPLETED`.

### F.101 GOLDENGATESETTINGS_EXTRACT_WARNLONGTRANS_CHECKINTERVAL

Specifies the frequency in seconds with which Oracle GoldenGate checks for long-running transactions.

Parameter Relationships

`GOLDENGATESETTINGS_EXTRACT_WARNLONGTRANS_*` parameters specify a length of time in seconds that a transaction can be open before Extract generates a warning message that the transaction is long-running.

The `GOLDENGATESETTINGS_EXTRACT_*` parameters define settings for the Integrated Extract process.

Only one Extract can be configured.

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_EXTRACT_WARNLONGTRANS_CHECKINTERVAL = integer`
Default value | There is no default value
Valid values | An integer value is expected
Required | No
Modifiable on Resume | Until `ZDM_CREATE_GG_EXTRACT_SRC` phase is `COMPLETED`.

### F.102 GOLDENGATESETTINGS_EXTRACT_WARNLONGTRANS_DURATION

Specifies a length of time in seconds that a transaction can be open before the GoldenGate Extract process generates a warning message that the transaction is long-running.

Parameter Relationships

`GOLDENGATESETTINGS_EXTRACT_WARNLONGTRANS_*` parameters specify a length of time in seconds that a transaction can be open before Extract generates a warning message that the transaction is long-running.

The `GOLDENGATESETTINGS_EXTRACT_*` parameters define settings for the Integrated Extract process.

Only one Extract can be configured.

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_EXTRACT_WARNLONGTRANS_DURATION = integer`
Default value | There is no default value
Valid values | An integer value is expected
Required | No
Modifiable on Resume | Until `ZDM_CREATE_GG_EXTRACT_SRC` phase is `COMPLETED`.

### F.103 GOLDENGATESETTINGS_EXTRACT_EXCLUDEOBJECTS

Specifies the objects that will be migrated during target database instantiation (initial load). However, the specified objects will not be captured by Oracle GoldenGate Extract. Instead, the specified objects will be reloaded during switchover when there is no active workload on the source database.

Following are the allowed values and their format:

    GOLDENGATESETTINGS_EXTRACT_EXCLUDEOBJECTS-1=<object details>

    GOLDENGATESETTINGS_EXTRACT_EXCLUDEOBJECTS-n=[owner:<ownerValue>, objectName:<objectNameValue>, objectType:<objectTypeValue>]

Example: Two entries

`GOLDENGATESETTINGS_EXTRACT_EXCLUDEOBJECTS-1=owner:<ownerValue1st>, objectName:<objectNameValue1st>, objectType:<objectTypeValue1st>`

`GOLDENGATESETTINGS_EXTRACT_EXCLUDEOBJECTS-2=owner:<ownerValue2nd>, objectName:<objectNameValue2nd>, objectType:<objectTypeValue2nd>`

Note:

You can specify the parameter only when starting a job.

You cannot modify when resuming or modifying a job.

Do not specify the tables already being excluded by Oracle GoldenGate `reload_query_advisor` using this parameter; otherwise an input validation error will occur.

The specified tables are instantiated in the target database during initial load using Data Pump. Subsequently, during switchover, ZDM reloads the tables only if they have been modified in source database after initial load.

You can skip Oracle GoldenGate `reload_query_advisor` by setting the parameter `GOLDENGATESETTINGS_SKIPRELOADQUERYADVISOR` to `TRUE`.

Parameter Relationships

The `GOLDENGATESETTINGS_EXTRACT_*` parameters define settings for the Integrated Extract process. Only one Extract can be configured.

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_EXTRACT_EXCLUDEOBJECTS =`
Default value | There is no default value
Required | No
Modifiable on Resume | No

### F.104 GOLDENGATESETTINGS_REPLICAT_EXCLUDEOBJECTS

Specifies the objects that will be migrated during target database instantiation (initial load). However, the specified objects will not be replicated by Oracle GoldenGate Replicat. Instead, the specified objects will be reloaded during switchover when there is no active workload on source database.

Following are the allowed values and their format:

`GOLDENGATESETTINGS_REPLICAT_EXCLUDEOBJECTS-1=<object details>`

`GOLDENGATESETTINGS_REPLICAT_EXCLUDEOBJECTS-n=[owner:<ownerValue>, objectName:<objectNameValue>, objectType:<objectTypeValue>]`

Example: Two entries

`GOLDENGATESETTINGS_REPLICAT_EXCLUDEOBJECTS-1=owner:<ownerValue1st>, objectName:<objectNameValue1st>, objectType:<objectTypeValue1st>`

`GOLDENGATESETTINGS_REPLICAT_EXCLUDEOBJECTS-2=owner:<ownerValue2nd>, objectName:<objectNameValue2nd>, objectType:<objectTypeValue2nd>`

Note:

You cannot specify the parameter when you start a job.

You can modify the parameter when you resume or modify a job.

You can modify the parameter only to add tables to the exclusion list.

Do not specify the tables already being excluded by Oracle GoldenGate `reload_query_advisor` using this parameter; otherwise an input validation error will occur.

If Replicat is online: ZDM will stop Replicat, update parameters, and restart Replicat.

The `modify` job accepts updated response file containing parameters `GOLDENGATESETTINGS_REPLICAT_EXCLUDEOBJECTS` and/or `GOLDENGATESETTINGS_EXCLUDERELOAD`.

Parameter Relationships

The `GOLDENGATESETTINGS_EXTRACT_*` parameters define settings for the Integrated Extract process. Only one Extract can be configured.

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_REPLICAT_EXCLUDEOBJECTS =`
Default value | There is no default value
Required | No
Modifiable on Resume | Until ZDM_PREPARE_SWITCHOVER_APP phase is COMPLETED.

### F.105 GOLDENGATESETTINGS_EXCLUDERELOAD

Specifies the database objects to be excluded from reload during switchover.

By default, tables excluded from Extract or Replicat will be reloaded during switchover only if the tables have been modified in source database since initial load. To override this default behavior, database objects specified in this parameter are excluded from reloading during the switchover regardless of modifications.

Following are the allowed values and their format:

`GOLDENGATESETTINGS_EXCLUDERELOAD-1=<object details>``GOLDENGATESETTINGS_EXCLUDERELOAD-n=[owner:<ownerValue>, objectName:<objectNameValue>, objectType:<objectTypeValue>]`

Example: Two entries

`GOLDENGATESETTINGS_EXCLUDERELOAD-1=owner:<ownerValue1st>, objectName:<objectNameValue1st>, objectType:<objectTypeValue1st>``GOLDENGATESETTINGS_EXCLUDERELOAD-2=owner:<ownerValue2nd>, objectName:<objectNameValue2nd>, objectType:<objectTypeValue2nd>`

Parameter Relationships

You can specify tables identified by Oracle GoldenGate `reload_query_advisor` or tables included in lists `GOLDENGATESETTINGS_EXTRACT_EXCLUDEOBJECTS`, `GOLDENGATESETTINGS_REPLICAT_EXCLUDEOBJECTS`.

The `modify` job accepts updated response file containing parameters `GOLDENGATESETTINGS_REPLICAT_EXCLUDEOBJECTS` and/or `GOLDENGATESETTINGS_EXCLUDERELOAD`.

Modify a ZDM job specifying parameter `GOLDENGATESETTINGS_EXCLUDERELOAD` to indicate tables which should not be reloaded during switchover.

The `GOLDENGATESETTINGS_EXTRACT_*` parameters define settings for the Integrated Extract process. Only one Extract can be configured.

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_EXCLUDERELOAD =`
Default value | There is no default value
Required | No
Modifiable on Resume | Until ZDM_PREPARE_SWITCHOVER_APP phase is COMPLETED.

### F.106 GOLDENGATESETTINGS_SKIPRELOADQUERYADVISOR

Specifies if Oracle GoldenGate reload advisor to identify unsupported tables is skipped.

By default, GOLDENGATESETTINGS_SKIPRELOADQUERYADVISOR is FALSE, so Oracle GoldenGate `reload_query_advisor` is executed for source database to identify highly active tables lacking row uniqueness. The results reported by the `reload_query_advisor` are used to exclude source tables from Oracle GoldenGate Extract. Instead, the reported tables will be reloaded during application switchover downtime.
You can override the default behavior to skip Oracle GoldenGate `reload_query_advisor` and instead specify `GOLDENGATESETTINGS_EXTRACT_EXCLUDEOBJECTS` when starting a job or `GOLDENGATESETTINGS_REPLICAT_EXCLUDEOBJECTS` when resuming or modifying a job.

Parameter Relationships

The `GOLDENGATESETTINGS_EXTRACT_*` parameters define settings for the Integrated Extract process. Only one Extract can be configured.

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_EXCLUDERELOAD = TRUE | FALSE`
Default value | `FALSE`
Valid values | TRUE FALSE
Required | No
Modifiable on Resume |

### F.107 GOLDENGATESETTINGS_EXTRACT_PARALLELISM

Specifies the number of processes supporting the database logmining server.

Parameter Relationships

The `GOLDENGATESETTINGS_EXTRACT_*` parameters define settings for the Integrated Extract process. Only one Extract can be configured.

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_EXTRACT_PARALLELISM = integer`
Default value | 2
Valid values | A positive integer value is expected Note: Parallelism greater than 1 is not supported for Oracle Database Standard Edition 2.
Required | No
Modifiable on Resume | Until `ZDM_CREATE_GG_EXTRACT_TGT` phase is `COMPLETED`.

### F.108 GOLDENGATESETTINGS_RELOADUNREPLICATEDOBJECTS

Specifies whether to reload objects that are not supported by Oracle GoldenGate for replication.

Parameter Relationships

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Set this parameter to `TRUE` to reload objects that are not supported by Oracle GoldenGate for replication.

For Online logical migration, ZDM evaluation phase `ZDM_VALIDATE_SRC` queries view `DBA_GOLDENGATE_SUPPORT_MODE` and reports the list of tables with Oracle GoldenGate `support_mode = NONE` or `support_mode = PLSQL` as objects to be excluded for online logical migration.

Set the ZDM parameter GOLDENGATESETTINGS_RELOADUNREPLICATEDOBJECTS to:

- automatically exclude tables with Oracle GoldenGate support_mode = NONE or support_mode = PLSQL for Oracle GoldenGate replication.
- automatically reload tables with Oracle GoldenGate support_mode = NONE or support_mode = PLSQL in target database using Oracle Data Pump during ZDM phase ZDM_RELOAD_PARALLEL_EXPORT_IMPORT during switchover window.

As part of online logical migrations, when value of the `GOLDENGATESETTINGS_RELOADUNREPLICATEDOBJECTS = TRUE`, then the audit trails are also imported during the reload phase `ZDM_RELOAD_PARALLEL_EXPORT_IMPORT`.

When value of the `GOLDENGATESETTINGS_RELOADUNREPLICATEDOBJECTS = TRUE`, then `SOURCEDATABASE_ALLOWTEMPTABLE` is set to `TRUE` by default. If this is unexpected, then you need to set the value of `SOURCEDATABASE_ALLOWTEMPTABLE` to `FALSE`. However, setting it to `FALSE` can lead to Datapump import performance issue.

For more details, see Handling Application Switchover in a Logical Migration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_RELOADUNREPLICATEDOBJECTS = TRUE | FALSE`
Default value | `FALSE`
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_SRC` phase is completed.

### F.109 GOLDENGATESETTINGS_REPLICAT_MAPPARALLELISM

Specifies the number of threads used to read GoldenGate trail files.

Starting with Oracle Zero Downtime Migration 21c (21.4) release, this property is deprecated and will be desupported in a future release. For more information, see GOLDENGATESETTINGS_REPLICAT_PERFORMANCEPROFILE.

Valid for Parallel Replicat.

Parameter Relationships

The `GOLDENGATESETTINGS_REPLICAT_*` parameters define settings for the Parallel Replicat process.

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_REPLICAT_MAPPARALLELISM = integer`
Default value | 4
Valid values | An integer value is expected
Required | No
Modifiable on Resume | Until `ZDM_CREATE_GG_REPLICAT_TGT` phase is `COMPLETED`.

### F.110 GOLDENGATESETTINGS_REPLICAT_MAXAPPLYPARALLELISM

Defines the range in which the GoldenGate Replicat automatically adjusts its apply parallelism.

Starting with Oracle Zero Downtime Migration 21c (21.4) release, this property is deprecated and will be desupported in a future release. For more information, see GOLDENGATESETTINGS_REPLICAT_PERFORMANCEPROFILE.

Valid for Parallel Replicat.

Parameter Relationships

The `GOLDENGATESETTINGS_REPLICAT_*` parameters define settings for the Parallel Replicat process.

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_REPLICAT_MAXAPPLYPARALLELISM = integer`
Default value | 50
Valid values | An integer value is expected
Required | No
Modifiable on Resume | Until `ZDM_CREATE_GG_REPLICAT_TGT` phase is `COMPLETED`.

### F.111 GOLDENGATESETTINGS_REPLICAT_MINAPPLYPARALLELISM

Defines the range in which the GoldenGate Replicat automatically adjusts its apply parallelism.

Starting with Oracle Zero Downtime Migration 21c (21.4) release, this property is deprecated and will be desupported in a future release. For more information, see GOLDENGATESETTINGS_REPLICAT_PERFORMANCEPROFILE.

Valid for Parallel Replicat.

Parameter Relationships

The `GOLDENGATESETTINGS_REPLICAT_*` parameters define settings for the Parallel Replicat process.

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_REPLICAT_MINAPPLYPARALLELISM = integer`
Default value | 4
Valid values | An integer value is expected
Required | No
Modifiable on Resume | Until `ZDM_CREATE_GG_REPLICAT_TGT` phase is `COMPLETED`.

### F.112 GOLDENGATESETTINGS_REPLICAT_PERFORMANCEPROFILE

Tunes GoldenGate Replicat.

Starting with Oracle Zero Downtime Migration 21c (21.4) release, the following properties are deprecated and will be desupported in a future release:

- `GOLDENGATESETTINGS_REPLICAT_MAPPARALLELISM`
- `GOLDENGATESETTINGS_REPLICAT_APPLYPARALLELISM`
- `GOLDENGATESETTINGS_REPLICAT_MAXAPPLYPARALLELISM`
- `GOLDENGATESETTINGS_REPLICAT_MINAPPLYPARALLELISM`

These parameters are replaced by the `GOLDENGATESETTINGS_REPLICAT_PERFORMANCEPROFILE` parameter. If you configure the `GOLDENGATESETTINGS_REPLICAT_PERFORMANCEPROFILE` parameter, then you do not have to configure these deprecated parameters. However, if you do configure these deprecated parameters, then the `GOLDENGATESETTINGS_REPLICAT_PERFORMANCEPROFILE` parameter will not be valid.

Set the performance profile to automatically configure relevant parameters to achieve the desired throughput and latency.

Parameter Relationships

The `GOLDENGATESETTINGS_REPLICAT_*` parameters define settings for simplifying the tuning of GoldenGate Replicat.

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_REPLICAT_PERFORMANCEPROFILE = `HIGH`|`LOW``
Default value | `HIGH`
Valid values | Use `HIGH` when there is no concurrent workload on target database. Use `LOW` when there is concurrent workload on target database. Note: When `HIGH` is set, `Replicat Mappers` = `5` and `Appliers` = `2 * CPU_COUNT` When `LOW` is set, `Replicat Mappers` = `4` and `Appliers` = `CPU_COUNT / 2`
Required | No
Modifiable on Resume | Until `ZDM_CREATE_GG_REPLICAT_TGT` phase is `COMPLETED`.

### F.113 GOLDENGATESETTINGS_REPLICATEDDL

Specifies whether to set Oracle GoldenGate Replicat parameter `GOLDENGATESETTINGS_REPLICATEDDL`.

During the migration period it is recommended to avoid DDL operations. When DDL is replicated, Oracle GoldenGate Replicat serializes data to ensure that there are no locking issues between DML and DDL on the same objects. This can slow down the replication progress.

Parameter Relationships

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_REPLICATEDDL = TRUE | FALSE`
Default value | `FALSE`
Required | No
Modifiable on Resume | Until ZDM_MONITOR_GG_LAG phase is `COMPLETED`.

### F.114 GOLDENGATESETTINGS_RELOADAQOBJECTS

Allows users to specify if AQ objects need to be reloaded post import.

Note:

If you intend to reload AQ, then apply the following there is RDBMS patches for source and target databases:

- Apply the patch for bug 34174611 on source database.
- Apply the patch for Bug 34314402 that addresses table_exists_action for AQ tables on target database.

Ensure that you have applied the respective patches as mentioned above for the source and target databases before setting GOLDENGATESETTINGS_RELOADAQOBJECTS=TRUE.

When GOLDENGATESETTINGS_RELOADAQOBJECTS = TRUE, ZDM attempts to reload the AQ objects as part of the ZDM_RELOAD_PARALLEL_EXPORT_IMPORT phase post the initial import and replication. When GOLDENGATESETTINGS_RELOADAQOBJECTS = FALSE, ZDM assumes that the source database does not contain any AQ objects which should be reloaded.

Parameter Relationships

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_RELOADAQOBJECTS = TRUE | FALSE`
Default value | `FALSE`
Required | No
Modifiable on Resume | Until ZDM_CREATE_GG_REPLICAT_TGT phase is `COMPLETED`.

### F.115 GOLDENGATESETTINGS_REPLICATIONMODE

Allows the users to select INTEGRATED or NONINTEGRATED replication.

Parameter Relationships

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

For more information on `INTEGRATED` and `NONINTEGRATED` replication , see Configuring Oracle GoldenGate Replicat.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_REPLICATIONMODE = PARALLEL_INTEGRATED | PARALLEL_NON_INTEGRATED`
Default value | `NON_INTEGRATED`
Required | No
Modifiable on Resume | Until ZDM_CREATE_GG_REPLICAT_TGT phase is `COMPLETED`.

### F.116 GOLDENGATESETTINGS_REPLICAT_SPLITTRANSRECS

Specifies that large transactions should be divided into pieces of specified size (records) and applied in parallel.

Parameter Relationships

Valid for Parallel Replicat.

The `GOLDENGATESETTINGS_REPLICAT_*` parameters define settings for simplifying the tuning of GoldenGate Replicat.

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_REPLICAT_SPLITTRANSRECS = integer`
Default value | `100000`
Valid values | An integer value is expected.
Required | No
Modifiable on Resume | Until `ZDM_CREATE_GG_REPLICAT_TGT` phase is `COMPLETED`.

### F.117 GOLDENGATESETTINGS_FEATUREGROUP

Allows the users to select specific feature groups for procedural replication. The feature group name includes`ALL_SUPPORTED`, `AQ`, `FGA`, `DBFS`, and so on.

See Oracle Fusion Middleware Reference for Oracle GoldenGate, 18c (18.1.0) for more information.

Parameter Relationships

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_FEATUREGROUP = <feature_group_name>`
Default value | `ALL_SUPPORTED`
Required | No
Modifiable on Resume | Until ZDM_MONITOR_GG_LAG phase is `COMPLETED`.

### F.118 GOLDENGATESETTINGS_ENABLEPROCEDURALREPLICATION

Allows the users to enable procedural replication.

Parameter Relationships

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_ENABLEPROCEDURALREPLICATION = TRUE | FALSE`
Default value | `FALSE`
Required | No
Modifiable on Resume | Until ZDM_CREATE_GG_REPLICAT_TGT phase is `COMPLETED`.

### F.119 GOLDENGATESETTINGS_ENABLEEVENTBASEDSWITCHOVER

Allows the users to automatically enable event based switchover.

Parameter Relationships

To enable event based switchover, set the value of the parameter as `TRUE`. ZDM creates an event table in source and target databases, and creates event trigger in source database. When you resume or modify a job with `-performswitchover` argument, ZDM inserts a record in the source event table. Once the event is triggered, the REPLICAT stops after processing the transaction indicating switchover readiness. After REPLICAT stops, ZDM proceeds with switchover readiness validation and allows database to be switched over.

If you set the value of the parameter as `TRUE` then ZDM performs the following actions:

1. Creates event table and triggers in the source database under `ggadmin` user.
2. Creates event table in target database under `ggadmin` user.
3. Resumes and modifies new argument `-performswitchover` so that you can indicate when the source database is ready for switchover.
4. Inserts a record in the source event table.
5. Performs readiness validation and allows database to be switched over.
6. Deletes the event table on both the source and target databases in ZDM_CLEAN_UP.

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_ENABLEEVENTBASEDSWITCHOVER = TRUE | FALSE`
Default value | `FALSE`
Required | No
Modifiable on Resume | Until ZDM_VALIDATE_SRC phase is `COMPLETED`.

### F.120 GENFIXUP

Displays the path to remedial scripts for failing checks when a migration is run with Cloud Premigration Advisor Tool (CPAT) enabled. Generate the ZDM fixup scripts.

Parameter Relationships

The following values are possible:

- `YES`: Generate the SQL fixup scripts for checks such as `gg_enabled_replication, gg_force_logging, gg_supplemental_log_data_min, has_libraries, has_low_streams_pool_size, has_columns_of_rowid_type, has_java_objects` and `has_java_source`.
- `NO`: Does not generate SQL fixup scripts.

Property | Description
--- | ---
Syntax | `GENFIXUP = NO | YES`
Default value | `NO`
Required | No
Modifiable on Resume | Until ZDM_SETUP_SRC phase is `COMPLETED`.

### F.121 GOLDENGATESETTINGS_USEFLASHBACKQUERY

Specifies whether to set Oracle GoldenGate Extract parameters that allow ID KEY support mode objects to be replicated.

If you set parameter `GOLDENGATESETTINGS_USEFLASHBACKQUERY = TRUE`, Zero Downtime Migration sets the following Oracle GoldenGate Extract parameters that allow ID KEY support mode objects to be replicated.

Parameter Relationships

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_USEFLASHBACKQUERY = TRUE | FALSE`
Default value | `FALSE`
Required | No
Modifiable on Resume |

### F.122 GOLDENGATESETTINGS_USEMIGRATIONMODE

Specifies whether to configure Oracle GoldenGate Extract with the MIGRATION_MODE option.

If you set parameter `GOLDENGATESETTINGS_USEMIGRATIONMODE = TRUE`, then Extract configured with this option automatically includes all supported tables, includes DDL on supported tables, and excludes unsupported objects such as advanced queuing, text indexes, materialized views, and so on.

Extract is automatically configured with MIGRATION_MODE when at least one of the following is true:

- If `GOLDENGATESETTINGS_USEMIGRATIONMODE = TRUE`.
- Oracle source database version is higher than or equal to Oracle Database 19c (19.25) and GoldenGate build is higher than or equal to Release Update 23.6.

Restrictions:

- MIGRATION_MODE option is only supported for Data Pump job mode FULL, so TABLE and SCHEMA options are not allowed.
- MIGRATION_MODE only works with per PDB configuration, Extract configured with CDB or multi-PDBs will cause errors.
- The properties GOLDENGATESETTINGS_USEFLASHBACKQUERY, GOLDENGATESETTINGS_ENABLEPROCEDURALREPLICATION and GOLDENGATESETTINGS_REPLICATEDDL cannot be used together with MIGRATION_MODE.

Parameter Relationships

For online logical migrations, you can set the optional `GOLDENGATESETTINGS_*` parameters to provide Zero Downtime Migration with details about the Oracle GoldenGate Microservices configuration.

Property | Description
--- | ---
Syntax | `GOLDENGATESETTINGS_USEMIGRATIONMODE = TRUE | FALSE`
Default value | `FALSE`
Required | No
Modifiable on Resume | Until ZDM_VALIDATE_SRC phase is completed.

### F.123 IGNOREEXPORTERRORS

Specifies comma separated list of ORA errors to be ignored for Oracle Data Pump export. For any new error to be ignored, suffix the new error to the list of default errors to be ignored.

Note:

Starting with Oracle Zero Downtime Migration 26 (26.1) release, the following parameters are deprecated and will be desupported in a future release:

- `IGNOREIMPORTERRORS`
- `IGNOREEXPORTERRORS`

These are replaced by the `IGNOREERROR` parameter.

Property | Description
--- | ---
Syntax | `IGNOREEXPORTERRORS = ORA_error_list`
Default value | `ORA-31684,ORA-39111,ORA-39082`
Range of values | `ORA-31684,ORA-39111,ORA-39082`
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_EXPORT_SRC` phase is `COMPLETED`.

### F.124 IGNOREIMPORTERRORS

Specifies comma separated list of ORA errors to be ignored for Oracle Data Pump import. For any new error to be ignored, suffix the new error to the list of default errors to be ignored.

Note:

Starting with Oracle Zero Downtime Migration 26 (26.1) release, the following parameters are deprecated and will be desupported in a future release:

- `IGNOREIMPORTERRORS`
- `IGNOREEXPORTERRORS`

These are replaced by the `IGNOREERROR` parameter.

Property | Description
--- | ---
Syntax | `IGNOREIMPORTERRORS = ORA_error_list`
Default value | `ORA-31684,ORA-39111,ORA-39082`
Range of values | `ORA-31684,ORA-39111,ORA-39082`
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_IMPORT_TGT` phase is `COMPLETED`.

### F.125 IGNOREPHASEERRORS-n

Indicates whether non-critical errors for specified phase will be ignored.

ZDM provides the new `IGNOREPHASEERRORS-n` parameter to suppress noncritical failures and for the selected phases without affecting overall job success. Each entry uses the format:

`IGNOREPHASEERRORS-n= name:<PHASE>,value:<TRUE|FALSE>`, where n starts at 1 and increments for each phase. Only the allowed phases are supported.

For example,

`IGNOREPHASEERRORS-1= name:ZDM_ADVANCE_SEQUENCES,value:TRUE` indicates that errors in `ZDM_ADVANCE_SEQUENCES` phase are non-critical and can be ignored. ZDM checks the errors in failing phase and if critical reported them as fatal, otherwise only logs them.

Property | Description
--- | ---
Syntax | `IGNOREPHASEERRORS-n = name:"<phase name>",value:<>`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_IMPORT_TGT` phase is `COMPLETED`.

### F.126 IGNOREERROR

Allows you to ignore specific Data Pump errors by specifying error-matching strings as parameter values.

The legacy parameters IGNOREIMPORTERRORS and IGNOREEXPORTERRORS accept a comma-separated list of specific ORA error codes for example., ORA-XXXX and suppress those exact errors during the Data Pump export and import phase. However, these legacy parameters do not support error string matching. IGNOREERROR is therefore an enhancement, providing more flexible error matching capabilities. To maintain mutual exclusivity between IGNOREIMPORTERRORS or IGNOREEXPORTERRORS, and IGNOREERROR, a check has been added in the GHCTL layer to give an error if they are used together.

To ignore all export and import errors, you can specify the keyword ALL in the IGNOREERROR value for example,`DATAPUMPSETTINGS_IGNOREERROR-1=ALL`.

Note:

Starting with Oracle Zero Downtime Migration 26 (26.1) release, the following parameters are deprecated and will be desupported in a future release:

- `IGNOREIMPORTERRORS`
- `IGNOREEXPORTERRORS`

These are replaced by the `IGNOREERROR` parameter.

Property | Description
--- | ---
Syntax | `IGNOREERROR = name:"<phase name>",value:<>`
Default value | `There is no default value`
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_IMPORT_TGT` phase is `COMPLETED`.

### F.127 INCLUDEOBJECTS-LIST_ELEMENT_NUMBER

Specifies database objects to include for migration.

To include multiple objects, increment the integer appended to the parameter name, as shown in the examples below.

`INCLUDEOBJECTS-1=owner:ownerValue1, objectName:objectNameValue1, objectType:objectTypeValue1`

`INCLUDEOBJECTS-2=owner:ownerValue2, objectName:objectNameValue2, objectType:objectTypeValue2`

See Selecting Objects for Migration for more information about using `INCLUDEOBJECTS`.

Property | Description
--- | ---
Syntax | `INCLUDEOBJECTS-LIST_ELEMENT_NUMBER = owner:ownerValue, objectName:objectNameValue, objectType:objectTypeValue`
Default value | There is no default value
Range of values | An entry specifying the owner, object name, and object type is expected, as shown in the examples above.
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_EXPORT_SRC` phase is `COMPLETED`, or until `ZDM_DATAPUMP_IMPORT_TGT` phase when using `DATA_TRANSFER_MEDIUM=DBLINK`.

### F.128 MIGRATION_METHOD

In a logical migration, specifies whether the migration is online logical or offline logical

The required `MIGRATION_METHOD` parameter specifies whether the migration is online (Data Pump with Oracle GoldenGate replication) or offline (Data Pump only).

Property | Description
--- | ---
Syntax | `MIGRATION_METHOD = {ONLINE_LOGICAL | OFFLINE_LOGICAL}`
Default value | `OFFLINE_LOGICAL`
Range of values | `ONLINE_LOGICAL` migrate the database with Data Pump, with replication using Oracle GoldenGate for minimal downtime `OFFLINE_LOGICAL` migrate the database with Data Pump, with no replication
Required | Yes
Modifiable on Resume | No

### F.129 MIGRATE_APEX

Specify if you want to enable the migration of APEX workspace metadata from the source to the target database.

ZDM migrates APEX workspace metadata if you set this parameter to `TRUE` and if the source and target versions are compatible. The APEX workspace metadata is staged to a staging table in user specified for export and imported in the target database as a post Data Pump import action.

Property | Description
--- | ---
Syntax | `MIGRATE_APEX = {TRUE | FALSE}`
Default value | `FALSE`
Required | No
Modifiable on Resume | Until ZDM_VALIDATE_SRC phase is COMPLETED

### F.130 MIGRATE_AWR

Allows you to migrate the AWR report from the source to the target database.

If you set value of the `MIGRATE_AWR` parameter to `TRUE`, then:

- Three additional phases `ZDM_EXPORT_AWR_SRC`, `ZDM_TRANSFER_AWR_DUMPS_SRC` and `ZDM_IMPORT_AWR_TGT` are included in the workflow to handle the migration of AWR data.
- If you set value of the `MIGRATE_AWR` parameter to `TRUE`, then ZDM will migrate the AWR report from source database to target database.

Property | Description
--- | ---
Syntax | `MIGRATE_AWR = {TRUE | FALSE}`
Default value | `FALSE`
Required | No
Modifiable on Resume | No

### F.131 MIGRATE_STS

Allows you to migrate the STS data from the source to the target database.

If you set value of the `MIGRATE_STS` parameter to `TRUE`, then ZDM migrates the STS data from source database to target database.

Property | Description
--- | ---
Syntax | `MIGRATE_STS = {TRUE | FALSE}`
Default value | `FALSE`
Required | Yes
Modifiable on Resume | No

### F.132 OCIAUTHENTICATIONDETAILS_REGIONID

Specifies the OCI region identifier.

See the Region Identifier column in the table at Regions and Availability Domains.

Parameter Relationships

To call REST APIs, you must configure the `OCIAUTHENTICATIONDETAILS_*` parameters.

Property | Description
--- | ---
Syntax | `OCIAUTHENTICATIONDETAILS_REGIONID = region_id`
Default value | There is no default value
Required | Yes
Modifiable on Resume | Yes

### F.133 OCIAUTHENTICATIONDETAILS_USERPRINCIPAL_FINGERPRINT

Specifies the fingerprint of the public API key.

See Required Keys and OCIDs for more information.

Parameter Relationships

To call REST APIs, you must configure the `OCIAUTHENTICATIONDETAILS_*` parameters.

Property | Description
--- | ---
Syntax | `OCIAUTHENTICATIONDETAILS_USERPRINCIPAL_FINGERPRINT = fingerprint`
Default value | There is no default value
Required | Yes
Modifiable on Resume | Yes

### F.134 OCIAUTHENTICATIONDETAILS_USERPRINCIPAL_PRIVATEKEYFILE

Specifies the absolute path of API private key file.

See Required Keys and OCIDs for more information.

Parameter Relationships

To call REST APIs, you must configure the `OCIAUTHENTICATIONDETAILS_*` parameters.

Property | Description
--- | ---
Syntax | `OCIAUTHENTICATIONDETAILS_USERPRINCIPAL_PRIVATEKEYFILE = path`
Default value | There is no default value
Required | Yes
Modifiable on Resume | Yes

### F.135 OCIAUTHENTICATIONDETAILS_USERPRINCIPAL_TENANTID

Specifies the OCID of the OCI tenancy.

You can find the tenant OCID on OCI at Governance and Administration, Administration, Tenancy Details. The tenancy OCID is shown under Tenancy Information.

Example: ocid1.tenancy.oc1..aaaaaaaaba3pv6wkcr4jqae5f44n2b2m2yt2j6rx32uzr4h25vqstifsfdsq

See Managing the Tenancy and Required Keys and OCIDs for more information.

Parameter Relationships

To call OCI REST APIs, you must configure the `OCIAUTHENTICATIONDETAILS_*` parameters.

Property | Description
--- | ---
Syntax | `OCIAUTHENTICATIONDETAILS_USERPRINCIPAL_TENANTID = ocid_string`
Default value | There is no default value
Valid values | A string value is expected
Required | Yes
Modifiable on Resume | Yes

### F.136 OCIAUTHENTICATIONDETAILS_USERPRINCIPAL_USERID

Specifies the OCID of the IAM user.

You can find the IAM OCID on OCI at Console, Profile, User Settings.

See Managing Users and Required Keys and OCIDs for more information.

Parameter Relationships

To call OCI REST APIs, you must configure the `OCIAUTHENTICATIONDETAILS_*` parameters.

Property | Description
--- | ---
Syntax | `OCIAUTHENTICATIONDETAILS_USERPRINCIPAL_USERID = userid`
Default value | There is no default value
Required | Yes
Modifiable on Resume | Yes

### F.137 OCIPROXY_HOSTNAME

Specifies the HTTP proxy hostname required for OCI REST endpoint access from ZDM host.

Parameter Relationships

The `OCIPROXY_*` parameters specify details about the proxy for connecting to OCI REST endpoints.

Property | Description
--- | ---
Syntax | `OCIPROXY_HOSTNAME = hostname`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.138 OCIPROXY_PORT

Specifies the HTTP proxy port required for OCI REST endpoint access from ZDM host.

Parameter Relationships

The `OCIPROXY_*` parameters specify details about the proxy for connecting to OCI REST endpoints.

Property | Description
--- | ---
Syntax | `OCIPROXY_PORT = port number`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.139 OCIPROXY_PROTOCOL

Specifies the HTTP proxy protocol required for OCI REST endpoint access from ZDM host.

Parameter Relationships

The `OCIPROXY_*` parameters specify details about the proxy for connecting to OCI REST endpoints.

Property | Description
--- | ---
Syntax | `OCIPROXY_PROTOCOL = HTTP or HTTPS`
Default value | `None`
Required | Yes
Modifiable on Resume | Yes

### F.140 OCISDKCONFIG_REGISTERREGIONDETAILS_REALM_KEY

Specify the `REALM_KEY` properties if you will register a new OCI realm required by `REGION` properties.

Parameter Relationships

Refer to Realm Key in the table available at About Regions and Availability Domains.

Note:

ZDM is bundled with a list of the known OCI regions and any region that gets added after the release of ZDM may not get recognized and the ZDM job may report an error on an unidentified OCI region. If the given OCI region is not recognized by ZDM, specify the OCI region details in `OCISDKCONFIG_REGISTERREGIONDETAILS*` for a database in the given region.

The `OCISDKCONFIG_*` parameters specify OCI SDK configurations.

Property | Description
--- | ---
Syntax | `OCISDKCONFIG_REGISTERREGIONDETAILS_REALM_KEY =`
Default value | There is no default value
Required | No
Modifiable on Resume | Can be modified in any phase, no restrictions.

### F.141 OCISDKCONFIG_REGISTERREGIONDETAILS_REALM_DOMAINCOMPONENT

Specify the second level domain of the realm. Specify the REALM_DOMAINCOMPONENT properties if you will register a new OCI realm required by REGION properties.

Parameter Relationships

Note:

ZDM is bundled with a list of the known OCI regions and any region that gets added after the release of ZDM may not get recognized and the ZDM job may report an error on an unidentified OCI region. If the given OCI region is not recognized by ZDM, specify the OCI region details in `OCISDKCONFIG_REGISTERREGIONDETAILS*` for a database in the given region.

The `OCISDKCONFIG_*` parameters specify OCI SDK configurations.

Property | Description
--- | ---
Syntax | `OCISDKCONFIG_REGISTERREGIONDETAILS_REALM_DOMAINCOMPONENT =`
Default value | There is no default value
Required | No
Modifiable on Resume | Can be modified in any phase, no restrictions.

### F.142 OCISDKCONFIG_REGISTERREGIONDETAILS_REGION_ID

Specify the `REGISTERREGIONDETAILS_*` properties when working with a new OCI region.

Parameter Relationships

Refer to Region Identifier in the table available at About Regions and Availability Domains.

Note:

ZDM is bundled with a list of the known OCI regions and any region that gets added after the release of ZDM may not get recognized and the ZDM job may report an error on an unidentified OCI region. If the given OCI region is not recognized by ZDM, specify the OCI region details in `OCISDKCONFIG_REGISTERREGIONDETAILS*` for a database in the given region.

The `OCISDKCONFIG_*` parameters specify OCI SDK configurations.

Property | Description
--- | ---
Syntax | `OCISDKCONFIG_REGISTERREGIONDETAILS_REGION_ID =`
Default value | There is no default value
Required | No
Modifiable on Resume | Can be modified in any phase, no restrictions.

### F.143 OCISDKCONFIG_REGISTERREGIONDETAILS_REGION_KEY

Specify the `REGISTERREGIONDETAILS_*` properties when working with a new OCI region.

Parameter Relationships

Refer to Region Key in the table available at About Regions and Availability Domains.

Note:

ZDM is bundled with a list of the known OCI regions and any region that gets added after the release of ZDM may not get recognized and the ZDM job may report an error on an unidentified OCI region. If the given OCI region is not recognized by ZDM, specify the OCI region details in `OCISDKCONFIG_REGISTERREGIONDETAILS*` for a database in the given region.

The `OCISDKCONFIG_*` parameters specify OCI SDK configurations.

Property | Description
--- | ---
Syntax | `OCISDKCONFIG_REGISTERREGIONDETAILS_REGION_KEY =`
Default value | There is no default value
Required | No
Modifiable on Resume | Can be modified in any phase, no restrictions.

### F.144 OCISDKCONFIG_REGISTERREGIONDETAILS_REGION_REALMKEY

Specify the `REGISTERREGIONDETAILS_*` properties when working with a new OCI region.

Parameter Relationships

Refer to Realm Key in the table available at About Regions and Availability Domains.

Note:

ZDM is bundled with a list of the known OCI regions and any region that gets added after the release of ZDM may not get recognized and the ZDM job may report an error on an unidentified OCI region. If the given OCI region is not recognized by ZDM, specify the OCI region details in `OCISDKCONFIG_REGISTERREGIONDETAILS*` for a database in the given region.

The `OCISDKCONFIG_*` parameters specify OCI SDK configurations.

Property | Description
--- | ---
Syntax | `OCISDKCONFIG_REGISTERREGIONDETAILS_REGION_REALMKEY =`
Default value | There is no default value
Required | No
Modifiable on Resume | Can be modified in any phase, no restrictions.

### F.145 PROFILE

Specifies the full path to the source database profile file. ZDM maintains a key-value template for each of the supported database PROFILE. ZDM defines custom defaults with every PROFILE supported parameter.

Property | Description
--- | ---
Syntax | `PROFILE = {EBS.profile, FA.profile}`
Default value | `NONE`
Range of values |
Required | No
Modifiable on Resume | Yes

### F.146 RUNCPATREMOTELY

Specifies whether Cloud Premigration Advisor Tool (CPAT) should run on the Zero Downtime Migration service host with a remote connection to the source database.

See Running CPAT with a Remote Connection for details.

Property | Description
--- | ---
Syntax | `RUNCPATREMOTELY = {TRUE | FALSE}`
Default value | `FALSE`
Range of values | `TRUE` = run CPAT remotely `FALSE` = do not run CPAT remotely
Required | No
Modifiable on Resume | No

### F.147 RUNFIXUPS

Specifies if you want to run automated fixups on the target database host.

Property | Description
--- | ---
Syntax | `RUNFIXUPS = {TRUE | FALSE}`
Default value | `FALSE`
Range of values | `TRUE` = Automated fixup scripts are processed for the target database. `FALSE` = Automated Fixup scripts are not processed for the target database.
Required | No
Modifiable on Resume | No

### F.148 REFRESHMVIEWS

Specifies whether you want to add the `ZDM_REFRESH_MVIEW` phase, for refreshing the materialized views post migration.

If `REFRESHMVIEW = FALSE` , then the `ZDM_REFRESH_MVIEW` phase is not added and materialized views are not refreshed post migration.

Note:

If you do not set this property, by default the `ZDM_REFRESH_MVIEW` phase will be part of the migration for CLI based migration. However, for the Database Migration Service, the `ZDM_REFRESH_MVIEW` phase will not be a part of the migration.
See Logical Migration Phase Descriptions for details.

Property | Description
--- | ---
Syntax | `REFRESHMVIEWS = {TRUE | FALSE}`
Default value | `NULL`
Range of values | `TRUE` = enables refresh of materialized views `FALSE` = does not enable refresh of materialized views `NULL`
Required | No
Modifiable on Resume | No

### F.149 RELOADOBJECTS-LIST_ELEMENT_NUMBER

Specifies if the database objects have to be migrated in offline mode in an online job during target database instantiation.

Note:

Starting with Oracle Zero Downtime Migration 26 (26.1) release, the `RELOADOBJECTS` parameter is deprecated and will be desupported in a future release. It is replaced by the following parameters:

- `GOLDENGATESETTINGS_EXTRACT_EXCLUDEOBJECTS`
- `GOLDENGATESETTINGS_REPLICAT_EXCLUDEOBJECTS`
- `GOLDENGATESETTINGS_EXCLUDERELOAD`
- `GOLDENGATESETTINGS_SKIPRELOADQUERYADVISOR`

Objects are migrated to the target database part of Data Pump for the target database instantiation. However, the objects are not considered for online syncing from source to target using Oracle GoldenGate. This can cater to any objects that are not to be replicated or not supported for replication. If objects are to be excluded from migration, then use the `EXCLUDEOBJECTS` parameter.

For objects specified in `RELOADOBJECTS-*`, objects with prefix `AQ$_` will be ignored. Basically, AQ objects are ignored if specified in the RELOADOBJECTS- property. To include AQ objects for reload, you must use `GOLDENGATESETTINGS_RELOADAQOBJECTS=TRUE`. ZDM reloads all the AQ objects in such case.

The specified objects are not replicated using Oracle GoldenGate. Instead, the specified objects are reloaded to the target database using Oracle Data Pump during phase `ZDM_RELOAD_PARALLEL_EXPORT_IMPORT` when there is no active workload on the source database.

Note:

- This parameter is only supported for online logical migration.
- Use of wildcard expressions are allowed.

To reload multiple objects, increment the integer appended to the parameter name, as shown in the examples below.

`RELOADOBJECTS-1=owner:ownerValue1, objectName:objectNameValue1, objectType:objectTypeValue1`

`RELOADOBJECTS-2=owner:ownerValue2, objectName:objectNameValue2, objectType:objectTypeValue2`

See Selecting Objects for Migration for more information about using `RELOADOBJECTS`.

Note:

You must note the following restrictions:

- Ensure to not reload `AQ$` objects or any `ORACLE_MAINTAINED` objects.
- Using `DBLINK` method is not supported for the reload feature.
- The base `AQ` tables can be reloaded, which will reload all the dependent objects.
- To reload the base AQ tables, the Oracle Database 19c source database must include the latest Datapump Bundle patch that includes patch for bug 34174611.
- Reload of base AQ should not be performed for database versions earlier than Oracle Database 19c.
- Reloading the base AQ tables with support mode as `internal` or `PLSQL` without the patch for bug 34174611 results in missing AQ$ table.

Property | Description
--- | ---
Syntax | `RELOADOBJECTS-LIST_ELEMENT_NUMBER = owner:ownerValue, objectName:objectNameValue, objectType:objectTypeValue`
Default value | `False`
Range of values | `True` `False`
Required | No
Modifiable on Resume | Until `ZDM_VALIDATE_SRC` phase is `COMPLETED`.

### F.150 COPYCPATREPORTTOZDMHOST

Specifies whether to copy the CPAT report log from the source database server to the ZDM server host job log directory for easier access to logs and more efficient troubleshooting.

Use this parameter when value of `RUNCPATREMOTELY=FALSE` and CPAT reports are required to be located in ZDM host. The `COPYCPATREPORTTOZDMHOST` parameter is skipped and the value is always `FALSE` when `RUNCPATREMOTELY=TRUE`.

Property | Description
--- | ---
Syntax | `COPYCPATREPORTTOZDMHOST = {TRUE | FALSE}`
Default value | `FALSE`
Range of values | `TRUE` = copy the CPAT report log `FALSE` = do not copy the CPAT report log
Required | No
Modifiable on Resume | No

### F.151 FORCECPATENUSLOCALE

Forces CPAT to use the en_US.UTF-8 Locale.

Property | Description
--- | ---
Syntax | `FORCECPATENUSLOCALE = {TRUE | FALSE}`
Default value | `FALSE`
Range of values | `TRUE` = Enable CPAT to use the en_US.UTF-8 Locale. `FALSE` = Allows CPAT to use the default locale.
Required | No
Modifiable on Resume | Yes

### F.152 SOURCECONTAINERDATABASE_ADMINUSERNAME

Specifies the source CDB administrator user name.

Parameter Relationships

For online logical migrations, the `SOURCECONTAINERDATABASE_*` parameters specify connection details for the source database CDB root.

Note:

`SOURCECONTAINERDATABASE_*` is required for online migration when the source is a PDB. The Oracle GoldenGate Capture runs at `CDB$ROOT` level.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_ADMINUSERNAME = username`
Default value | There is no default value
Required | No
Modifiable on Resume | No

### F.153 SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IDENTITYFILE

Specifies the identity file to access the bastion, as part of the database connection details for bastion-based access to the database.

Parameter Relationships

For online logical migrations, the `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source CDB.

The `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_*` parameters specify details for bastion based access to the database.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IDENTITYFILE = bastion_id_file`
Default value | There is no default value
Required | Not mandatory for migration jobs
Modifiable on Resume | Yes

### F.154 SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IP

Specifies the IP address of the source CDB bastion host, as part of the database connection details for bastion-based access to the database.

Parameter Relationships

For online logical migrations, the `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source CDB root.

The `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_*` parameters specify details for bastion based access to the database.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IP = bastion_ip_address`
Default value | There is no default value
Required | Not mandatory for migration jobs
Modifiable on Resume | Yes

### F.155 SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_PORT

Specifies the bastion host port, as part of the database connection details for bastion-based access to the container database (CDB).

Parameter Relationships

For online logical migrations, the `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source CDB root.

The `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_*` parameters specify details for bastion based access to the database.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_PORT = bastion_port_number`
Default value | There is no default value
Required | Not mandatory for migration jobs
Modifiable on Resume | Yes

### F.156 SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_REMOTEHOSTIP

Specifies the remote host IP address to access from the bastion, as part of the database connection details for bastion-based access to the container database (CDB).

Parameter Relationships

For online logical migrations, the `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source CDB root.

The `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_*` parameters specify details for bastion based access to the database.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_REMOTEHOSTIP = ip_address`
Default value | There is no default value
Required | Not mandatory for migration jobs
Modifiable on Resume | Yes

### F.157 SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_USERNAME

Specifies the user name to access the bastion, as part of the database connection details for bastion-based access to the container database (CDB).

Parameter Relationships

For online logical migrations, the `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source CDB root.

The `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_*` parameters specify details for bastion based access to the database.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_USERNAME = username`
Default value | There is no default value
Required | Not mandatory for migration jobs
Modifiable on Resume | Yes

### F.158 SOURCECONTAINERDATABASE_CONNECTIONDETAILS_HOST

Specifies the listener host name or IP address for the source container database (CDB).

Parameter Relationships

For online logical migrations, the `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source CDB root.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_HOST = listener_host`
Default value | There is no default value
Required | Not mandatory for migration jobs Not required for migrations to Autonomous Database.
Modifiable on Resume | Yes

### F.159 SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PORT

Specifies the listener port number for the source container database (CDB).

Parameter Relationships

For online logical migrations, the `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source CDB root.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PORT = listener_port`
Default value | There is no default value
Required | Not mandatory for migration jobs Not required for migrations to Autonomous Database.
Modifiable on Resume | Yes

### F.160 SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PROTOCOL

Specifies the proxy protocol for the CDB.

Parameter Relationships

For online logical migrations, the `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source CDB root.

The `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS_*` parameters specify connection details for the source CDB root through an HTTP proxy.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PROTOCOL = <protocolValue>`
Default value | There is no default value. Following values are supported: `HTTP` `HTTPS`
Required | No
Modifiable on Resume | Yes

### F.161 SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS_HOSTNAME

Specifies the HTTPS proxy host name for the CDB.

Parameter Relationships

For online logical migrations, the `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source CDB root.

The `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS_*` parameters specify connection details for the source CDB root through an HTTP proxy.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS_HOSTNAME = proxy_hostname`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.162 SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PORT

Specifies the HTTPS proxy host port number for the CDB.

Parameter Relationships

For online logical migrations, the `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source CDB root.

The `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS_*` parameters specify connection details for the source CDB root through an HTTP proxy.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PORT = proxy_port`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.163 SOURCECONTAINERDATABASE_CONNECTIONDETAILS_SERVICENAME

Specifies the fully qualified source CDB service name.

Parameter Relationships

For online logical migrations, the `SOURCECONTAINERDATABASE_*` parameters specify connection details for the source database CDB root.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_SERVICENAME = service_name`
Default value | There is no default value
Required | Not mandatory for migration jobs Not required for Autonomous Database
Modifiable on Resume | No

### F.164 SOURCECONTAINERDATABASE_CONNECTIONDETAILS_TLSDETAILS_CREDENTIALSLOCATION

Specifies the directory containing client credentials (wallet, keystore, trustfile, etc.) for the CDB.

Parameter Relationships

Note:

This parameter is not required for Autonomous Database.

For online logical migrations, the `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source CDB root.

The `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_TLSDETAILS_*` parameters specify details for TLS connection to the database CDB. These settings are not required if you are using TCP.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_TLSDETAILS_CREDENTIALSLOCATION = directory`
Default value | There is no default value
Required | Not mandatory for migration jobs Not required for Autonomous Database Not required if you are using TCP
Modifiable on Resume | Yes

### F.165 SOURCECONTAINERDATABASE_CONNECTIONDETAILS_TLSDETAILS_DISTINGUISHEDNAME

Specifies the distinguished name (DN) of the database server (`SSL_SERVER_CERT_DN`).

Parameter Relationships

Note:

This parameter is not required for Autonomous Database.

For online logical migrations, the `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source CDB root.

The `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_TLSDETAILS_*` parameters specify details for TLS connection to the CDB. These settings are not required if you are using TCP.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_CONNECTIONDETAILS_TLSDETAILS_DISTINGUISHEDNAME = distinguished_name`
Default value | There is no default value
Required | Not mandatory for migration jobs Not required for Autonomous Database Not required if you are using TCP
Modifiable on Resume | Yes

### F.166 SOURCECONTAINERDATABASE_GGADMINUSERNAME

Specifies the source CDB GoldenGate administrator user name.

Parameter Relationships

For online logical migrations, the `SOURCECONTAINERDATABASE_*` parameters specify connection details for the source database CDB root.

Property | Description
--- | ---
Syntax | `SOURCECONTAINERDATABASE_GGADMINUSERNAME = GoldenGate administrator username`
Default value | There is no default value
Required | Not mandatory for migration jobs
Modifiable on Resume | No

### F.167 SOURCEDATABASE_ADMINUSERNAME

Specifies the source database administrator user name.

Parameter Relationships

The `SOURCEDATABASE_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_ADMINUSERNAME = source administrator username`
Default value | There is no default value
Required | Yes
Modifiable on Resume | No

### F.168 SOURCEDATABASE_ALLOWTEMPTABLE

Indicates whether a new table should be created to store the unsupported table names of Oracle GoldenGate.

Parameter Relationships

The `SOURCEDATABASE_*` parameters specify connection details for the source database.

ZDM fetches the list of unsupported table names of Oracle GoldenGate from the metadata tables and stores them separately in a temporary table. Setting this parameter to `TRUE` allows ZDM to create a new `TEMP_ZDM_<jobid>` table in the source database. ZDM stores all the Oracle GoldenGate unsupported table names in this table. Once reload is completed, this table is dropped as part of the `ZDM_CLEANUP_SRC` phase.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_ALLOWTEMPTABLE= {TRUE | FALSE}`
Default value | `FALSE`
Required | No
Modifiable on Resume | No

### F.169 SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IDENTITYFILE

Specifies the identity file to access the bastion for bastion-based access to the database.

Parameter Relationships

The `SOURCEDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IDENTITYFILE = identity file`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.170 SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IP

Specifies the IP address of the bastion host for bastion-based access to the database.

Parameter Relationships

The `SOURCEDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IP = ip address`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.171 SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_PORT

Specifies the port number of the bastion host for bastion-based access to the database.

Parameter Relationships

The `SOURCEDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_PORT = port_number`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.172 SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_REMOTEHOSTIP

Specifies the remote host IP address to access from the bastion for bastion-based access to the database.

Parameter Relationships

The `SOURCEDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_REMOTEHOSTIP = ip_address`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.173 SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_USERNAME

Specifies the user name to access the bastion for bastion-based access to the database.

Parameter Relationships

The `SOURCEDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_USERNAME = username`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.174 SOURCEDATABASE_CONNECTIONDETAILS_HOST

Specifies the source database listener host name or IP address.

Parameter Relationships

The `SOURCEDATABASE_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_CONNECTIONDETAILS_HOST = hostname_or_ip`
Default value | There is no default value
Required | Yes* *Not required for Autonomous Database.
Modifiable on Resume | Yes

### F.175 SOURCEDATABASE_CONNECTIONDETAILS_PORT

Specifies the source database listener port number.

Parameter Relationships

The `SOURCEDATABASE_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_CONNECTIONDETAILS_PORT = listener port number`
Default value | There is no default value
Required | Yes* *Not required for Autonomous Database.
Modifiable on Resume | Yes

### F.176 SOURCEDATABASE_CONNECTIONDETAILS_PROXYDETAILS_HOSTNAME

Specifies the proxy host name to connect to the source database through an HTTPS proxy.

Parameter Relationships

The `SOURCEDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_CONNECTIONDETAILS_PROXYDETAILS_HOSTNAME = proxy host name`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.177 SOURCEDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PORT

Specifies the HTTP proxy port number to connect to the source database through an HTTPS proxy.

Parameter Relationships

The `SOURCEDATABASE_CONNECTIONDETAILS` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PORT = proxy port number`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.178 SOURCEDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PROTOCOL

Specifies the proxy protocol to connect to the source database through a proxy.

Parameter Relationships

The `SOURCEDATABASE_CONNECTIONDETAILS` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PROTOCOL = HTTP or HTTPS`
Default value | `HTTP`
Required | No
Modifiable on Resume | Yes

### F.179 SOURCEDATABASE_CONNECTIONDETAILS_SERVICENAME

Specifies the source database fully qualified service name.

Parameter Relationships

The `SOURCEDATABASE_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_CONNECTIONDETAILS_SERVICENAME = service name`
Default value | There is no default value
Required | Yes* *Not required for Autonomous Database
Modifiable on Resume | No

### F.180 SOURCEDATABASE_CONNECTIONDETAILS_TLSDETAILS_CREDENTIALSLOCATION

Specifies the directory containing client credentials (wallet, keystore, trustfile, etc.) for a TLS connection to the database.

Parameter Relationships

The `SOURCEDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_CONNECTIONDETAILS_TLSDETAILS_CREDENTIALSLOCATION = directory`
Default value | There is no default value
Required | Not mandatory for migration jobs Not required if using TCP Not required for Autonomous Database
Modifiable on Resume | Yes

### F.181 SOURCEDATABASE_CONNECTIONDETAILS_TLSDETAILS_DISTINGUISHEDNAME

Specifies the distinguished name (DN) of the database server (`SSL_SERVER_CERT_DN`) for a TLS connection to the database.

Parameter Relationships

The `SOURCEDATABASE_*` parameters specify connection details for the source database.

The `SOURCEDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_CONNECTIONDETAILS_TLSDETAILS_DISTINGUISHEDNAME = distinguished_name`
Default value | There is no default value
Required | Not mandatory for migration jobs Not required if using TCP Not required for Autonomous Database
Modifiable on Resume | Yes

### F.182 SOURCEDATABASE_ENVIRONMENT_DBTYPE

Indicates the type of database to migrate from the specified environment.

If you specify that the source database environment is Amazon Web Services RDS by setting `SOURCEDATABASE_ENVIRONMENT_NAME=AMAZON`, then you must also set `SOURCEDATABASE_ENVIRONMENT_DBTYPE=RDS_ORACLE`.

See Migrating from Amazon Web Services RDS to Oracle Autonomous AI Database.

Parameter Relationships

The `SOURCEDATABASE_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_ENVIRONMENT_DBTYPE = RDS_ORACLE`
Default value | `ORACLE`
Required | No
Modifiable on Resume | No

### F.183 SOURCEDATABASE_ENVIRONMENT_NAME

Specifies the environment of the source database.

You can specify whether the source database environment is Oracle (`ORACLE`) or Amazon Web Services RDS (`AMAZON`).

If you set `SOURCEDATABASE_ENVIRONMENT_NAME=AMAZON` you must also set `SOURCEDATABASE_ENVIRONMENT_DBTYPE=RDS_ORACLE`. See Migrating from Amazon Web Services RDS to Oracle Autonomous Database.

Parameter Relationships

The `SOURCEDATABASE_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_ENVIRONMENT_NAME = [ORACLE|AMAZON]`
Default value | `ORACLE`
Required | No
Modifiable on Resume | No

### F.184 SOURCEDATABASE_GGADMINUSERNAME

Specifies the GoldenGate administrator user name for online logical migrations.

Parameter Relationships

The `SOURCEDATABASE_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_GGADMINUSERNAME = gg_admin_username`
Default value | There is no default value
Required | No
Modifiable on Resume | No

### F.185 SOURCEDATABASE_OCID

Specifies the OCID of the source Autonomous Database.

Parameter Relationships

Note:

Using the `SOURCEDATABASE_OCID` parameter, you can migrate from an Autonomous database to an Autonomous database within same tenancy and region. However, to migrate an Autonomous database to an Autonomous database across tenancy and regions use the SOURCEDATABASE_CONNECTIONDETAILS_* parameters. Also, ensure to provide the OCIAUTHENTICATIONDETAILS_* of target region or tenancy. For logical online migration, ensure to provision GoldenGate hub in the target region or tenancy.

The `SOURCEDATABASE_*` parameters specify connection details for the source database.

Property | Description
--- | ---
Syntax | `SOURCEDATABASE_OCID = ocid of source adb`
Default value | There is no default value
Required | No
Modifiable on Resume | No

### F.186 SOURCESTANDBYDATABASE_CONNECTIONDETAILS_HOST

Specifies the listener host name or IP address of the source standby database.

Parameter Relationships

The `SOURCESTANDBYDATABASE_*` parameters specify connection details for the source standby database.

Property | Description
--- | ---
Syntax | `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_HOST = ocid of source adb`
Default value | There is no default value
Required | Yes Not required for Oracle Autonomous AI Database.
Modifiable on Resume | No

### F.187 SOURCESTANDBYDATABASE_CONNECTIONDETAILS_PORT

Specifies the listener port number of the source standby database.

Parameter Relationships

The `SOURCESTANDBYDATABASE_*` parameters specify connection details for the source standby database.

Property | Description
--- | ---
Syntax | `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_PORT = listener port number`
Default value | There is no default value
Required | Yes Not required for Oracle Autonomous AI Database.
Modifiable on Resume | No

### F.188 SOURCESTANDBYDATABASE_CONNECTIONDETAILS_SERVICENAME

Specifies the fully qualified service name of the source standby database.

Parameter Relationships

The `SOURCESTANDBYDATABASE_*` parameters specify connection details for the source standby database.

Property | Description
--- | ---
Syntax | `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_SERVICENAME = service name`
Default value | There is no default value
Required | Yes Not required for Oracle Autonomous AI Database.
Modifiable on Resume | No

### F.189 SOURCESTANDBYDATABASE_CONNECTIONDETAILS_TLSDETAILS_DISTINGUISHEDNAME

Specifies the distinguished name (DN) of the database server (`SSL_SERVER_CERT_DN`) for a TLS connection to the database.

Parameter Relationships

The `SOURCESTANDBYDATABASE_*` parameters specify connection details for the source standby database.

The `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source standby database.

Property | Description
--- | ---
Syntax | `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_TLSDETAILS_DISTINGUISHEDNAME = distinguished_name`
Default value | There is no default value
Required | Yes Not required for Oracle Autonomous AI Database. Not mandatory for migration jobs Not required if using TCP
Modifiable on Resume | Yes

### F.190 SOURCESTANDBYDATABASE_CONNECTIONDETAILS_TLSDETAILS_CREDENTIALSLOCATION

Specifies the directory containing client credentials such as wallet, keystore, trustfile, and so on for a TLS connection to the database.

Parameter Relationships

The `SOURCESTANDBYDATABASE_*` parameters specify connection details for the source standby database.

The `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source standby database.

Property | Description
--- | ---
Syntax | `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_TLSDETAILS_CREDENTIALSLOCATION = directory`
Default value | There is no default value
Required | Yes Not required for Oracle Autonomous AI Database. Not mandatory for migration jobs Not required if using TCP
Modifiable on Resume | Yes

### F.191 SOURCESTANDBYDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IP

Specifies the IP address of the bastion host for bastion-based access to the database.

Parameter Relationships

The `SOURCESTANDBYDATABASE_*` parameters specify connection details for the source standby database.

The `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source standby database.

Property | Description
--- | ---
Syntax | `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IP = ip address`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.192 SOURCESTANDBYDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_PORT

Specifies the port number of the bastion host for bastion-based access to the database.

Parameter Relationships

The `SOURCESTANDBYDATABASE_*` parameters specify connection details for the source standby database.

The `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source standby database.

Property | Description
--- | ---
Syntax | `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_PORT = port_number`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.193 SOURCESTANDBYDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IDENTITYFILE

Specifies the identity file to access the bastion for bastion-based access to the database.

Parameter Relationships

The `SOURCESTANDBYDATABASE_*` parameters specify connection details for the source standby database.

The `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source standby database.

Property | Description
--- | ---
Syntax | `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IDENTITYFILE = identity file`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.194 SOURCESTANDBYDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_USERNAME

Specifies the user name to access the bastion for bastion-based access to the database.

Parameter Relationships

The `SOURCESTANDBYDATABASE_*` parameters specify connection details for the source standby database.

The `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source standby database.

Property | Description
--- | ---
Syntax | `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_USERNAME = username`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.195 SOURCESTANDBYDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_REMOTEHOSTIP

Specifies the remote host IP address to access from the bastion for bastion-based access to the database.

Parameter Relationships

The `SOURCESTANDBYDATABASE_*` parameters specify connection details for the source standby database.

The `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source standby database.

Property | Description
--- | ---
Syntax | `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_REMOTEHOSTIP = ip address`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.196 SOURCESTANDBYDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PROTOCOL

Specifies the proxy protocol to connect to the source standby database through a proxy.

Parameter Relationships

The `SOURCESTANDBYDATABASE_*` parameters specify connection details for the source standby database.

The `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source standby database.

Property | Description
--- | ---
Syntax | `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PROTOCOL = HTTP or HTTPS`
Default value | `HTTP`
Required | No
Modifiable on Resume | Yes

### F.197 SOURCESTANDBYDATABASE_CONNECTIONDETAILS_PROXYDETAILS_HOSTNAME

Specifies the proxy host name to connect to the source standby database through an HTTPS proxy.

Parameter Relationships

The `SOURCESTANDBYDATABASE_*` parameters specify connection details for the source standby database.

The `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source standby database.

Property | Description
--- | ---
Syntax | `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_PROXYDETAILS_HOSTNAME = proxy host name`
Default value | `There is no default value`
Required | No
Modifiable on Resume | Yes

### F.198 SOURCESTANDBYDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PORT

Specifies the HTTP proxy port number to connect to the source standby database through an HTTPS proxy.

Parameter Relationships

The `SOURCESTANDBYDATABASE_*` parameters specify connection details for the source standby database.

The `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the source standby database.

Property | Description
--- | ---
Syntax | `SOURCESTANDBYDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PORT = proxy port number`
Default value | `There is no default value`
Required | No
Modifiable on Resume | Yes

### F.199 STS_SCHEMANAME

Specifies the schema under which the staging table is created. Specify the schema name where you want to create the STS staging table.

Parameter Relationships

Note:

If you do not specify STS_SCHEMANAME, then the staging table is created under the exporting schema.

Property | Description
--- | ---
Syntax | `STS_SCHEMANAME = schema_name`
Default value | There is no default value
Required | No
Modifiable on Resume | No

### F.200 STS_SQLSETNAME

Specifies the name of the SQL tuning set to be packed. Specify the name of the SQL tuning set to be packed.

Parameter Relationships

Property | Description
--- | ---
Syntax | `STS_SQLSETNAME = schema_name`
Default value | There is no default value
Required | No
Modifiable on Resume | No

### F.201 STS_SQLSETREPLACE

Determines if an existing SQL tuning set has to be replaced while unpacking the STS data.

Parameter Relationships

If you set the parameter to `TRUE`, then while unpacking the STS staging table, if the SQL tuning set already exists then the existing SQL tuning set is replaced.

Property | Description
--- | ---
Syntax | `STS_SQLSETREPLACE = <TRUE | FALSE>`
Default value | `FALSE`
Required | No
Modifiable on Resume | No

### F.202 STS_SQLSETOWNER

Specifies the owner of the SQL Tuning Set. By default, this parameter is null.

Parameter Relationships

If you do not provide the value in the parameter, then ZDM assumes `SYS` as the SQL set owner.

Property | Description
--- | ---
Syntax | `STS_SQLSETOWNER = <sqlset_owner>`
Default value | `null`
Required | No
Modifiable on Resume | No

### F.203 TABLESPACEDETAILS_AUTOCREATE

Specifies whether Zero Downtime Migration automatically creates DATA, TEMPORARY, and UNDO tablespaces at the target database necessary to allocate space in the database to contain schema objects.

This option is prohibited for Autonomous Database Shared targets.

See Automatic Tablespace Creation for more information.

Parameter Relationships

In a logical migration, the `TABLESPACEDETAILS_*` parameters specify details that allow Zero Downtime Migration to automatically create the required tablespaces at target database.

Property | Description
--- | ---
Syntax | `TABLESPACEDETAILS_AUTOCREATE={TRUE | FALSE}`
Default value | `TRUE`
Range of values | `TRUE` - Zero Downtime Migration automatically creates tablespaces `FALSE` - Zero Downtime Migration does not create tablespaces Note: The value of `TABLESPACEDETAILS_AUTOCREATE` is set to `TRUE` by default for ADBS target and for all the other targets it is set to `FALSE` by default.
Required | No This option is prohibited for Autonomous Database Shared targets.
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`

### F.204 TABLESPACEDETAILS_AUTOREMAP

Specifies whether Zero Downtime Migration automatically remaps a tablespace at the target database.

See Automatic Tablespace Remap for more information.

Parameter Relationships

In a logical migration, the `TABLESPACEDETAILS_*` parameters specify details that allow Zero Downtime Migration to automatically create the required tablespaces at target database.

Property | Description
--- | ---
Syntax | `TABLESPACEDETAILS_AUTOREMAP={TRUE | FALSE}`
Default value | `FALSE`
Range of values | `TRUE` - Zero Downtime Migration automatically remaps tablespaces `FALSE` - Zero Downtime Migration does not remap tablespaces
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_IMPORT_TGT` phase is `COMPLETED`

### F.205 TABLESPACEDETAILS_EXCLUDE

Specifies tablespaces to be excluded from automatic creation at the target database.

See Automatic Tablespace Creation for more information.

Example

`TABLESPACEDETAILS_EXCLUDE=B2B_LOB_TS,B2B_HR_TS`

Parameter Relationships

In a logical migration, the `TABLESPACEDETAILS_*` parameters specify details that allow Zero Downtime Migration to automatically create the required tablespaces at target database.

Property | Description
--- | ---
Syntax | `TABLESPACEDETAILS_EXCLUDE=tablespace_names`
Default value | By default SYSTEM, SYSAUX, and USERS tablespaces are excluded.
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`

### F.206 TABLESPACEDETAILS_EXTENDSIZEMB

Specifies an extend size for `AUTOEXTEND` in support of automatic tablespace creation.

Properly setting `TABLESPACEDETAILS_EXTENDSIZEMB` enables `AUTOEXTEND` to avoid extend errors when automatic tablespace creation is enabled.

See Automatic Tablespace Creation for more information.

Parameter Relationships

In a logical migration, the `TABLESPACEDETAILS_*` parameters specify details that allow Zero Downtime Migration to automatically create the required tablespaces at target database.

Property | Description
--- | ---
Syntax | `TABLESPACEDETAILS_EXTENDSIZEMB=MB`
Default value | `512`
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`

### F.207 TABLESPACEDETAILS_REMAPTARGET

Specifies tablespaces to be remapped.

For a tablespace to be used as REMAP target, the user performing the import operation, for example `SYSTEM`, should have some quota on the chosen tablespace.

See Automatic Tablespace Remap for more information.

Parameter Relationships

In a logical migration, the `TABLESPACEDETAILS_*` parameters specify details that allow Zero Downtime Migration to automatically create the required tablespaces at target database.

Property | Description
--- | ---
Syntax | `TABLESPACEDETAILS_REMAPTARGET=target_tablespace_names`
Default value | By default the DATA tablespace is remapped.
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_IMPORT_TGT` phase is `COMPLETED`

### F.208 TABLESPACEDETAILS_REMAPTEMPTARGET

Specifies the TEMP tablespace at the target database to which the temporary tablespace of the source database needs to be remapped.

Name of `TEMP` tablespace at target to which the source database temporary tablespace need to be remapped. Setting `TABLESPACEDETAILS_AUTOREMAP` to `TRUE` and setting this parameter enables remap of temporary tablespaces.

Parameter Relationships

In a logical migration, the `TABLESPACEDETAILS_*` parameters specify details that allow Zero Downtime Migration to automatically create the required tablespaces at target database.

Property | Description
--- | ---
Syntax | `TABLESPACEDETAILS_REMAPTEMPTARGET={TRUE | FALSE}`
Default value | Remap by default to temporary tablespace TEMP for migrating to Autonomous Database. No default for migrating to non Autonomous targets
Range of values | `TRUE` - Zero Downtime Migration automatically remaps TEMP tablespaces. `FALSE` - Zero Downtime Migration does not remap TEMP tablespaces.
Required | No
Modifiable on Resume | Until `ZDM_DATAPUMP_IMPORT_TGT` phase is `COMPLETED` .

### F.209 TABLESPACEDETAILS_USEBIGFILE

Specifies whether to use bigfile tablespaces, if Zero Downtime Migration is configured to create tablespaces automatically.

Using bigfile tablespaces, which can be up to 128 TB, significantly reduces the number of data files for your database. Combined with Oracle Managed Files (OMF), bigfile tablespaces simplify data file management.

See Automatic Tablespace Creation for more information.

Parameter Relationships

In a logical migration, the `TABLESPACEDETAILS_*` parameters specify details that allow Zero Downtime Migration to automatically create the required tablespaces at target database.

Property | Description
--- | ---
Syntax | `TABLESPACEDETAILS_USEBIGFILE={TRUE | FALSE}`
Default value | `FALSE`
Range of values | `TRUE` - Zero Downtime Migration automatically creates bigfile tablespaces `FALSE` - Zero Downtime Migration does not create bigfile tablespaces
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`

### F.210 TABLESPACEDETAILS_BLOCKSIZE

Specifies the size of Oracle database blocks in kilobytes (KB).

Parameter Relationships

If you do not specify any value for `TABLESPACEDETAILS_BLOCKSIZE`, then the source tablespace blocksize is considered. You can query the source blocksize using the following SQL command:

    select block_size from dba_tablespaces;

In a logical migration, the `TABLESPACEDETAILS_*` parameters specify details that allow Zero Downtime Migration to automatically create the required tablespaces at target database.

Note:

Ensure that the target database has `db_block_size` set to `16k` or set `db_16k_cache_size` if `db_block_size` is `8k`. See DB_nK_CACHE_SIZE for the appropriate value to be specified for `db_16k_cache_size`.

Property | Description
--- | ---
Syntax | `TABLESPACEDETAILS_BLOCKSIZE= 12 or 32`
Default value | There is no default value
Range of values | `8` `12` `16` `32`
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`

### F.211 TARGETDATABASE_ADMINUSERNAME

Specifies the target database administrator user name.

Parameter Relationships

The `TARGETDATABASE_*` parameters specify connection details for the target OCI database.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_ADMINUSERNAME = username`
Default value | There is no default value
Required | Yes
Modifiable on Resume | No

### F.212 TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IDENTITYFILE

Specifies the identity file to access the bastion for bastion-based access to the target database.

Parameter Relationships

The `TARGETDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the target OCI database.

These are optional for Autonomous Database; however if an HTTP proxy is required to connect, specify them.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IDENTITYFILE = bastion_id_file`
Default value | There is no default value
Required | Not mandatory for migration jobs
Modifiable on Resume | Yes

### F.213 TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IP

Specifies the IP address of the bastion host for bastion-based access to database.

Parameter Relationships

The `TARGETDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the target OCI database.

These are optional for Autonomous Database; however if an HTTP proxy is required to connect, specify them.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IP = ip address`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.214 TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_PORT

Specifies the port number of the bastion host for bastion-based access to database.

Parameter Relationships

The `TARGETDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the target OCI database.

These are optional for Autonomous Database; however if an HTTP proxy is required to connect, specify them.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_PORT = port_number`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.215 TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_REMOTEHOSTIP

Specifies the remote host IP address to access from the bastion for bastion-based access to database.

Parameter Relationships

The `TARGETDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the target OCI database.

These are optional for Autonomous Database; however if an HTTP proxy is required to connect, specify them.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_REMOTEHOSTIP = ip_address`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.216 TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_USERNAME

Specifies the user name to access the bastion for bastion-based access to database.

Parameter Relationships

The `TARGETDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the target OCI database.

These are optional for Autonomous Database; however if an HTTP proxy is required to connect, specify them.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_USERNAME = username`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.217 TARGETDATABASE_CONNECTIONDETAILS_HOST

Specifies the listener host name or IP address.

Parameter Relationships

The `TARGETDATABASE_CONNECTIONDETAILS` parameters specify connection details for the target OCI database.

These properties are optional for Autonomous Database; however if an HTTP proxy is required to connect, specify them.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_CONNECTIONDETAILS_HOST = hostname_or_ip`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.218 TARGETDATABASE_CONNECTIONDETAILS_PORT

Specifies the listener port number.

Parameter Relationships

The `TARGETDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the target OCI database.

These are optional for Autonomous Database; however if an HTTP proxy is required to connect, specify them.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_CONNECTIONDETAILS_PORT = listener port number`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.219 TARGETDATABASE_CONNECTIONDETAILS_PROXYDETAILS_HOSTNAME

Specifies the proxy host name for connecting to the target database through an HTTPS proxy.

Parameter Relationships

The `TARGETDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the target OCI database.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_CONNECTIONDETAILS_PROXYDETAILS_HOSTNAME = proxy host name`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.220 TARGETDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PORT

Specifies the HTTP proxy port number for connecting to the source database through an HTTPS proxy.

Parameter Relationships

The `TARGETDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the target OCI database.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PORT = proxy port number`
Default value | There is no default value
Required | No
Modifiable on Resume | Yes

### F.221 TARGETDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PROTOCOL

Specifies the proxy protocol to connect to the target database through a proxy.

Parameter Relationships

The `TARGETDATABASE_CONNECTIONDETAILS` parameters specify connection details for the target OCI database.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PROTOCOL = HTTP or HTTPS`
Default value | `HTTP`
Required | No
Modifiable on Resume | Yes

### F.222 TARGETDATABASE_CONNECTIONDETAILS_SERVICENAME

Specifies the fully qualified service name.

This parameter is optional for Oracle Autonomous AI Database targets; however if an HTTP proxy is required to connect, specify it.

In addition, for Oracle Autonomous AI Database on Dedicated Exadata Infrastructure and Oracle Autonomous Database on Exadata Cloud@Customer with fractional OCPU service you must specify the appropriate service alias in the parameter.

You can specify any predefined fractional service alias available; however, for Autonomous Transaction Processing workloads TP* services are preferred over LOW* services because LOW* is meant for low priority batch jobs.

- `TP_TLS`, `TP`, `LOW_TLS` or `LOW` (for Autonomous Transaction Processing workloads)
- `LOW_TLS` or `LOW` (for Autonomous Data Warehouse workloads)

See also Connecting to a DB System and About Connecting to a Dedicated Autonomous Database

Parameter Relationships

The `TARGETDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the target OCI database.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_CONNECTIONDETAILS_SERVICENAME = service_name_or_alias`
Default value | There is no default value
Valid values | For non-Autonomous, specify the fully qualified service name. For Autonomous, you can specify the service alias for fractional OCPU service as: `TP_TLS`, `TP`, `LOW_TLS` or `LOW` (for Autonomous Transaction Processing workloads) `LOW_TLS` or `LOW` (for Autonomous Data Warehouse workloads)
Required | No
Modifiable on Resume | No

### F.223 TARGETDATABASE_CONNECTIONDETAILS_TLSDETAILS_CREDENTIALSLOCATION

Specifies the directory containing client credentials (wallet, keystore, trustfile, etc.) for a TLS connection.

Parameter Relationships

The `TARGETDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the target OCI database.

These are optional for Autonomous Database; however if an HTTP proxy is required to connect, specify them.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_CONNECTIONDETAILS_TLSDETAILS_CREDENTIALSLOCATION = directory`
Default value | There is no default value
Required | Not mandatory for migrations Not required if using TCP
Modifiable on Resume | Yes

### F.224 TARGETDATABASE_CONNECTIONDETAILS_TLSDETAILS_DISTINGUISHEDNAME

Specifies the distinguished name (DN) of the database server (`SSL_SERVER_CERT_DN`) for a TLS connection.

Parameter Relationships

The `TARGETDATABASE_CONNECTIONDETAILS_*` parameters specify connection details for the target OCI database.

These are optional for Autonomous Database; however if an HTTP proxy is required to connect, specify them.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_CONNECTIONDETAILS_TLSDETAILS_DISTINGUISHEDNAME = distinguished_name`
Default value | There is no default value
Required | Required if the DB connection is over TLS.
Modifiable on Resume | Yes

### F.225 TARGETDATABASE_GGADMINUSERNAME

Specifies the GoldenGate administrator user name for online logical migrations.

Parameter Relationships

The `TARGETDATABASE_*` parameters specify connection details for the target OCI database.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_GGADMINUSERNAME = gg_admin_username`
Default value | There is no default value
Required | No
Modifiable on Resume | No

### F.226 TARGETDATABASE_OCID

Specifies the Oracle Cloud resource identifier.

Parameter Relationships

The `TARGETDATABASE_*` parameters specify connection details for the target OCI database.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_OCID = ocid`
Default value | There is no default value
Required | Yes This is an optional parameter if `TARGETDATABASE_DBTYPE` is set to valid a value.
Modifiable on Resume | No

### F.227 TARGETDATABASE_DBTYPE

Specifies the target database type if OCID of the target database is not provided.

Parameter Relationships

You can migrate database to Oracle Autonomous AI Database on Exadata Cloud@Customer without needing an OCID if value of `TARGETDATABASE_DBTYPE = ADBCC`.

The `TARGETDATABASE_*` parameters specify connection details for the target OCI database.

Property | Description
--- | ---
Syntax | `TARGETDATABASE_DBTYPE = dbtypeValue`
Default value | There is no default value The following values are supported: `ORACLE` `ADBD` `ADBS` `ADBCC` `EXADATA`
Required | No
Modifiable on Resume | No

### F.228 WALLET_USERACTION

Allows you to provide the auto login wallet path, which contains the username and its password.

Note:

This parameter is supported only for logical migration.
The path should be resolvable from the Zero Downtime Migration service host.

About the WALLET_* Parameters

The `WALLET_*` parameters specify the full path for the auto login wallet file on the Zero Downtime Migration service host.

Property | Description
--- | ---
Syntax | `WALLET_USERACTION = wallet_path`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`.

### F.229 WALLET_AMAZONS3SECRET

Specifies the Amazon S3 Secret Key wallet path.

The path should be resolvable from the Zero Downtime Migration service host.

About the WALLET_* Parameters

The `WALLET_*` parameters specify the full path for the auto login wallet file on the Zero Downtime Migration service host.

Property | Description
--- | ---
Syntax | `WALLET_AMAZONS3SECRET = wallet_path`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`.

### F.230 WALLET_OCIAUTHTOKEN

Specifies the absolute path to the directory that contains the auto login wallet file `cwallet.sso`, which is used to get the OCI Auth Token password.

Note:

This parameter is applicable only when the source database is Oracle Autonomous Database on Shared Exadata Infrastructure or Oracle Autonomous Database on Dedicated Exadata Infrastructure.
The path should be resolvable from the Zero Downtime Migration service host.

About the WALLET_* Parameters

The `WALLET_*` parameters specify the full path for the auto login wallet file on the Zero Downtime Migration service host.

Property | Description
--- | ---
Syntax | `WALLET_OCIAUTHTOKEN = wallet_path`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`.

### F.231 WALLET_DATAPUMPENCRYPTION

Specifies the absolute path to the directory that contains the auto login wallet file `cwallet.sso`, which is used to get the Data Pump encryption password.

The path should be resolvable from the Zero Downtime Migration service host.

About the WALLET_* Parameters

The `WALLET_*` parameters specify the full path for the auto login wallet file on the Zero Downtime Migration service host.

Property | Description
--- | ---
Syntax | `WALLET_DATAPUMPENCRYPTION = wallet_path`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`.

### F.232 WALLET_OGGADMIN

Specifies the absolute path to the directory that contains the auto login wallet file `cwallet.sso`, which is used to get the Oracle GoldenGate hub administrative password.

The path should be resolvable from the Zero Downtime Migration service host.

About the WALLET_* Parameters

The `WALLET_*` parameters specify the full path for the auto login wallet file on the Zero Downtime Migration service host.

Property | Description
--- | ---
Syntax | `WALLET_OGGADMIN = wallet_path`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`.

### F.233 WALLET_SOURCECONTAINER

Specifies the absolute path to the directory that contains the auto login wallet file `cwallet.sso`, which is used to get the source database administrative user password.

The path should be resolvable from the Zero Downtime Migration service host.

About the WALLET_* Parameters

The `WALLET_*` parameters specify the full path for the auto login wallet file on the Zero Downtime Migration service host.

Property | Description
--- | ---
Syntax | `WALLET_SOURCECONTAINER = wallet_path`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`.

### F.234 WALLET_SOURCECGGADMIN

Specifies the absolute path to the directory that contains the auto login wallet file `cwallet.sso`, which is used to get the source database administrative `c##ggadmin` user password.

The path should be resolvable from the Zero Downtime Migration service host.

About the WALLET_* Parameters

The `WALLET_*` parameters specify the full path for the auto login wallet file on the Zero Downtime Migration service host.

Property | Description
--- | ---
Syntax | `WALLET_SOURCECGGADMIN = wallet_path`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`.

### F.235 WALLET_SOURCEGGADMIN

Specifies the absolute path to the directory that contains the auto login wallet file `cwallet.sso`, which is used to get the source database administrative user `ggadmin` password.

The path should be resolvable from the Zero Downtime Migration service host.

About the WALLET_* Parameters

The `WALLET_*` parameters specify the full path for the auto login wallet file on the Zero Downtime Migration service host.

Property | Description
--- | ---
Syntax | `WALLET_SOURCEGGADMIN = wallet_path`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`.

### F.236 WALLET_TARGETADMIN

Specifies the absolute path to the directory that contains the auto login wallet file `cwallet.sso`, which is used to get the target database administrative admin password.

The path should be resolvable from the Zero Downtime Migration service host.

About the WALLET_* Parameters

The `WALLET_*` parameters specify the full path for the auto login wallet file on the Zero Downtime Migration service host.

Property | Description
--- | ---
Syntax | `WALLET_TARGETADMIN = wallet_path`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`.

### F.237 WALLET_TARGETGGADMIN

Specifies the absolute path to the directory that contains the auto login wallet file `cwallet.sso`, which is used to get the target database administrative user `ggadmin` password.

The path should be resolvable from the Zero Downtime Migration service host.

About the WALLET_* Parameters

The `WALLET_*` parameters specify the full path for the auto login wallet file on the Zero Downtime Migration service host.

Property | Description
--- | ---
Syntax | `WALLET_TARGETGGADMIN = wallet_path`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`.

### F.238 WALLET_OGGSERVICEADMIN

Specifies the absolute path to the directory that contains the auto login wallet file `cwallet.sso`, for specifying the Oracle Cloud Infrastructure GoldenGate administrative password.

The path should be accessible from the Zero Downtime Migration node.

About the WALLET_* Parameters

The `WALLET_*` parameters specify the full path for the auto login wallet file on the Zero Downtime Migration service host.

Property | Description
--- | ---
Syntax | `WALLET_OGGSERVICEADMIN = Absolute path to wallet on ZDM host`
Default value | There is no default value
Required | No
Modifiable on Resume | Until `ZDM_PREPARE_DATAPUMP_SRC` phase is `COMPLETED`.