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.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Range of values |
|
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.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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Until |
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 |
|
Default value |
There is no default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
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 |
|
Default value |
There is no default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
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 |
|
Default value |
There is no default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
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 |
|
Default value |
There is no default value |
Range of values |
Enter the storage bucket name |
Required |
No |
Modifiable on Resume |
Until |
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 |
|
Default value |
There is no default value |
Range of values |
Enter the storage bucket namespace |
Required |
No |
Modifiable on Resume |
Until |
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 |
|
Default value |
|
Valid values |
|
Required |
No |
Modifiable on Resume |
Until |
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 |
|
Default value |
|
Range of values |
See |
Required |
No |
Modifiable on Resume |
Until |
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 |
|
Default value |
There is no default value |
Valid values |
An integer value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.11 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_IMPORTPARALLELISMDEGREE
Specifies the maximum number of worker processes that can be used for a Data Pump Import job.
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 |
|
Default value |
There is no default value |
Valid values |
An integer value is expected |
Required |
No |
Modifiable on Resume |
Until |
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 |
|
Default value |
There is no default value |
Valid values |
An integer value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.13 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 |
|
Default value |
|
Valid values |
Following are the supported values:
|
Required |
No |
Modifiable on Resume |
No |
F.14 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 |
|
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.15 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 |
|
Default value |
|
Valid values |
|
Required |
No |
Modifiable in Resume |
Until |
F.16 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 |
|
Default value |
|
Valid values |
|
Required |
No |
Modifiable on Resume |
No |
F.17 DATAPUMPSETTINGS_DATAPUMPPARAMETERS_RETAININDEX
Specifies whether to retain the index.
Parameter Relationships
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 |
|
Default value |
|
Valid values |
|
Required |
No |
Modifiable on Resume |
Until |
F.18 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 |
|
Default value |
Otherwise, default value is |
Valid values |
|
F.19 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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Until |
F.20 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 |
|
Default value |
There is no default value |
Range of values |
Name of directory object in the database. |
Required |
No |
Modifiable on Resume |
Until |
F.21 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, theUTL_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 |
|
Default value |
There is no default value |
Range of values |
Absolute path of directory on database server |
Required |
No |
Modifiable on Resume |
Until |
F.22 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 |
|
Default value |
|
Required |
No |
F.23 DATAPUMPSETTINGS_FIXINVALIDOBJECTS
Specifies whether invalid objects are recompiled in the database as part of the migration job.
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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Until |
F.24 DATAPUMPSETTINGS_IMPORTDIRECTORYOBJECT_PATH
Specifies the 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, theUTL_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 |
|
Default value |
There is no default value |
Range of values |
Absolute path of directory on database server |
Required |
No |
Modifiable on Resume |
Until |
F.25 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 |
|
Default value |
There is no default value |
Range of values |
Name of directory object in database |
Required |
No |
Modifiable on Resume |
Until |
F.26 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 |
|
Default value |
|
Range of values |
See Oracle Data Pump Export Modes for more information. |
Required |
No |
Modifiable on Resume |
No |
F.27 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 |
|
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.28 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 |
See Remaps Provided by the METADATA_REMAP Procedure for more information about the values that can be specified for |
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 |
F.29 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 Transforms Provided by the METADATA_TRANFORM Procedure 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 Transforms Provided by the METADATA_TRANFORM Procedure for more information about the values that can be specified for |
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.30 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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Until |
F.31 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 |
|
Default value |
10 |
Range of values |
An integer value is expected |
Required |
No |
Modifiable on Resume |
No |
F.32 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 |
|
Default value |
|
Valid values |
|
Required |
No |
Modifiable on Resume |
No |
F.33 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 |
|
Default value |
For regular export/import job, the dumps are cleaned up in OSS or FSS. |
Valid values |
|
Required |
No |
Modifiable on Resume |
Until |
F.34 DATAPUMPSETTINGS_REUSE_DUMPPREFIX
(Optional) Specifies the dump prefix of the existing dump files from a previous job.
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, setDATAPUMPSETTINGS_RETAINDUMPS
to TRUE
.
ZDM_<jobID>_DP_EXPORT_<#>_dmp
.
Note:
SettingREUSE
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 |
|
Default value |
None |
Valid values |
NA |
Required |
No |
Modifiable on Resume |
No |
F.35 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 |
|
Default value |
|
Valid values |
|
Required |
No |
Modifiable on Resume |
No |
F.36 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.
Note:
Database initialization parameterMAX_DATAPUMP_JOBS_PER_PDB
determines the maximum number of concurrent Oracle Data Pump jobs for each
PDB.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Range of values |
An integer equal to or less than database initialization parameter
|
Required |
No |
Modifiable on Resume |
Until |
F.37 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 parameterMAX_DATAPUMP_JOBS_PER_PDB
determines the maximum number of
concurrent Oracle Data Pump jobs for each PDB.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value. |
Range of values |
LIST_ELEMENT_NUMBER must be a unique integer value for each batch specified
|
Required |
No |
Modifiable on Resume |
Until |
F.38 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 |
|
Default value |
|
Valid values |
|
Required |
No |
Modifiable on Resume |
No |
F.39 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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Until |
F.40 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 |
|
Default value |
3 |
Range of values |
This parameter accepts integer values |
Required |
No |
Modifiable on Resume |
Until |
F.41 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 |
|
Default value |
3 |
Range of values |
This parameter accepts integer values |
Required |
No |
Modifiable on Resume |
Until |
F.42 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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Until |
F.43 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 Database using an S3 bucket, you
must also set the DUMPTRANSFERDETAILS_S3BUCKET_*
parameters.
See Migrating from Amazon Web Services RDS to Oracle Autonomous Database for details.
Parameter Relationships
The DUMPTRANSFERDETAILS_*
parameters specify details
to transfer dumps from the source node to the target node.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.44 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 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.45 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 Database using an S3 bucket, you
must also set the DUMPTRANSFERDETAILS_S3BUCKET_*
parameters.
See Migrating from Amazon Web Services RDS to Oracle Autonomous Database for details.
Parameter Relationships
The DUMPTRANSFERDETAILS_*
parameters specify details to
transfer dumps from the source node to the target node.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.46 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.47 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.48 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.49 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.50 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 |
|
Default value |
|
Range of values |
An integer value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.51 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 |
|
Default value |
|
Required |
No |
F.52 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 |
|
Default value |
|
Required |
No |
F.53 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.54 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.55 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.56 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.57 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.58 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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Until |
F.59 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
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.60 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.61 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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
Yes |
F.62 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.63 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 |
|
Default value |
|
Required |
No |
F.64 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 |
|
Default value |
|
Required |
No |
F.65 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 |
|
Default value |
|
Range of values |
An integer value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.66 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.67 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.68 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.69 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.70 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.71 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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Until |
F.72 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.73 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.74 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.75 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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
Until |
F.76 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 |
|
Default value |
No default value |
Range of values |
A string value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.77 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.78 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.79 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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
Yes |
F.80 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 |
|
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 |
F.81 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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Yes |
F.82 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 |
|
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 |
F.83 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 |
|
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 |
F.84 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 |
|
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 |
F.85 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 |
|
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 |
F.86 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 |
|
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 |
F.87 GOLDENGATESETTINGS_ACCEPTABLELAG
Specifies GoldenGate end-to-end latency lag time
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 |
|
Default value |
30 seconds |
Required |
No |
Required |
No |
Modifiable on Resume |
Until |
F.88 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 |
|
Default value |
|
Valid values |
|
Required |
No |
Modifiable on Resume |
Until |
F.89 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 |
|
Default value |
There is no default value |
Valid values |
An integer value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.90 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 |
|
Default value |
There is no default value |
Valid values |
An integer value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.91 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 |
|
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 |
F.92 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.
- 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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
Until ZDM_VALIDATE_SRC phase is completed.
|
F.93 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 |
|
Default value |
4 |
Valid values |
An integer value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.94 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 |
|
Default value |
50 |
Valid values |
An integer value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.95 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 |
|
Default value |
4 |
Valid values |
An integer value is expected |
Required |
No |
Modifiable on Resume |
Until |
F.96 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 |
|
Default value |
|
Valid values |
Use Use Note:
|
Required |
No |
Modifiable on Resume |
Until |
F.97 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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
Until ZDM_MONITOR_GG_LAG phase is COMPLETED .
|
F.98 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.
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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
Until ZDM_CREATE_GG_REPLICAT_TGT phase is COMPLETED .
|
F.99 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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
Until ZDM_CREATE_GG_REPLICAT_TGT phase is COMPLETED .
|
F.100 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 |
|
Default value |
|
Valid values |
An integer value is expected. |
Required |
No |
Modifiable on Resume |
Until |
F.101 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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
Until ZDM_MONITOR_GG_LAG phase is COMPLETED .
|
F.102 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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
Until ZDM_CREATE_GG_REPLICAT_TGT phase is COMPLETED .
|
F.103 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
YES
: Generate the SQL fixup scripts for checks such asgg_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
andhas_java_source
.NO
: Does not generate SQL fixup scripts.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Required |
No |
Modifiable on Resume |
Until ZDM_SETUP_SRC phase is COMPLETED .
|
F.104 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.
Note:
Zero Downtime Migration 21.3 users must apply Patch 33509650: ZDM PATCH USING MOS to use this feature.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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
F.105 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.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Until |
F.106 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.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Until |
F.107 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 |
|
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 |
F.108 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 |
|
Default value |
|
Range of values |
|
Required |
Yes |
Modifiable on Resume |
No |
F.109 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 |
|
Default value |
There is no default value |
Required |
Yes |
Modifiable on Resume |
Yes |
F.110 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 |
|
Default value |
There is no default value |
Required |
Yes |
Modifiable on Resume |
Yes |
F.111 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 |
|
Default value |
There is no default value |
Required |
Yes |
Modifiable on Resume |
Yes |
F.112 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 |
|
Default value |
There is no default value |
Valid values |
A string value is expected |
Required |
Yes |
Modifiable on Resume |
Yes |
F.113 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 |
|
Default value |
There is no default value |
Required |
Yes |
Modifiable on Resume |
Yes |
F.114 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.115 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.116 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 |
|
Default value |
|
Required |
Yes |
Modifiable on Resume |
Yes |
F.117 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 inOCISDKCONFIG_REGISTERREGIONDETAILS*
for a database in the given region.
The OCISDKCONFIG_*
parameters specify OCI SDK configurations.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Can be modified in any phase, no restrictions. |
F.118 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 inOCISDKCONFIG_REGISTERREGIONDETAILS*
for a database in the given region.
The OCISDKCONFIG_*
parameters specify OCI SDK configurations.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Can be modified in any phase, no restrictions. |
F.119 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 inOCISDKCONFIG_REGISTERREGIONDETAILS*
for a database in the given region.
The OCISDKCONFIG_*
parameters specify OCI SDK configurations.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Can be modified in any phase, no restrictions. |
F.120 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 inOCISDKCONFIG_REGISTERREGIONDETAILS*
for a database in the given region.
The OCISDKCONFIG_*
parameters specify OCI SDK configurations.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Can be modified in any phase, no restrictions. |
F.121 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 inOCISDKCONFIG_REGISTERREGIONDETAILS*
for a database in the given region.
The OCISDKCONFIG_*
parameters specify OCI SDK configurations.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Can be modified in any phase, no restrictions. |
F.122 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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Yes |
F.123 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.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
No |
F.124 RUNFIXUPS
Specifies if you want to run automated fixups on the target database host.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
No |
F.125 REFRESHMVIEWS
Specifies whether you want to add the ZDM_REFRESH_MVIEW
phase, for refreshing the materialized views post migration.
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 theZDM_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.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
No |
F.126 RELOADOBJECTS-LIST_ELEMENT_NUMBER
Specifies if the database objects have to be migrated in offline mode in an online job during target database instantiation.
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.
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 anyORACLE_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
orPLSQL
without the patch for bug 34174611 results in missing AQ$ table.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Range of values |
True
|
Required |
No |
Modifiable on Resume |
Until |
F.127 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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
No |
F.128 FORCECPATENUSLOCALE
Forces CPAT to use the en_US.UTF-8 Locale.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Yes |
F.129 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
No |
F.130 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 |
|
Default value |
There is no default value |
Required |
Not mandatory for migration jobs |
Modifiable on Resume |
Yes |
F.131 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 |
|
Default value |
There is no default value |
Required |
Not mandatory for migration jobs |
Modifiable on Resume |
Yes |
F.132 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 |
|
Default value |
There is no default value |
Required |
Not mandatory for migration jobs |
Modifiable on Resume |
Yes |
F.133 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 |
|
Default value |
There is no default value |
Required |
Not mandatory for migration jobs |
Modifiable on Resume |
Yes |
F.134 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 |
|
Default value |
There is no default value |
Required |
Not mandatory for migration jobs |
Modifiable on Resume |
Yes |
F.135 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 |
|
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.136 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 |
|
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.137 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 |
|
Default value |
There is no default value. Following values are supported:
|
Required |
No |
Modifiable on Resume |
Yes |
F.138 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.139 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.140 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 |
|
Default value |
There is no default value |
Required |
Not mandatory for migration jobs Not required for Autonomous Database |
Modifiable on Resume |
No |
F.141 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 |
|
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.142 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 |
|
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.143 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 |
|
Default value |
There is no default value |
Required |
Not mandatory for migration jobs |
Modifiable on Resume |
No |
F.144 SOURCEDATABASE_ADMINUSERNAME
Specifies the source database administrator user name.
Parameter Relationships
The SOURCEDATABASE_*
parameters specify connection
details for the source database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Required |
Yes |
Modifiable on Resume |
No |
F.145 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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
No |
F.146 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.147 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.148 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.149 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.150 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.151 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 |
|
Default value |
There is no default value |
Required |
Yes* *Not required for Autonomous Database. |
Modifiable on Resume |
Yes |
F.152 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 |
|
Default value |
There is no default value |
Required |
Yes* *Not required for Autonomous Database. |
Modifiable on Resume |
Yes |
F.153 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.154 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.155 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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
Yes |
F.156 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 |
|
Default value |
There is no default value |
Required |
Yes* *Not required for Autonomous Database |
Modifiable on Resume |
No |
F.157 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 |
|
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.158 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 |
|
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.159 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 Database.
Parameter Relationships
The SOURCEDATABASE_*
parameters specify connection
details for the source database.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Required |
No |
Modifiable on Resume |
No |
F.160 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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
No |
F.161 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
No |
F.162 SOURCEDATABASE_OCID
Specifies the OCID of the source Autonomous Database.
Parameter Relationships
Note:
Using theSOURCEDATABASE_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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
No |
F.163 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 |
|
Default value |
|
Range of values |
|
Required |
No This option is prohibited for Autonomous Database Shared targets. |
Modifiable on Resume |
Until |
F.164 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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Until |
F.165 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 |
|
Default value |
By default SYSTEM, SYSAUX, and USERS tablespaces are excluded. |
Required |
No |
Modifiable on Resume |
Until |
F.166 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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
Until |
F.167 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 |
|
Default value |
By default the DATA tablespace is remapped. |
Required |
No |
Modifiable on Resume |
Until |
F.168 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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Until |
F.169 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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Until |
F.170 TABLESPACEDETAILS_BLOCKSIZE
Specifies the size of Oracle database blocks in kilobytes (KB).
Parameter Relationships
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 |
|
Default value |
|
Range of values |
|
Required |
No |
Modifiable on Resume |
Until |
F.171 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 |
|
Default value |
There is no default value |
Required |
Yes |
Modifiable on Resume |
No |
F.172 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 |
|
Default value |
There is no default value |
Required |
Not mandatory for migration jobs |
Modifiable on Resume |
Yes |
F.173 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.174 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.175 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.176 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.177 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.178 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.179 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.180 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Yes |
F.181 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 |
|
Default value |
|
Required |
No |
Modifiable on Resume |
Yes |
F.182 TARGETDATABASE_CONNECTIONDETAILS_SERVICENAME
Specifies the fully qualified service name.
This parameter is optional for Oracle Autonomous Database targets; however if an HTTP proxy is required to connect, specify it.
In addition, for Oracle Autonomous 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
orLOW
(for Autonomous Transaction Processing workloads)LOW_TLS
orLOW
(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 |
|
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:
|
Required |
No |
Modifiable on Resume |
No |
F.183 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 |
|
Default value |
There is no default value |
Required |
Not mandatory for migrations Not required if using TCP |
Modifiable on Resume |
Yes |
F.184 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 |
|
Default value |
There is no default value |
Required |
Required if the DB connection is over TLS. |
Modifiable on Resume |
Yes |
F.185 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
No |
F.186 TARGETDATABASE_OCID
Specifies the Oracle Cloud resource identifier.
Parameter Relationships
The TARGETDATABASE_*
parameters specify connection details for the
target OCI database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Required |
Yes This is an optional parameter if |
Modifiable on Resume |
No |
F.187 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 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 |
|
Default value |
There is no default value The following values are supported:
|
Required |
No |
Modifiable on Resume |
No |
F.188 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.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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.189 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.190 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.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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.191 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.192 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.193 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.194 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.195 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.196 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.197 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |
F.198 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 |
|
Default value |
There is no default value |
Required |
No |
Modifiable on Resume |
Until |