Teradata SQL Error and Failure Codes from Error 9848 To 9880

SQLServerF1_Header_Small

9848 Cannot add system-versioning to the table: %VSTR.
Explanation: A table with a join index and/or a trigger defined on it or if it is a temporal table with unique or primary
key constraints that requires system-defined JI then table cannot be altered to add a system-versioning column.
Generated By: RES modules.
For Whom: The end user.
Remedy: Drop any join indexes and/or triggers or unique or primary constraints that requires sytem-defined JI(if the
table being altered is a temporal table) and resubmit the request. Recreate the dropped join indexes and/or triggers or
unique or primary key constraints once the table is altered.

9850 Invalid input to table operator: %VSTR.
Explanation: The call to the table operator had invalid input parameters. The specific error is given in the error message.
Generated By: Parser.
For Whom: End User
Remedy: Fix the problem mentioned in the specific error message and resubmit the request

9851 The file %VSTR already exists in the database.
Explanation: The user tried to create a table, view, macro, trigger, procedure, function, jar or File (UIF) whereas a File
(UIF) with that name already existed in that database. This error can be returned by the following DDLs: – INSTALL_FILE –
CREATE TABLE, VIEW,MACRO, TRIGGER, PROCEDURE or FUNCTION statement or an INSTALL_FILE –
INSTALL_JAR or REPLACE_JAR
Generated By: RES modules.
For Whom: End User
Remedy: Resubmit the request using a new file name

9852 The file %VSTR does not exist in the database.
Explanation: The error can be generated by one of the following statements: REPLACE_FILE, REMOVE_FILE,
REDISTRIBUTE_FILE or SHOW FILE. If the specified file is not found in the database, the error is returned
Generated By: RES modules.
For Whom: End User
Remedy: Correct the name of the file in teh SQL and resubmit the request.

9853 Script execution failed: %VSTR.
Explanation: The error can be returned in the following cases: 1) Executable for script cannot be determined. 2) Cannot
find executable for script. 3) Invalid return value from script. 4) Invalid data type passed to script
Generated By: RES/UDF modules.
For Whom: End User
Remedy: Correct the script invocation and resubmit the request.

9854 Invalid invocation: %VSTR
Explanation: The error can be generated when processing the input parameters for the specified function. The failing
function name and the specific error will be displayed in the error message
Generated By: RES modules.
For Whom: End User
Remedy: Fix the problem mentioned in the specific error message and resubmit the request

9855 Script execution in progress in the database. Please try again
Explanation: A script is being executed in the database where the file is being replaced/removed. As a result the
replace/remove cannot be done
Generated By: CUF modules.
For Whom: End User
Remedy: Resubmit the request after a while.

9856 %VSTR
Explanation: An error was generated during processing of UIF related operations. Details are given in the error message
Generated By: SYN/RES modules.
For Whom: End User
Remedy: Correct the statement based on the error message and resubmit the request

9857 A file named %VSTR is already installed in the database
Explanation: The INSTALL_FILE attempted to install a file with a filename that was already present in the database
Generated By: RES modules.
For Whom: End User
Remedy: Resubmit the request using a new Linux file name

9859 %s
Explanation: This is an internal error for debugging purposes only.
Generated By: Parser modules.
For Whom: System Support Representative.
Remedy: Contact your System Support Representative.

9880 Invalid TimeDateWZControl setting in DBSControl for OVERRIDE parcel.
Explanation: Unity issued a request with an OVERRIDE parcel containing timestamp related data and the DBSControl
General group field TimeDateWZControl setting is not 2(enabled with UTC) or higher.
Generated By: PAR modules.
For Whom: Unity.
Remedy: Modify DBSControl General group field TimeDateWZControl to be 2 (enabled with UTC) or 3 (enabled with
LOCAL).

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