Teradata SQL Error and Failure Codes from Error 3240 To 3257

3240 Invalid security Token is provided.
Explanation: The Security Token for the group doesn’t match.
Generated By: RCT modules.
For Whom: User.
Remedy: Re-submit the Connect request with a valid Security Token.

3243 Maximum number of Replication Groups allowed has been reached.
Explanation: The maximum number of Replication Groups allowed in the database at this moment has been reached.
Generated By: RCT modules.
For Whom: User.
Remedy: Drop unused group(s) before creating a new group.

3244 Maximum number of Replicated tables allowed for this replication group has been reached.
Explanation: The maximum number of replicated tables allowed for the group has been reached.
Generated By: RCT modules.
For Whom: User.
Remedy: Drop the unused replicated tables from the group before adding new tables.

3245 Maximum number of Replicated tables allowed for this system has been reached.
Explanation: Either the maximum number of replicated tables allowed for the system has been reached.
Generated By: RCT modules.
For Whom: User.
Remedy: Drop the unused replicated tables from the group or from the other groups before adding new tables.

3250 User does not have the necessary Access Right for this request.
Explanation: The user does not have the proper access rights to execute this request.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Obtain the necessary access right and resubmit the request.

3251 Required Input Data Parcel missing or wrong size for this request.
Explanation: An input Data Parcel is missing, or the size of the parcel is incorrect.
Generated By: PFMUsTsk.
For Whom: Application programmer.
Remedy: Correct the error and resubmit the request.

3252 Invalid Session Id/User Name pair. Name does not match SessionId.
Explanation: The user name specified in the request does not match that of the user logged on via the session id.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Correct the error and resubmit the request. The IDENTIFY SESSION request can be used to determine the correct
user name if the session id and host id are known.

3253 Monitor Access Denied: User has no Monitor Privileges.
Explanation: The user does not have the proper access rights to execute this Monitor request.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Obtain the proper access right and resubmit the request.

3254 The specified Version is not supported.
Explanation: The user-specified Monitor Version Id is not supported in the current version of Teradata software or the
new PMPC command is not supported in the specified Monitor Version.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3255 Invalid Rate: Must be from 0 to 3600, inclusive, or OFF.
Explanation: The Rate the user specified in a SET RESOURCE RATE request or SET SESSION RATE is not in the range 0
to 3600, inclusive.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3256 No such Session is currently logged on.
Explanation: The Session Id specified in the request is not logged on to the given PE.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3257 The specified Table Identifier does not exist.
Explanation: The Table Identifier specified in the request does not exist in the current Database.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Correct the error and resubmit the request

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