Teradata SQL Error and Failure Codes from Error 3258 To 3268

3258 The specified User/Database Identifier does not exist.
Explanation: The User/Database 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.

3259 The LIST SESSIONS option must have a value of Y,y,N,n,BLANK or NULL.
Explanation: The value given for the LIST SESSIONS option of an ABORT SESSION request is not one of the following
characters: “Y”, “y”,”N”,”n”, BLANK, or NULL.
The LIST SESSIONS option is used to specify whether the user wishes to be given the list of sessions identified as matching
the abort criteria.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3260 The LOGOFF SESSIONS option must have a value of Y,y,N,n,BLANK or NULL.
Explanation: The value given for the LOGOFF SESSIONS option of an ABORT SESSION request is not one of the following
characters: “Y”, “y”, “N”, “n”, BLANK, or NULL.
The LOGOFF SESSIONS option is used to specify whether the aborted sessions are to be logged off after the aborting is
complete.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3261 The OVERRIDE option must have a value of Y,y,N,n,BLANK or NULL.
Explanation: The value given for the OVERRIDE option of an ABORT SESSION request is not one of the following characters:
“Y”, “y”, “N”, “n”, BLANK, or NULL.
The OVERRIDE option is used to specify whether the ABORT SESSION request should skip sessions that have an In-Doubt
transaction, are being Switched to another PE, or are already executing their own ABORT SESSION requests.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3262 The LOCAL CHANGE option must have a value of Y,y,N,n,BLANK or NULL.
Explanation: The value given for the LOCAL CHANGE option of a SET SESSION RATE request is not one of the following
characters: “Y”, “y”, “N”, “n”, BLANK, or NULL.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3263 The LOGGING CHANGE option must have a value of Y,y,N,n,BLANK or NULL.
Explanation: The value given for the LOGGING CHANGE option of a SET RESOURCE RATE request is not one of the
following characters: “Y”, “y”, “N”, “n”, BLANK, or NULL.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3264 This error code is OBSOLETE.
Explanation: This error code, valid prior to V2R2, is now OBSOLETE.
Generated By: None.
For Whom: None.
Remedy: None.

3265 Transaction has been Aborted by Administrator or Operations Staff.
Explanation: Someone with the proper Access Right has completed executing an ABORT SESSION command from a
Host, OR, someone has completed executing an ABORT SESSION command from the DBC Console -DBW (which requires
no Access Right).
Generated By: PFMUsTsk or PFMCoTsk.
For Whom: Operations Staff.
Notes: This message is informational. The ABORT SESSION rolled back work in progress for the affected sessions and
may optionally have logged those sessions off the Teradata DBS.
Remedy: None.

3266 Transaction has been Aborted and Session Logged Off by Operations Staff.
Explanation: Someone with the proper Access Right has completed executing an ABORT SESSION command from a
Host, OR, someone has completed executing an ABORT SESSION command from the DBC Console – DBW (which requires
no Access Right), and the command was issued with the LOGOFF SESSIONS option, thus forcing one or more sessions off
the Teradata DBS.
Generated By: PFMUsTsk or PFMCoTsk.
For Whom: Operations Staff.
Notes: This message is informational.
Remedy: None.

3267 No sessions meet the Abort criteria.
Explanation: An attempt was made to execute an ABORT SESSION request, but the request failed because no session
met the specified selection criteria.
Generated By: PFMCoTsk.
For Whom: End User.
Remedy: Resubmit the request after modifying the criteria.

3268 Command Disallowed: An identified session is not currently Abortable.
Explanation: The ABORT SESSION request from the Teradata DBS Console could not be honored as specified. Additional
information is included in the error log.
Each ABORT SESSION request locks up some resources available to the PFMCoTsk and may lead to resource exhaustion
under the following conditions:
1. The system is under heavy load.
2. The user had issued a number of “abort session …” requests that are queued up and have not completed processing.
Under such a scenario, instead of restarting the DBS, this error is returned back to the user so that the request can be resubmitted
at a later time. Depending on the available resources for the PFMCoTsk, the “abort session…” request will be processed
to completion.
Generated By: PFMCoTsk.
For Whom: System Operator.
Remedy: Determine the cause for the failure, correct the problem, and resubmit the request.

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