4102 035K

What would you do if you knew?
Unity Data Mover

Installation, Configuration, and Upgrade Guide
for Customers
Release 15.10
B035-4102-035K
May 2015
The product or products described in this book are licensed products of Teradata Corporation or its affiliates.
Teradata, Active Data Warehousing, Active Enterprise Intelligence, Applications-Within, Aprimo Marketing Studio, Aster, BYNET,
Claraview, DecisionCast, Gridscale, MyCommerce, QueryGrid, SQL-MapReduce, Teradata Decision Experts, "Teradata Labs" logo, Teradata
ServiceConnect, Teradata Source Experts, WebAnalyst, and Xkoto are trademarks or registered trademarks of Teradata Corporation or its
affiliates in the United States and other countries.
Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc.
AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc.
Apache, Apache Avro, Apache Hadoop, Apache Hive, Hadoop, and the yellow elephant logo are either registered trademarks or trademarks
of the Apache Software Foundation in the United States and/or other countries.
Apple, Mac, and OS X all are registered trademarks of Apple Inc.
Axeda is a registered trademark of Axeda Corporation. Axeda Agents, Axeda Applications, Axeda Policy Manager, Axeda Enterprise, Axeda
Access, Axeda Software Management, Axeda Service, Axeda ServiceLink, and Firewall-Friendly are trademarks and Maximum Results and
Maximum Support are servicemarks of Axeda Corporation.
Data Domain, EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation.
GoldenGate is a trademark of Oracle.
Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company.
Hortonworks, the Hortonworks logo and other Hortonworks trademarks are trademarks of Hortonworks Inc. in the United States and other
countries.
Intel, Pentium, and XEON are registered trademarks of Intel Corporation.
IBM, CICS, RACF, Tivoli, and z/OS are registered trademarks of International Business Machines Corporation.
Linux is a registered trademark of Linus Torvalds.
LSI is a registered trademark of LSI Corporation.
Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United
States and other countries.
NetVault is a trademark or registered trademark of Dell Inc. in the United States and/or other countries.
Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries.
Oracle, Java, and Solaris are registered trademarks of Oracle and/or its affiliates.
QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation.
Quantum and the Quantum logo are trademarks of Quantum Corporation, registered in the U.S.A. and other countries.
Red Hat is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Used under license.
SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries.
SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc.
SPARC is a registered trademark of SPARC International, Inc.
Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States
and other countries.
Unicode is a registered trademark of Unicode, Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other product and company names mentioned herein may be the trademarks of their respective owners.
The information contained in this document is provided on an "as-is" basis, without warranty of any kind, either express
or implied, including the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. In no
event will Teradata Corporation be liable for any indirect, direct, special, incidental, or consequential damages, including
lost profits or lost savings, even if expressly advised of the possibility of such damages.
The information contained in this document may contain references or cross-references to features, functions, products, or services that are
not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features,
functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions,
products, or services available in your country.
Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or
updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this
information at any time without notice.
To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this
document. Please e-mail: teradata-books@lists.teradata.com
Any comments or materials (collectively referred to as "Feedback") sent to Teradata Corporation will be deemed non-confidential. Teradata
Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display,
transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis.
Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose
whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback.
Copyright 2013 - 2015 by Teradata. All Rights Reserved.
Table of Contents
Preface.............................................................................................................................................................5
Purpose.................................................................................................................................................................. 5
Audience................................................................................................................................................................ 5
Revision History................................................................................................................................................... 5
Additional Information........................................................................................................................................5
Related Links..................................................................................................................................................5
Related Documents....................................................................................................................................... 6
Customer Education..................................................................................................................................... 6
Customer Support......................................................................................................................................... 6
Product Safety Information.................................................................................................................................6
Chapter 1:
Overview........................................................................................................................................................7
Dependencies........................................................................................................................................................ 7
Data Mover Server Requirements............................................................................................................... 7
External Component Requirements........................................................................................................... 7
Required Permissions....................................................................................................................................7
Required Open Ports on the Teradata Managed Server...........................................................................7
Best Practices for Data Mover Networking.......................................................................................................8
Chapter 2:
Configuring the Environment................................................................................................... 9
Configuring the Data Mover Daemon...............................................................................................................9

The daemon.properties File..........................................................................................................................9
1Dynamic Properties........................................................................................................................... 11
Configuration Properties............................................................................................................................11
Configuring the Data Mover Agent................................................................................................................. 15
Installing and Configuring the Data Mover Agent on a Linux Teradata Server.................................16
The agent.properties File............................................................................................................................ 16
1Dynamic Properties........................................................................................................................... 18
Configuring the Data Mover Command-Line Interface............................................................................... 18
Configuring the Data Mover Command-Line Interface on a Linux Teradata Server........................18
Unity Data Mover

Installation, Configuration, and Upgrade Guide for Customers Release 15.10 3
Table of Contents
Installing and Configuring the Data Mover Command-Line Interface on Non-Teradata Servers...18
The commandline.properties File...............................................................................................................20
About Configuring High Availability................................................................................................................21
Configuring Automatic Failover.................................................................................................................22
Synchronizing Master and Slave Repository..................................................................................... 23
Configuring Dual Active Java Message Service (JMS) Brokers.......................................................23
Configuring the Sync Service...............................................................................................................24
Configuring the Cluster and Starting the Monitoring Service........................................................25
Failover.properties File........................................................................................................... 25
Checking the Status of Master and Slave Components....................................................................26
Enabling Synchronization.................................................................................................................... 26
Configuring the Synchronization Service Without Automatic Failover............................................... 27
Configuring the Synchronization Service.......................................................................................... 27
Configuring Data Mover to Use Unity Ecosystem Manager......................................................................... 27
Configuring Multiple Managed Servers........................................................................................................... 28
Configuring Data Mover to Log to TVI........................................................................................................... 29
Enabling Logging TVI Alerts When a Failover Occurs.......................................................................... 29
Configuring Data Mover Managed Server to Increase Network Throughput............................................ 29
About Adding Source and Target COP Entries........................................................................................ 30
About Defining Routes for Source and Target COP Entries...................................................................31
Restarting the Network................................................................................................................................31
About Verifying the Route Changes...........................................................................................................31
Data Mover Log Files.......................................................................................................................................... 32
Chapter 3:
Upgrading Software.......................................................................................................................... 33
About Upgrading Data Mover Software...........................................................................................................33

Creating an Incident............................................................................................................................................33
Upgrading the Data Mover Command-Line Interface on Non-Teradata Servers......................................34
Upgrading the Data Mover Agent on a Linux Teradata Server.....................................................................36
Appendix A:
Administrative Tasks....................................................................................................................... 37
Data Mover Components Script........................................................................................................................ 37

Creating a Diagnostic Bundle for Support....................................................................................................... 37
Unity Data Mover

4 Installation, Configuration, and Upgrade Guide for Customers Release 15.10
Preface
Purpose
This guide provides customer information and procedures for installing, configuring, and
upgrading Unity Data Mover software.
Audience
This guide is intended for use by:
System administrators
Database administrators and relational database developers
Customers
Teradata Customer Support
Revision History
Date Release Description
May 2015 15.10 Updated for the 15.10 release.
Additional Information
Related Links
URL Description
https://tays.teradata.com Use Teradata At Your Service to access Orange Books, technical
alerts, and knowledge repositories, view and join forums, and
download software packages.
www.teradata.com External site for product, service, resource, support, and other
customer information.
Unity Data Mover

Preface
Product Safety Information
Related Documents
Documents are located at www.info.teradata.com.
Title Publication ID
Unity Data Mover User Guide B035-4101
Describes how to use the Unity Data Mover portlets and command-line interface.
Parallel Upgrade Tool (PUT) Reference B035-5713
Describes how to install application software using PUT.
Teradata Viewpoint User Guide B035-2206
Describes the Teradata Viewpoint portal, portlets, and system administration
features.
Customer Education
Teradata Customer Education delivers training for your global workforce, including
scheduled public courses, customized on-site training, and web-based training. For
information about the classes, schedules, and the Teradata Certification Program, go to
www.teradata.com/TEN/.
Customer Support
Customer support is available around-the-clock, seven days a week through the Global
Technical Support Center (GSC). To learn more, go to https://tays.teradata.com.
Product Safety Information

