Teradata SQL Error and Failure Codes from Error 11982 to 11991

SQLServerF1

11992 A client slot is vacated slot = %d old process id = %d old task id = %d new process id = %d new task id = %d
Explanation: The client slot assigned to a client has been re-assigned to another client from a different process.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The vacated client should close the RSS handle and either exit or re-acquire a new RSS handle thru the rssuseropen()
call.
Remedy: Contact the Global Support Center.

11993 RSS Client Service is disabled
Explanation: RSS Client Service is disabled by a flag in control GDO.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: To enable RSS Client Service, reset the RSS Disable Client flag in control GDO.
Remedy: Contact the Global Support Center.

11994 No vdisk found for VprocId %d
Explanation: RSS API rssgetsvdskidx did not find vdisk matching requested vproc id. Verify the AMP vdisk configuration
and status.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS messages are normally warnings only, but the calling routine may be coded to terminate after the error message
is displayed.
Remedy: Contact the Global Support Center.

11995 Two devices have the same device information.
Explanation: A new device being registered with RSS has the same identifying information as an existing device. May
be a system configuration issue.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only, but the calling routine may be coded to terminate after the error
message is displayed.
Remedy: Contact the Global Support Center.

11998 %$HeaderRSS debug event; %s.
Explanation: This event is used for RSS debugging.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The event is used in debugging environment only.
Remedy: Contact the Global Support Center.

11999 %$HeaderAn RSS internal software error occurred; %s.
Explanation: This event is used to report a variety of low-probability errors in RSS service calls.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only, but the calling routine may be coded to terminate after the error
message is displayed.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

12000 %s
Explanation: This event code is used to log text messages received or generated by the PDE console subsystem.
Generated By: PDE console subsystem.
For Whom: System Support Representative.
Remedy: In some cases, this is simply an informational message and no action is needed. If the message text indicates
that an error occurred, or if the message is repeated frequently or appears to be associated with other abnormal console
behavior, save the portion of the log for the period in question and report the problem to the Global Support Center. Otherwise,
no response is needed.

12001 %s
Explanation: An unexpected message was received by the console interface module. The message text is a variable
string giving the reason for the error. This typically indicates a protocol violation of some kind in the dialog between the
PDE console control programs and the DBW database window. It has no impact on the actual operation of the DBS.
Generated By: PDE console subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

12010 The system debugger is not active.
Explanation: A start command was issued in the database console supervisor window with the debug option, requesting
that the task to be started run under the control of the system debugger, but the system debugger is not currently active.
The task has been started, but will not run until the debugger is attached and system execution continued.
Generated By: PDE console subsystem.
For Whom: Systems Engineer, Operator.
Remedy: Start the system debugger, attach to the system, set any breakpoints needed, and continue execution. Or stop
the task and restart it without specifying debug.

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