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 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://access.teradata.com.
-
Create a support incident including the following settings:
Option Setting Product Area System Management Utilities Problem Type Teradata Data Mover -
Record the incident number and leave it open to attach the diagnostic bundle.
The interactive script prompts you to enter the incident number and other information related to the issue.
-
As the root user, locate the scripts at /opt/teradata/datamover/support/ for every Data Mover server in your environment, and do the following:
Be sure to include relevant problem descriptions for troubleshooting as prompted. The dmsupport.sh script collects the following information from the Data Mover log files on the Data Mover managed server:Server Type Description Data Mover Server Run dmsupport.sh to create a diagnostic bundle. Server Running Only Data Mover Agent Run dmagentsupport.sh to create a diagnostic bundle. - Activemq queue information
- Recent temp and task directories
The dmagentsupport.sh file collects the following information from a server running only the Data Mover agent:Output File Contents datamover-job-status - Data Mover health information
- Data Mover and TTU packages rpm information
- List of total and failed Data Mover jobs
- List of job steps for failed jobs
datamover-properties All data Mover properties files, including the following: - List of files from the Data Mover components installation directory
- ps aux command output
datamover-server-details OS, kernel, CPU, memory, and disk space information, including the following: - jstack and jmap output for tdactivemq, daemon, and agent processes
- Data Mover log files from the agent server
- Recent temp and task directories
- Data Mover agent.properties files
- List of files from the DataMover components installation directory
- OS, kernel, CPU, memory, and disk space information
- Data Mover and TTU packages rpm information
If the bundle size is larger than 49 MB, additional .zip files are created as follows:- DataMover-$currentdate-$hostname-2.zip
- DataMover-$currentdate-$hostname-3.zip
- Update the incident, browse to the resulting .zip files, attach the resulting files to the incident, and submit them.
- Contact Teradata Customer Support when the diagnostic bundle is ready for review, and include your incident number for reference.
- [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.