This document may contain information addressing product safety practices related to data
or property damage, identified by the word Notice. A notice indicates a situation which, if not
avoided, could result in damage to property, such as equipment or data, but not related to
personal injury.
Example
Notice: Improper use of the Reconfiguration utility can result in data loss.
Unity Data Mover

CHAPTER 1
Overview
Dependencies
Data Mover Server Requirements

Software Level
Server SUSE Linux Enterprise Server 11 SP 1
Internal Repository Teradata Database 14.00
Teradata REST Version 15.00
Note: For non-Teradata servers, you must install or upgrade to JRE 7 before installing or
upgrading any components.
External Component Requirements

The versions of components that Data Mover works with are listed below.
Software Level
Teradata Database Versions 13.10 to 15.10
Teradata Hadoop Appliance Versions 1.3.2, 2.1.x, 2.1.7
Teradata Aster Database Versions 5.10, 6.0, 6.10
Teradata Viewpoint Version 15.00 or 15.10
Cloudera Distribution of Version 4.3
Hadoop
Required Permissions
You must be a root user to install and configure Data Mover components.
Required Open Ports on the Teradata Managed Server

The ports listed below must be open for incoming and outgoing traffic on the Data Mover
managed server:
Port Number Used By
22 SSH
Unity Data Mover

Chapter 1 Overview
Best Practices for Data Mover Networking
Port Number Used By

1025 CLI and JDBC
25268 ARC access module
25168 ARC server
61616 ActiveMQ
25368 Master sync service
Best Practices for Data Mover Networking

A comprehensive knowledge article about Data Mover networking best practices is available
to help you understand and resolve a variety of performance issues, including test and
validation procedures for suggested changes.
The Data Mover Networking Best Practices knowledge article is located at http://
cks.teradata.com/8525621800464274/0/41A6F00B2FF7E06485257D330008E2DF.
Unity Data Mover

CHAPTER 2
Configuring the Environment
Configuring the Data Mover Daemon

1 Edit the daemon.properties file and restart the Data Mover daemon to implement
the changes.
For properties that can be set dynamically, the changes take effect one minute after the
updated daemon.properties file is saved. There is no need to restart the daemon
service if you are only updating dynamic properties.
2 Use the list_configuration and save_configuration commands to modify the other
Data Mover properties.
The daemon.properties File

The following table shows the properties in daemon.properties.
Property Description Default Value
arcserver.port=port A long-lived server port on the machine running the 25168
DMDaemon, which is used for inbound socket connections
from DM Agents.
broker.port=port The port number of the machine where the Java Message 61616
Service (JMS) message broker is listening.
broker.url=url The hostname or IP address of the machine running the Java localhost
Message Service (JMS) message broker.
cluster.enabled=setting When set to True, establishes a connection to a secondary False
for cluster Java Message Service (JMS) broker in case the primary JMS
broker fails.
viewpoint.url The hostname or IP address for the Viewpoint Authentication http://localhost
server.
Example: viewpoint.url=http://localhost
viewpoint.port The port number for the Viewpoint Authentication server. 80
Example: viewpoint.port=80
logger.useTviLogger=sett The TVI logger can be set to true or false. If set to true, True
ing for TVI messages fatal error messages are sent to TVI. Dynamic property.1
Unity Data Mover

Chapter 2 Configuring the Environment

jobExecutionCoordinator. The maximum number of jobs allowed to run on the daemon 20
maxConcurrentJobs=maximu at the same time. Additional jobs are placed on the queue and
m number of jobs run when slots become available. Dynamic property. 1
jobExecutionCoordinator. The maximum number of jobs allowed in the job queue. 20
maxQueuedJobs=maximum Additional jobs are placed in a higher level memory queue
number of jobs allowed until slots are available in the job queue. Dynamic property.
1n
in queue
log4j.appender.logfile=o Informs the logging application to use a specific appender.
rg.apache.log4j.RollingF It is recommended that this property value not be changed.
ileAppender
log4j.appender.logfile.f Relative or absolute path of the log file. If changing log file dmDaemon.log
ile=file path name location, specify the absolute path of the file. For Windows,
specify back slash instead of forward slash, for example, C:
\Program File\Teradata\Log\dmDaemon.log.
Both file path and file name can be set dynamically.1

log4j.appender.logfile.l Dynamic property. 1
ayout=org.apache.log4j.P Note: Do not edit. This is an internal setting for logging
atternLayout infrastructure.
log4j.appender.logfile.m The number of backup logging files that are created. After the 3
axBackupIndex=<number of maximum number of files has been created, the oldest file is
backup files> erased. Dynamic property. 1
Example
If Max Backups = 3, three backup logs are created:
dmDaemon.log.1
dmDaemon.log.2
dmDaemon.log.3
If the current dmDaemon.log size exceeds 10MB, it rolls to
become the new dmDaemon.log.1 and a new
dmDaemon.log is created. The previous dmDaemon.log.2
becomes the new dmDaemon.log.3. The previous
dmDaemon.log.3 is deleted.
log4j.appender.logfile.m The maximum size of the logging file before being rolled over 10MB
axFileSize=<maximum size to backup files. Dynamic property. 1
of log files>
log4j.appender.logfile.l The pattern of the log file layout, where: %d [%t] %-5p
ayout.ConversionPattern= d = date %c{3} - %m%n
<log file pattern t = thread
layout> p = log level
c = class name
m= message
n = message
Dynamic property when layout is PatternLayout.1
Unity Data Mover

Information for creating a layout is at: http://

logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/
PatternLayout.html
log4j.rootLogger=<level 6 levels of logging, TRACE | DEBUG | INFO | WARN | INFO,logfile
of logging> ERROR | FATAL. From trace level to application error.
LOG_LEVEL can be updated dynamically, but not
logfile.1
Value is:
LOG_LEVEL, logfile
Note: Do not remove the term logfile.
If the Viewpoint Authentication server has HTTPS enabled, you can set the following if you
want to authenticate via HTTPS instead: viewpoint.url to https://localhost and
viewpoint.port to 443.
1Dynamic Properties
updated daemon.properties file is saved. There is no need to restart the daemon service
if you are only updating dynamic properties. For example:
If you changed the value of log4j.rootLogger from the default of INFO, logfile
to DEBUG, logfile, any debug messages generated would start appearing in the log file
one minute after saving the updated properties file.
If you changed the value of jobExecutionCoordinator.maxConcurrentJobs from
the default value of 20 to a new value of 25, the new value of 25 would take effect one
minute after saving the updated daemon.properties file.
Configuration Properties
Property Description Default

agentCollector.agentHeartbea Sets the amount of time in milliseconds to wait for an agent 600000
tWaitMillis heartbeat before assuming it has gone out of service.
blocked.job.maxAllowedLimit The maximum number of jobs that can be marked as 5
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.
blocked.job.retry.enabled When set to True, detects any locks on the source/target False
objects being moved and retries running the job after a specified
interval.
blocked.job.retry.interval Sets an interval to retry running any jobs blocked because of 1 HOUR
locks on source/target objects.
Time unit can be specified as HOURS or MINUTES.
Unity Data Mover


blocked.job.retry.maxInterva Sets the maximum interval for attempting to start any jobs 1 HOUR
l blocked because of locks on source/target objects.
Jobs are marked as FAILED after this interval is exceeded if
they are still blocked.
Time unit can be specified as HOURS or MINUTES.
daemon.default.compareDDL.en Enables/disables the default compareDDL behavior at the
abled daemon level.
databaseQueryService.useBase Sets all data dictionary queries on Teradata source and target True
ViewsOnly systems to use the base views instead of X or VX views.
deadlock.retry.enabled When set to True, if an SQL query execution fails with DBS False
error (2631) because of a deadlock, retries executing the query
after a specified interval.
deadlock.retry.interval The interval during which to retry executing an SQL query that 1 MINUTE
fails with a DBS deadlock error (2631).
Time unit can be specified as SECONDS or MINUTES.
deadlock.retry.maxAttempts The maximum number of attempts to retry executing an SQL 10
query that fails with a DBS deadlock error (2631).
different.session.charsets.e Determines whether or not specifying different source and False
nabled target session character sets in a job is allowed.
Default value False means this is not allowed.
event.table.default Default event table in which to save event details. Events are sent NULL
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:
<value>event1</value>
<value>event2</value>
hadoop.connector.max.task.sl Specifies the maximum number of concurrent Hadoop 2
ot Connector tasks.
hadoop.default.mapper.export Specifies the number of mappers for Hadoop to Teradata jobs. 8
This property only used when hadoop.default.mapper.type is
DataMover. - Default is 8
hadoop.default.mapper.import Specifies the number of mappers for Teradata to Hadoop jobs. 20
This property is only used when hadoop.default.mapper.type is
DataMover.
hadoop.default.mapper.type Determines which product will decide the default number of DataMover
mappers for a Hadoop job. Possible values are TDCH and
DataMover.
hanging.job.check.enabled If enabled, an internal process awakens periodically and reviews Disabled
active jobs to see if any are hanging.
Unity Data Mover


hanging.job.check.rate Rate at which to check for hanging jobs (in hours). 1 HOUR
hanging.job.timeout.acquisit If the progress of a new job is not reported within this period (in 1 HOUR
ion hours), the job will be aborted.
Timeout is specifically for the acquisition phase.
hanging.job.timeout.in.minut Internal use only. If enabled, causes all hanging.job Disabled
es parameters to use minutes instead of hours.
hanging.job.timeout.large.ap If the progress of a new job is not reported within this period (in 4 HOURS
ply hours), the job is aborted.
Timeout specifically for the TPTAPI apply phase for a large
object.
hanging.job.timeout.large.bu If the progress of a new job is not reported within this period (in 4 HOURS
ild hours), the job is aborted.
Timeout specifically for the ARC build phase for a large object.
hanging.job.timeout.large.in If the progress of a new job is not reported within this period (in 4 HOURS
itiate hours), the job is aborted.
Timeout specifically for the initiate phase for a large object.
hanging.job.timeout.medium.a If the progress of a new job is not reported within this period (in 2 HOURS
pply hours), the job is aborted.
Timeout specifically for the TPTAPI apply phase for a medium
object.
hanging.job.timeout.medium.b If the progress of a new job is not reported within this period (in 2 HOURS
uild hours), the job is aborted.
Timeout specifically for the ARC build phase for a medium
object.
hanging.job.timeout.medium.i If the progress of a new job is not reported within this period (in 2 HOURS
nitiate hours), the job is aborted.
Timeout specifically for the initiate phase for a medium object.
hanging.job.timeout.range.la Defines the minimum size (in MB, GB, TB, or default GB if the 10 GB
rge.min unit is not provided) for an object to be considered a large
object.
hanging.job.timeout.range.sm Defines the maximum size (in MB, GB, TB, or default MB if the 5 MB
all.max unit is not provided) for an object to be considered a small
object.
hanging.job.timeout.small.ap If the progress of a new job is not reported within this period (in 1 HOUR
ply hours), the job is aborted.
Timeout specifically for the TPTAPI apply phase for a small
object.
hanging.job.timeout.small.bu If the progress of a new job is not reported within this period (in 1 HOUR
ild hours), the job is aborted.
Timeout specifically for the ARC build phase for a small object.
Unity Data Mover


hanging.job.timeout.small.in If the progress of a new job is not reported within this period (in 1 HOUR
itiate hours), the job is aborted.
Timeout specifically for the initiate phase for a small object.
job.allowCommandLineUser When set to True, the daemon will always allow False
CommandLine requests when the security level is Daemon.
job.databaseClientEncryption When set to True, utilities such as ARC, JDBC, and TPTAPI False
initiate encrypted sessions to both the source and target
database systems.
Note: Performance decreases when encryption is initiated.
job.default.queryband Provides a set of name/value pairs to be used as the default Applicatio

query band for all jobs. nName=DM;V
ersion=15.
10
job.default.queryband.enable Enable to use of the default query band features. False
d
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 False
system in a Data Mover job.
job.onlineArchive When set to True, online archiving is used for objects that False
merit the use of ARC.
Note: Performance decreases when this setting is used for object
availability.
job.overwriteExistingObjects When set to True, objects that already exist on the target False
database system are overwritten.
job.securityMgmtLevel The level of security management enabled. Valid choices are Job
Daemon and Job.
job.useGroupUserIdPool Defines a set of system names and credentials. When creating a None
job, this group user id pool can be used for the source or target
in place of directly specifying credentials in the job.
job.useSecurityMgmt When set to True, some Data Mover commands require the False
admin username and password to be specified when executing
the command. For a complete list of commands affected by this
parameter, see the Unity Data Mover User Guide.
job.useSyncService Records any changes to the Data Mover repository tables False
(inserts/updates/deletes) in an audit log table.
The value must be set to True to use the Sync service.
job.useUserIdPool Uses a target user from the pool of users. This enables the
running of multiple arc tasks at the same time.
repository.purge.definition. Enables the automated purging of job definitions. False
enabled
Unity Data Mover

Configuring the Data Mover Agent

repository.purge.enabled Enables/disables the repository purge feature. The default value False
False means purging is disabled.
repository.purge.history.uni The unit for job history data to be kept in the repository before Days
t purging should occur.
The current supported values are Days, Weeks, Months, and
Years.
repository.purge.history.uni The number of units for job history data to be kept in the 60
tcount repository before purging should occur.
This value is combined with the value for
repository.purge.history.unit to determine the
amount of time before purging should occur for old jobs (for
example, 60 days, 3 years, or 10 months).
The value of -1 disables the purging by time.
repository.purge.hour The hour when the daily repository purging should start. 1
Default value 1 means 1 am.
repository.purge.minute The minute when the daily repository purging should start. 0
repository.purge.percent The percentage of repository permspace that needs to be 50
available to determine when purging should occur. The default
value 50 means the repository should be purged when more
than 50% of the available permspace is in use. The value of -1
disables the purging by percentage.
sqlh.max.task.slot Specifies the limit for maximum number of concurrent SQL-H 2
tasks.
system.default.database.enab Enables/disables the default target/staging databases at the False
led system level. The default value False means disabled.
target.system.load.slots Controls the total number of load slots that Data Mover can use 5
at one time on target Teradata systems.
tmsm.frequency.bytes Controls the frequency of messages sent to Unity Ecosystem 2147483647
Manager when using byte-based utilities (for example, ARC). BYTES
Note: Providing a low value can hurt performance. The
recommendation is to use default value.
tmsm.mode Controls how Data Mover directs Unity Ecosystem Manager None
messages. Possible values are BOTH, ONLY_REAL_TMSM,
ONLY_INTERNAL_TMSM, and NONE. When set to BOTH,
messages are sent to the real Unity Ecosystem Manager and
written to the TDI event tables.

The agent.properties file is located in the /etc/opt/teradata/datamover
directory.
Unity Data Mover

1 Edit the agent.properties file and restart the Data Mover agent to implement the
changes.
updated agent.properties file is saved. There is no need to restart the agent service if
you are only updating dynamic properties.
Installing and Configuring the Data Mover Agent on a Linux Teradata

Server
1 Install the appropriate DMAgent software package for your system as follows:
Operating Actions
System
Linux (for non- a. At the command line, type the following to install the DMAgent and
Teradata servers) TTU packages:
./ dminstallupgradeagent
b. Answer the prompts as needed, and press Enter to accept the defaults
where appropriate.
c. Type rpm -qa |grep DMAgent to verify the installation.
The agent.properties File

The following table shows the properties in agent.properties.
agent.id=id Unique identifier for this agent. Agent1
arc.port=port number Port number that can be used by Teradata ARC to 25268
manage ARC streams.
cluster.enabled= setting When set to True, establishes a connection to a False
for cluster secondary Java Message Service (JMS) broker in case
the primary JMS broker fails.
broker.port=port number The port number of the machine where the Java 61616
Message Service (JMS) Message Broker is listening.
broker.url=url The hostname or IP address of the machine running localhost
the Java Message Service (JMS) Message Broker.
log4j.appender.logfile=org. Informs the logging application to use a specific
apache.log4j.RollingFileApp appender.
ender It is recommended that this property value not be
changed.
log4j.appender.logfile.file Relative or absolute path of the log file. If changing log dmAgent.log
=log file path file location, specify the absolute path of the file. For
Windows, specify back slash instead of forward slash,
for example, C:\ProgramFile\Teradata\Log
\dmAgent.log.
Unity Data Mover

