Teradata SQL Error and Failure Codes from Error 3740 To 3751

SQLServerF1_Header_Small

3740 %$DBSHeader : The user issued a diagnostic statement.
Explanation: Diagnostic statements can be issued only by the user “DBC”.
Generated By: SYN modules.
For Whom: The DBA or the System Support Representative.
Notes: The first 72 characters of the request are in the error log. Many diagnostic statements are restricted to the user.
Remedy: This information is for the Teradata operator.

3743 DUMP/RESTORE DATABASE statements cannot appear in macros.
Explanation: DUMP or RESTORE statements are not valid in macros.
Generated By: SYN modules.
For Whom: The DBA and the End User.
Remedy: Do not put a DUMP or RESTORE statement in a macro.

3744 Database already contains a permanent journal table.
Explanation: A MODIFY DATABASE statement has specified a new permanent journal table and one currently exists. A
database can contain only one permanent journal table.
Generated By: OPT modules.
For Whom: End User.
Remedy: Change statement and resubmit.

3745 Invalid message category for a Teradata SQL start request.
Explanation: Invalid category for the message.
Generated By: SQL modules.
For Whom: System Support Representative.
Notes: The error parcel INFO field contains the category in which the message was sent.
Remedy: If this error persists, contact your support representative.

3746 Invalid class or kind for a Teradata SQL start request.
Explanation: Message header has an invalid class or kind.
Generated By: SQL modules.
For Whom: System Support Representative.
Notes: The error parcel INFO field contains an invalid class or invalid kind.
Remedy: If this error persists, contact your support representative.

3747 No startup string defined for this user.
Explanation: The user sent a RUNSTARTUP or FMRUNSTARTUP and no startup string was defined.
Generated By: ITB and SQL modules.
For Whom: End User.
Remedy: Ignore the error or define a startup string by using the MODIFY USER statement.

3748 Parcel kind or ordering is invalid.
Explanation: The sequence of parcels received by the Teradata SQL Parser was invalid.
Possible causes are:
(a) the request did not begin with either an OPTIONS parcel followed by either REQ, FMREQ, INDICREQ, RUNSTARTUP,
FMRUNSTARTUP, or IVRUNSTARTUP parcel, or
(b) the request did not begin with either a REQ, FMREQ, INDICREQ, RUNSTARTUP, FMRUNSTARTUP or
IVRUNSTARTUP parcel, or
(c) the request did not end with a RESP or KEEPRESP parcel, or
(d) a continuation or ABORT request was sent to the Teradata SQL Parser instead of to the dispatcher.
Generated By: SQL modules.
For Whom: System Support Representative.
Remedy: Correct the program and resubmit the request.

3749 Options Parcel information is invalid.
Explanation: RequestMode field was not an ’F’, ’R’, ’I’ or binary zero. DBCFunction field was not ’P’, ’E’, or binary zero.
The flags RFU_1 – RFU_8 were not binary zero.
Generated By: SQL modules.
For Whom: System Support Representative.
Remedy: Correct the program and resubmit the request.

3750 Illegal Kanji object name %VSTR.
Explanation: Kanji Object names in Teradata SQL must obey the following rules. 1) SBC Katakana characters are those
defined in JIS- x0201. 2) The MBC Kanji characters are those defined in JIS- x0208, and 3) The object name can be converted
to any other supported Kanji character, and will not exceed 30 bytes in this set. The given name abused one of those rules.
Those rules are verified only when an object is created. They are not verified when an object is referenced.
Generated By: Resolver modules.
For Whom: End User.
Remedy: Correct the object name to apply to the above rules and resubmit the request.

3751 Expected a digit for the exponent.
Explanation: An exponent is missing in a floating constant.
Generated By: LEX modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request

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