Parameter | Default (Valid Values) |
Description |
---|---|---|
AllowAccessLockInWriteRequest | FALSE (TRUE, FALSE) | When set to TRUE, Business Continuity Manager performs content replication for write requests that include an Access Lock. If set to FALSE, the Access Lock is upgraded instead. |
AutoSelfHealingInterval | 0 (0 to infinity) | The interval in seconds that the sequencer attempts to validate, re-activate, and resync any tables that have become unrecoverable due to data inconsistencies. (0 to disable). |
AutoSelfHealingOptions | 0 (0 or 1) | Controls whether the self-healing loop performs validate (0) or validate and resync (1). |
AutoSelfHealingThreads | 1 (1 to infinity) | The number of concurrent threads used to send table validation and resync requests in the self-healing loop. |
AutoTableValidateAttempts | 0 (1 to infinity) | The number of times table validation is attempted on a table that has become unrecoverable due to data inconsistency. (-1 for unlimited, 0 to disable). |
BlockedSessionThreshold_1 | 10:60:100 | These parameters are used to set the threshold values for blocked sessions, allowing you to define the sizes of these thresholds. They are essential for maintaining records and triggering alerts when blocked sessions reach predefined thresholds. Syntax: <minutes blocked>:<threshold for warning>:<threshold for critical> |
BlockedSessionThreshold_2 | 20:50:80 | |
BlockedSessionThreshold_3 | 30:40:60 | |
BlockedSessionThreshold_4 | 60:30:50 | |
BlockedSessionThreshold_5 | 120:20:40 | |
CatalogRequestTimeout | 600 (sec) | Configures the timeout value for a catalog request between processes, ensuring that the next request is only sent after the timeout period has elapsed. |
CDCForNonDetCtas | True | This parameter controls the replication of Non-Deterministic CTAS query/table on standby systems. When enabled, CTAS replication is done using CDC. If disabled, then the CTAS replication is done using content replication. |
CDMStreamSupportEnabled | True (True or False) | When enabled and supported by the Teradata system, CDM Streaming protocol is used to extract and apply change data. The parameter should only be disabled if an issue occurs when CDM Streaming is used. |
CDMMultiStreamSupportEnabled | True (True or False) | When enabled and supported by the Teradata system, CDM Multi-Stream protocol is used to extract and apply change data. The parameter should only be disabled if a issue occurs when CDM Multi-Stream is used. |
CDMSessionQueueLimit | 1000 (100 to infinity) | The maximum amount (in MB) of queued change data information held in memory for a session before Business Continuity Manager starts throttling the read of incoming CDM data. |
CDMMaxDataConnectionsPerGroup | 25 (1 to 1024) | Specifies the maximum number of data connections to connect per replication group. |
CDMreplicationforvtgtt | 1 (0, 1) | You can set the CDM replication feature using this parameter.
|
DataFileAsyncNonBlockingWrite | True (True or False) | By default, data files are distributed across
regions asynchronously and limited by network capacity. When a data file size exceeds the network buffer,
the write continues or pauses, based on the threshold setting in the
DfsAsyncWriteMaxOutstandingMegaBytes parameter.
Only GSC configures this
parameter.
|
DefaultObjectResyncOption | 260 (1, 2, 4, 129, 130, 132, 257, 258, or 260) | Controls the default option for resyncing
unrecoverable tables.
|
DefaultObjectResyncTimeout | 300 (30 to infinity) | Sets the default timeout (in seconds) for synchronizing tables using the table sync service. |
DefaultObjectValidationTimeout | 300 (30 to infinity) | Sets the default timeout (in seconds) for validating tables using the table validation service. |
DfsAsyncWriteMaxOutstandingMegaBytes | 50 megabytes (1 to infinity) | Maximum amount of outstanding DFS file data on a
network buffer for asynchronous writes to a remote node. If reached, data files writes either pause (blocking mode) or continue (non-blocking mode), depending on the DataFileAsyncNonBlockingWrite setting. |
directconnectcontrol | 0 (0, 2) | This parameter governs the response of Business Continuity Manager to the SQL statements executed directly on managed systems. |
DirectSessionIdleTimeout | 0 (disabled) (0 to infinity) | The number of seconds a direct session remains idle until Business Continuity Manager closes the matching Business Continuity Manager managed session. This feature is disabled by default because matching Business Continuity Manager managed session for direct sessions is automatically closed on logoff. This parameter is required to close Business Continuity Manager managed session for direct sessions for sessions from a connection pool. |
dynamicDFSIOTimeouts | 2 (0, 1, or 2) | Controls the behavior of read and write timeouts in
DFS.
|
EnableActivityTrackingObfuscation | False (True or False) | Prevents the collection of sensitive information in support bundles. The sensitive information includes SQL statements and IP addresses to be collected in log files, alerts, backtraces, core files, and so on. This value must be set to true for any of the other EnableActivityTrackingObfuscation* configuration values to take effect. |
EnableActivityTrackingObfuscationBacktraces | False (True or False) | Prevents the collection of backtraces in support bundles. |
EnableActivityTrackingObfuscationCores | False (True or False) | Prevents the collection of core files in support bundles. |
EnableActivityTrackingObfuscationIPAlerts | False (True or False) | Prevents the collection of IP addresses in alerts. |
EnableActivityTrackingObfuscationIPLogs | False (True or False) | Prevents the collection of IP addresses in log files. |
EnableActivityTrackingObfuscationSQLAlerts | False (True or False) | Prevents the collection of SQL statements in alerts. |
EnableActivityTrackingObfuscationSQLLogs | False (True or False) | Prevents the collection of SQL statements in log files. |
GatewayMonitorMinTimeout | 2 (Process Type or Per Process) | Minimum period of time (in milliseconds) for the monitor to start for each gateway. If the gateway does not respond, it is marked as down, and the timeout is adjusted by the value in GatewayMonitorTimeoutAdjust. |
GatewayMonitorTimeoutAdjust | 2 (Process Type or Per Process) | The increment size (in milliseconds) used to adjust the gateway monitor timeout automatically. Business Continuity Manager automatically adjusts the timeout value used within GatewayMonitorMinTimeout and GatewayMonitorMaxTimeout, based on current gateway response times. |
GatewayMonitorMaxTimeout | 3 (Process Type or Per Process) | Maximum period of time (in milliseconds) allowed when attempting a handshake with the gateway. |
GlobalDeadlockDetectionInterval | 0 (0, 10 seconds to infinity) | The interval in seconds determines how often
Business Continuity Manager detects a global deadlock between Business Continuity Manager and the database. Business Continuity Manager reads the session-level statistics from the
database. The database updates its session-level statistics at an
interval set by the session rate for the database. Accounting for both
rates, the longest time to detect a deadlock between Business Continuity Manager and the database is the session rate for the
database plus the time set in the GlobalDeadlockDetectionInterval. The default value 0 (zero) disables the setting. |
LoadReadFromDiskThreshold | 5000 (1000-to infinity) | Parameter that controls the queue size before compelling a system to disk during a client load. If a queue for the slower system during a client load exceeds this threshold, the system instead loads data from disk for the current checkpoint instead of continuing to load data parcels from memory. Note that this feature (moving a slower system to read from disk instead of in-memory queue) only applies if LoadSpeedThrottle is disabled. |
LoadSpeedThrottle | Enabled (Enabled, Disabled) | Controls whether the load throttling feature is enabled. If enabled, Business Continuity Manager throttles faster systems down to make sure that the slower system does not fall too far behind. By default, slower system can fall behind by 5000 data parcels before the faster systems throttle down. This feature is only supported forBusiness Continuity Manager managed sessions and does not apply to directly connected sessions. The LoadSpeedThrottleThresholds configuration parameter controls this threshold. |
LoadSpeedThrottleThreshold | Max=5000 | Optional configuration that controls both the maximum queue size before the throttle feature kicks in and how large the queue can be before delaying new data parcel queuing. Represented as a maximum value, set to 5000 by default. This means for a client load job, if the slower system queue is at 5000 data parcels or greater, the feature throttles the faster system. New data packets are held in memory until the queue for all systems has dropped below the minimum. The minimum, by default, is set to 4999. When the queue drops below 4999, the system can process new data parcels. |
OperationPurgeTime | 168 hours | Sets the default expiration period in hours after
which a completed operation can be purged. To purge operations immediately after they complete, set the expiration time to 0 (zero) hours. The last operation on a valid object, such as a table, or a system, is not purged to make sure the persistence of a history for the object. |
PassiveRoutingFeature | Enabled | Enables the passive routing feature. |
replicationinterface | 0 (0, 5) | Use this parameter to configure the replication interface method for CDM. Set the parameter to 5 to activate CDM. |
ReplicationEnableIDC | False (True/False) | If enabled (True), Business Continuity Manager will connect to the Input Data Capture (IDC) replication group, which provides information about direct loads. |
SetReadOnlyOnWriteFailure | False (True or False) | With the default value (true), when a recoverable transient error occurs on a request that reads and writes to multiple tables, all the tables being read from are placed in the Read-Only state. All the tables being written to are placed in the Interrupted state. If the feature is turned off (false), all the tables being written are placed in an Interrupted state, while the tables being read remain Active. |
StandbySystemFailoverWaitTime | 0 (0 to infinity) | The wait time in seconds before Business Continuity Manager initiates automatic or manual failover to the standby systems. |
ValidationMetric | 1 (1 -Rowcount, 2 -Checksum, 3 -(Rowcount + Checksum)) | Controls the default metric for validating tables. This validation metrics will be considered while executing Object Validate command on a table, such as Object validate <Object> on 1,2. |
ValidationUsername | dbc | Database username used to validate tables. Must have the correct select permissions to read tables to validate their content. |