Teradata SQL Error and Failure Codes from Error 12100 to 12109

SQLServerF1

12100 There is no current logmark.
Explanation: A logcont(), logcall() or logclear() service call was issued when there was no logmark region in effect. This
indicates an error in the program that issued the call.
Generated By: PDE logging subsystem.
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.

12101 Log message category is undefined.
Explanation: A logsetcat() service call was passes an undefined category code. This indicates an error in the program
that issued the call.
Generated By: PDE logging subsystem.
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.

12102 One or more CPU hardware category events have been discarded.
Explanation: This event code is reserved for future use.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Remedy: None. This event is never logged in this release.

12103 One or more memory hardware category events have been discarded.
Explanation: This event code is reserved for future use.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Remedy: None. This event is never logged in this release.

12104 One or more Bynet hardware category events have been discarded.
Explanation: Too many Bynet hardware category events were being received, so some of them have been discarded.
Preceding log messages for host events should give a fair sample of the kind of events that were occurring.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Notes: This message is only written to the log file and DBS event log. It does not appear on the console.
Remedy: If the events that were logged before they started being discarded indicate a real problem, contact the Global
Support Center. Otherwise, no action is needed.

12105 One or more disk hardware category events have been discarded.
Explanation: This event code is reserved for future use.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Remedy: None. This event is never logged in this release.

12106 One or more channel hardware category events have been discarded.
Explanation: This event code is reserved for future use.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Remedy: None. This event is never logged in this release.

12107 One or more host category events have been discarded.
Explanation: Too many host category events were being received, so some of them have been discarded. Preceding log
messages for host events should give a fair sample of the kind of events that were occurring.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Notes: This message is only written to the log file and DBS event log. It does not appear on the console.
Remedy: If the events that were logged before they started being discarded indicate a real problem, contact the Global
Support Center. Otherwise, no action is needed.

12108 One or more driver category events have been discarded.
Explanation: Too many driver category events were being received, so some of them have been discarded. Preceding log
messages for driver events should give a fair sample of the kind of events that were occurring.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Notes: This message is only written to the log file and DBS event log. It does not appear on the console.
Remedy: If the events that were logged before they started being discarded indicate a real problem, contact the Global
Support Center. Otherwise, no response is needed.

12109 One or more resource category events have been discarded.
Explanation: Too many resource category events were being received, so some of them have been discarded. Preceding
log messages for resource category events should give a fair sample of the kind of events that were occurring.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Notes: This message is only written to the log file and DBS event log. It does not appear on the console.
Remedy: If the events that were logged before they started being discarded indicate a real problem, contact the Global
Support Center. Otherwise, no response is needed.

Above are list of Teradata Errors or Failure Codes from Error 12100 to 12109 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 *