Teradata SQL Error and Failure Codes from Error 11035 to 11039

SQLServerF1

11035 Flavor FSGACQDUALBOTH and at least one copy in memory
Explanation: Can not do an ACQBOTH
Generated By: DBS file segment services.
For Whom: System Support Representative.

11036 A requested I/O operation failed to complete successfully.
Explanation: An error has been reported to the PDE FSG subsystem by the I/O subsystem. The I/O operation could not
complete, even after Teradata Virtual Storage retried the I/O five times. This causes the DBS to restart.
Generated By: PDE restart.
For Whom: PDE fsg file segment management.
Remedy: Contact the Global Support Center

11037 Bad wlsn passed to fsg.
Explanation: The wlsn passed to fsg conflicts with wlsn in memory Either a smaller modwlsn was passed on a release,
or a write was issued on a segment with wlsn bigger than lastwrittenlog.
Generated By: DBS file segment management.
For Whom: System Support Representative.
Notes: The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11038 I/O data corruption during asynchronous write.
Explanation: I/O data corruption during asynchronous write. It is to report the mismatch between the 8th and 9th bytes
of the datablock and the last two bytes of the datablock which contains version number. It is also used to report the mismatch
between the block length in the datablock and the length in sdb.
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.

11039 A task exited with a write access to a non-ageless segment
Explanation: A task exited and it owned a write access to a non-ageless filesys segment. This causes the DBS to restart.
Generated By: PDE restart.
For Whom: PDE fsg file segment management.
Remedy: Contact the Global Support Center

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