Both file path and file name can be set dynamically.1

log4j.appender.logfile.layo Dynamic property. 1
ut=org.apache.log4j.Pattern Note: Do not edit. This is an internal setting for logging
Layout infrastructure.
log4j.appender.logfile.maxB The number of backup logging files that are created. 3

ackupIndex=number of backup After the maximum number of files has been created,
logging files the oldest file is erased. Dynamic property. 1
Example
dmAgent.log.1
dmAgent.log.2
dmAgent.log.3
If the current dmAgent.log size exceeds 10MB, it rolls
to become the new dmAgent.log.1 and a new
dmAgent.log is created. The previous
dmAgent.log.2 becomes the new dmAgent.log.3.
The previous dmAgent.log.3 is deleted.
log4j.appender.logfile.maxF The maximum size of the logging file before being 10MB
ileSize=maximum size of log rolled over to backup files. Dynamic property. 1
files
log4j.appender.logfile.layo The pattern of the log file layout, where: %d [%t] %-5p %c{3}
ut.ConversionPattern=log d = date - %m%n
file pattern layout t = thread
p = log level
c = class name
m= message
n = message
Dynamic property. 1 Information for creating a layout
is at: http://logging.apache.org/log4j/1.2/apidocs/org/
apache/log4j/PatternLayout.html
log4j.rootLogger=level of 6 levels of logging, TRACE | DEBUG | INFO | WARN | INFO,logfile
logging ERROR | FATAL. From trace level to application error.
LOG_LEVEL can be updated dynamically, but not
logfile.1
Value is:
LOG_LEVEL, logfile
agent.maxConcurrentTasks=ma The maximum number of tasks allowed to run on this 5

ximum number of tasks agent at the same time.
Unity Data Mover

Configuring the Data Mover Command-Line Interface
Note that tasks are distributed to agents using a round

robin method. Task size is not currently considered, so
load may not be balanced if one agent is randomly
assigned larger tasks than another.
logger.useTviLogger=setting The TVI logger can be set to true or false. If set to True
for TVI messages true, fatal error messages are sent to TVI. Dynamic
property. 1
1Dynamic Properties
updated agent.properties file is saved. There is no need to restart the agent service if you
are only updating dynamic properties. For example:
If you changed the value of log4j.rootLogger from the default of INFO, logfile to
DEBUG, logfile, any debug messages generated would start appearing in the log file
one minute after saving the updated properties file.
If you changed the value of agent.maxConcurrentTasks from the default value of 5 to
a new value of 6, the new value of 6 would take effect one minute after saving the updated
agent.properties file.
Configuring the Data Mover Command-Line

Interface
Configuring the Data Mover Command-Line Interface on a Linux Teradata

Server
The Data Mover Command-Line Interface is installed for Linux Teradata servers with PUT.
Configure the commandline properties if you want to customize these settings.
1 Edit the commandline.properties file located in the /etc/opt/teradata/
datamover directory.
Installing and Configuring the Data Mover Command-Line Interface on

Non-Teradata Servers
The Data Mover Command-Line Interface must be installed for Linux on non-Teradata
servers, Windows, Solaris Sparc, and IBM AIX systems using the following procedure. You
cannot use PUT to install the Command-Line Interface on those systems.
Steps 1 through 4 do not apply to installation on Windows systems.
1 Add the following lines of code to the end of the /etc/profile file to update the
JAVA_HOME and PATH environment variables for all users:
export JAVA_HOME={full path of java installation location}
Unity Data Mover

export PATH=$JAVA_HOME/bin:$PATH
2 Run the command: source /etc/profile
3 Run the command: java -version and verify that the output shows JRE.1.7.
4 Open the .profile file of the root user and verify that the values for the JAVA_HOME
and PATH environment variables are the same as those defined in/etc/profile.
If the values are different, the java -version command will not produce the correct
output during install time, and the installation will fail.
5 Install the appropriate DMCmdline software package for your system as follows:
Operating Actions
System
Linux (for a. At the command line, type export DM_INTERACTIVE_INSTALL=1 to set
non- the environment variable for interactive install.
Teradata
b. At the command line, type the following:
servers)
gunzip DMCmdline__linux_i386.15.10.00.00.tar.gz
tar xvf DMCmdline__linux_i386.15.10.00.00.tar
cd DMCmdline.15.10*
rpm -Uvh DMCmdline__linux_noarch.15.10.00.00-1.rpm
c. Answer the prompts as needed, and press Enter to accept the defaults where
appropriate.
d. Type rpm -qa |grep DMCmdline to verify the installation.
Windows a. Copy the Data Mover directory on the media to a folder on the hard drive.
b. Go to DataMover/Windows and unzip tdm-
windows__windows_i386.15.10.00.00.zip.
c. Go to the DISK1 directory and run setup.exe.
d. Answer the prompts as needed and press Next to accept defaults where
appropriate.
e. Click Install when finished.
f. Go to Start > Control Panel > Add or Remove Programs to verify
installation.
Solaris a. At the command line, type the following to install:

Sparc
gunzip tdm-solaris__solaris_sparc.15.10.00.00.tar.gz
tar xvf tdm-solaris__solaris_sparc.15.10.00.00.tar
pkgadd -d 'pwd' DMCmdline
b. Answer the prompts as needed and press Enter to accept defaults where
appropriate.
c. Type pkginfo -l DMCmdline to verify the installation.
IBM AIX a. At the command line, type the following to install:

gunzip tdm-aix__aix_power.15.10.00.00.tar.gz
tar xvf tdm-aix__aix_power.15.10.00.00.tar
Unity Data Mover

Operating Actions
System
installp -acF -d ./DMCmdline DMCmdline

b. Answer the prompts as needed and press Enter to accept defaults where
appropriate.
c. Type lslpp -l "DM*" to verify the installation.
6 If the broker URL needs to be changed, edit the commandline.properties file located
in the TDM_install_directory\CommandLine\commandline.properties
directory after installation.
7 Specify the broker URL and broker port number for communicating with the JMS bus.
The broker URL value is the machine name or IP address of the machine where
ActiveMQ runs. The broker port value should also be the same as the port number that
ActiveMQ uses. The defaults are broker.url=localhost and broker.port=61616.
The commandline.properties File

cluster.enabled= setting When set to True, establishes a connection to a secondary Java False
for cluster Message Service (JMS) broker in case the primary JMS broker fails.
broker.port=<port> The port number of the machine where the Java Message Service 61616
(JMS) Message Broker is listening.
broker.url=<url> The hostname or IP address of the machine running the Java localhost
Message Service (JMS) Message Broker.
log4j.appender.logfile=o Informs the logging application to use a specific appender.
rg.apache.log4j.RollingF It is recommended that this property value not be changed.
ileAppender
log4j.appender.logfile.f Relative or absolute path of the logfile. If changing log file location, dmCommandLine
ile=<file path name> specify the absolute path of the file. For Windows, specify back slash .log
instead of forward slash, for example, C:\Program File
\Teradata\Log\dmCommandLine.log.
log4j.appender.logfile.l Note: Do not edit. This is an internal setting for logging
ayout=org.apache.log4j.P infrastructure.
atternLayout
log4j.appender.logfile.m The number of backup logging files that are created. After the 3
axBackupIndex=<number of maximum number of files has been created, the oldest file is erased.
backup files> Example
dmCommandLine.log.1
dmCommandLine.log.2
dmCommandLine.log.3
Unity Data Mover

About Configuring High Availability
If the current dmCommandLine.log size exceeds 10MB, it rolls to

become the new dmCommandLine.log.1 and a new
dmCommandLine.log is created. The previous
dmCommandLine.log.2 becomes the new dmCommandLine.log.
3. The previous dmCommandLine.log.3 is deleted.
log4j.appender.logfile.m The maximum size of the logging file before being rolled over to 10MB
axFileSize=<maximum size backup files.
of log files>
log4j.appender.logfile.l The pattern of the log file layout, where: %d [%t] %-5p
ayout.ConversionPattern= d = date %c{3} - %m%n
<log file pattern t = thread
layout> p = log level
c = class name
m= message
n = message
Information for creating a layout is at: http://logging.apache.org/
log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html
log4j.rootLogger=<level 6 levels of logging, TRACE < DEBUG < INFO < WARN < ERROR < INFO,logfile
of logging> FATAL. From trace level to application error.
Value is:
<LOG_LEVEL>, logfile

