G Zero Downtime Migration Logical Migration Response File Parameters Reference
The following topics describe the Zero Downtime Migration response file parameters supported for logical migrations.
DATA_TRANSFER_MEDIUM
In a logical migration, the optional DATA_TRANSFER_MEDIUM
parameter specifies how data will be transferred from the source database system to the
target database system for initial load.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Range of values |
|
DATAPUMPSETTINGS_CREATEAUTHTOKEN
DATAPUMPSETTINGS_CREATEAUTHTOKEN
is one of the optional
settings for logical migrations using Data Pump.
If you are not using a network database link for Data Pump Import, an
OCI Auth Token will be created for the specified OCI user to import Data Pump dump
files from the Object Storage into an Autonomous Database. To reuse an existing Auth
Token, set this property to FALSE
.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Range of values |
|
DATAPUMPSETTINGS_DATABASELINKDETAILS_NAME
DATAPUMPSETTINGS_DATABASELINKDETAILS_NAME
specifies the
name of the database link from the OCI database to the on-premise database. ZDM creates the
database link if the link does not already exist.
The DATAPUMPSETTINGS_DATABASELINKDETAILS
parameters are optional
details for creating a network database link from OCI database to the on-premise
database. It is one of the optional settings for logical migrations using Data
Pump.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Range of values |
A string value is expected |
DATAPUMPSETTINGS_DATABASELINKDETAILS_WALLETBUCKET_BUCKETNAME
DATAPUMPSETTINGS_DATABASELINKDETAILS_WALLETBUCKET_BUCKETNAME
specifies
the OCI Object Storage bucket.
The DATAPUMPSETTINGS_DATABASELINKDETAILS_WALLETBUCKET
parameters, in the case of Autonomous Database, specifies 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.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Range of values |
A string value is expected |
DATAPUMPSETTINGS_DATABASELINKDETAILS_WALLETBUCKET_NAMESPACENAME
DATAPUMPSETTINGS_DATABASELINKDETAILS_WALLETBUCKET_NAMESPACENAME
specifies the Object Storage namespace.
The DATAPUMPSETTINGS_DATABASELINKDETAILS_WALLETBUCKET
parameters, in
the case of Autonomous Database, specifies the OCI Object Storage bucket 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.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Range of values |
A string value is expected |
DATAPUMPSETTINGS_DATABUCKET_BUCKETNAME
DATAPUMPSETTINGS_DATABUCKET_BUCKETNAME
is one of the
optional settings for logical migrations using Data Pump.
In lieu of a network database link, this OCI Object Storage bucket will be used to
store Data Pump dump files for migrating to an Autonomous Database. Use with
DATAPUMPSETTINGS_DATABUCKET_NAMESPACENAME
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Range of values |
Enter the storeage bucket name |
DATAPUMPSETTINGS_DATABUCKET_NAMESPACENAME
DATAPUMPSETTINGS_DATABUCKET_NAMESPACENAME
is one of the
optional settings for logical migrations using Data Pump.
In lieu of a network database link, this OCI Object Storage bucket will
be used to store Data Pump dump files for migrating to an Autonomous Database. Use
with DATAPUMPSETTINGS_DATABUCKET_BUCKETNAME
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Range of values |
Enter the storeage bucket namespace |
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_TABLEEXISTSACTION
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_TABLEEXISTSACTION
specifies the action to be performed when data is loaded into a preexisting
table.
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 |
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_USERMETADATA
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_USERMETADATA
is used
for EXPORT and Network IMPORT. If set to a nonzero value for schema-mode operations, it
specifies that the metadata to re-create the user's schemas should also be part of the
operation.
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 |
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_IMPORTPARALLELISMDEGREE
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_IMPORTPARALLELISMDEGREE
specifies the maximum number of worker processes that can be used for a Data Pump Import
job. For migration to an Autonomous Database target, ZDM automatically queries its CPU core
count and sets this parameter.
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 |
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_EXPORTPARALLELISMDEGREE
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, ZDM automatically queries its CPU core
count and sets this parameter.
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 |
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_EXCLUDETYPELIST
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_EXCLUDETYPELIST
specifies a comma separated list of object types to exclude.
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 |
Example
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_EXCLUDETYPELIST=cluster,dblink,comment
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_SKIPCURRENT
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_SKIPCURRENT
, when
enabled, causes actions that were 'in progress' on a previous execution of the job to be
skipped when the job restarts. The skip is only honored for Import jobs.
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 will identify which actions are skipped. 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.
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 |
|
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_NOCLUSTER
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_NOCLUSTER
, when
enabled, all Data Pump workers are started on the current instance; otherwise, workers are
started on instances usable by the job.
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 |
|
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_RETAININDEX
DATAPUMPSETTINGS_DATAPUMPPARAMETERS_RETAININDEX
, when
enabled, retains the index.
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 |
|
DATAPUMPSETTINGS_DELETEDUMPSINOSS
DATAPUMPSETTINGS_DELETEDUMPSINOSS
is used to indicate
whether dump files which are uploaded to Object Storage as part of the migration are
retained.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Range of values |
|
DATAPUMPSETTINGS_EXPORTDIRECTORYOBJECT_NAME
In lieu of a network database link, this directory on the server file system
of an on-premises database is used to store Data Pump Export dump files.
DATAPUMPSETTINGS_EXPORTDIRECTORYOBJECT_NAME
specifies the object name.
ZDM creates this object if it does not already exist
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Range of values |
Name of directory object in the database. |
DATAPUMPSETTINGS_EXPORTDIRECTORYOBJECT_PATH
In lieu of a network database link, this directory on the server file system
of an on-premises database is used to store Data Pump Export dump files.
DATAPUMPSETTINGS_EXPORTDIRECTORYOBJECT_PATH
specifies the object path.
ZDM 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.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Range of values |
Absolute path of directory on database server |
DATAPUMPSETTINGS_FIXINVALIDOBJECTS
DATAPUMPSETTINGS_FIXINVALIDOBJECTS
specifies whether
invalid objects are recompiled in the database as part of the ZDM Data Pump migration
procedure.
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 ZDM migration procedure, so that issues with invalid objects, and any required dependencies are resolved before users encounter these invalid objects.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Range of values |
|
DATAPUMPSETTINGS_IMPORTDIRECTORYOBJECT_NAME
DATAPUMPSETTINGS_IMPORTDIRECTORYOBJECT_NAME
specifies the
name of an import directory object.
In lieu of a network database link, this directory on the server
file system of OCI database will be used to store Data Pump dump files. ZDM will
create this object if it does not already exist. In case of Autonomous Database,
DATA_PUMP_DIR
object will already exist
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Range of values |
Name of directory object in database |
DATAPUMPSETTINGS_IMPORTDIRECTORYOBJECT_PATH
DATAPUMPSETTINGS_IMPORTDIRECTORYOBJECT_PATH
specifies the
path of an import directory object.
In lieu of a network database link, this directory on the server file
system of OCI database will be used to store Data Pump dump files. ZDM will create
this object if it does not already exist. In case of Autonomous Database,
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.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Range of values |
Absolute path of directory on database server |
DATAPUMPSETTINGS_JOBMODE
DATAPUMPSETTINGS_JOBMODE
specifies the Data Pump export
mode.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Range of values |
See Oracle Data Pump Export Modes for more information. |
DATAPUMPSETTINGS_METADATAFILTERS-LIST_ELEMENT_NUMBER
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.
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. |
DATAPUMPSETTINGS_METADATAREMAPS-LIST_ELEMENT_NUMBER
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.
Property | Description |
---|---|
Syntax |
|
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. |
DATAPUMPSETTINGS_METADATATRANSFORMS-LIST_ELEMENT_NUMBER
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
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. |
DATAPUMPSETTINGS_MONITORINTERVALMINUTES
DATAPUMPSETTINGS_MONITORINTERVALMINUTES
specifies the Data
Pump monitor interval in minutes. This setting is optional.
Property | Description |
---|---|
Syntax |
|
Default value |
10 |
Range of values |
An integer value is expected |
DATAPUMPSETTINGS_OMITENCRYPTIONCLAUSE
DATAPUMPSETTINGS_OMITENCRYPTIONCLAUSE
, when enabled, 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.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Valid values |
|
DATAPUMPSETTINGS_SECUREFILELOB
DATAPUMPSETTINGS_SECUREFILELOB
, when enabled, sets
TRANSFORM=LOB_STORAGE:SECUREFILE
, which directs Data Pump to transform
basic LOBs into securefile LOBs during the Data Pump import.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Valid values |
|
DATAPUMPSETTINGS_SKIPDEFAULTTRANSFORM
DATAPUMPSETTINGS_SKIPDEFAULTTRANSFORM
, when enabled, skips
default transform parameters. Set this property to TRUE
to avoid all
internal ZDM transform defaults.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Valid values |
|
DUMPTRANSFERDETAILS_PARALLELCOUNT
DUMPTRANSFERDETAILS_PARALLELCOUNT
specifies the maximum
number of Export dump files to transfer to Object Storage or remote node in
parallel.
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 |
DUMPTRANSFERDETAILS_RETRYCOUNT
DUMPTRANSFERDETAILS_RETRYCOUNT
specifies the number of
times to retry upload or transfer of dump failure.
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 |
DUMPTRANSFERDETAILS_RSYNCAVAILABLE
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.
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 |
|
DUMPTRANSFERDETAILS_SOURCE_OCIHOME
DUMPTRANSFERDETAILS_SOURCE_OCIHOME
specifies the Oracle
Cloud OCI-CLI Binary 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.
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 |
DUMPTRANSFERDETAILS_SOURCE_PARTSIZEMB
DUMPTRANSFERDETAILS_SOURCE_PARTSIZEMB
specifies the part
size in MB for chunked transfer.
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 |
An integer value is expected |
DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_DUMPDIRPATH
DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_DUMPDIRPATH
specifies the absolute path of the directory to copy or upload dump files.
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.
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.
Property | Description |
---|---|
Syntax |
|
Default value |
No default value |
Range of values |
A string value is expected |
DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_HOST
DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_HOST
specifies the
dump transfer node host name.
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.
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.
Property | Description |
---|---|
Syntax |
|
Default value |
No default value |
Range of values |
A string value is expected |
DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_SUDOPATH
DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_SUDOPATH
specifies
the Sudo path on the dump transfer node.
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.
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.
Property | Description |
---|---|
Syntax |
|
Default value |
No default value |
Range of values |
A string value is expected |
DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_USER
DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_USER
specifies the
user allowed to execute OCI CLI in the dump transfer node.
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.
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 havihas the Data Pump
export or import directory path shared with it. This avoids the requirement of
installing OCI CLI on the database node.
Property | Description |
---|---|
Syntax |
|
Default value |
No default value |
Range of values |
A string value is expected |
DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_USERKEY
DUMPTRANSFERDETAILS_SOURCE_TRANSFERNODE_USER
specifies the
user's authentication key.
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.
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 havihas the Data Pump
export or import directory path shared with it. This avoids the requirement of
installing OCI CLI on the database node.
Property | Description |
---|---|
Syntax |
|
Default value |
No default value |
Range of values |
A string value is expected |
DUMPTRANSFERDETAILS_SOURCE_USEOCICLI
DUMPTRANSFERDETAILS_SOURCE_USEOCICLI
indicates that
transfer dump files use Oracle Cloud Infrastructure command line interface
(CLI).
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 |
|
DUMPTRANSFERDETAILS_TARGET_OCIHOME
DUMPTRANSFERDETAILS_TARGET_OCIHOME
specifies the Oracle
Cloud Infrastructure command line interface (CLI) Binary 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.
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 |
DUMPTRANSFERDETAILS_TARGET_PARTSIZEMB
DUMPTRANSFERDETAILS_TARGET_PARTSIZEMB
specifies the part
size in MB for chunked transfer.
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 |
DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_DUMPDIRPATH
DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_DUMPDIRPATH
specifies the absolute path of the directory to copy or upload dump files.
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.
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.
Property | Description |
---|---|
Syntax |
|
Default value |
No default value |
Range of values |
A string value is expected |
DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_HOST
DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_HOST
specifies the
dump transfer node host name.
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.
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.
Property | Description |
---|---|
Syntax |
|
Default value |
No default value |
Range of values |
A string value is expected |
DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_SUDOPATH
DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_SUDOPATH
specifies
the Sudo path on the dump transfer node.
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.
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.
Property | Description |
---|---|
Syntax |
|
Default value |
No default value |
Range of values |
A string value is expected |
DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_USER
DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_USER
specifies the
user allowed to execute OCI CLI in the dump transfer node.
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.
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.
Property | Description |
---|---|
Syntax |
|
Default value |
No default value |
Range of values |
A string value is expected |
DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_USERKEY
DUMPTRANSFERDETAILS_TARGET_TRANSFERNODE_USER
specifies the
user's authentication key.
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.
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.
Property | Description |
---|---|
Syntax |
|
Default value |
No default value |
Range of values |
A string value is expected |
DUMPTRANSFERDETAILS_TARGET_USEOCICLI
DUMPTRANSFERDETAILS_TARGET_USEOCICLI
indicates that
transfer dump files use Oracle Cloud Infrastructure command line interface
(CLI).
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 |
|
DUMPTRANSFERDETAILS_TRANSFERTARGET_DUMPDIRPATH
DUMPTRANSFERDETAILS_TRANSFERTARGET_DUMPDIRPATH
specifies
the absolute path of the directory to copy or upload dump files.
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 |
DUMPTRANSFERDETAILS_TRANSFERTARGET_HOST
DUMPTRANSFERDETAILS_TRANSFERTARGET_HOST
specifies the dump
transfer node host name.
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 |
DUMPTRANSFERDETAILS_TRANSFERTARGET_SUDOPATH
DUMPTRANSFERDETAILS_TRANSFERTARGET_SUDOPATH
specifies the
Sudo path on the dump transfer node.
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 |
DUMPTRANSFERDETAILS_TRANSFERTARGET_USER
DUMPTRANSFERDETAILS_TRANSFERTARGET_USER
specifies the user
allowed to execute OCI CLI in specified node.
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 |
|
Range of values |
An integer value is expected |
DUMPTRANSFERDETAILS_TRANSFERTARGET_USERKEY
DUMPTRANSFERDETAILS_TRANSFERTARGET_USERKEY
specifies the
user's authentication key.
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 |
EXCLUDEOBJECTS-LIST_ELEMENT_NUMBER
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:ownerValue1st, objectName:objectNameValue1st
EXCLUDEOBJECTS-1=owner:ownerValue2nd, objectName:objectNameValue2nd
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value. |
Range of values |
Only You can filter owner and object values by any valid pattern in Java class Pattern. For example, you can enter .* in the
|
GOLDENGATEHUB_ADMINUSERNAME
For online logical migration, you must set the
GOLDENGATEHUB
parameters to provide Zero Downtime Migration with
details about Oracle GoldenGate Microservices configuration.
GOLDENGATEHUB_ADMINUSERNAME
specifies the GoldenGate hub administrator
user name.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Range of values |
Oracle GoldenGate hub's administrator user name |
GOLDENGATEHUB_COMPUTEID
For online logical migration, you must set the
GOLDENGATEHUB
parameters to provide ZDM with details about Oracle
GoldenGate Microservices configuration. GOLDENGATEHUB_COMPUTEID
specifies
the Oracle Cloud identifier of the VM.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Range of values |
Oracle Cloud identifier of the VM |
GOLDENGATEHUB_SOURCEDEPLOYMENTNAME
For online logical migration, you must set the
GOLDENGATEHUB
parameters to provide ZDM with details about Oracle
GoldenGate Microservices configuration. GOLDENGATEHUB_SOURCEDEPLOYMENTNAME
specifies the name of the GoldenGate Microservices deployment to operate on the source
database.
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 |
GOLDENGATEHUB_TARGETDEPLOYMENTNAME
For online logical migration, you must set the
GOLDENGATEHUB
parameters to provide ZDM with details about Oracle
GoldenGate Microservices configuration. GOLDENGATEHUB_TARGETDEPLOYMENTNAME
specifies the name of the GoldenGate Microservices deployment to operate on the target
database.
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 |
GOLDENGATEHUB_URL
For online logical migration, you must set the
GOLDENGATEHUB
parameters to provide ZDM with details about Oracle
GoldenGate Microservices configuration. GOLDENGATEHUB_URL
specifies the
Oracle GoldenGate hub's REST endpoint.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Range of values |
Oracle GoldenGate hub's REST endpoint |
GOLDENGATESETTINGS_ACCEPTABLELAG
For online logical migration, you can set the optional
GOLDENGATESETTINGS
parameters to provide ZDM with details about Oracle
GoldenGate Microservices configuration. ZDM will monitor GoldenGate end-to-end latency
until the lag time is lower than the specified value, in seconds, in
GOLDENGATESETTINGS_ACCEPTABLELAG
.
Property | Description |
---|---|
Syntax |
|
Default value |
30 seconds |
GOLDENGATESETTINGS_EXTRACT_NAME
GOLDENGATESETTINGS_EXTRACT_NAME
specifies a name for the
Extract processes.
For online logical migration, you can set the optional
GOLDENGATESETTINGS
parameters to provide ZDM with details about
Oracle GoldenGate Microservices configuration.
The GOLDENGATESETTINGS_EXTRACT
parameters define settings for the
Integrated Extract process. Only one Extract can be configured.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Valid values |
A string value is expected |
GOLDENGATESETTINGS_EXTRACT_PERFORMANCEPROFILE
GOLDENGATESETTINGS_EXTRACT_PERFORMANCEPROFILE
tunes
Integrated Capture. Use this setting to automatically configure relevant parameters to
achieve the desired throughput and latency. This parameter is optional.
For online logical migration, you can set the optional
GOLDENGATESETTINGS
parameters to provide ZDM with details about
Oracle GoldenGate Microservices configuration.
The GOLDENGATESETTINGS_EXTRACT
parameters define settings for the
Integrated Extract process. Only one Extract can be configured.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Valid values |
|
GOLDENGATESETTINGS_EXTRACT_WARNLONGTRANS_CHECKINTERVAL
GOLDENGATESETTINGS_EXTRACT_WARNLONGTRANS_CHECKINTERVAL
specifies the frequency in seconds with which Oracle GoldenGate checks for long-running
transactions. This parameter is optional.
For online logical migration, you can set the optional
GOLDENGATESETTINGS
parameters to provide ZDM with details about
Oracle GoldenGate Microservices configuration.
The GOLDENGATESETTINGS_EXTRACT
parameters define
settings for the Integrated Extract process. Only one Extract can be configured.
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.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Valid values |
An integer value is expected |
GOLDENGATESETTINGS_EXTRACT_WARNLONGTRANS_DURATION
GOLDENGATESETTINGS_EXTRACT_WARNLONGTRANS_DURATION
specifies
a length of time in seconds that a transaction can be open before Extract generates a
warning message that the transaction is long-running. This parameter is
optional.
For online logical migration, you can set the optional
GOLDENGATESETTINGS
parameters to provide ZDM with details about
Oracle GoldenGate Microservices configuration.
The GOLDENGATESETTINGS_EXTRACT
parameters define
settings for the Integrated Extract process. Only one Extract can be configured.
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.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Valid values |
An integer value is expected |
GOLDENGATESETTINGS_REPLICAT_MAPPARALLELISM
GOLDENGATESETTINGS_REPLICAT_MAPPARALLELISM
specifies the
number of threads used to read trail files (valid for Parallel Replicat). This parameter is
optional.
For online logical migration, you can set the optional
GOLDENGATESETTINGS
parameters to provide ZDM with details about
Oracle GoldenGate Microservices configuration.
The GOLDENGATESETTINGS_REPLICAT
parameters define
settings for the Parallel Replicat process.
Property | Description |
---|---|
Syntax |
|
Default value |
4 |
Valid values |
An integer value is expected |
GOLDENGATESETTINGS_REPLICAT_MAXAPPLYPARALLELISM
GOLDENGATESETTINGS_REPLICAT_MAXAPPLYPARALLELISM
defines the
range in which the Replicat automatically adjusts its apply parallelism (valid for Parallel
Replicat). This parameter is optional.
For online logical migration, you can set the optional
GOLDENGATESETTINGS
parameters to provide ZDM with details about
Oracle GoldenGate Microservices configuration.
The GOLDENGATESETTINGS_REPLICAT
parameters define
settings for the Parallel Replicat process.
Property | Description |
---|---|
Syntax |
|
Default value |
50 |
Valid values |
An integer value is expected |
GOLDENGATESETTINGS_REPLICAT_MINAPPLYPARALLELISM
GOLDENGATESETTINGS_REPLICAT_MINAPPLYPARALLELISM
defines the
range in which the Replicat automatically adjusts its apply parallelism (valid for Parallel
Replicat). This parameter is optional.
For online logical migration, you can set the optional
GOLDENGATESETTINGS
parameters to provide ZDM with details about
Oracle GoldenGate Microservices configuration.
The GOLDENGATESETTINGS_REPLICAT
parameters define
settings for the Parallel Replicat process.
Property | Description |
---|---|
Syntax |
|
Default value |
4 |
Valid values |
An integer value is expected |
GOLDENGATESETTINGS_REPLICAT_NAME
GOLDENGATESETTINGS_REPLICAT_NAME
specifies a name for the
Replicat process. This parameter is optional.
For online logical migration, you can set the optional
GOLDENGATESETTINGS
parameters to provide ZDM with details about
Oracle GoldenGate Microservices configuration.
The GOLDENGATESETTINGS_REPLICAT
parameters define
settings for the Parallel Replicat process.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Valid values |
A string value is expected |
INCLUDEOBJECTS-LIST_ELEMENT_NUMBER
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:ownerValue1st, objectName:objectNameValue1st
INCLUDEOBJECTS-1=owner:ownerValue2nd, objectName:objectNameValue2nd
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Range of values |
An entry specifying the owner and object name is expected, as shown in the examples above. |
MIGRATION_TYPE
In a logical migration, the required MIGRATION_TYPE
parameter specifies whether the migration is online or offline.
Property | Description |
---|---|
Syntax |
|
Default value |
|
Range of values |
|
OCIAUTHENTICATIONDETAILS_REGIONID
To call REST APIs, you must configure the
OCIAUTHENTICATIONDETAILS
parameters.
OCIAUTHENTICATIONDETAILS_REGIONID
specifies the OCI region
identifier.
See the Region Identifier column in the table at Regions and Availability Domains.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
OCIAUTHENTICATIONDETAILS_USERPRINCIPAL_FINGERPRINT
To call REST APIs, you must configure the
OCIAUTHENTICATIONDETAILS
parameters.
OCIAUTHENTICATIONDETAILS_USERPRINCIPAL_FINGERPRINT
specifies the
fingerprint of the public API key.
See Required Keys and OCIDs for more information.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
OCIAUTHENTICATIONDETAILS_USERPRINCIPAL_PRIVATEKEYFILE
To call REST APIs, you must configure the
OCIAUTHENTICATIONDETAILS
parameters.
OCIAUTHENTICATIONDETAILS_USERPRINCIPAL_PRIVATEKEYFILE
specifies the
absolute path of API private key file.
See Required Keys and OCIDs for more information.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
OCIAUTHENTICATIONDETAILS_USERPRINCIPAL_TENANTID
To call OCI REST APIs, you must configure the
OCIAUTHENTICATIONDETAILS
parameters.
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.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
Valid values |
A string value is expected |
OCIAUTHENTICATIONDETAILS_USERPRINCIPAL_USERID
To call OCI REST APIs, you must configure the
OCIAUTHENTICATIONDETAILS
parameters.
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.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
OCIPROXY_HOSTNAME
The OCIPROXY
parameters specify details about the proxy for
connecting to OCI REST endpoints. OCIPROXY_HOSTNAME
specifies the HTTP
proxy host name.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
OCIPROXY_PORT
The OCIPROXY
parameters specify details about the proxy for
connecting to OCI REST endpoints. OCIPROXY_PORT
specifies the HTTP proxy
port number.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCECONTAINERDATABASE_ADMINUSERNAME
For online logical migrations, the SOURCECONTAINERDATABASE
parameters specify connection details for the source container root.
SOURCECONTAINERDATABASE_ADMINUSERNAME
specifies the database
administrator user name.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IDENTITYFILE
For online logical migrations, the SOURCECONTAINERDATABASE
parameters specify connection details for the source container root.
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IDENTITYFILE
specifies the identity file to access bastion, as part of the database connection details
for bastion-based access to database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IP
For online logical migrations, the SOURCECONTAINERDATABASE
parameters specify connection details for the source container root.
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IP
specifies
the IP addressof the bastion host, as part of the database connection details for
bastion-based access to database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_PORT
For online logical migrations, the SOURCECONTAINERDATABASE
parameters specify connection details for the source container root.
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_PORT
specifies
the bastion host port detail, as part of the database connection details for bastion-based
access to database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_REMOTEHOSTIP
For online logical migrations, the SOURCECONTAINERDATABASE
parameters specify connection details for the source container root.
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 database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_USERNAME
For online logical migrations, the SOURCECONTAINERDATABASE
parameters specify connection details for the source container root.
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_USERNAME
specifies the user name to access the bastion, as part of the database connection details
for bastion-based access to database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_HOST
For online logical migrations, the SOURCECONTAINERDATABASE
parameters specify connection details for the source container root.
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_HOST
specifies the listener
host name or IP address. Not required for migrations to Autonomous Database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PORT
For online logical migrations, the SOURCECONTAINERDATABASE
parameters specify connection details for the source container root.
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PORT
specifies the listener
port number. Not required for migrations to Autonomous Database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS_HOSTNAME
For online logical migrations, the
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS
parameters
specify connection details for the source container root through an HTTP proxy.
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS_HOSTNAME
specifies the HTTPS proxy host name.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PORT
For online logical migrations, the
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS
parameters
specify connection details for the source container root through an HTTP proxy.
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PORT
specifies
the HTTPS proxy host port number.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_SERVICENAME
For online logical migrations, the SOURCECONTAINERDATABASE
parameters specify connection details for the source container root.
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_SERVICENAME
specifies the
fully qualified service name. Not required for Autonomous Database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_TLSDETAILS_CREDENTIALSLOCATION
For online logical migrations, the
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_TLSDETAILS
parameters specify
details for TLS connection to the database. These settings are not required if you are using
TCP.
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_TLSDETAILS_CREDENTIALSLOCATION
specifies the directory containing client credentials (wallet, keystore, trustfile, etc.).
Not required for Autonomous Database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_TLSDETAILS_DISTINGUISHEDNAME
For online logical migrations, the
SOURCECONTAINERDATABASE_CONNECTIONDETAILS_TLSDETAILS
parameters specify
details for TLS connection to the database. These settings are not required if you are using
TCP. SOURCECONTAINERDATABASE_CONNECTIONDETAILS_TLSDETAILS_DISTINGUISHEDNAME
specifies the distinguished name (DN) of the database server
(SSL_SERVER_CERT_DN
). Not required for Autonomous Database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCECONTAINERDATABASE_GGADMINUSERNAME
For online logical migrations, the SOURCECONTAINERDATABASE
parameters specify connection details for the source container root.
SOURCECONTAINERDATABASE_GGADMINUSERNAME
specifies the GoldenGate
administrator username.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCEDATABASE_ADMINUSERNAME
The SOURCEDATABASE
parameters specify connection
details for the source database. SOURCEDATABASE_ADMINUSERNAME
specifies the
source database administrator user name.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IDENTITYFILE
The SOURCEDATABASE
parameters specify connection
details for the source database. For bastion-based access to the database,
SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IDENTITYFILE
specifies
the identity file to access the bastion.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IP
The SOURCEDATABASE
parameters specify connection
details for the source database. For bastion-based access to the database,
SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IP
specifies the IP
address of the bastion host.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_PORT
The SOURCEDATABASE
parameters specify connection
details for the source database. For bastion-based access to the database,
SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_PORT
specifies the port
number of the bastion host.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_REMOTEHOSTIP
The SOURCEDATABASE
parameters specify connection
details for the source database. For bastion-based access to the database,
SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_REMOTEHOSTIP
specifies
the remote host IP address to access from the bastion.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_USERNAME
The SOURCEDATABASE
parameters specify connection
details for the source database. For bastion-based access to the database,
SOURCEDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_USERNAME
specifies the
user name to access the bastion.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCEDATABASE_CONNECTIONDETAILS_HOST
The SOURCEDATABASE
parameters specify connection
details for the source database. SOURCEDATABASE_CONNECTIONDETAILS_HOST
specifies the listener host name or IP address. Not required for Autonomous
Database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCEDATABASE_CONNECTIONDETAILS_PORT
The SOURCEDATABASE
parameters specify connection
details for the source database. SOURCEDATABASE_CONNECTIONDETAILS_PORT
specifies the listener port number. Not required for Autonomous Database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCEDATABASE_CONNECTIONDETAILS_PROXYDETAILS_HOSTNAME
The SOURCEDATABASE
parameters specify connection
details for the source database. For connecting to the source database through an HTTPS
proxy, SOURCEDATABASE_CONNECTIONDETAILS_PROXYDETAILS_HOSTNAME
specifies the
proxy host name.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCEDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PORT
The SOURCEDATABASE
parameters specify connection
details for the source database. For connecting to the source database through an HTTPS
proxy, SOURCEDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PORT
specifies the
HTTP proxy port number.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCEDATABASE_CONNECTIONDETAILS_SERVICENAME
The SOURCEDATABASE
parameters specify connection
details for the source database.
SOURCEDATABASE_CONNECTIONDETAILS_SERVICENAME
specifies the fully
qualified service name. Not required for Autonomous Database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCEDATABASE_CONNECTIONDETAILS_TLSDETAILS_CREDENTIALSLOCATION
The SOURCEDATABASE
parameters specify connection
details for the source database. For a TLS connection to the database, set
SOURCEDATABASE_CONNECTIONDETAILS_TLSDETAILS_CREDENTIALSLOCATION
, which
specifies the directory containing client credentials (wallet, keystore, trustfile, etc.)
Not required if using TCP. Not required for Autonomous Database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCEDATABASE_CONNECTIONDETAILS_TLSDETAILS_DISTINGUISHEDNAME
The SOURCEDATABASE
parameters specify connection
details for the source database. For a TLS connection to the database, set
SOURCEDATABASE_CONNECTIONDETAILS_TLSDETAILS_DISTINGUISHEDNAME
, which
specifies the distinguished name (DN) of the database server
(SSL_SERVER_CERT_DN
). Not required if using TCP. Not required for
Autonomous Database.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
SOURCEDATABASE_GGADMINUSERNAME
The SOURCEDATABASE
parameters specify connection details
for the source database. For online logical migrations,
SOURCEDATABASE_GGADMINUSERNAME
specifies the GoldenGate administrator
user name.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
TARGETDATABASE_ADMINUSERNAME
The TARGETDATABASE
parameters specify connection details
for the target OCI database. TARGETDATABASE_ADMINUSERNAME
specifies the
database administrator user name.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IDENTITYFILE
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. For bastion-based access to
database, TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IDENTITYFILE
specifies the identity file to access the bastion.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IP
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. For bastion-based access to
database, TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_IP
specifies the
IP address of the bastion host.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_PORT
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. For bastion-based access to
database, TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_PORT
specifies
the port number of the bastion host.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_REMOTEHOSTIP
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. For bastion-based access to
database, TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_REMOTEHOSTIP
specifies the remote host IP address to access from the bastion.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_USERNAME
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. For bastion-based access to
database, TARGETDATABASE_CONNECTIONDETAILS_BASTIONDETAILS_USERNAME
specifies the user name to access the bastion.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
TARGETDATABASE_CONNECTIONDETAILS_HOST
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.
TARGETDATABASE_CONNECTIONDETAILS_HOST
specifies the listener host name
or IP address.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
TARGETDATABASE_CONNECTIONDETAILS_PORT
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.
TARGETDATABASE_CONNECTIONDETAILS_PORT
specifies the listener port
number.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
TARGETDATABASE_CONNECTIONDETAILS_PROXYDETAILS_HOSTNAME
The TARGETDATABASE_CONNECTIONDETAILS
parameters specify
connection details for the target OCI database. For connecting to the target database
through an HTTPS proxy,
TARGETDATABASE_CONNECTIONDETAILS_PROXYDETAILS_HOSTNAME
specifies the
proxy host name.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
TARGETDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PORT
The TARGETDATABASE_CONNECTIONDETAILS
parameters specify
connection details for the target OCI database. For connecting to the source database
through an HTTPS proxy, TARGETDATABASE_CONNECTIONDETAILS_PROXYDETAILS_PORT
specifies the HTTP proxy port number.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
TARGETDATABASE_CONNECTIONDETAILS_SERVICENAME
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.
TARGETDATABASE_CONNECTIONDETAILS_SERVICENAME
specifies the fully
qualified service name.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
TARGETDATABASE_CONNECTIONDETAILS_TLSDETAILS_CREDENTIALSLOCATION
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. For a TLS connection,
TARGETDATABASE_CONNECTIONDETAILS_TLSDETAILS_CREDENTIALSLOCATION
specifies the directory containing client credentials (wallet, keystore, trustfile, etc.)
Not required if using TCP.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
TARGETDATABASE_CONNECTIONDETAILS_TLSDETAILS_DISTINGUISHEDNAME
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. For a TLS connection,
TARGETDATABASE_CONNECTIONDETAILS_TLSDETAILS_DISTINGUISHEDNAME
specifies
the distinguished name (DN) of the database server (SSL_SERVER_CERT_DN
).
Not required if using TCP.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |
TARGETDATABASE_GGADMINUSERNAME
The TARGETDATABASE
parameters specify connection details
for the target OCI database. For online logical migrations,
TARGETDATABASE_GGADMINUSERNAME
specifies the GoldenGate administrator
user name.
Property | Description |
---|---|
Syntax |
|
Default value |
There is no default value |