Teradata SQL Error and Failure Codes from Error 5932 To 5942

SQLServerF1_Header_Small

5932 EXTUSER logon may only be directory-based.
Explanation: Logon name of EXTUSER may only be used for directory-based logon.
Generated By: SES module.
For Whom: End User.
Remedy: Change to a valid logon name.

5933 Role being dropped is not an external role.
Explanation: An external role may be dropped by a DROP EXTERNAL ROLE statement, but not a DROP ROLE statement.
Generated By: OPD module.
For Whom: End User.
Remedy: Add EXTERNAL keyword and re-submit request.

5934 Role being dropped is an external role.
Explanation: DROP EXTERNAL ROLE may not be used to drop a database role. Use DROP ROLE statement instead.
Generated By: OPD module.
For Whom: End User.
Remedy: Remove the EXTERNAL keyword and re-submit request.

5935 External user has not been assigned a default database.
Explanation: An external user’s default database is taken from the profile assigned to him/her. If one is not specified in the profile, or no profile is assigned in the directory to the user, then this error message is returned.
Generated By: RES module.
For Whom: End User.
Remedy: Specify a default database in the external user’s profile, or use the DATABASE statement to specify a default
database.

5936 External role ’%VSTR’ was not assigned to user.
Explanation: The specified external role was not assigned to the user in the Directory.
Generated By: OPD module.
For Whom: End User.
Remedy: Specify a role that was either assigned to the user in the Directory, or granted to the user in the Database.

5937 An OUT parameter can not be used as source of data.
Explanation: An OUT parameter cannot be used as a source of data. Data can only be assigned to it.
Generated By: Resolver.
For Whom: End User.
Remedy: Change the paramter type or use a variable/input parameter in the statement and recreate the stored procedure.

5938 .ALL keyword in SELECT is not ANSI.
Explanation: ANSI does not allow the .ALL keyword in SELECT
Generated By: SYN modules.
For Whom: User.
Remedy: If script is to be full ANSI compliant, change the indicated statement.

5939 Invalid usage of SELECT INTO in a subquery.
Explanation: A Select-Into statement cannot be specified in a subquery.
Generated By: Resolver.
For Whom: End User.
Remedy: Change the query and recreate the stored procedure.

5940 Excessively complex expression.
Explanation: Parser detected a complex query. If the expression is processed, the parser may run out of the stack space
or can cause DBC crash. Possible reason could be * an IN LIST condition with many char strings not separated by commas
or a single insert trying to insert many char strings which actually require an insert for each string. * The query is too complex and is taking more than the allowed stack space.
Generated By: RES modules during expression resolution. or GNX module during compiled code generation phase.
For Whom: End User.
Remedy: Correct the condition and resubmit.

5941 Problem encountered while receiving messages from multiple AMPs during multi amp sampling.
Explanation: The system encountered an error while receiving messages from multiple AMPs during multiple AMP
sampling.
Generated By: mgc modules.
For Whom: Database Administrator.
Remedy: The system automatically switches to default one AMP sampling. Please contact your system support representative with all the details.

5942 Maximum deadlock retries limit reached during multi amp sampling on a AMP.
Explanation: Whenever the system encounters a deadlock response from an amp during sampling, it does retries on
that AMP to get the data. If the maximum number of retries is reached, it then post this error message in the event log. This could generally happen if the system is too busy.
Generated By: mgc modules.
For Whom: Database Administrator.
Remedy: The system automatically switches to default one AMP sampling. If the above symptom persists, please contact
your system support representative with all the details.

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