Teradata SQL Error and Failure Codes from Error 11026 to 11032

SQLServerF1

11026 Read error detected during read of segment.
Explanation: Read error detected during read of segment.
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.
Explanation: This is an informative code, not an error – the filesystem issued a fsginfoseg call, and there are no fsg segments
in memory.
Generated By: DBS file segment management.
For Whom: File System.
Remedy: nothing.

11028 Write error during synchronous write.
Explanation: Write error during synchronous write.
Generated By: DBS file segment management.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
Remedy: Contact the Global Support Center.

11029 Read error (invalid extent) detected during read of segment.
Explanation: Read error detected during read of segment.
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.

11030 Conditional write lock request did not result in a write lock.
Explanation: Conditional write lock request did not result in a write lock.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.

11032 This is not an AMP type vproc or it is not in the proper state.
Explanation: This is not an AMP type vproc or it is not in the proper state.
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 11026 to 11032 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 *