How to Use and Understand Server Management Errors | Teradata Data Mover - 17.11 - Using Server Management Logging - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
17.11
Release Date
October 2021
Content Type
User Guide
Publication ID
B035-4101-091K
Language
English (United States)

Server Management allows critical failures, or TVI alerts, to be reported to Teradata immediately. Logging by Server Management is enabled by default, but can be disabled by setting the value of the logger.useTviLogger property in agent.properties or daemon.properties to false.

Server Management errors that are reported by Data Mover are listed below by message ID number. All of the errors are critical.

4601001
Synopsis: Daemon port in use.
Meaning: The daemon port that is used for inbound socket connections from agents is in use by some other process.
Probable Cause: Daemon port is in use by some other process.
Recommendations: Change the daemon port to an available port number or terminate any process that is using the existing daemon port.
4601002
Synopsis: Unexpected repository state.
Meaning: The Data Mover repository is in an unexpected state.
Probable Cause: The Data Mover repository server may be down or the repository may not have the correct list of tables.
Recommendations: The Postgres instance being used as the Data Mover repository may not have logons enabled or it may need to be restarted. The Data Mover Daemon may need to be re-installed to update the repository with the correct list of tables as well.
4601003
Synopsis: Daemon cannot connect to JMS broker.
Meaning: The JMS broker is unreachable from the daemon.
Probable Cause: ActiveMQ service may be down or daemon may have incorrect broker port/url configuration.
Recommendations: Restart ActiveMQ Service. Verify broker port/url on the daemon.
4601004
Synopsis: Daemon cannot connect to agent.
Meaning: Data Mover agents cannot be reached.
Probable Cause: Data Mover agent may be down.
Recommendations: Restart the Data Mover agent.
4601005
Synopsis: Insufficient space in job repository.
Meaning: The Data Mover job repository has run out of space.
Probable Cause: Insufficient space allocation to the job repository.
Recommendations: Check disk space for directory /var/opt/teradata/postgres/data. Allocate more space to this directory or clean up old jobs or delete old log files in directory /var/opt/teradata/postgres/data/log/.
4601006
Synopsis: Daemon cannot write to the specified Event table.
Meaning: The Data Mover Job cannot write events to the specified Event table.
Probable Cause: Event table is not reachable or there is no more room available in the Event table database.
Recommendations: Check if the Event table is accessible from the Data Mover Daemon server. Also check if the Event table database has sufficient space to store new events.
4601007
Synopsis: The daemon repository purge task has timed out multiple times.
Meaning: The Data Mover job respository is not being cleaned properly.
Probable Cause: The database may be locked or overloaded.
Recommendations: Ensure that the Data Mover repository is not locked by another process. Ensure that the Data Mover repository is not on a shared database which is frequently busy with other requests.
4601008
Synopsis: Data Mover Repository exceeded threshold.
Meaning: The row count in one or more repository tables exceeded the threshold limit of 1 million rows.
Probable Cause: Data Mover performance may degrade and failures may occur.
Recommendations: Confirm the Data Mover Purge service is enabled; if the Purge service is already enabled, modify the purge process to purge additional data.
4602001
Synopsis: Agent cannot connect to JMS broker.
Meaning: The JMS broker is unreachable from the agent.
Probable Cause: ActiveMQ service may be down or agent may have incorrect broker port/url configuration.
Recommendations: Restart ActiveMQ Service. Verify broker port/url on agent.
4603001
Synopsis: Data Mover daemon component is unavailable.
Meaning: The Data Mover Monitoring Service cannot detect the Data Mover daemon component.
Probable Cause: The Data Mover daemon or the Data Mover daemon server may be down.
Recommendations: Failover has been initiated to switch DM components to run on standby. Please investigate the root cause of the failure and run “dmcluster switchback” on the active server when the problem is addressed.
4603002
Synopsis: Data Mover repository is unavailable.
Meaning: The Data Mover monitoring service cannot detect the Data Mover repository database.
Probable Cause: The Data Mover repository database may not be running or the Data Mover repository server may be down.
Recommendations: Failover has been initiated to switch DM components to run on standby. Please investigate the root cause of the failure and run “dmcluster switchback” on the active server when the problem is addressed.
4603003
Synopsis: All Data Mover agent components are unavailable.
Meaning: The Data Mover monitoring service cannot detect any running Data Mover agent components.
Probable Cause: All the Data Mover agent components may be down.
Recommendations: Failover has been initiated to switch DM components to run on standby. Please investigate the root cause of the failure and run “dmcluster switchback” on the active server when the problem is addressed.
4603005
Synopsis: Data Mover Sync Monitor is unavailable on active server.
Meaning: The Data Mover Failover Monitoring service cannot detect the Sync Monitor, which tracks the replication progress when DM components are running on active.
Probable Cause: The Sync Monitor may not be running.
Recommendations: Check DM Sync log on active server. If replication service is broken, run 'dmcluster switchback' to reconfigure.
4603009
Synopsis: ActiveMQ component is unavailable.
Meaning: The Data Mover Failover Monitoring Service cannot detect the ActiveMQ component.
Probable Cause: ActiveMQ component may not be running.
Recommendations: Failover has been initiated to switch DM components to run on standby. Please investigate the root cause of the failure and run “dmcluster switchback” on the active server when the problem is addressed.
4603011
Synopsis: Data Mover REST component is unavailable.
Meaning: The Data Mover Monitoring Service cannot detect the Data Mover REST component.
Probable Cause: Data Mover REST component may be down.
Recommendations: Failover has been initiated to switch DM components to run on standby. Please investigate the root cause of the failure and run “dmcluster switchback” on the active server when the problem is addressed.
4603101
Synopsis: Data Mover Daemon component is unavailable.
Meaning: The Data Mover Failover Monitoring Service cannot detect the Data Mover Daemon component.
Probable Cause: The Data Mover Daemon or the Data Mover Daemon server may be down.
Recommendations: No failover will occur as DM components are already running on standby due to previous failover. Please investigate the root cause of the failover and run “dmcluster switchback” on the active server when the problem is addressed.
4603102
Synopsis: Data Mover Repository is unavailable.
Meaning: The Data Mover Failover Monitoring Service cannot detect the Data Mover Repository Database.
Probable Cause: The Data Mover Repository Database may not be running or the the Data Mover Repository server may be down.
Recommendations: No failover will occur as DM components are already running on standby due to previous failover. Please investigate the root cause of the failover and run “dmcluster switchback” on the active server when the problem is addressed.
4603103
Synopsis: All Data Mover Agent components are unavailable.
Meaning: The Data Mover Failover Monitoring Service cannot detect any running Data Mover Agent components.
Probable Cause: All the Data Mover Agent components may be down.
Recommendations: No failover will occur as DM components are already running on standby due to previous failover. Please investigate the root cause of the failover and run “dmcluster switchback” on the active server when the problem is addressed.
4603109
Synopsis: ActiveMQ component is unavailable.
Meaning: The Data Mover Failover Monitoring Service cannot detect the ActiveMQ component.
Probable Cause: ActiveMQ component may not be running.
Recommendations: No failover will occur as DM components are already running on standby due to previous failover. Please investigate the root cause of the failover and run “dmcluster switchback” on the active server when the problem is addressed.
4603111
Synopsis: Data Mover REST component is unavailable.
Meaning: The Data Mover Monitoring Service cannot detect the Data Mover REST component.
Probable Cause: Data Mover REST component may be down.
Recommendations: No failover will occur as DM components are already running on standby due to previous failover. Please investigate the root cause of the failover and run “dmcluster switchback” on the active server when the problem is addressed.
4604001
Synopsis: Data Mover sync monitor service stop running or cannot start.
Meaning: The sync monitor service stopped due to an error.
Probable Cause: The sync monitor service cannot connect to active repository or replication is broken.
Recommendations: Check sync service log for any database connectivity error. If replication is broken, run dmsync config to reconfigure replication service between active and standby repositories.
4604002
Synopsis: Standby repository has too much data lagging.
Meaning: The standby repository data replication is behind specified data lagging threshold.
Probable Cause: The standby repository data replication is too slow or has stopped working.
Recommendations: Check sync service log and postgres log for any error messages.
4604003
Synopsis: Replication slot is not active for a standby or replication data lagging values are null.
Meaning: The standby replication slot active flag value is false or the data lagging values are null.
Probable Cause: The replication between active and standby repository is broken.
Recommendations: Run dmsync config to reconfig replication service between active and standby repository.
Server Management life cycle errors that are reported by Data Mover are listed below by message ID number.
1601001
Synopsis: Data Mover daemon started.
Meaning: The Data Mover daemon component has been started.
Probable Cause: The Data Mover daemon component may have been restarted or the node was rebooted.
Recommendations: None.
1602001
Synopsis: Data Mover agent started.
Meaning: The Data Mover agent component has been started.
Probable Cause: The Data Mover agent component may have been restarted or the node was rebooted.
Recommendations: None.