#[non_exhaustive]pub struct OracleSettings {Show 44 fields
pub add_supplemental_logging: Option<bool>,
pub archived_log_dest_id: Option<i32>,
pub additional_archived_log_dest_id: Option<i32>,
pub extra_archived_log_dest_ids: Option<Vec<i32>>,
pub allow_select_nested_tables: Option<bool>,
pub parallel_asm_read_threads: Option<i32>,
pub read_ahead_blocks: Option<i32>,
pub access_alternate_directly: Option<bool>,
pub use_alternate_folder_for_online: Option<bool>,
pub oracle_path_prefix: Option<String>,
pub use_path_prefix: Option<String>,
pub replace_path_prefix: Option<bool>,
pub enable_homogenous_tablespace: Option<bool>,
pub direct_path_no_log: Option<bool>,
pub archived_logs_only: Option<bool>,
pub asm_password: Option<String>,
pub asm_server: Option<String>,
pub asm_user: Option<String>,
pub char_length_semantics: Option<CharLengthSemantics>,
pub database_name: Option<String>,
pub direct_path_parallel_load: Option<bool>,
pub fail_tasks_on_lob_truncation: Option<bool>,
pub number_datatype_scale: Option<i32>,
pub password: Option<String>,
pub port: Option<i32>,
pub read_table_space_name: Option<bool>,
pub retry_interval: Option<i32>,
pub security_db_encryption: Option<String>,
pub security_db_encryption_name: Option<String>,
pub server_name: Option<String>,
pub spatial_data_option_to_geo_json_function_name: Option<String>,
pub standby_delay_time: Option<i32>,
pub username: Option<String>,
pub use_b_file: Option<bool>,
pub use_direct_path_full_load: Option<bool>,
pub use_logminer_reader: Option<bool>,
pub secrets_manager_access_role_arn: Option<String>,
pub secrets_manager_secret_id: Option<String>,
pub secrets_manager_oracle_asm_access_role_arn: Option<String>,
pub secrets_manager_oracle_asm_secret_id: Option<String>,
pub trim_space_in_char: Option<bool>,
pub convert_timestamp_with_zone_to_utc: Option<bool>,
pub open_transaction_window: Option<i32>,
pub authentication_method: Option<OracleAuthenticationMethod>,
}
Expand description
Provides information that defines an Oracle endpoint.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.add_supplemental_logging: Option<bool>
Set this attribute to set up table-level supplemental logging for the Oracle database. This attribute enables PRIMARY KEY supplemental logging on all tables selected for a migration task.
If you use this option, you still need to enable database-level supplemental logging.
archived_log_dest_id: Option<i32>
Specifies the ID of the destination for the archived redo logs. This value should be the same as a number in the dest_id column of the v$archived_log view. If you work with an additional redo log destination, use the AdditionalArchivedLogDestId
option to specify the additional destination ID. Doing this improves performance by ensuring that the correct logs are accessed from the outset.
additional_archived_log_dest_id: Option<i32>
Set this attribute with ArchivedLogDestId
in a primary/ standby setup. This attribute is useful in the case of a switchover. In this case, DMS needs to know which destination to get archive redo logs from to read changes. This need arises because the previous primary instance is now a standby instance after switchover.
Although DMS supports the use of the Oracle RESETLOGS
option to open the database, never use RESETLOGS
unless necessary. For additional information about RESETLOGS
, see RMAN Data Repair Concepts in the Oracle Database Backup and Recovery User's Guide.
extra_archived_log_dest_ids: Option<Vec<i32>>
Specifies the IDs of one more destinations for one or more archived redo logs. These IDs are the values of the dest_id
column in the v$archived_log
view. Use this setting with the archivedLogDestId
extra connection attribute in a primary-to-single setup or a primary-to-multiple-standby setup.
This setting is useful in a switchover when you use an Oracle Data Guard database as a source. In this case, DMS needs information about what destination to get archive redo logs from to read changes. DMS needs this because after the switchover the previous primary is a standby instance. For example, in a primary-to-single standby setup you might apply the following settings.
archivedLogDestId=1; ExtraArchivedLogDestIds=\[2\]
In a primary-to-multiple-standby setup, you might apply the following settings.
archivedLogDestId=1; ExtraArchivedLogDestIds=\[2,3,4\]
Although DMS supports the use of the Oracle RESETLOGS
option to open the database, never use RESETLOGS
unless it's necessary. For more information about RESETLOGS
, see RMAN Data Repair Concepts in the Oracle Database Backup and Recovery User's Guide.
allow_select_nested_tables: Option<bool>
Set this attribute to true
to enable replication of Oracle tables containing columns that are nested tables or defined types.
parallel_asm_read_threads: Option<i32>
Set this attribute to change the number of threads that DMS configures to perform a change data capture (CDC) load using Oracle Automatic Storage Management (ASM). You can specify an integer value between 2 (the default) and 8 (the maximum). Use this attribute together with the readAheadBlocks
attribute.
read_ahead_blocks: Option<i32>
Set this attribute to change the number of read-ahead blocks that DMS configures to perform a change data capture (CDC) load using Oracle Automatic Storage Management (ASM). You can specify an integer value between 1000 (the default) and 200,000 (the maximum).
access_alternate_directly: Option<bool>
Set this attribute to false
in order to use the Binary Reader to capture change data for an Amazon RDS for Oracle as the source. This tells the DMS instance to not access redo logs through any specified path prefix replacement using direct file access.
use_alternate_folder_for_online: Option<bool>
Set this attribute to true
in order to use the Binary Reader to capture change data for an Amazon RDS for Oracle as the source. This tells the DMS instance to use any specified prefix replacement to access all online redo logs.
oracle_path_prefix: Option<String>
Set this string attribute to the required value in order to use the Binary Reader to capture change data for an Amazon RDS for Oracle as the source. This value specifies the default Oracle root used to access the redo logs.
use_path_prefix: Option<String>
Set this string attribute to the required value in order to use the Binary Reader to capture change data for an Amazon RDS for Oracle as the source. This value specifies the path prefix used to replace the default Oracle root to access the redo logs.
replace_path_prefix: Option<bool>
Set this attribute to true in order to use the Binary Reader to capture change data for an Amazon RDS for Oracle as the source. This setting tells DMS instance to replace the default Oracle root with the specified usePathPrefix
setting to access the redo logs.
enable_homogenous_tablespace: Option<bool>
Set this attribute to enable homogenous tablespace replication and create existing tables or indexes under the same tablespace on the target.
direct_path_no_log: Option<bool>
When set to true
, this attribute helps to increase the commit rate on the Oracle target database by writing directly to tables and not writing a trail to database logs.
archived_logs_only: Option<bool>
When this field is set to True
, DMS only accesses the archived redo logs. If the archived redo logs are stored on Automatic Storage Management (ASM) only, the DMS user account needs to be granted ASM privileges.
asm_password: Option<String>
For an Oracle source endpoint, your Oracle Automatic Storage Management (ASM) password. You can set this value from the asm_user_password
value. You set this value as part of the comma-separated value that you set to the Password
request parameter when you create the endpoint to access transaction logs using Binary Reader. For more information, see Configuration for change data capture (CDC) on an Oracle source database.
asm_server: Option<String>
For an Oracle source endpoint, your ASM server address. You can set this value from the asm_server
value. You set asm_server
as part of the extra connection attribute string to access an Oracle server with Binary Reader that uses ASM. For more information, see Configuration for change data capture (CDC) on an Oracle source database.
asm_user: Option<String>
For an Oracle source endpoint, your ASM user name. You can set this value from the asm_user
value. You set asm_user
as part of the extra connection attribute string to access an Oracle server with Binary Reader that uses ASM. For more information, see Configuration for change data capture (CDC) on an Oracle source database.
char_length_semantics: Option<CharLengthSemantics>
Specifies whether the length of a character column is in bytes or in characters. To indicate that the character column length is in characters, set this attribute to CHAR
. Otherwise, the character column length is in bytes.
Example: charLengthSemantics=CHAR;
database_name: Option<String>
Database name for the endpoint.
direct_path_parallel_load: Option<bool>
When set to true
, this attribute specifies a parallel load when useDirectPathFullLoad
is set to Y
. This attribute also only applies when you use the DMS parallel load feature. Note that the target table cannot have any constraints or indexes.
fail_tasks_on_lob_truncation: Option<bool>
When set to true
, this attribute causes a task to fail if the actual size of an LOB column is greater than the specified LobMaxSize
.
If a task is set to limited LOB mode and this option is set to true
, the task fails instead of truncating the LOB data.
number_datatype_scale: Option<i32>
Specifies the number scale. You can select a scale up to 38, or you can select FLOAT. By default, the NUMBER data type is converted to precision 38, scale 10.
Example: numberDataTypeScale=12
password: Option<String>
Endpoint connection password.
port: Option<i32>
Endpoint TCP port.
read_table_space_name: Option<bool>
When set to true
, this attribute supports tablespace replication.
retry_interval: Option<i32>
Specifies the number of seconds that the system waits before resending a query.
Example: retryInterval=6;
security_db_encryption: Option<String>
For an Oracle source endpoint, the transparent data encryption (TDE) password required by AWM DMS to access Oracle redo logs encrypted by TDE using Binary Reader. It is also the TDE_Password
part of the comma-separated value you set to the Password
request parameter when you create the endpoint. The SecurityDbEncryptian
setting is related to this SecurityDbEncryptionName
setting. For more information, see Supported encryption methods for using Oracle as a source for DMS in the Database Migration Service User Guide.
security_db_encryption_name: Option<String>
For an Oracle source endpoint, the name of a key used for the transparent data encryption (TDE) of the columns and tablespaces in an Oracle source database that is encrypted using TDE. The key value is the value of the SecurityDbEncryption
setting. For more information on setting the key name value of SecurityDbEncryptionName
, see the information and example for setting the securityDbEncryptionName
extra connection attribute in Supported encryption methods for using Oracle as a source for DMS in the Database Migration Service User Guide.
server_name: Option<String>
Fully qualified domain name of the endpoint.
For an Amazon RDS Oracle instance, this is the output of DescribeDBInstances, in the Endpoint.Address
field.
spatial_data_option_to_geo_json_function_name: Option<String>
Use this attribute to convert SDO_GEOMETRY
to GEOJSON
format. By default, DMS calls the SDO2GEOJSON
custom function if present and accessible. Or you can create your own custom function that mimics the operation of SDOGEOJSON
and set SpatialDataOptionToGeoJsonFunctionName
to call it instead.
standby_delay_time: Option<i32>
Use this attribute to specify a time in minutes for the delay in standby sync. If the source is an Oracle Active Data Guard standby database, use this attribute to specify the time lag between primary and standby databases.
In DMS, you can create an Oracle CDC task that uses an Active Data Guard standby instance as a source for replicating ongoing changes. Doing this eliminates the need to connect to an active database that might be in production.
username: Option<String>
Endpoint connection user name.
use_b_file: Option<bool>
Set this attribute to True to capture change data using the Binary Reader utility. Set UseLogminerReader
to False to set this attribute to True. To use Binary Reader with Amazon RDS for Oracle as the source, you set additional attributes. For more information about using this setting with Oracle Automatic Storage Management (ASM), see Using Oracle LogMiner or DMS Binary Reader for CDC.
use_direct_path_full_load: Option<bool>
Set this attribute to True to have DMS use a direct path full load. Specify this value to use the direct path protocol in the Oracle Call Interface (OCI). By using this OCI protocol, you can bulk-load Oracle target tables during a full load.
use_logminer_reader: Option<bool>
Set this attribute to True to capture change data using the Oracle LogMiner utility (the default). Set this attribute to False if you want to access the redo logs as a binary file. When you set UseLogminerReader
to False, also set UseBfile
to True. For more information on this setting and using Oracle ASM, see Using Oracle LogMiner or DMS Binary Reader for CDC in the DMS User Guide.
secrets_manager_access_role_arn: Option<String>
The full Amazon Resource Name (ARN) of the IAM role that specifies DMS as the trusted entity and grants the required permissions to access the value in SecretsManagerSecret
. The role must allow the iam:PassRole
action. SecretsManagerSecret
has the value of the Amazon Web Services Secrets Manager secret that allows access to the Oracle endpoint.
You can specify one of two sets of values for these permissions. You can specify the values for this setting and SecretsManagerSecretId
. Or you can specify clear-text values for UserName
, Password
, ServerName
, and Port
. You can't specify both. For more information on creating this SecretsManagerSecret
and the SecretsManagerAccessRoleArn
and SecretsManagerSecretId
required to access it, see Using secrets to access Database Migration Service resources in the Database Migration Service User Guide.
secrets_manager_secret_id: Option<String>
The full ARN, partial ARN, or friendly name of the SecretsManagerSecret
that contains the Oracle endpoint connection details.
secrets_manager_oracle_asm_access_role_arn: Option<String>
Required only if your Oracle endpoint uses Automatic Storage Management (ASM). The full ARN of the IAM role that specifies DMS as the trusted entity and grants the required permissions to access the SecretsManagerOracleAsmSecret
. This SecretsManagerOracleAsmSecret
has the secret value that allows access to the Oracle ASM of the endpoint.
You can specify one of two sets of values for these permissions. You can specify the values for this setting and SecretsManagerOracleAsmSecretId
. Or you can specify clear-text values for AsmUser
, AsmPassword
, and AsmServerName
. You can't specify both. For more information on creating this SecretsManagerOracleAsmSecret
and the SecretsManagerOracleAsmAccessRoleArn
and SecretsManagerOracleAsmSecretId
required to access it, see Using secrets to access Database Migration Service resources in the Database Migration Service User Guide.
secrets_manager_oracle_asm_secret_id: Option<String>
Required only if your Oracle endpoint uses Automatic Storage Management (ASM). The full ARN, partial ARN, or friendly name of the SecretsManagerOracleAsmSecret
that contains the Oracle ASM connection details for the Oracle endpoint.
trim_space_in_char: Option<bool>
Use the TrimSpaceInChar
source endpoint setting to trim data on CHAR and NCHAR data types during migration. The default value is true
.
convert_timestamp_with_zone_to_utc: Option<bool>
When true, converts timestamps with the timezone
datatype to their UTC value.
open_transaction_window: Option<i32>
The timeframe in minutes to check for open transactions for a CDC-only task.
You can specify an integer value between 0 (the default) and 240 (the maximum).
This parameter is only valid in DMS version 3.5.0 and later.
authentication_method: Option<OracleAuthenticationMethod>
Specifies using Kerberos authentication with Oracle.
Implementations§
Source§impl OracleSettings
impl OracleSettings
Sourcepub fn add_supplemental_logging(&self) -> Option<bool>
pub fn add_supplemental_logging(&self) -> Option<bool>
Set this attribute to set up table-level supplemental logging for the Oracle database. This attribute enables PRIMARY KEY supplemental logging on all tables selected for a migration task.
If you use this option, you still need to enable database-level supplemental logging.
Sourcepub fn archived_log_dest_id(&self) -> Option<i32>
pub fn archived_log_dest_id(&self) -> Option<i32>
Specifies the ID of the destination for the archived redo logs. This value should be the same as a number in the dest_id column of the v$archived_log view. If you work with an additional redo log destination, use the AdditionalArchivedLogDestId
option to specify the additional destination ID. Doing this improves performance by ensuring that the correct logs are accessed from the outset.
Sourcepub fn additional_archived_log_dest_id(&self) -> Option<i32>
pub fn additional_archived_log_dest_id(&self) -> Option<i32>
Set this attribute with ArchivedLogDestId
in a primary/ standby setup. This attribute is useful in the case of a switchover. In this case, DMS needs to know which destination to get archive redo logs from to read changes. This need arises because the previous primary instance is now a standby instance after switchover.
Although DMS supports the use of the Oracle RESETLOGS
option to open the database, never use RESETLOGS
unless necessary. For additional information about RESETLOGS
, see RMAN Data Repair Concepts in the Oracle Database Backup and Recovery User's Guide.
Sourcepub fn extra_archived_log_dest_ids(&self) -> &[i32]
pub fn extra_archived_log_dest_ids(&self) -> &[i32]
Specifies the IDs of one more destinations for one or more archived redo logs. These IDs are the values of the dest_id
column in the v$archived_log
view. Use this setting with the archivedLogDestId
extra connection attribute in a primary-to-single setup or a primary-to-multiple-standby setup.
This setting is useful in a switchover when you use an Oracle Data Guard database as a source. In this case, DMS needs information about what destination to get archive redo logs from to read changes. DMS needs this because after the switchover the previous primary is a standby instance. For example, in a primary-to-single standby setup you might apply the following settings.
archivedLogDestId=1; ExtraArchivedLogDestIds=\[2\]
In a primary-to-multiple-standby setup, you might apply the following settings.
archivedLogDestId=1; ExtraArchivedLogDestIds=\[2,3,4\]
Although DMS supports the use of the Oracle RESETLOGS
option to open the database, never use RESETLOGS
unless it's necessary. For more information about RESETLOGS
, see RMAN Data Repair Concepts in the Oracle Database Backup and Recovery User's Guide.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .extra_archived_log_dest_ids.is_none()
.
Sourcepub fn allow_select_nested_tables(&self) -> Option<bool>
pub fn allow_select_nested_tables(&self) -> Option<bool>
Set this attribute to true
to enable replication of Oracle tables containing columns that are nested tables or defined types.
Sourcepub fn parallel_asm_read_threads(&self) -> Option<i32>
pub fn parallel_asm_read_threads(&self) -> Option<i32>
Set this attribute to change the number of threads that DMS configures to perform a change data capture (CDC) load using Oracle Automatic Storage Management (ASM). You can specify an integer value between 2 (the default) and 8 (the maximum). Use this attribute together with the readAheadBlocks
attribute.
Sourcepub fn read_ahead_blocks(&self) -> Option<i32>
pub fn read_ahead_blocks(&self) -> Option<i32>
Set this attribute to change the number of read-ahead blocks that DMS configures to perform a change data capture (CDC) load using Oracle Automatic Storage Management (ASM). You can specify an integer value between 1000 (the default) and 200,000 (the maximum).
Sourcepub fn access_alternate_directly(&self) -> Option<bool>
pub fn access_alternate_directly(&self) -> Option<bool>
Set this attribute to false
in order to use the Binary Reader to capture change data for an Amazon RDS for Oracle as the source. This tells the DMS instance to not access redo logs through any specified path prefix replacement using direct file access.
Sourcepub fn use_alternate_folder_for_online(&self) -> Option<bool>
pub fn use_alternate_folder_for_online(&self) -> Option<bool>
Set this attribute to true
in order to use the Binary Reader to capture change data for an Amazon RDS for Oracle as the source. This tells the DMS instance to use any specified prefix replacement to access all online redo logs.
Sourcepub fn oracle_path_prefix(&self) -> Option<&str>
pub fn oracle_path_prefix(&self) -> Option<&str>
Set this string attribute to the required value in order to use the Binary Reader to capture change data for an Amazon RDS for Oracle as the source. This value specifies the default Oracle root used to access the redo logs.
Sourcepub fn use_path_prefix(&self) -> Option<&str>
pub fn use_path_prefix(&self) -> Option<&str>
Set this string attribute to the required value in order to use the Binary Reader to capture change data for an Amazon RDS for Oracle as the source. This value specifies the path prefix used to replace the default Oracle root to access the redo logs.
Sourcepub fn replace_path_prefix(&self) -> Option<bool>
pub fn replace_path_prefix(&self) -> Option<bool>
Set this attribute to true in order to use the Binary Reader to capture change data for an Amazon RDS for Oracle as the source. This setting tells DMS instance to replace the default Oracle root with the specified usePathPrefix
setting to access the redo logs.
Sourcepub fn enable_homogenous_tablespace(&self) -> Option<bool>
pub fn enable_homogenous_tablespace(&self) -> Option<bool>
Set this attribute to enable homogenous tablespace replication and create existing tables or indexes under the same tablespace on the target.
Sourcepub fn direct_path_no_log(&self) -> Option<bool>
pub fn direct_path_no_log(&self) -> Option<bool>
When set to true
, this attribute helps to increase the commit rate on the Oracle target database by writing directly to tables and not writing a trail to database logs.
Sourcepub fn archived_logs_only(&self) -> Option<bool>
pub fn archived_logs_only(&self) -> Option<bool>
When this field is set to True
, DMS only accesses the archived redo logs. If the archived redo logs are stored on Automatic Storage Management (ASM) only, the DMS user account needs to be granted ASM privileges.
Sourcepub fn asm_password(&self) -> Option<&str>
pub fn asm_password(&self) -> Option<&str>
For an Oracle source endpoint, your Oracle Automatic Storage Management (ASM) password. You can set this value from the asm_user_password
value. You set this value as part of the comma-separated value that you set to the Password
request parameter when you create the endpoint to access transaction logs using Binary Reader. For more information, see Configuration for change data capture (CDC) on an Oracle source database.
Sourcepub fn asm_server(&self) -> Option<&str>
pub fn asm_server(&self) -> Option<&str>
For an Oracle source endpoint, your ASM server address. You can set this value from the asm_server
value. You set asm_server
as part of the extra connection attribute string to access an Oracle server with Binary Reader that uses ASM. For more information, see Configuration for change data capture (CDC) on an Oracle source database.
Sourcepub fn asm_user(&self) -> Option<&str>
pub fn asm_user(&self) -> Option<&str>
For an Oracle source endpoint, your ASM user name. You can set this value from the asm_user
value. You set asm_user
as part of the extra connection attribute string to access an Oracle server with Binary Reader that uses ASM. For more information, see Configuration for change data capture (CDC) on an Oracle source database.
Sourcepub fn char_length_semantics(&self) -> Option<&CharLengthSemantics>
pub fn char_length_semantics(&self) -> Option<&CharLengthSemantics>
Specifies whether the length of a character column is in bytes or in characters. To indicate that the character column length is in characters, set this attribute to CHAR
. Otherwise, the character column length is in bytes.
Example: charLengthSemantics=CHAR;
Sourcepub fn database_name(&self) -> Option<&str>
pub fn database_name(&self) -> Option<&str>
Database name for the endpoint.
Sourcepub fn direct_path_parallel_load(&self) -> Option<bool>
pub fn direct_path_parallel_load(&self) -> Option<bool>
When set to true
, this attribute specifies a parallel load when useDirectPathFullLoad
is set to Y
. This attribute also only applies when you use the DMS parallel load feature. Note that the target table cannot have any constraints or indexes.
Sourcepub fn fail_tasks_on_lob_truncation(&self) -> Option<bool>
pub fn fail_tasks_on_lob_truncation(&self) -> Option<bool>
When set to true
, this attribute causes a task to fail if the actual size of an LOB column is greater than the specified LobMaxSize
.
If a task is set to limited LOB mode and this option is set to true
, the task fails instead of truncating the LOB data.
Sourcepub fn number_datatype_scale(&self) -> Option<i32>
pub fn number_datatype_scale(&self) -> Option<i32>
Specifies the number scale. You can select a scale up to 38, or you can select FLOAT. By default, the NUMBER data type is converted to precision 38, scale 10.
Example: numberDataTypeScale=12
Sourcepub fn read_table_space_name(&self) -> Option<bool>
pub fn read_table_space_name(&self) -> Option<bool>
When set to true
, this attribute supports tablespace replication.
Sourcepub fn retry_interval(&self) -> Option<i32>
pub fn retry_interval(&self) -> Option<i32>
Specifies the number of seconds that the system waits before resending a query.
Example: retryInterval=6;
Sourcepub fn security_db_encryption(&self) -> Option<&str>
pub fn security_db_encryption(&self) -> Option<&str>
For an Oracle source endpoint, the transparent data encryption (TDE) password required by AWM DMS to access Oracle redo logs encrypted by TDE using Binary Reader. It is also the TDE_Password
part of the comma-separated value you set to the Password
request parameter when you create the endpoint. The SecurityDbEncryptian
setting is related to this SecurityDbEncryptionName
setting. For more information, see Supported encryption methods for using Oracle as a source for DMS in the Database Migration Service User Guide.
Sourcepub fn security_db_encryption_name(&self) -> Option<&str>
pub fn security_db_encryption_name(&self) -> Option<&str>
For an Oracle source endpoint, the name of a key used for the transparent data encryption (TDE) of the columns and tablespaces in an Oracle source database that is encrypted using TDE. The key value is the value of the SecurityDbEncryption
setting. For more information on setting the key name value of SecurityDbEncryptionName
, see the information and example for setting the securityDbEncryptionName
extra connection attribute in Supported encryption methods for using Oracle as a source for DMS in the Database Migration Service User Guide.
Sourcepub fn server_name(&self) -> Option<&str>
pub fn server_name(&self) -> Option<&str>
Fully qualified domain name of the endpoint.
For an Amazon RDS Oracle instance, this is the output of DescribeDBInstances, in the Endpoint.Address
field.
Sourcepub fn spatial_data_option_to_geo_json_function_name(&self) -> Option<&str>
pub fn spatial_data_option_to_geo_json_function_name(&self) -> Option<&str>
Use this attribute to convert SDO_GEOMETRY
to GEOJSON
format. By default, DMS calls the SDO2GEOJSON
custom function if present and accessible. Or you can create your own custom function that mimics the operation of SDOGEOJSON
and set SpatialDataOptionToGeoJsonFunctionName
to call it instead.
Sourcepub fn standby_delay_time(&self) -> Option<i32>
pub fn standby_delay_time(&self) -> Option<i32>
Use this attribute to specify a time in minutes for the delay in standby sync. If the source is an Oracle Active Data Guard standby database, use this attribute to specify the time lag between primary and standby databases.
In DMS, you can create an Oracle CDC task that uses an Active Data Guard standby instance as a source for replicating ongoing changes. Doing this eliminates the need to connect to an active database that might be in production.
Sourcepub fn use_b_file(&self) -> Option<bool>
pub fn use_b_file(&self) -> Option<bool>
Set this attribute to True to capture change data using the Binary Reader utility. Set UseLogminerReader
to False to set this attribute to True. To use Binary Reader with Amazon RDS for Oracle as the source, you set additional attributes. For more information about using this setting with Oracle Automatic Storage Management (ASM), see Using Oracle LogMiner or DMS Binary Reader for CDC.
Sourcepub fn use_direct_path_full_load(&self) -> Option<bool>
pub fn use_direct_path_full_load(&self) -> Option<bool>
Set this attribute to True to have DMS use a direct path full load. Specify this value to use the direct path protocol in the Oracle Call Interface (OCI). By using this OCI protocol, you can bulk-load Oracle target tables during a full load.
Sourcepub fn use_logminer_reader(&self) -> Option<bool>
pub fn use_logminer_reader(&self) -> Option<bool>
Set this attribute to True to capture change data using the Oracle LogMiner utility (the default). Set this attribute to False if you want to access the redo logs as a binary file. When you set UseLogminerReader
to False, also set UseBfile
to True. For more information on this setting and using Oracle ASM, see Using Oracle LogMiner or DMS Binary Reader for CDC in the DMS User Guide.
Sourcepub fn secrets_manager_access_role_arn(&self) -> Option<&str>
pub fn secrets_manager_access_role_arn(&self) -> Option<&str>
The full Amazon Resource Name (ARN) of the IAM role that specifies DMS as the trusted entity and grants the required permissions to access the value in SecretsManagerSecret
. The role must allow the iam:PassRole
action. SecretsManagerSecret
has the value of the Amazon Web Services Secrets Manager secret that allows access to the Oracle endpoint.
You can specify one of two sets of values for these permissions. You can specify the values for this setting and SecretsManagerSecretId
. Or you can specify clear-text values for UserName
, Password
, ServerName
, and Port
. You can't specify both. For more information on creating this SecretsManagerSecret
and the SecretsManagerAccessRoleArn
and SecretsManagerSecretId
required to access it, see Using secrets to access Database Migration Service resources in the Database Migration Service User Guide.
Sourcepub fn secrets_manager_secret_id(&self) -> Option<&str>
pub fn secrets_manager_secret_id(&self) -> Option<&str>
The full ARN, partial ARN, or friendly name of the SecretsManagerSecret
that contains the Oracle endpoint connection details.
Sourcepub fn secrets_manager_oracle_asm_access_role_arn(&self) -> Option<&str>
pub fn secrets_manager_oracle_asm_access_role_arn(&self) -> Option<&str>
Required only if your Oracle endpoint uses Automatic Storage Management (ASM). The full ARN of the IAM role that specifies DMS as the trusted entity and grants the required permissions to access the SecretsManagerOracleAsmSecret
. This SecretsManagerOracleAsmSecret
has the secret value that allows access to the Oracle ASM of the endpoint.
You can specify one of two sets of values for these permissions. You can specify the values for this setting and SecretsManagerOracleAsmSecretId
. Or you can specify clear-text values for AsmUser
, AsmPassword
, and AsmServerName
. You can't specify both. For more information on creating this SecretsManagerOracleAsmSecret
and the SecretsManagerOracleAsmAccessRoleArn
and SecretsManagerOracleAsmSecretId
required to access it, see Using secrets to access Database Migration Service resources in the Database Migration Service User Guide.
Sourcepub fn secrets_manager_oracle_asm_secret_id(&self) -> Option<&str>
pub fn secrets_manager_oracle_asm_secret_id(&self) -> Option<&str>
Required only if your Oracle endpoint uses Automatic Storage Management (ASM). The full ARN, partial ARN, or friendly name of the SecretsManagerOracleAsmSecret
that contains the Oracle ASM connection details for the Oracle endpoint.
Sourcepub fn trim_space_in_char(&self) -> Option<bool>
pub fn trim_space_in_char(&self) -> Option<bool>
Use the TrimSpaceInChar
source endpoint setting to trim data on CHAR and NCHAR data types during migration. The default value is true
.
Sourcepub fn convert_timestamp_with_zone_to_utc(&self) -> Option<bool>
pub fn convert_timestamp_with_zone_to_utc(&self) -> Option<bool>
When true, converts timestamps with the timezone
datatype to their UTC value.
Sourcepub fn open_transaction_window(&self) -> Option<i32>
pub fn open_transaction_window(&self) -> Option<i32>
The timeframe in minutes to check for open transactions for a CDC-only task.
You can specify an integer value between 0 (the default) and 240 (the maximum).
This parameter is only valid in DMS version 3.5.0 and later.
Sourcepub fn authentication_method(&self) -> Option<&OracleAuthenticationMethod>
pub fn authentication_method(&self) -> Option<&OracleAuthenticationMethod>
Specifies using Kerberos authentication with Oracle.
Source§impl OracleSettings
impl OracleSettings
Sourcepub fn builder() -> OracleSettingsBuilder
pub fn builder() -> OracleSettingsBuilder
Creates a new builder-style object to manufacture OracleSettings
.
Trait Implementations§
Source§impl Clone for OracleSettings
impl Clone for OracleSettings
Source§fn clone(&self) -> OracleSettings
fn clone(&self) -> OracleSettings
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for OracleSettings
impl Debug for OracleSettings
Source§impl PartialEq for OracleSettings
impl PartialEq for OracleSettings
impl StructuralPartialEq for OracleSettings
Auto Trait Implementations§
impl Freeze for OracleSettings
impl RefUnwindSafe for OracleSettings
impl Send for OracleSettings
impl Sync for OracleSettings
impl Unpin for OracleSettings
impl UnwindSafe for OracleSettings
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the foreground set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red()
and
green()
, which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg()
:
use yansi::{Paint, Color};
painted.fg(Color::White);
Set foreground color to white using white()
.
use yansi::Paint;
painted.white();
Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightBlack
.
§Example
println!("{}", value.bright_black());
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightGreen
.
§Example
println!("{}", value.bright_green());
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightYellow
.
§Example
println!("{}", value.bright_yellow());
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightMagenta
.
§Example
println!("{}", value.bright_magenta());
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightWhite
.
§Example
println!("{}", value.bright_white());
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the background set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red()
and
on_green()
, which have the same functionality but
are pithier.
§Example
Set background color to red using fg()
:
use yansi::{Paint, Color};
painted.bg(Color::Red);
Set background color to red using on_red()
.
use yansi::Paint;
painted.on_red();
Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightBlack
.
§Example
println!("{}", value.on_bright_black());
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightGreen
.
§Example
println!("{}", value.on_bright_green());
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightYellow
.
§Example
println!("{}", value.on_bright_yellow());
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightBlue
.
§Example
println!("{}", value.on_bright_blue());
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightMagenta
.
§Example
println!("{}", value.on_bright_magenta());
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightCyan
.
§Example
println!("{}", value.on_bright_cyan());
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightWhite
.
§Example
println!("{}", value.on_bright_white());
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute
value
.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold()
and
underline()
, which have the same functionality
but are pithier.
§Example
Make text bold using attr()
:
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);
Make text bold using using bold()
.
use yansi::Paint;
painted.bold();
Source§fn underline(&self) -> Painted<&T>
fn underline(&self) -> Painted<&T>
Returns self
with the
attr()
set to
Attribute::Underline
.
§Example
println!("{}", value.underline());
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Returns self
with the
attr()
set to
Attribute::RapidBlink
.
§Example
println!("{}", value.rapid_blink());
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi
Quirk
value
.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask()
and
wrap()
, which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk()
:
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);
Enable wrapping using wrap()
.
use yansi::Paint;
painted.wrap();
Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition
value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted
only when both stdout
and stderr
are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);