Teradata SQL Error and Failure Codes from Error 11079 to 11084

SQLServerF1

11079 Received Teradata Vitual Storage error.
Explanation: An error has been reported to the PDE fsg subsystem by the TVSA extent driver. Refer to the previous log
entries for any possible additional information about this error.
If an 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 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.

11080 A read to disk was returned to Teradata with good status, but the read actually did not occur.
Explanation: The storage subsystem has returned a read with good status to Teradata, but the read actually did not
occur. This means there is a bug in the underlying storage subsystem. In order to prevent data corruption, the read will be
retried one more time. If the read is still unsuccessful after the retry due to a false read, the node is crashed on purpose for
further analysis by the storage subsystem support team.
Generated By: DBS file segment management.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11081 No room for segment to grow inside the allocated space.
Explanation: The length argument passed to a file segment service is out of range.
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.

11082 Cannot clear IO errors for this vproc.
Explanation: This could happen when trying to clear IO errors on a ’FATAL**’ AMP. To recover from this problem, fix
the hardware errors on the associated pdisks and restart the DBS. The PDE startup when it opens the associated pdisks
clears the IO errors automatically.
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.

11084 Not enough physical memory for FSG subsystem.
Explanation: There is not enough physical memory available on the node for the FSG subsystem, given the number of
AMPs and total vprocs to be started on the node in a minimum clique configuration. This message is always preceded by a
11085 event which gives the details on the calculations that determined the amount of physical memory available to FSG on
this node, given the current minimum clique size.
Generated By: TPA Initialization.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart. After three failures, PDE stops retrying and remains down.
Remedy: If PDE is attempting to reserve more physical memory for FSG than is actually needed to run the database,
reduce the amount of physical memory is tries to use by adjusting the value of one or more of the variables used to calculate
this value, as described under the 11085 event.

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