Teradata SQL Error and Failure Codes from Error 3269 To 3276

3269 Warning: An identified session is not currently Abortable.
Explanation: A session selected to be aborted by an ABORT SESSION request is in a state that precludes its being
aborted. Any (other) abortable sessions selected by the same request will be aborted.
A session is in such a state under the following conditions:
1. The session is doing a transaction commit or rollback and the LOGOFF SESSIONS option was not specified for this
ABORT SESSION request.
2. The session is in-doubt (using the Two Phase Commit protocol) or executing an ABORT SESSION request, itself, and the
OVERRIDE option was specified for this ABORT SESSION request.
3. The session is being switched to another PE and the LOGOFF SESSIONS and OVERRIDE options were specified for this
ABORT SESSION request.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: This is a warning; no remedy is necessary.

3270 Warning: DBC Recovery has occurred.
Explanation: The returned Resource/Session Usage values may have been affected by a System Restart or Single Processor
Recovery.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: This message is informational. Its purpose is to warn the user that the usage values may not reach a steady
state until the requests on the Teradata system attain their normal level of activity.

3271 Data Unavailable: Resource Usage Sampling is not currently enabled.
Explanation: The user requested Resource monitoring, but the ResMonitor Rate is zero.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Set the ResMonitor Rate to a valid non-zero value, wait for at least one collection period to expire, and resubmit
this request.

3272 Warning: Resource Data is incomplete because %VSTR.
Explanation: Resource Usage data is incomplete for one of the following reasons:
1. The Teradata system has gone through recovery and a full collection period has not expired since.
2. The Resource Monitor Rate has been changed and a full collection period has not expired since.
3. For the MONITOR SUMMARY request only, Resource Monitoring is not enabled.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Wait for a full collection period to expire and resubmit the request, or in the case of a MONITOR SUMMARY
request when the Resource Monitoring is not enabled, set the Resource Monitor Rate to a valid non-zero value, wait for a full collection period to expire, and resubmit the request.

3273 Warning: Resource Monitoring rate has been altered.
Explanation: The returned Resource Usage data supplied by this request may be of greater or lesser accuracy than previous executions of this command due to the change in the Resource Monitoring Rate.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: This warning is informational.

3274 Data Unavailable: Session Usage sampling is not currently enabled.
Explanation: The MONITOR SESSION request failed becauase both the Local and the System-wide Session Monitoring
Rates are zero.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Set the Session Monitoring Rate to a valid non-zero value, wait for a full collection period to expire, and resubmit this request.

3275 Warning: Session Data is incomplete because %VSTR.
Explanation: Session Usage data is incomplete for one of the following reasons:
1. The Teradata system has gone through recovery and a full collection period has not expired since.
2. The Resource Monitor Rate has been changed and a full collection period has not expired since.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: Wait for a full collection period to expire and resubmit the request.

3276 Warning: Session Monitoring Rate has been altered.
Explanation: The Session Usage data returned by this request may be of greater or lesser accuracy than previous executions of this command due to the change in the Session Monitoring Rate.
Generated By: PFMUsTsk.
For Whom: End User.
Remedy: This warning is informational.

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