Teradata SQL Error and Failure Codes from Error 3716 To 3726

3716 Column name list and Select list mismatched.
Explanation: Column name list and Select list must have the same number of expanded object.
Generated By: Resolver.
For Whom: End User.
Remedy: Correct and resubmit the request.

3717 Too many users or databases listed in GRANT/REVOKE statement.
Explanation: The maximum number of users and/or databases that access rights can be granted to or revoked from in
one statement is 25.
Generated By: RES modules.
For Whom: End User.
Remedy: Separate the statement into two or more statements each granting to or revoking from no more than 25 users or
databases.

3718 Conversion from FLOAT type to CHARACTER type is illegal for column %VSTR.
Explanation: The user tried to insert FLOAT data into a CHARACTER column during FASTLOAD. This conversion is
not supported.
Generated By: OPT modules.
For Whom: End User.
Remedy: None, change type of data and resubmit request.

3719 Join update of non-hashed table ’%VSTR’ is not allowed.
Explanation: The submitted request requires a complex update (for example, a join update) of a non-hashed table. Such
updates are not allowed.
Generated By: OPT modules.
For Whom: End User.
Notes: This event code applies to some non-hashed system tables that are owned by user DBC. It does not apply to user
tables or any other hashed tables.
To determine whether your Teradata SQL request involves a complex update, use the EXPLAIN modifier.
Remedy: Change the request to use a simpler operation such as a single-table update, or submit the request for user
tables only. If this event code occurs after the above actions are taken, contact your support representative.

3720 This view does not contain any complete index columns of the underlying table.
Explanation: This error message is issued when HELP INDEX is attempted on a view which does not contain any complete
index of the underlying table. (i.e., either contains no indexes at all or contains SOME columns of a multi-column
index.)
Generated By: OPT modules.
For Whom: End User
Remedy: Do a HELP INDEX on a view with at least one complete index.

3721 The cursor parcel sent by the host was missing or invalid.
Explanation: Either the cursor parcel was not sent for an updatable cursor update or updatable cursor delete, or the
information in the cursor parcel was invalid.
Generated By: GNC and PAR modules.
For Whom: End User.
Remedy: Correct the cursor parcel and resubmit request.

3722 Only a COMMIT WORK or null statement is legal after a DDL Statement.
Explanation: A DDL statement was issued previously. By our current rules, the only time that a DDL statement can be
issued inside is when it is the last statement in that transaction. The only statements allowed after a DDL statement are a COMMIT WORK, an unconditional ROLLBACK WORK, or a NULL statement.
Generated By: RES modules.
For Whom: End User.
Remedy: Commit the transaction immediately after the DDL statement.

3723 The cursor UPDATE or DELETE statement references an invalid table.
Explanation: A cursor UPDATE or DELETE statement must reference the same table as the one from which the rows
were retrieved in SELECT statement that opened the cursor.
Generated By: OPT and GNC modules.
For Whom: End User.
Remedy: Change table reference and resubmit the request.

3724 No more memory in cursor segment for cursor SELECT request.
Explanation: Each cursor SELECT request requires some memory from the cursor segment to store some information
about the cursor but there is no memory left in the cursor segment to do this.
Generated By: GNC modules.
For Whom: End User.
Remedy: Close some open cursor transactions then resubmit request.

3725 Statement not allowed for an ANSI session.
Explanation: The statement you entered cannot be executed when the transaction semantics are set to ANSI.
Generated By: PAR modules.
For Whom: End User.
Remedy: Logon with the transaction semantics set to BTET to execute the statement.

3726 Invalid FORMAT string.
Explanation: The FORMAT string is invalid.
Generated By: synddesc module.
For Whom: End User.
Remedy: Correct the format.

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