Teradata SQL Error and Failure Codes from Error 3583 To 3596

SQLServerF1_Header_Small

3583 Too many HostIDs and UserIDs listed in GRANT/REVOKE LOGON.
Explanation: The GRANT/REVOKE LOGON statement creates or updates a dictionary table row, and generates other
steps, for each HostId-UserId combination. If the product of the number of HostIds and UserIds listed in a single
GRANT/REVOKE LOGON statement exceeds 25, the steps generated will require more memory space than is available to
parse and execute the statement.
Generated By: OPT modules.
For Whom: End User.
Remedy: Separate the statement into two or more statements each having a small enough number of HostIds and User-
Ids such that (HostID Count * UserId Count) <= 25.

3584 ’%VSTR’ is not a database.
Explanation: The MODIFY DATABASE expects a ’database’ but encounter a ’user’.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct statement and resubmit the request.

3585 USING modifier NOT allowed with DDL.
Explanation: Data definition statements must not have a USING modifier.
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Remove the USING modifier and resubmit request.

3586 Processor specification error(too many or invalid values).
Explanation: It is incorrect to specify more than five processor identifications in a host utility statement.
Generated By: GEN modules.
For Whom: End User.
Remedy: Use additional statements to specify additional processors and resubmit request.

3587 Host utilities cannot be processed in field mode.
Explanation: All host utility requests must be made in record mode.
Generated By: GEN modules.
For Whom: End User.
Remedy: Change the request from field mode to record mode and resubmit it.

3588 A User may not be assigned a NULL password.
Explanation: The password for a user cannot be set as NULL.
Generated By: OPT modules.
For Whom: The DBA.
Remedy: Give user a valid password.

3589 Statement must be inside a user-generated transaction.
Explanation: This host utility statement must be inside a transaction. That is, the user must have first sent a BEGIN
TRANSACTION statement.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3591 END TRANSACTION must be the last statement in a request.
Explanation: The END TRANSACTION statement must be the last statement when more than one statement is in the
request.
Generated By: OPT modules.
For Whom: End User.
Remedy: Reorder the statements in the request so that any BEGIN TRANSACTION statement occurs first and any END
TRANSACTION statement occurs last.

3592 BEGIN TRANSACTION must be the first statement in a request.
Explanation: The BEGIN TRANSACTION statement must be the first statement when more than one statement is in a
request.
Generated By: OPT modules.
For Whom: End User.
Remedy: Reorder the statements in the request so that any BEGIN TRANSACTION statement occurs first and any END
TRANSACTION statement occurs last.

3593 No DATA parcel sent and request uses a USING clause.
Explanation: The user request specified a USING clause, but a DATA parcel was not sent with the request.
A possible reason for this is the use of an EXECUTE statement for a MACRO which has a USING clause in its definition. A
processor such as BTEQ will send a DATA parcel only if it sees a USING clause in the source text. Some other processors
have interfaces that determine whether to send DATA parcels without requiring an explicit USING clause in the source
text.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the program to send the DATA parcel and resubmit the request.

3596 Invalid restore of database DBC.
Explanation: The user requested an invalid restore of database DBC. For instance, there are tables, views, macros, etc.
from some other database on the system, or the command specifies a single table from DBC, specifies an EXCLUDE list, or
specifies an AMP= clause. A restore of database DBC is permitted only on a new or empty system.
Generated By: OPT modules.
For Whom: End User.
Remedy: The user must delete any tables, views, or macros, etc. assigned to any database other than database DBC. The
user must change the command to remove any invalid options. Then re-submit the request.

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