Server Management allows critical failures 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.
Data Mover server logs are frequently rolled up with an extension; in the list below, this is represented by an asterisk (*) for diagnostic bundle contents. For example, dmDaemon.log* represents the list of all dmDaemon logs available on the server. For more information about diagnostic bundles, see Creating a Diagnostic Bundle for Support.
- 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.
- Diagnostic Bundle Contains: dmDaemon.log*, daemon.properties
- 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.
- Diagnostic Bundle Contains: dmDaemon.log*
- Recommendations: The Teradata Database instance used as the Data Mover repository may not have logons enabled or may need to be restarted. The Data Mover daemon may also need to be re-installed to update the repository with the correct list of tables.
- 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.
- Diagnostic Bundle Contains: dmDaemon.log*, daemon.properties
- 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.
- Diagnostic Bundle Contains: dmAgent.log*, daemon.properties, agent.properties
- 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.
- Diagnostic Bundle Contains: dmDaemon.log*
- Recommendations: Allocate more space to the Repository or clean up old jobs.
- 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.
- Diagnostic Bundle Contains: dmDaemon.log*, daemon.properties
- 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.
- 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.
- Diagnostic Bundle Contains: dmAgent.log*, agent.properties
- 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: Restart the Data Mover daemon in Master/Slave mode.
- 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: Restart the Data Mover Repository Database.
- 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: Restart the Data Mover agents.
- 4604001
- Synopsis: Unable to start Data Mover slave sync service.
- Meaning: The slave sync service did not start correctly or stopped with an error.
- Probable Cause: The sync service failed when calling a stored procedure in the Data Mover repository. The stored procedure could be in a bad state.
- Diagnostic Bundle Contains: dmSync.log*, sync.properties
- Recommendations: Try running "call sqlj.redistribute_jar('DMXSPJar')" sql on the Data Mover repository.
- 4604002
- Synopsis: Data Mover slave sync service cannot connect to master node.
- Meaning: The slave sync service shut down because it cannot connect to the master node.
- Probable Cause: The master sync service shut down or is not accessible.
- Diagnostic Bundle Contains: dmSync.log*, sync.properties
- Recommendations: Check whether the master sync service is running and accessible from slave node.
- 4604003
- Synopsis: Data Mover slave sync service shut down with error when replicating repository.
- Meaning: The slave sync service encountered a fatal error when replicating the repository and shut down.
- Probable Cause: The slave sync service may have failed to run a stored procedure to replicate the repository and needs to shut down.
- Diagnostic Bundle Contains: dmSync.log*, sync.properties
- Recommendations: Check the sync service log for detail of the sql error messages.
- 4604004
- Synopsis: Data Mover slave sync service failed to execute sql received from master node.
- Meaning: The slave sync service failed to run sql received from master node. The master node and slave node could be out of sync.
- Probable Cause: The slave sync service failed to run SQL.
- Diagnostic Bundle Contains: dmSync.log*, sync.properties
- Recommendations: Check slave node sync service log for detailed sql error messages. This error may cause master and slaves to be out of sync. Run backup and restore to sync them up.
- 4604005
- Synopsis: Data Mover master sync service is down.
- Meaning: The master sync service is not running.
- Probable Cause: The master sync service was stopped manually or due to error.
- Recommendations: Please see dmSync.log on both master and slave sync servers for details.
- 4604006
- Synopsis: Data Mover slave sync service is down.
- Meaning: The slave sync service is not running.
- Probable Cause: The slave sync service was stopped manually or due to error.
- Recommendations: Please see dmSync.log on both master and slave sync servers for details.
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.