Teradata SQL Error and Failure Codes from Error 11006 to 11010

SQLServerF1

11006 Lock request would block.
Explanation: The requested try lock leads to wait, so fsg returns.
Generated By: DBS file segment management.
For Whom: System Support Representative.
Notes: This event does not cause an error.
Remedy: Contact the Global Support Center.

11007 Attempt to upgrade lock as a result of special action.
Explanation: The requested read lock leads to deadlock. Upgrade lock not allowed at end action.
Generated By: DBS file segment services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
Remedy: Contact the Global Support Center.

11008 Deadlock detected with some other process.
Explanation: Deadlock detected.
Generated By: DBS file segment management.
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.

11009 Deadlock detected with self.
Explanation: Self deadlock detected.
Generated By: DBS file segment management.
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.

11010 Attempt to change ident of segment to one already found in memory.
Explanation: Attemp to change a segment identifier to an already existant one.
Generated By: DBS file segment services.
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.

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