Teradata SQL Error and Failure Codes from Error 10326to 10330

SQLServerF1

10326 The persistent segment list has been truncated to fit the buffer.
Explanation: The user’s buffer is too small to receive the entire list of segments. The list is truncated to the maximum
number of segments that will fit.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This message is informational only.
Remedy: This event should not appear in the log file. If it does, contact the Global Support Center.

10327 The segment cannot be discarded with the persistent flag set.
Explanation: A segment was flagged to persist across restarts and the application attempted to discard or drop it with
the normal API. Persistent segments can only be discarded using the persistent API.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This message indicates an application software bug.
Remedy: Contact the Global Support Center.

10328 Cannot allocate kernel memory for a buffer in SEG.
Explanation: An allocation failed to acquire the memory needed for a buffer in the SEG subsystem.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This message indicates a problem with memory resources. It might indicate a memory leak.
Remedy: Contact the Global Support Center.

10329 A bad handle was used for a persistent segment.
Explanation: The handle used to identify a persistent segment is bad.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This event indicates a PDE kernel problem. It is usually non-fatal but it might cause a resource leak.
Remedy: Contact the Global Support Center.

10330 The segment is not persistent as expected.
Explanation: The segment is expected to be persistent but it is not in the global persistent list.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This event usually means the application is trying to determine if a segment at a particular memory location is
persistent or not. It is only an error if the segment is expected to be persistent.
Remedy: Contact the Global Support Center.

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