Teradata SQL Error and Failure Codes from Error 12196 to 12303

SQLServerF1

12196 ERRLOGTEST4: 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: 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.

12198 A test event was signaled.
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.

12199 Kernel event number %d is invalid.
Explanation: A PDE kernel driver attempted to log an undefined event code. This indicates a PDE kernel driver bug.
Generated By: PDE logging subsystem.
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: Contact the Global Support Center.

12300 Unable to collect trace due to lack of memory %s
Explanation: The thread responsible for merging trace data from the per-cpu buffer files is unable to allocate memory
requred for the attempt. Trace collection may be re-tried at a later time.
Generated By: PDE tracing subsystem, tra_kollect thread..
For Whom: Field Engineer.
Remedy: This message indicates that PDEMAIN is running out of memory. The trace daemon thread or trace collection
thread has failed. PDE must be stopped and re-started to clear up the out-of-memory condition

12301 Trace collection prematurely terminated due to %s PDE error event code: %d OS event code: %d
Explanation: A thread responsible for merging trace entries from the per-cpu buffer files has detected an error that prevents
successful completion of this operation. The attempt has been terminated.
Generated By: PDE tracing subsystem, tra_kollect thread.
For Whom: Field Engineer.
Remedy: This message indicates that the collect daemon thread has encountered a condition that has caused it to abandon
its attempt to merge the trace buffers. Collection may be retried later, after the condition has been cleared up.

12302 Trace collection disabled due to %s PDE error event code: %d OS event code: %d
Explanation: One of the threads responsible for collection of trace data has encountered an error condition that requires
the thread to be terminated. No further trace collection is possible, but the system is functional otherwise.
Generated By: PDE tracing subsystem, tra_kollect or tradaemon thread.
For Whom: Field Engineer.
Remedy: This message indicates that the collect daemon or the trace daemon thread has encountered an unrecoverable
error condition and terminated. No trace collection is possible until PDE is stopped and restarted.

12303 Trace subsystem internal error.
Explanation: A PDE kernel service has attempted to add a trace entry from an elevated system protection level (IRQL >
DISPATCH_LEVEL on Windows), or before the trace subsytem has been fully initialized. The trace is not collected.
Generated By: PDE tracing subsystem.
For Whom: Field Engineer.
Remedy: This message indicates that a minor PDE program logic error. It has no effect on normal system operation,
except that an expected internal trace has not been collected.

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