Teradata SQL Error and Failure Codes from Error 6948 To 6958

SQLServerF1_Header_Small

6948 UDT expression, of type %TVMID, needs an explicit cast to a compatible type before usage in %VSTR.
Explanation: UDT expressions could be compatible with system operators/functions only when the dbscontrol flag DisableUDTImplCastForSysFuncOp
is set to zero.
Generated By: RES and OPT modules.
For Whom: End User.
Remedy: Resubmit the request either not using UDTs, cast the UDT to the appropriate datatype, or ensure the dbscontrol
flag DisableUDTImplCastForSysFuncOp is set to zero.

6949 Unable to determine best cast from multiple cast definitions involving UDT type %TVMID.
Explanation: There are more than one CAST definitions that will satisfy the requested source and target relationship.
Generated By: RES module.
For Whom: End User.
Remedy: Resubmit the request with a CAST that is more precise or remove enough existing CASTs so that a CAST may
be chosen.

6950 Returning LOB inline in MultipartRecord mode is not supported for XSP.
Explanation: Currently returning LOB inline in MultipartRecord mode with XSP is not supported.
Generated By: OPT modules.
For Whom: End User.
Remedy: Return LOB in locator mode instead.

6951 DDL is not supported in multi-statement request within a stored procedure.
Explanation: This error occurs in the following situation: a. Any DDL statement is specified in a stored procedure using
the multi-statement request and dynamic SQL feature of stored procedures. For instance, DATABASE statement, SET SQL
statements, multi statement requests, CREATE USER/DATABASE statement without FROM clause. This is a run-time
error.
Generated By: RES Modules.
For Whom: End user.
Remedy: Do not use the DDL in multi-statement request. Recreate the stored procedure if necessary.

6952 Indexes cannot be created or dropped during random AMP sample emulation.
Explanation: When random AMP sample emulation is active for a table indexes cannot be created or dropped on that
table.
Generated By: OPT modules.
For Whom: End User.
Remedy: If you want to turn off random AMP sample emulation use the DIAGNOSTIC HELP SAMPLES to determine
the samples that have been set and the DIAGNOSTIC SET SAMPLES statement to turn them off. If you want to emulate
with the index change you must make the change on the target system and then re-extract the random AMP samples.

6953 The authorization definition specified in the statement does not match with the actual definition.
Explanation: This error is generated when an UDF/XSP is created with authorization defined, and the authorization
definition being specified in the CREATE/REPLACE UDF/XSP statement does not match with the actual authorization
definition.
Generated By: Resolver
For Whom: UDF/UDT/XSP/AUTH developer
Remedy: Check the authorization definition.

6954 Not authorized on %VSTR. Exceeded allowed attempts, the authorization statement has been disabled.
Explanation: To avoid having a user submit the authorization statement repeatedly in an attempt to obtain password
information, the user is allowed three tries to get the authorization information correct after which the CREATE/REPLACE
AUTHORIZATION statement will be disabled. The user will have to logoff and log back in to reset the lockout.
The maximum number of failed attempts within a 5 minutes period is 3.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the login information in the statement and resubmit it in another session.

6955 The Create/Replace Authorization statement is disabled.
Explanation: The Create/Replace Authorization statement is disabled due to the maximum number of failed attempts,
which is 3, has been reached within a 5 minutes timeframe.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the login information in the statement and resubmit it in another session.

6956 Column %VSTR has statistics and cannot be dropped or modified.
Explanation: A column with any stats defined on it cannot be dropped or modified by a ALTER TABLE statement.
Generated By: OPD modules.
For Whom: End User.
Remedy: If the column needs to be dropped or modified, drop all the multi-column statistics defined on that column
with the DROP STATISTICS statement.

6957 Logging for online archive is not allowed on journal tables.
Explanation: This error occurs when trying to execute LOGGING ONLINE ARCHIVE ON statement on journal tables.
Generated By: RES modules.
For Whom: End User.
Remedy: Do not submit LOGGING ONLINE ARCHIVE ON statement on journal tables.

6958 LOGGING ONLINE ARCHIVE ON statement for database %VSTR is not supported.
Explanation: LOGGING ONLINE ARCHIVE ON statement does not support the specified database.
For instance, LOGGING ONLINE ARCHIVE ON statement is not supported for database DBC or database SYSUDTLIB.
Generated By: RES modules.
For Whom: End User.
Remedy: Do not submit LOGGING ONLINE ARCHIVE ON statement on the specified database.

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