Teradata SQL Error and Failure Codes from Error 12110 to 12122

SQLServerF1

12110 One or more system category events have been discarded.
Explanation: Too many system category events were being received, so some of them have been discarded. Preceding
log messages for system 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.

12111 One or more user category events have been discarded.
Explanation: Too many user category events were being received, so some of them have been discarded. Preceding log
messages for user 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.

12112 One or more occurrence category events have been discarded.
Explanation: Too many occurrence category events were being received, so some of them have been discarded. Preceding
log messages for occurrence 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.

12113 One or more abnormality category events have been discarded.
Explanation: Too many abnormality category events were being received, so some of them have been discarded. Preceding
log messages for abnormality 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.

12114 User event number %d is invalid.
Explanation: A user task (as opposed to a kernel driver) attempted to log an unknown event code, or an event that can
only be logged by the kernel.
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.

12116 %s
Explanation: This message is only logged to the DBS event table. It is used to capture the operating system console messages
written through /dev/osm and put them in the DBS log table.
Generated By: PDE logging subsystem.
For Whom: Operator, System Administrator, or System Support Representative.
Remedy: If the text of the message indicates a serious problem, or if it appears to be associated with other abnormal system
behavior, contact the Global Support Center. Otherwise, no response is needed.

12122 %s
Explanation: This event code is used by various programs to insert an arbitrary line of text into the log. These messages
are typically simple informational text.
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: In most cases, no response is needed. If the message appears to be associated with some sort of abnormal
behavior, report the problem to the Global Support Center.

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