A High Availability configuration is the base configuration for a Data Mover system. If the
primary component of a system goes down, a High Availability configuration ensures that
the system continues to function with a secondary component.
This configuration depends on a monitoring service, which monitors the primary, or master,
components through SSH connections to see if services are running. If any of the main
components are down, a failover sequence begins the process of allowing the slave
component to take over for the master component. The daemon, agent and Sync service that
will be monitored by the monitoring service on the master and slave components must be
run using user dmuser with default password (dmuser). The monitoring service cannot be
used to monitor the daemon, agent and Sync service components if a user other than
dmuser has been set up to run these services.
The following work together to maintain High Availability:
SSH logons
Dual Active Java Message Service (JMS) brokers
Synchronization service
Master and slave components
Unity Data Mover

Configuring Automatic Failover
Data Mover provides automatic failover support when multiple Data Mover servers are
configured in a dual environment. Automatic failover configuration requires that:
You have two additional monitoring severs to monitor the master and slave components.
It is highly recommended that you use a Viewpoint managed server for this purpose.
Each monitoring server must be local to the site and ideally be attached to the same
network as the components being monitored to avoid automatic failovers caused by
network partitions.
The DMFailover package must be installed on all servers, including the master and slave
daemon, monitoring, and agent servers that are part of the cluster.
If additional monitoring servers are not available, you can enable failover by using the Data
Mover synchronization service. The synchronization service alone does not support
automatic failover and requires manual intervention to enable failover from master to slave
components. If configuring the synchronization service without configuring automatic
failover, see Configuring the Synchronization Service Without Automatic Failover.
The following files, located in the /opt/teradata/client/nn.nn/datamover/
failover/ folder, are required when using the monitoring service. The product version is
indicated by the nn.nn in the filename.
File Description
/etc/opt/teradata/ Specifies the master and slave components to be monitored
datamover/
failover.properties
/opt/teradata/client/ Script for setting up SSH log on, configuring the servers in master and slave modes, starting
nn.nn/datamover/ and stopping the monitoring service, and checking the status of the master and slave
failover/dmcluster components
/opt/teradata/client/ Executable binary file used for automatic failover
nn.nn/datamover/
failover/DMFailover.jar
/opt/teradata/client/ Specifies if TVI alerts need to be sent if the monitoring service detects a failure. This file is
nn.nn/datamover/ used only on the monitoring server.
failover/
monitor.properties
The following tasks must be performed to configure automatic failover:

1. Synchronizing Master and Slave Repository
2. Configuring Dual Active Java Message Service (JMS) Brokers
3. Configuring the Synchronization Service
4. Configuring the Cluster and Starting the Monitoring Service
5. Checking the Status of Master and Slave Components
6. Enabling Synchronization
Unity Data Mover

Synchronizing Master and Slave Repository

Before starting the failover service, the master and slave repositories must be synchronized.
If they are not synchronized, the slave may not function correctly after it is switched to
master mode when failover occurs.
1 Run /opt/teradata/client/nn.nn/datamover/failover/dmcluster
stopmonitor on the master and slave monitor systems, if they are running.
2 Ensure that both master and slave daemon have no running jobs., if they are, wait until
they finish or stop and cleanup them up.
3 Run /opt/teradata/datamover/nn.nn/dmsync stop on the master and the slave
to stop the synchronization services, if they are running.
4 Run datamove backup_daemon on the master to back up the repository. By default,
backup_daemon writes backup files to /var /opt/teradata/datamover/
daemon_backup.
5 Run /etc/init.d/dmdaemon stop on the master to stop the daemon on the master.
6 Copy the directory on the master containing the backup files to the slave.
7 Give the appropriate permissions to the backup files on the slave by executing chmod -
R 755 <directory_name> on the directory containing the backup files.
8 Run /etc/init.d/dmdaemon start on the slave to start the daemon on the slave.
9 If you used the default backup directory for backup_daemon, run datamove
restore_daemon -backup_target_dir /var/opt/teradata/datamover/
daemon/daemon_backup to restore the repository to the slave.
10 Run /etc/init.d/dmdaemon stop on the slave to stop the daemon on the slave.
11 After synchronizing the master and slave repositories, delete the following files, if they
exist, before starting the failover service:
dmSyncMaster.sql and slave_x.lastread on the master server
dmSyncSlave.sql and slave_sql.lastExecuted on the slave server
These files are created under the path specified by the sql.log.directory property in the
sync.properties file
Note: Do not delete the files until after you have run the backup_daemon and
restore_daemon commands.
Configuring Dual Active Java Message Service (JMS) Brokers

Dual active Java Message Service (JMS) brokers ensure that there is no loss of service if a
primary JMS broker is down. The files needed on both the local and remote sites to
configure dual active JMS brokers are:
daemon.properties
agent.properties
commandline.properties
Unity Data Mover

1 Log onto the local daemon host and run the following command as root:
./dmcluster configactivemq -e true -s slaveDaemonHost-p 61616
2 Log on to the remote daemon host and run the following command as root:
./dmcluster configactivemq -e true -s masterDaemonHost -p 61616
Where:
Designation Description
-e Enable network of brokers configuration
-s Remote host/server name where the other

ActiveMQ instance is running
-p Port to connect to the remote ActiveMQ
3 Inspect TDActiveMQ logs to ensure no errors/warnings are present:

/var/opt/teradata/tdactivemq/logs/activemq.log
4 Enter cluster.enabled=true in daemon.properties, agent.properties, and
commandline.properties on the local and remote sites to enable connection to a
secondary JMS broker.
5 Edit the broker.url property in daemon.properties, agent.properties, and
commandline.properties on the local and remote sites to specify a secondary JMS
host.
For example, enter: broker.url=primaryJmshost, secondaryJmsHost
On the local site, the primaryJmshost will be the master daemon host and the
secondaryJmsHost will be the slave daemon host. On the remote site, the primaryJmshost
will be the slave daemon host and the secondaryJmsHost will be the master daemon host.
Note: In order to restore the ActiveMQ to the standard, non-cluster configuration, run
the command ./dmcluster configactivemq -e false on the local and remote
daemon hosts. Inspect TDActiveMQ logs to ensure that TDActiveMQ is restarted in a
standard (non-cluster) configuration with no errors.
Configuring the Sync Service
1 Log on to the Master Sync service host on local.repository.host and edit the
sync.properties file:
a Specify the master.port as the port through which the Master and Slave
synchronization services communicate.
b Specify the master.host as remote.repository.host, which is the name of the
host where the Synchronization service will run.
2 Log on to the Slave Sync service host on remote.repository.host and edit the
sync.properties file:
a Specify the master.port as the port through which the Master and Slave
synchronization services communicate.
Unity Data Mover

b Specify the master.host as local.repository.host, which is the name of the

host where the other Synchronization service will run.
The sync.isMaster property does not need to be modified. The failover process is
responsible for starting the Sync service as Master or Slave when a failover occurs.
Configuring the Cluster and Starting the Monitoring Service

The monitoring service uses SSH connections to the servers it monitors. This command
typically takes a few minutes to complete and does the following:
Sets up the SSH logons for the monitoring services so that they can log on without a
password to the servers where the monitored components are installed.
Stops all Data Mover services except ActiveMQ on the remote site.
Configures and starts the local daemon, agents, and local sync service in master mode.
Starts the remote sync service in slave mode.
Starts the monitoring service on local.monitor.host to monitor the local Data
Mover components.
1 Log on to the master daemon server and edit the /etc/opt/teradata/datamover/
failover.properties file for your system. For details about the Failover.properties
file, see Failover.properties File
2 Run the following command as root:
./dmcluster config
Note: In a default installation, the master repository host is the same as the master
daemon host and the slave repository host is the same as the slave daemon host.
Failover.properties File
The Data Mover failover.properties file contains the files that control the failover process.
When setting up your failover process, edit these files according to the system you are
configuring.
Property Name Description
local.daemon.host Host where the local (master) daemon runs.
remote.daemon.host Host where the remote (slave) daemon runs.
local.monitor.host Host where the monitoring service that monitors the local (master) services runs.
remote.monitor.host Host where the monitoring service that monitors the remote (slave) services runs.
local.repository.host Host where the repository used by the local daemon is installed.
This should be the same host the synchronization service is installed on. If the
repository is installed on the same server as the daemon, this value is the same as
local.daemon.host.
remote.repository.host Host where the repository used by the remote daemon is installed.
This should be the same host the synchronization service is installed on. If the
repository is installed on the same server as the daemon, this value is the same as
remote.daemon.host.
Unity Data Mover

Property Name Description

local.agents.host Host where the agents used by the local (master) daemon are installed. If more than
one agent is used, specify a comma-separated list of agents; the order of the list does
not matter.
remote.agents.host The hosts where the agents used by the remote (slave) daemon are installed. If more
than one agent is used, specify a comma-separated list of agents; the order of the list
does not matter.
If external agents are shared between the master and slave, the shared agent names must be
specified for both local.agents.host and remote.agents.host.
Checking the Status of Master and Slave Components
1 Use the following command to verify the status of the cluster:
./dmcluster status
You should see something similar to the following:

---------------------------------------------------------------------------------------
| LOCAL CLUSTER |
---------------------------------------------------------------------------------------
| COMPONENT | HOST NAME | STATUS |
---------------------------------------------------------------------------------------
| DM Daemon | 10.25.33.31 | RUNNING |
| ActiveMQ | 10.25.33.31 | RUNNING |
| DM Monitoring Service | 10.25.32.163 | RUNNING |
| DM Sync Service | 10.25.33.31 | MASTER |
| DM Agent | 10.25.33.31 | RUNNING |
---------------------------------------------------------------------------------------
| REMOTE CLUSTER |
---------------------------------------------------------------------------------------
| COMPONENT | HOST NAME | STATUS |
---------------------------------------------------------------------------------------
| DM Daemon | 153.64.29.55 | STOPPED |
| ActiveMQ | 153.64.29.55 | RUNNING |
| DM Monitoring Service | 10.25.33.245 | STOPPED |
| DM Sync Service | 153.64.29.55 | SLAVE |
| DM Agent | 153.64.29.55 | STOPPED |
---------------------------------------------------------------------------------------
Enabling Synchronization
1 Run the list_configuration command on the Master Daemon server.

The resulting configuration file is ./configuration.xml.
2 Edit this file by setting the value for the key job.useSyncService under the property
element to TRUE.
The default value for this key is FALSE.
3 Run the save_configuration command.
Unity Data Mover

Configuring Data Mover to Use Unity Ecosystem Manager
Configuring the Synchronization Service Without Automatic Failover
You can configure the synchronization service to enable failover when automatic failover
cannot be used. The synchronization service uses the following files:
File Description
/etc/opt/teradata/datamover/sync.properties Settings that the Data Mover Replication Service uses for
synchronizing master with slave repositories
/opt/teradata/datamover/daemon/nn.nn/ Executable binary file used by the synchronization services
DMReplication.jar
/opt/teradata/datamover/daemon/nn.nn/dmsync Script for starting the synchronization service
Note: nn.nn refers to the major and minor version number of the product.
Configuring the Synchronization Service
1 Edit the sync.properties file on the Master Sync server and set the sync.isMaster
property to true.
2 Edit the sync.properties file on the Slave Sync server and set the sync.isMaster
property to false.
3 Set the master.port property in the sync.properties file on the Master and Slave
Sync server as the port through which the master and slave synchronization services
communicate.
4 Run /opt/teradata/datamover/daemon/nn.nn/dmsync start on the Master Sync
server to start the synchronization service as Slave.
5 Run /opt/teradata/datamover/daemon/nn.nn/dmsync start on the Slave Sync
server to start the synchronization service as Slave.
6 When the Synchronization services are started, enable synchronization by setting the
job.useSyncService configuration property to true.
Configuring Data Mover to Use Unity Ecosystem

Manager
1 In the /etc/opt/teradata/datamover/apiconfig.xml file, edit the host and
port properties for the location of the Resilient Publisher.
2 Run the list_configuration command to output a configuration file.
For more information, see the Unity Data Mover User Guide.
3 Set the appropriate values for the configuration settings for your site.
Parameter Description Default

tmsm.frequency.bytes Controls the frequency, in number of bytes/MB/GB, of job 2147483647
progress events sent to Unity Ecosystem Manager.
Unity Data Mover

Configuring Multiple Managed Servers
Parameter Description Default
Note: Using a low value can hurt performance. The

recommendation is to use the default value.
tmsm.mode Controls how Data Mover directs Unity Ecosystem Manager NONE
messages.
Valid Values:
BOTH
ONLY_REAL_TMSM
ONLY_INTERNAL_TMSM
NONE
When set to:
BOTH, messages are sent to the Unity Ecosystem Manager
system and written to the table-driven interface event tables.
ONLY_INTERNAL_TMSM, Data Mover only writes
messages to the TMSMEVENT table defined by the table-
driven interface.
ONLY_REAL_TMSM, Data Mover only sends messages to
the Unity Ecosystem Manager system.
If Data Mover cannot send events to the real Unity Ecosystem
Manager product then those events will be stored in a
store.dat file located in the INSTALLDIR/teradata/
datamover/daemon/nn.nn/null/dataStore directory. If
the value for tmsm.mode is BOTH or ONLY_REAL_TMSM,
and Data Mover cannot send events to the real Unity Ecosystem
Manager product, then the store.dat file can grow to be very
large. To prevent the store.dat file from taking up too much
disk space on the DM managed server, change the value for
tmsm.mode to ONLY_INTERNAL_TMSM or NONE, or make
sure Data Mover can send events to the real Unity Ecosystem
Manager product.
For more information about Unity Ecosystem Manager, see the Unity Ecosystem Manager
User Guide.
Configuring Multiple Managed Servers

Having more than one Data Mover managed server in the environment can improve
performance when copying data from one Teradata Database system to another. Each Data
Mover managed server can have one or more Data Mover components running on it.
If the Data Mover agent must be run on a system other than the Data Mover daemon, the
host name for the server running the Data Mover daemon must be resolved to a publicly-
accessible IP address in the /etc/hosts file.
Unity Data Mover

Configuring Data Mover to Log to TVI
If only agents are running on the additional Data Mover managed servers, they must be
configured to work with the Data Mover managed server that has the Data Mover daemon
running on it.
When using multiple Data Mover agents, each Data Mover agent must have a unique Agent
ID.
1 Provide the correct Apache Active MQ broker url and port number values in one
of the following ways:
During installation of the Data Mover agent component on the Data Mover managed
server
After installation by modifying the broker.url and broker.port in the
agent.properties file where ActiveMQ runs.
2 Edit the Agent ID property in the agent.properties file.
3 Restart the Data Mover agent service to implement the changes.
Configuring Data Mover to Log to TVI

The logger.useTviLogger property in the agent.properties and
daemon.properties files configures Unity Data Mover to log to Teradata Vital Structure
(TVI). The property defaults to True, so logging to TVI is automatic and allows critical
failures to be reported to Teradata immediately.
1 Log on to the agent and daemon servers and do the following:
a Set the logger.useTviLogger property in the daemon.properties file to True.
b Set the logger.useTviLogger property in the agent.properties file to True.
Enabling Logging TVI Alerts When a Failover Occurs
1 Log on to the local and remote monitoring servers: local.monitor.host and

remote.monitor.host.
2 On /opt/teradata/client/nn.nn/datamover/failover/
monitor.properties, do the following:
Set the value for monitor.useTviLogger as True.
Make sure that tvilogger.properties exists and has been configured with the
correct TVI logging method.
Configuring Data Mover Managed Server to

Increase Network Throughput
All network traffic coming into and out of the DM managed server goes through the default
Ethernet port for the server unless it is specifically routed. If the default Ethernet port is used
Unity Data Mover

