Teradata SQL Error and Failure Codes from Error 3835 To 3847

3835 A 2PC abort has occurred.
Explanation: A 2PC Abort was received from the host or the Resolver Base Module. The 2PC transaction is aborted or
rolled back.
Generated By: ParDrivr.
For Whom: End User.
Remedy: None – status notification.

3836 A 2PC parcel must be the last parcel in a request.
Explanation: No parcels can follow a 2PC parcel, but the Parser detected another parcel. The transaction is rolled back.
Generated By: ParDrivr.
For Whom: End User.
Remedy: Resubmit all requests; reissue the 2PC parcel with no trailing parcels.

3837 A 2PC Abort or Commit cannot be combined with other requests.
Explanation: Abort or Commit parcels must be solo – they cannot follow SQL requests. The transaction is rolled back.
Generated By: ParDrivr.
For Whom: End User.
Remedy: Resubmit the request without the 2PC parcel. Submit the Abort or Commit as a solitary request.

3839 A command intended only for Teradata internal testing was incorrect.
Explanation: Several statements intended for use only by TERADATA personnel require confirmation. The confirmation
was not given correctly.
Generated By: SynDiag module.
For Whom: TERADATA personnel.
Remedy: Resubmit the statement and confirm it correctly.

3840 Teradata has been restarted as requested by the user.
Explanation: This message is displayed to tell the user that the DBC has been restarted as a result of submitting the command:
DIAGNOSTIC DBCRESTART
Generated By: SynDiag module.
For Whom: The end user.
Remedy: None.

3841 Diagnostic CONVERT not allowed if logons are enabled.
Explanation: DIAGNOSTIC CONVERT is used during the dictionary table conversion. It expects logons to have been
disabled.
Generated By: SYN modules.
For Whom: The DBA.
Remedy: Make sure that logons are disabled.

3842 Diagnostic CONVERT not allowed if multiple users logged on.
Explanation: DIAGNOSTIC CONVERT is used during the dictionary table conversion. It expects the current user to be
DBC and the only user.
Generated By: SYN modules.
For Whom: The DBA.
Remedy: Make sure there are no other users logged on.

3843 Table/View/Macro type specification does not match ’%VSTR’.
Explanation: The object type specified in BEGIN/END LOGGING statement does not match the actual type of the
object.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

3844 Reference to AccLogTbl not valid unless solitary.
Explanation: Any DML statement that references AccLogTbl is treated as a DDL statement. It must follow the rule that
DDL statements are not allowed in a multi-statement request. A DDL may be used in a macro, but only when the only
statement in the macro is the DDL.
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Submit each statement as a separate transaction.

3846 The Access Logging feature has not been installed.
Explanation: The applicable macro (AccLogRule) has not been created for access logging control or a RESTART has not
been performed since it was created.
Generated By: RES modules.
For Whom: End User.
Remedy: User should check with the system administrator regarding the availability of this feature.

3847 Illegal use of a WITH clause.
Explanation: If a query contains a UNION, MINUS, or INTERSECT operator, then a WITH clause cannot be used with
the query.
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

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