Teradata SQL Error and Failure Codes from Error 11207 to 11211

SQLServerF1

11207 Teradata I/O Scheduler (tdsched) is not installed or the correct version is not running.
Explanation: Priority Scheduler requires a specific version of tdsched for optimum I/O scheduling. If tdsched is not
installed or the correct version is not running, then the I/O scheduling functionality will be either degraded and/or be limited.
Generated By: PDE system services.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11208 WD id is not valid.
Explanation: A PDE sch priority service has been given an invalid Workload Definition Identifier value.
Generated By: PDE scheduler services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11209 Session info is not valid.
Explanation: A PDE sch priority service has been given session info with an invalid host or session number.
Generated By: PDE scheduler services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11210 Request already in WD move operation.
Explanation: A PDE sch priority service is unable to move a request to a different WD because a move request is already
being processed.
Generated By: PDE scheduler services.
For Whom: PDE and DBS developers.
Notes: This event may be reported under routine circumstances when a request is the target of multiple move orders.
These orders may originate from the user, msg subsystem, or sch tactical exception handling.
Remedy: Resubmit move request.

11211 Submit event failed.
Explanation: A PDE sch priority service is unable to submit an event for a request.
Generated By: PDE scheduler services.
For Whom: PDE and DBS developers.
Notes: This is likely due to a lack of available memory at the time of the event submission. The event could be related to
a request move, share modification, VP or WD settings modification, or other reason.
Remedy: Resubmit move request.

Above are list of Teradata Errors or Failure Codes from Error 11207 to 11211 received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *