Teradata SQL Error and Failure Codes from Error 3277 To 3287

SQLServerF1_Header_Small

3277 An informative event was logged.
Explanation: This is a general error code used as a wrapper for informational messages. The specific information is
encoded within the event message.
Generated By: PFMCoTsk.
For Whom: System Operator
Remedy: None. The messages generated under this code are informational.

3278 Monitor Access Denied: No Monitor Session available
Explanation: The user is denied the logon because all Monitor sessions are currently in use on the given PE. Each online PE can support up to four Monitor sessions.
Open API: There are no more monitor partition session contexts available on the given PE to process Open API request.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Attempt to logon on through a different PE that does has not reached it Monitor session limit or logon later
when there is a Monitor session available.
Open API: Resubmit the request through a different BTEQ session on a different PE or close a PM API application on the PE and resubmit the Open API request.

3279 There are no more Monitor Sessions available.
Explanation: The Teradata system has reached the maximum number of Monitor sessions that are allowed to be logged
on at one time. The Teradata system has a system-wide limit of 128 concurrent Monitor sessions.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Wait for a logged-on Monitor user to log off and resubmit the logon request.

3280 Request not allowed now. System is not online.
Explanation: An attempt was made to execute a Monitor request from the Teradata Console before the system was fully online.
Generated By: PFMCoTsk.
For Whom: System Operator.
Remedy: Resubmit the request after the Teradata system has come fully online.

3281 Internal Error: Inconsistent Monitor software condition detected.
Explanation: An unexpected internal error occurred and the Monitor software forced a Teradata restart.
Generated By: PFMUsTsk or PFMCoTsk.
For Whom: Support Representative.
Remedy: Save all relevant information and the crash dump and notify your Support Representative.

3282 Internal Error: Unexpected thread event detected.
Explanation: Monitor software detected an unexpected thread event and forced a Teradata restart.
Generated By: PFMUsTsk or PFMCoTsk.
For Whom: Support Representative.
Remedy: Save all relevant information and the crash dump and notify your Support Representative.

3283 Internal Error: No free context blocks are available.
Explanation: Monitor software detected that the running task had run out of one of the various types of context blocks,
and so it forced a Teradata restart.
Generated By: PFMCoTsk or PFMUsTsk.
For Whom: Support Representative.
Remedy: Save all relevant information and the crash dump and notify your Support Representative.

3284 Internal Error: Error message not found in table.
Explanation: A PFMUsTsk software module attempted to get the text of an error message that was not in its cache. This
is an internal-only informational code and should have no user visibility.
Generated By: PFMUsTsk.
For Whom: PFMUsTsk.
Remedy: None. This is an internal-only code.

3285 Internal Error: The Monitor session entry does not exists.
Explanation: A session that exists in the Monitor User Task (PFMUsTsk) is unknown to the Monitor Coordinator Task
(PFMCoTsk). PFMCoTsk forces a Teradata restart when it detects this inconsistent condition.
Generated By: PFMCoTsk.
For Whom: Support Representative.
Remedy: Save all relevant information and the crash dump and notify your Support Representative.

3286 Internal Error: No free segment pages are available.
Explanation: PFMCoTsk detected that the it had attempted to use too many predefined segment pages, and so it forced
a Teradata restart.
Generated By: PFMCoTsk.
For Whom: Support Representative.
Remedy: Save all relevant information and the crash dump and notify your Support Representative.

3287 Internal Error: The Monitor session already exists.
Explanation: The Monitor session to be logged onto the system already exists in either PFMUsTsk or PFMCoTsk. Whichever
of the two detects the error forces a Teradata restart.
Generated By: PFMCoTsk or PFMUsTsk.
For Whom: Support Representative.
Remedy: Save all relevant information and the crash dump and notify your Support Representative.

Above are list of Teradata Errors or Failure Codes from Error 3277 To 3287 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 *