Teradata SQL Error and Failure Codes from Error 11086 to 11095

SQLServerF1

11086 The FSG subsystem can not be initialized for the program. %s failed with OS error %d.
Explanation: An error occurred attempting to set up the FSG segment mapping for the program.
Generated By: DBS file segment management.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11091 Cannot open pdisk: %s
Explanation: The pdisk node and major/minor device number have been verified but the device open failed.
Generated By: DBS file segment management.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11093 The FSG system can not be initialized for the vproc. %s failed with OS error %d.
Explanation: An error occurred attempting to set up the FSG segment mapping for the vproc. This probably indicates a
PDE configuration error.
Generated By: DBS file segment management.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11094 Received OS I/O error.
Explanation: An error has been reported to the PDE fsg subsystem by the I/O subsystem. The I/O operation has
already been retried 5 times by the Teradata Virtual Storage extent driver. Refer to the previous log entries for descriptions
of the I/O error(s) which caused this error.
If an I/O error occurs for a read operation, an error is returned to the caller, which may ultimately cause the DBS to also
report an error and issue a tpareset.
If an I/O error occurs for a write operation, a tpareset will occur, the vproc will be marked down.
Generated By: PDE fsg file segment management.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11095 Unrecoverable error in DBS file segment management.
Explanation: This event is logged for various conditions that should be logically impossible that are detected by the DBS
file segment management subsystem. This indicates a PDE kernel driver bug.
Generated By: DBS file segment management.
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: Contact the Global Support Center.

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