Configuring Data Mover Managed Server to Increase Network Throughput
for all network communication, the other network ports on the DM managed server are
wasted. This could cause the network to slow down when processing Data Mover jobs, which
could lead to poor performance when copying data.
Data Mover jobs execute much faster if multiple Ethernet ports are used when copying data
between Teradata Database systems. The recommended way to increase network throughput
on the DM managed server is to set up specific network routes for all of the COP entries on
the source and target Teradata Database systems in the Data Mover jobs. A COP entry is the
IP address of a Teradata Database node. These specific network routes allow the DM Agent to
connect TCP sessions to the source and target systems using different Ethernet ports on the
DM managed server. This improves performance by distributing data across all available
network ports.
The topics in this section describe how to set up the routes using a 2-node Teradata Database
system called dmdev as a source and a 2-node Teradata Database system called dmtest as
target. The examples in this section assume the network ports eth4 and eth5 are connected
and available for use on the DM managed server.
Note: More than two ports on the DM managed server could be available in a customer
environment. The examples in this section use only 2-node source and target systems and
two available network ports on the DM managed server.
1 Add the IP addresses for all source and target COP entries in the /etc/hosts file on the
DM managed server.
2 Define the specific routes for the COP entries in the /etc/sysconfig/network/
routes file on the DM managed server.
3 Restart the network on the DM managed server.
4 Verify the route changes are in place on the DM managed server.
About Adding Source and Target COP Entries
The best way to define the IP addresses for the source and target COP entries is to configure
them through DNS. The example below defines the IP addresses for the source and target
COP entries in the /etc/hosts file instead because it is easier to explain all of the steps this
way.
The IP addresses (COP entries) for all nodes on the source and target systems are placed in
the /etc/hosts file so the DM Agent can resolve them when executing a job. Assume the
IP addresses of the two nodes on dmdev are 153.64.209.91 and 153.64.209.92, respectively,
and the IP addresses of the two nodes on dmtest are 153.64.106.78 and 153.64.106.79,
respectively, we add the following entries to the /etc/hosts file on the DM managed
server:
# COP entries for dmdev
153.64.209.91 dmdev dmdevcop1
153.64.209.92 dmdev dmdevcop2
# COP entries for dmtest

153.64.106.78 dmtest dmtestcop1
153.64.106.79 dmtest dmtestcop2
Unity Data Mover

Configuring Data Mover Managed Server to Increase Network Throughput
The COP entries for the source and target systems are now in the /etc/hosts file.
About Defining Routes for Source and Target COP Entries
Next, the network routes for the COP entries can be added to the /etc/sysconfig/
network/routes file. Assume the eth2 interface is used for all public network traffic to and
from the DM managed server and is, therefore, the default network interface for the server.
Assume the IP address 153.64.107.254 is the gateway for all traffic coming into and out of the
DM managed server. The following is added to the /etc/sysconfig/network/routes
file on the DM managed server to add specific routes for the COP entries on dmdev and
dmtest:
# default XXX.XXX.XXX.XXX - ethX

default 153.64.107.254 - eth2
# routes to system dmdev

153.64.209.91 153.64.107.254 - eth4
153.64.209.92 153.64.107.254 - eth4
# routes to system dmtest

153.64.106.78 153.64.107.254 - eth5
153.64.106.79 153.64.107.254 - eth5
These entries force all network traffic between the DM managed server and dmdev to use the
eth4 interface and all network traffic between the DM managed server and dmtest to use
the eth5 interface.
Restarting the Network
The network on the DM managed server must be restarted for the changes in the /etc/
sysconfig/network/routes file to take effect.
Notice: Be sure to check that restarting the network will not negatively affect any other users on the
server prior to executing this command.
1 Run the rcnetwork restart command to restart the network on the DM managed server.
About Verifying the Route Changes
The new routes configured can be verified with the ip or netstat commands. Following are
example outputs of these commands when the routes have been configured properly:
# ip route list
153.64.209.92 via 153.64.107.254 dev eth4
153.64.106.78 via 153.64.107.254 dev eth5
153.64.106.79 via 153.64.107.254 dev eth5
153.64.209.91 via 153.64.107.254 dev eth4
127.0.0.0/8 dev lo scope link
default via 153.64.107.254 dev eth2
Unity Data Mover

Data Mover Log Files
# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
153.64.209.92 153.64.107.254 255.255.255.255 UGH 0 0 0 eth4
153.64.106.78 153.64.107.254 255.255.255.255 UGH 0 0 0 eth5
153.64.106.79 153.64.107.254 255.255.255.255 UGH 0 0 0 eth5
153.64.209.91 153.64.107.254 255.255.255.255 UGH 0 0 0 eth4
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 153.64.107.254 0.0.0.0 UG 0 0 0 eth2
Data Mover Log Files

Data Mover log files are moved to the /var/opt/teradata/datamover/logs directory
as follows:
dmDaemon.log
dmAgent.log
dmSync.log
dmFailover.log
upgrade_backup.log
During Data Mover installation and upgrade, the log files are preserved with up to 10
backups. For example, dmdaemon-postinstall.log backups are preserved as dm-daemon-
postinstall.log.1, dmdaemon-postinstall.log.2, etc., up to dmdaemon-
postinstall.log10, where the most recent file is dmdaemon-postinstall.log.1. The
following log files, with date and timestamp details added, are preserved during installations
and upgrades:
/tmp/dmdaemon-postinstall.log
/tmp/dmagent-postinstall.log
/tmp/put-dmschemaupgrade.log
/tmp/put-dmlistagents.log
/var/opt/teradata/datamover/logs/upgrade_backup.log
Unity Data Mover

CHAPTER 3
Upgrading Software
About Upgrading Data Mover Software

You can upgrade the Unity Data Mover DMCmdline software package on non-Teradata
servers by following this process:
1. Create an incident on Teradata at Your Service.
2. Uninstall the DMCmdline package on your operating system.
3. Reinstall the DMCmdline package on your operating system.
4. Contact your Customer Service Representative.
Note: All Data Mover upgrades except for the DMCmdline package are performed by
Teradata Customer Support.
Note: The DMFailover package from the monitoring servers should be the same version as
the Failover package from the DM managed server.
Creating an Incident
You must obtain an Incident number from Teradata at Your Service prior to performing any
software upgrades.
1 On your Windows PC, open a web browser and go to Teradata At Your Service at https://
tays.teradata.com and log in.
2 Under the Product banner click Incident.
3 Click the Create tab.
4 Make the following selections as appropriate:
Note: Click the green arrows to move forward or back in the selection screens.
Option Description
Site The site where the activity will be performed.
Priority The Priority of the issue.
Product Area The area of the system where the issue is located or where work will be
performed.
Problem Type A list of Problem Types.
Unity Data Mover

Chapter 3 Upgrading Software
Upgrading the Data Mover Command-Line Interface on Non-Teradata Servers
Option Description
Synopsis A short Synopsis of the activity being performed.
Description A short description of the activity being performed.
5 Click Submit the Incident.

6 Click OK to confirm the submission of the incident.
The incident is added to the list of Incidents. The Status shows Pending (a blue circle)
until Customer Services accepts the incident, at which time the Status becomes Active (a
green circle).
Upgrading the Data Mover Command-Line

Interface on Non-Teradata Servers
The Data Mover Command-Line Interface must be installed for Solaris Sparc, IBM AIX,
Linux on non-Teradata servers, and Windows systems using the following procedures. You
cannot use PUT to install the Command-Line Interface on those systems.
Note: If there is an existing installation on the system, it must be uninstalled before re-
installing. You can have only one version of the Data Mover Command-Line package on a
server.
Steps 1 through 4 do not apply to installation on Windows systems.
1 Add the following lines of code to the end of the /etc/profile file to update the
JAVA_HOME and PATH environment variables for all users:
export JAVA_HOME={full path of java installation location}
export PATH=$JAVA_HOME/bin:$PATH
2 Run the command: source /etc/profile
3 Run the command: java -version and verify that the output shows JRE.1.7.
4 Open the .profile file of the root user and verify that the values for the JAVA_HOME
and PATH environment variables are the same as those defined in/etc/profile.
If the values are different, the java -version command will not produce the correct output
during install time, and the installation will fail.
5 Copy the properties file to an outside directory if you want to preserve any customization
that you made to the default values:
TDM_install_directory\CommandLine\commandline.properties
6 Uninstall and upgrade the appropriate software for your system as follows:
Unity Data Mover

Upgrading the Data Mover Command-Line Interface on Non-Teradata Servers
Operating Actions
System
Linux (for a. At the command line, type export DM_INTERACTIVE_INSTALL=1 to set
non- the environment variable for interactive install.
Teradata
b. At the command line, type the following:
servers)
gunzip DMCmdline__linux_i386.15.10.00.00.tar.gz
tar xvf DMCmdline__linux_i386.15.10.00.00.tar
cd DMCmdline.15.10*
rpm -Uvh DMCmdline__linux_noarch.15.10.00.00-1.rpm
c. Answer the prompts as needed, and press Enter to accept the defaults where
appropriate.
d. Type rpm -qa |grep DMCmdline to verify installation.
Solaris a. At the command line, type the following to uninstall:

