Teradata SQL Error and Failure Codes from Error 12123 to 12195

SQLServerF1

12123 A task snapshot dump has been taken for event number %d.
Explanation: This event is logged when a program requests a snapshot dump of itself. It is for informational purposes
only.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Remedy:

12124 A vproc snapshot dump has been taken for event number %d.
Explanation: This event is logged when a program requests a snapshot dump of its virtual processor. It is for informational
purposes only.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Remedy: If this is reported for an unknown reason, contact the Global Support Center. Otherwise, no response is
needed.

12126 The system is stopped for event number %d because the BreakStop flag is set in the Control GDO.
Attach the system debugger to continue.
Explanation: This message is issued when an unexpected fatal event is reported and the BreakStop flag is set in the Control
GDO and the system debugger is not attached to the system.
The purpose of the BreakStop flag is to stop the system when it is about to do an unplanned reset so that the problem can
be debugged. If the debugger is already attached, it will catch the event automatically; the BreakStop flag is irrelevant in
that case. But if the debugger is not attached, the system is stopped and this message is issued to inform the operator that
the debugger must be attached.
Generated By: PDE logging subsystem.
For Whom: Operator.
Remedy: Attach the system debugger and examine the reason for the failure. If on-line debugging is not desired, attach
the system debugger and continue the system to allow it to reset as if it had not been stopped. If the BreakStop flag had not
been intentionally set, turn it off with ctl.

12127 This Node is about to panic.
Explanation: This event is used to collect the DBS crash dump and the NT crash dump. The box will crash after the DBS
dump is taken.
This event might not be logged because NT did not flush the cache to the disk before it panic’ed.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Remedy: Contact the global support centre.

12128 The DBS is not responding.
Explanation: This event signifies that the DBS has exceeded the wait time of a sample job querying on DBS. This
logevent is not meant the system is going down or panic. It’s simply a notice.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Remedy: Contact the global support centre.

12192 ERRLOGTESTFSYS logged
Explanation: This event is reserved for use in PDE internal tests.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Remedy: This event should never occur at a customer site. If it does, contact the Global Support Center.

12193 ERRLOGTEST1: Logevent occurred in %s, line %d.
Explanation: This event is reserved for use in logging subsystem tests.
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. The associated
stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: This event should never occur at a customer site. If it does, contact the Global Support Center.

12194 ERRLOGTEST2: Logevent occurred in %s, line %d.
Explanation: TBD
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Notes: The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: This event should never occur at a customer site. If it does, contact the Global Support Center.

12195 ERRLOGTEST3: Logevent occurred in %s, line %d.
Explanation: This event is reserved for use in logging subsystem tests.
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. The associated
stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: This event should never occur at a customer site. If it does, contact the Global Support Center.

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