Property | Description | Default Value |
---|---|---|
agentCollector.agentHeartbeatWaitMillis | Sets the amount of time in milliseconds to wait for an agent heartbeat before assuming the agent has gone out of service. | 600000 |
blocked.job.maxAllowedLimit | The maximum number of jobs that can be marked as
BLOCKED and retried. If a job is detected as blocked when the
blocked.job.maxAllowedLimit has
already been reached, the job is added to the Job Queue. The value cannot be greater than 25% of the maximum concurrent job limit. |
5 |
blocked.job.retry.enabled | When set to True, detects any locks on the source/target objects being moved and retries running the job after a specified interval. | False |
blocked.job.retry.interval | Sets an interval to retry running any jobs
blocked because of locks on source/target objects. Time unit can be specified as HOURS or MINUTES. |
1 HOUR |
blocked.job.retry.maxInterval | Sets the maximum interval for attempting to
start any jobs blocked because of locks on source/target objects. Jobs are marked as FAILED after the maximum interval is exceeded the jobs are still blocked. Time unit can be specified as HOURS or MINUTES. |
1 HOUR |
daemon.default.compareDDL.enabled | Enables/disables the default compareDDL behavior at the daemon level. | |
databaseQueryService.useBaseViewsOnly | Sets all data dictionary queries on Teradata source and target systems to use the base views instead of X or VX views. | True |
deadlock.retry.enabled | When set to True, if an SQL query execution fails with DBS error (2631) because of a deadlock, retries executing the query after a specified interval. | False |
deadlock.retry.interval | The interval during which to retry executing an
SQL query that fails with a DBS deadlock error (2631). Time unit can be specified as SECONDS or MINUTES. |
1 MINUTE |
deadlock.retry.maxAttempts | The maximum number of attempts to retry executing an SQL query that fails with a DBS deadlock error (2631). | 10 |
different.session.charsets.enabled | Determines whether or not specifying different
source and target session character sets in a job is allowed. Default value False means this is not allowed. |
False |
event.table.default | Default event table in which to save event
details. Events are sent to this event table by default when tmsm.mode is either BOTH or
ONLY_INTERNAL_TMSM. Individual jobs can use a different event table
by using the log_to_event_table
job definition parameter. Multiple values can be
set as follows:
|
NULL |
hanging.job.check.enabled | If enabled, an internal process awakens periodically and reviews running jobs to see if any have stopped responding. | Disabled |
hanging.job.check.rate | Rate at which to check for jobs in halt (in hours). | 1 HOUR |
hanging.job.timeout.acquisition | If the progress of a new job is not reported within this period (in hours), the job is stopped. Timeout is specifically for the acquisition phase. |
1 HOUR |
hanging.job.timeout.large.apply | If the progress of a new job is not reported within this period (in hours), the job is stopped. Timeout specifically for the TPTAPI apply phase for a large object. |
4 HOURS |
hanging.job.timeout.large.build | If the progress of a new job is not reported within this period (in hours), the job is stopped. Timeout specifically for the DSA build phase for a large object. |
4 HOURS |
hanging.job.timeout.large.initiate | If the progress of a new job is not reported within this period (in hours), the job is stopped. Timeout specifically for the initiate phase for a large object. |
4 HOURS |
hanging.job.timeout.medium.apply | If the progress of a new job is not reported within this period (in hours), the job is stopped. Timeout specifically for the TPTAPI apply phase for a medium object. |
2 HOURS |
hanging.job.timeout.medium.build | If the progress of a new job is not reported within this period (in hours), the job is stopped. Timeout specifically for the DSA build phase for a medium object. |
2 HOURS |
hanging.job.timeout.medium.initiate | If the progress of a new job is not reported within this period (in hours), the job is stopped. Timeout specifically for the initiate phase for a medium object. |
2 HOURS |
hanging.job.timeout.range.large.min | Defines the minimum size (in MB, GB, TB, or default GB if the unit is not provided) for an object to be considered a large object. | 10 GB |
hanging.job.timeout.range.small.max | Defines the maximum size (in MB, GB, TB, or default MB if the unit is not provided) for an object to be considered a small object. | 5 MB |
hanging.job.timeout.small.apply | If the progress of a new job is not reported within this period (in hours), the job is stopped. Timeout specifically for the TPTAPI apply phase for a small object. |
1 HOUR |
hanging.job.timeout.small.build | If the progress of a new job is not reported within this period (in hours), the job is stopped. Timeout specifically for the DSA build phase for a small object. |
1 HOUR |
hanging.job.timeout.small.initiate | If the progress of a new job is not reported within this period (in hours), the job is stopped. Timeout specifically for the initiate phase for a small object. |
1 HOUR |
job.allowCommandLineUser | When set to True, the daemon allows CommandLine requests when the security level is Daemon. | False |
job.databaseClientEncryption | When set to True, utilities such as DSA, JDBC, and TPTAPI initiate encrypted sessions to both the source and target database systems.
Performance decreases when encryption is initiated.
|
False |
job.default.dsa.nontable | When set to true, Data Mover tries to use DSA for moving non-table objects such as macros, views and stored procedures. Do not change this property while jobs are being created, edited or running.
|
False |
job.default.foreign.server.on.target | If set to true, Data Mover tries to use foreign server on target system for T2T job. | False |
job.default.queryband | Provides a set of name/value pairs to be used as the default query band for all jobs. | ApplicationName=DM;Version=16.00 |
job.default.queryband.enabled | Enable to use of the default query band features. | False |
job.force.direction | Forces the direction of data movement from source to target system. | |
job.never.target.system | Prevents certain database systems from ever being a target system in a Data Mover job. | False |
job.onlineArchive | When set to True, online archiving is used for objects that merit the use of DSA.
Performance decreases when this setting is used for object availability.
|
False |
job.overwriteExistingObjects | When set to True, objects that already exist on the target database system are overwritten. | False |
job.securityMgmtLevel | The level of security management enabled. Valid choices are Daemon and Job. | Job |
job.useGroupUserIdPool | Defines a set of system names and credentials. When creating a job, this group user id pool can be used for the source or target in place of directly specifying credentials in the job. | None |
job.useSecurityMgmt | When set to True, Data Mover commands require the admin username and password to be specified when running the command. For a complete list of commands affected by this parameter, see the Teradata® Data Mover User Guide. | False |
job.useSyncService | Records any changes to the Data Mover repository tables (inserts/updates/deletes) in an audit log table. The value must be set to True to use the Sync service. |
False |
job.useUserIdPool | Uses a target user from the pool of users. | |
lighthouse.enable | Enable or disable the Lighthouse data collection feature. | True |
lighthouse.hour | The hour to begin the collection of the Data Mover matrixes. Default value 3 means 3 a.m. | 3 |
lighthouse.minute | The minute to begin the collection of the Data Mover matrixes. | 0 |
map | Represents the system-level map values for target systems with Teradata Database 16.10 or later. The map can be defined at the object, database, or job definition level. If the map is not defined, and objects are being copied to the target system as part of the job, then system-level maps are used for those objects in the target system. For more information, refer to About Teradata Database MAPS Architecture Feature Support in the Teradata® Data Mover User Guide. | False |
queryGridManagerEncryptedPassword | Sets the QueryGrid Manager user-encrypted password. Cannot be combined with queryGridManagerPassword. | |
queryGridManagerPassword | Sets the QueryGrid Manager user password. Cannot be combined with the queryGridManagerEncryptedPassword. | |
queryGridManagerUser | Sets the QueryGrid Manager Manager user. | Support |
querygrid.wait.final.status | When set to True, the system waits for QueryGrid Manager to return the final task status. Setting to True may impact system performance. | False |
repository.purge.definition.enabled | Enables the automated purging of job definitions. | False |
repository.purge.enabled | Enables/disables the repository clear feature. The default value False means the feature is disabled. | False |
repository.purge.history.unit | The unit for job history data to be kept in the repository before purging occurs. The current supported values are Days, Weeks, Months, and Years. |
Days |
repository.purge.history.unitcount | The number of units for job history data to be kept in the repository before purging occurs. This value is combined with the value for repository.purge.history.unit to determine the amount of time before purging occurs for old jobs (for example, 60 days, 3 years, or 10 months). The value of -1 disables the purging by time. |
60 |
repository.purge.hour | The hour to start the daily repository purging. Default value 1 means 1 am. | 1 |
repository.purge.minute | The minute to start the daily repository purging. | 0 |
repository.purge.percent | The percentage of repository permspace that needs to be available to determine when to clear the repository. The default value 50 means clear the repository when more than 50% of the available permspace is in use. The value of -1 disables the purging by percentage. | 50 |
skip.FLML.tables | Enables/disables a table from being Fast/Multi loaded, regardless of the utility being used. When enabled (true), the daemon marks the table as completed_with_warnings. When disabled (false) the daemon marks the table copy as failed. | False |
system.default.database.enabled | Enables/disables the default target/staging databases at the system level. The default value False means disabled. | False |
target.system.load.slots | Controls the total number of load slots that Data Mover can use at one time on target Teradata systems. | 5 |
tmsm.frequency.bytes | Controls the frequency of messages sent to Teradata Ecosystem Manager when using byte-based utilities.
Providing a low value can hurt performance. Teradata recommends using the default value.
|
2147483647 BYTES |
tmsm.mode | Controls how Data Mover directs Teradata Ecosystem Manager messages. Possible values are BOTH, ONLY_REAL_TMSM, ONLY_INTERNAL_TMSM, and NONE. When set to BOTH, messages are sent to the real Teradata Ecosystem Manager and written to the TDI event tables. | None |