Sparc
pkgrm DMCmdline
b. At the command line, type the following to upgrade:
gunzip tdm-solaris__solaris_sparc.15.10.00.00.tar.gz
tar xvf tdm-solaris__solaris_sparc.15.10.00.00.tar
pkgadd -d 'pwd' DMCmdline
c. Answer the prompts as needed and press Enter to accept defaults where
appropriate.
d. Type pkginfo -l DMCmdline to verify installation.
IBM AIX a. At the command line, type the following to uninstall:

installp -u DMCmdline
b. At the command line, type the following to upgrade:
gunzip tdm-aix__aix_power.15.10.00.00.tar.gz
tar xvf tdm-aix__aix_power.15.10.00.00.tar
installp -acF -d ./DMCmdline DMCmdline
c. Answer the prompts as needed and press Enter to accept defaults where
appropriate.
d. Type lslpp -l "DM*" to verify installation.
Windows a. To uninstall the existing DMCmdline software package, go to Start > Control
Panel > Add or Remove Programs; then, select Teradata Data Mover
Command Line Interface and click Remove.
b. Copy the Data Mover directory on the media to a folder on the hard drive.
c. Go to DataMover/Windows and unzip tdm-
windows__windows_i386.15.10.00.00.zip.
d. Go to the DISK1 directory and run setup.exe.
e. Answer the prompts as needed and press Next to accept defaults where
appropriate.
f. Click Install when finished.
Unity Data Mover

Upgrading the Data Mover Agent on a Linux Teradata Server
Operating Actions
System
g. Go to Start > Control Panel > Add or Remove Programs to verify

installation.
7 Restore the values from the properties file you copied to an outside directory if you want
to preserve any customization that you made to the default values and override the values
introduced by the patch
TDM_install_directory\CommandLine\commandline.properties
Upgrading the Data Mover Agent on a Linux

Teradata Server
You can upgrade the DMAgent software package for your system.
1 Copy the properties file to an outside directory if you want to preserve any customization
that you made to the default values:
TDM_install_directory\agent\agent.properties
2 Uninstall and upgrade the appropriate software for your system as follows:
Operating Actions
System
Linux (for non- a. At the command line, type the following to upgrade the DMAgent and
Teradata servers) TTU packages:
./ dminstallupgradeagent
b. Answer the prompts as needed, and press Enter to accept the defaults
where appropriate.
c. Type rpm -qa |grep DMAgent to verify the installation.
3 Restore the values from the properties file you copied to an outside directory if you want
to preserve any customization that you made to the default values and override the values
introduced by the patch:
TDM_install_directory\Agent\agent.properties
Unity Data Mover

APPENDIX A
Administrative Tasks
Data Mover Components Script

Data Mover 15.10 and later includes a single script that enables you to check status of, start,
or stop each Data Mover Component. The script name is dm-control.sh, and is installed
by the Data Mover daemon package on the Data Mover Managed Server in the
directory: /opt/teradata/datamover/daemon/15.10
The script includes the following commands:
Script Command Description
dm-control.sh status Displays status of Data Mover Daemon, Data
Mover Agent, Data Mover Sync, tmsmonitor,
Teradata Database, and Teradata ActiveMQ.
dm-control.sh start Starts all Data Mover components on the local
Data Mover Managed Server. This includes Data
Mover daemon, Data Mover agent, Teradata
ActiveMQ, and tmsmonitor. This does not
include the Data Mover sync service or the
failover monitoring service.
dm-control.sh stop Stops all Data Mover components on the local
Data Mover Managed Server. This includes Data
Mover daemon, Data Mover agent, Teradata
ActiveMQ, and tmsmonitor. This does not
include the Data Mover sync service or the
dm-control.sh restart Stops and starts all Data Mover components on
the local Data Mover Managed Server. This
includes Data Mover daemon, Data Mover agent,
Teradata ActiveMQ, and tmsmonitor. This does
not include the Data Mover sync service or the
Creating a Diagnostic Bundle for Support

For Data Mover situations such as job failure, job hanging, or other issues that require an
incident report, Teradata includes command-line, interactive scripts for collecting necessary
job and system information. The resulting diagnostic bundle enables Teradata Customer
Unity Data Mover

Appendix A Administrative Tasks
Creating a Diagnostic Bundle for Support
Support to provide optimum analysis and resolution. Customer support is available around-
the-clock, seven days a week through the Global Technical Support Center (GSC). To learn
more, go to https://tays.teradata.com.
1 Create a support incident including the following settings:
Option Setting
Product Area System Management Utilities
Problem Type Unity Data Mover
2 Record the incident number and leave it open to attach the diagnostic bundle.
Note: The interactive script prompts you to enter the incident number and other
information related to the issue.
3 Locate the scripts at /opt/teradata/datamover/support/ for every Data Mover
server in your environment, and do the following:
Server Type Description

Data Mover Managed Server Run dmsupport.sh to create a diagnostic bundle.
Server Running Only Data Mover Run dmagentsupport.sh to create a diagnostic
Agent bundle.
Be sure to include relevant problem descriptions for troubleshooting as prompted.

After the script collects the data, a bundle named DataMover-$currentdate-
$hostname-1.zip is created in /var/opt/teradata/datamover/support/
incidentnumber.
Note: If the bundle size is larger than 49MB, additional .zip files are created as follows:
DataMover-$currentdate-$hostname-2.zip
DataMover-$currentdate-$hostname-3.zip
4 Update the incident, browse to the resulting .zip files, attach the resulting files to the
incident, and submit them.
5 Contact Teradata Customer Support when the diagnostic bundle is ready for review, and
include your incident number for reference.
6 [Optional] If you do not wish to keep the .zip files, delete them from the
directory /var/opt/teradata/datamover/support/incidentnumber on the
Data Mover server.
Unity Data Mover


4102 035K

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

4102 035K

Încărcat de

Drepturi de autor:

Formate disponibile

What would you do if you knew?

Unity Data Mover

Configuring the Data Mover Daemon...............................................................................................................9

Unity Data Mover

About Upgrading Data Mover Software...........................................................................................................33

Data Mover Components Script........................................................................................................................ 37

Unity Data Mover

Unity Data Mover

Product Safety Information

Unity Data Mover

Data Mover Server Requirements

External Component Requirements

Required Open Ports on the Teradata Managed Server

Unity Data Mover

Port Number Used By

Best Practices for Data Mover Networking

Unity Data Mover

Configuring the Environment

Configuring the Data Mover Daemon

The daemon.properties File

Unity Data Mover

Property Description Default Value

Both file path and file name can be set dynamically.1

Unity Data Mover

Property Description Default Value

Information for creating a layout is at: http://

Property Description Default

Unity Data Mover

Property Description Default

Unity Data Mover

Property Description Default

Unity Data Mover

Property Description Default

job.default.queryband Provides a set of name/value pairs to be used as the default Applicatio

Unity Data Mover

Property Description Default

Configuring the Data Mover Agent

Unity Data Mover

Installing and Configuring the Data Mover Agent on a Linux Teradata

The agent.properties File

Unity Data Mover

Property Description Default Value

Both file path and file name can be set dynamically.1

log4j.appender.logfile.maxB The number of backup logging files that are created. 3

agent.maxConcurrentTasks=ma The maximum number of tasks allowed to run on this 5

Unity Data Mover

Property Description Default Value

Note that tasks are distributed to agents using a round

Configuring the Data Mover Command-Line

Configuring the Data Mover Command-Line Interface on a Linux Teradata

Installing and Configuring the Data Mover Command-Line Interface on

Unity Data Mover

Solaris a. At the command line, type the following to install:

IBM AIX a. At the command line, type the following to install:

Unity Data Mover

installp -acF -d ./DMCmdline DMCmdline

The commandline.properties File

Property Description Default Value

Unity Data Mover

Property Description Default Value

If the current dmCommandLine.log size exceeds 10MB, it rolls to

About Configuring High Availability

Unity Data Mover