Teradata SQL Error and Failure Codes from Error 9848 To 9880

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.

 

Teradata SQL Error and Failure Codes from Error 9838 To 9847

9838 The query ValidTime period specification requires a table with ValidTime period.
Explanation: If query ValidTime period specification is specified in the query then the table reference in the query must
be a ValidTime table.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove the query ValidTime period specification and resubmit.

9839 The column name specified in the FOR PORTION OF must be a ValidTime column defined using derived period.
Explanation: If FOR PORTION OF is specified in the update or delete operation, then the ValidTime column name specified
in the FOR PORTION OF must be a column defined using derived period.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove the FOR PORTION OF from the request and resubmit.

9840 Invalid expression with FOR PORTION OF specification.
Explanation: If FOR PORTION OF is specified in the update or delete operation, then there must not be any column reference
in the DateTime expression of FOR PORTION OF.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove the column reference form the DateTime expression of the FOR PORTION OF and resubmit.

9841 Start or end column of a system-time period reference in SET clause is invalid.
Explanation: If FOR PORTION OF is specified in the update operation and the table contains a system-time period definition,
then the SYSTEM_TIME period start column or the SYSTEM_TIME period end column must not be pecified in the
SET clause.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove the system-time start or end column from the SET clause and resubmit.

9842 The DateTime expression specified in FOR PORTION OF must be comparable to the data type of the start column of the ValidTime period.
Explanation: If FOR PORTION OF is specified in the update or delete operation then the data type of the DateTime
expression in the FOR PORTION OF must be comparable with the data type of the start column of the ValidTime period.
Generated By: RES modules.
For Whom: The end user.
Remedy: Rewrite the DateTime expression such that it results into comparable data type of the start column of the Valid-
Time period and resubmit.
9843 Query resulting in mixing of ANSI temporal syntax and Teradata temporal syntax is not allowed.
Explanation: Mix of ANSI temporal syntax with Teradata temporal syntax is not allowed.
Generated By: RES modules.
For Whom: The end user.
Remedy: Rewrite the query using either only ANSI temporal syntax or existing temporal syntax and resubmit.

9844 The source table cannot be a system-versioned table in a CREATE TABLE AS statement.
Explanation: The source table must not be a system-versioned table during CREATE TABLE AS operation.
Generated By: RES modules.
For Whom: The end user.
Remedy: Replace the source table reference with non system-versioned table and resubmit.

9845 System-time period start or end column cannot be referenced in the triggered action statement.
Explanation: The SYSTEM_TIME period start or end column must not be referenced in the triggered action statement.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove the start or end column of the SYSTEM_TIME period from the triggered action statement and resubmit.

9846 Start or end column of a ValidTime period cannot be referenced in the triggered action statement of the before trigger.
Explanation: The ValidTime period start or end column must not be referenced in the triggered action statement of a
before trigger.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove the start or end column of the ValidTime period from the triggered action statement of the before trigger
and resubmit.

9847 Nontemporal operations are not allowed on a system-versioned table.
Explanation: Any nontemporal operation such as alter table, CREATE TABLE.AS, insert and update are not allowed on
a system-versioned table.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove the GENERATED ALWAYS AS ROW START or GENERATED ALWAYS AS ROW END specification
and resubmit.

Above are list of Teradata Errors or Failure Codes from Error 9838 To 9847 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.

 

Teradata SQL Error and Failure Codes from Error 9828 To 9837

9828 Explicit temporal qualifier must not be specified along with without overlap specification.
Explanation: The unique or primary key constraint definition must not include explicit temporal qualifiers along with
<without overlaps specification>.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove the explicit temporal qualifier from the unique or primary key constraint definition and resubmit.

9829 Start or end column of a system-time period are not allowed in referencing or referenced
column list.
Explanation: The start or end column of a system-time period must not be included in the referencing or referenced column
list of a referential integrity constraint.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove start or end column of the system-time period from the referencing or referenced column list and
resubmit.

9830 The column name specified in referencing or referenced period specification must be of a
ValidTime column defined using derived period.
Explanation: If the referential integrity constraint is defined with referencing and referenced period specification, then
the ValidTime column name specified in the referencing and referenced period specification must be of a column defined
with derived period definition.
Generated By: RES modules.
For Whom: The end user.
Remedy: Define the ValidTime column with derived period definition and resubmit.

9831 Start or end column of a system-time period is not allowed in a check constraint.
Explanation: The start or end column of a system-time period must not be included in the check constraint.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove start or end column of the system-time period from the check constraint and resubmit.

9832 Specified alter table operation is not supported on a system-versioned table.
Explanation: If a table is a system-versioned table then add or drop column, add DEFAULT clause, add NULL or NOT
NULL, change column data type, drop identity column attribute, modify partition WITH DELETE or WITH INSERT,
ALTER TABLE TO CURRENT with WITH DELETE or WITH INSERT, revalidate primary index with WITH DELETE or
WITH INSERT and add NORMALIZATION option are not supported.
Generated By: RES modules.
For Whom: The end user.
Remedy: Drop system-versioning from the table and then do the required alter operation.

9833 The table is already system-versioned.
Explanation: If the table is already a system-versioned table, then alter table to add system-versioning cannot be done
on the same table.
Generated By: RES modules.
For Whom: The end user.
Remedy: Drop system-versioning and add system-versioning again if required.

9834 The table must be a system-versioned table.
Explanation: In order to do drop system-versioning operation the table must be a system-versioned table.
Generated By: RES modules.
For Whom: The end user.
Remedy: Add system-versioning and drop system-versioning again if required.

9835 %VSTR requires a system-versioned table or a transactiontime table.
Explanation: If query system-time period specification or query TransactionTime period specification is specified in the
query then the table reference in the query must be a system-versioned table or a transactiontime table.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove the query system-time period specification and resubmit.

9836 Invalid expression with %VSTR specification.
Explanation: The query system-time period specification must not include a column reference in the DateTime expression.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove the column reference form the DateTime expression of the query system-time period specification and
resubmit.

9837 The column name specified with without delete option must be of a ValidTime column or
TransactionTime column.
Explanation: The column name specified in the alter table drop column, without delete option must be of a ValidTime
column or TransactionTime column.
Generated By: RES modules.
For Whom: The end user.
Remedy: Replace the column reference in alter table drop column, without delete option with ValidTime column or
TransactionTime column and resubmit.

Above are list of Teradata Errors or Failure Codes from Error 9828 To 9837 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.

 

Teradata SQL Error and Failure Codes from Error 9818 To 9827

9818 Warning: XML Plan can’t be logged since the request is either not eligible for IPE or does not qualify.
Explanation: Request specified using DIAGNOSTIC DUMP XMLPLAN is either not eligible for IPE or doesnot qualify.
Hence, XML plan can’t be logged.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is not a user error
Remedy: Make sure the right request should be resubmitted with diagnostic DUMP XMLPLAN that is eligible for IPE
and also qualify for IPE.

9819 Warning: XML Plan can’t be applied since the request is either not eligible for IPE or does not qualify.
Explanation: Request specified using DIAGNOSTIC SET XMLPLAN is either not eligible for IPE or doesnot qualify.
Hence, XML plan can’t be applied.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is not a user error
Remedy: Make sure the right request should be resubmitted with diagnostic SET XMLPLAN that is eligible for IPE and
also qualify for IPE.

9820 A table cannot have more than one system-time period.
Explanation: A table must have only one SYSTEM_TIME column.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove the additional SYSTEM_TIME column and resubmit.

9821 System-versioning cannot be specified without system-time period.
Explanation: A table can be a system-versioned table only if SYSTEM_TIME period is present in the table.
Generated By: RES modules.
For Whom: The end user.
Remedy: Add SYSTEM_TIME column to the table and resubmit.

9822 The ValidTime column must be defined using a derived period definition in a systemversioned table.
Explanation: If the table is a system-versioned table then the ValidTime column in the table must be defined using
derived period.
Generated By: RES modules.
For Whom: The end user.
Remedy: Define ValidTime column using derived period and resubmit.

9823 Invalid system-time period definition.
Explanation: The data type of the start and end columns of the SYSTEM_TIME column must be of data type TIMESTAMP(
6) WITH TIME ZONE. The start column must be defined with GENERATED ALWAYS AS ROW START and end
column must be defined with GENERATED ALWAYS AS ROW END. The columns with GENERATED ALWAYS AS ROW
START and GENERATED ALWAYS AS ROW END must participate only in SYSTEM_TIME column.
Generated By: RES modules.
For Whom: The end user.
Remedy: Correct the SYSTEM_TIME column definition and resubmit.

9824 Invalid use of system-time period start or end column specification.
Explanation: The columns with GENERATED ALWAYS AS ROW START and GENERATED ALWAYS AS ROW END
specification must participate only in SYSTEM_TIME column.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove the GENERATED ALWAYS AS ROW START or GENERATED ALWAYS AS ROW END specification
and resubmit.

9825 A table cannot have both TransactionTime period and system-time period.
Explanation: A table cannot have both TransactionTime column and SYSTEM_TIME column.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove either the TransactionTime column or the SYSTEM_TIME column and resubmit.

9826 The column name specified in the without overlap specification must be a ValidTime column
defined using derived period.
Explanation: If the unique or primary key constraint is defined with <without overlaps specification>, then the Valid-
Time column name specified in the <without overlaps specification> must be of a column defined with derived period definition.
Generated By: RES modules.
For Whom: The end user.
Remedy: Define the ValidTime column using derived period definition and resubmit.

9827 The start or end column of a system-time period cannot be part of a unique column list.
Explanation: The start or end column of a system-time period must not be included in the unique or primary key column
list.
Generated By: RES modules.
For Whom: The end user.
Remedy: Remove start or end column of the system-time period from the unique or primary key column list and resubmit.

Above are list of Teradata Errors or Failure Codes from Error 9818 To 9827 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.

 

Teradata SQL Error and Failure Codes from Error 9808 To 9817

9808 Warning: Use of a discontinued diagnostic detected
Explanation: A discontinued diagnostic setting is in effect.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is not a user error
Remedy: Remove the discontinued diagnostic setting.

9809 Begin or end columns of a derived period cannot be part of a primary index if derived period is a temporal column.
Explanation: Derived period begin or end column can not be part of Primary Index.
Generated By: OPD modules
For Whom: The end user.
Remedy: Remove derived period begin or end column from primary index and submit.

9810 Warning: Ignoring invalid XML plan in effect for emulation. %s
Explanation: XMLPlan specified using DIAGNOSTIC SET XMLPLAN doesn’t match the current optimizer plan. Ignoring
the requested plan and continuing with the current plan. See the event log for the detected differences.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is not a user error
Remedy: Make sure the right XML plan specified. Check system and request names for correctness. Make sure to emulate
the other factors such as costs, statistics, and random AMP samples that influence the optimizer plans.

9811 Warning: Ignoring DUMP XMLPLAN diagnostic.
Explanation: Diagnostic DUMP XMLPLAN is ignored either because of not applicable for this request or failures in saving
the feedback information in the XML document.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is not a user error
Remedy: Make sure DUMP XML plan is used with non cached and for requests producing dynamic plans.

9812 Duplicate row exists in SystemFE.Opt_XMLPlan_Table.
Explanation: Diagnostic DUMP or SET XMLPLAN is issued with duplicate values for the combination of system name
and request name columns.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is a user error
Remedy: Resubmit diagnostic DUMP or SET XMLPLAN with non-duplicate values for for the combination of system
name and request name columns in SystemFE.Opt_XMLPlan_Table.

9813 XML plan does not exist in SystemFE.Opt_XMLPlan_Table.
Explanation: Unable to locate a row in SystemFE.opt_xmlplan_table with the specified system name and request name.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is a user error
Remedy: Check the system and request name for correctness or import the captured XMLPlan from the source system
before issuing this diagonstic.

9814 EXPLAIN is not supported for Diagnostic DUMP and SET XMLPLAN.
Explanation: Diagnostic DUMP/SET XMLPLAN is is supported with EXPLAIN modifier.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is a user error
Remedy: Submit diagnostic DUMP/SET XMLPLAN without EXPLAIN modifier.

9815 BLOCKCOMPRESSION attribute were not copied.
Explanation: This is only a warning to inform the user that the target table will not be inherited BLOCKCOMPRESSION
attribute from the source table.
For example,
CREATE VOLATILE TABLE Table1 AS Table2 WITH [NO] DATA;
CREATE GLOBAL TEMPORARY TABLE Table1 AS Table2 WITH [NO] DATA;
BLOCKCOMPRESSION attribute on Table2 (if exist) will not be copied to Table1.
Generated By: Resolver.
For Whom: End User.
Remedy: The message is for information only.

9816 XML plan logging is disabled in DBSControl settings.
Explanation: Diagnostic DUMP XMLPLAN failed since DBSControl DisableXMLPLANLogging option is disabled.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is a user error
Remedy: Resubmit Diagnostic DUMP XMLPLAN after enabling DisableXMLPLANLogging DBSControl option.

9817 Diagnostic DUMP/SET XMLPLAN is in effect already.
Explanation: Diagnostic DUMP/SET XMLPLAN failed since it is already active in the same session.
Generated By: Parser modules.
For Whom: EndUser.
Notes: This is a user error
Remedy: Resubmit Diagnostic DUMP/SET XMLPLAN in a new session or after deactivating the existing one.

Above are list of Teradata Errors or Failure Codes from Error 9808 To 9817 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.

 

Teradata SQL Error and Failure Codes from Error 9761 To 9807

9761 Dictionary load isolation information for %VSTR does not match header load isolation
information.
Explanation: This message is displayed if the load isolation information in the table header does not match the corresponding
information in DBC.TVM record for the table.
Generated By: Checktable.
For Whom: Site support representative.
Remedy: Contact your support representative.

9762 The RowLoadID value in the index sub-table and the base-row does not match.
Explanation: This message is displayed if the RowLoadID of the secondary index and the primary data does not match
for a LDI table.
Generated By: Checktable.
For Whom: Site support representative.
Remedy: Contact your support representative.

9771 AutoCheck detected NUSI corruption when transaction is in non-abortable state. %s
Explanation: Corruption was detected in the NUSI or CDT index while doing index maintenance during rollback or
deferred transaction.
Generated By: AutoCheck.
For Whom: Site support representative.
Remedy: Contact your support representative.

9801 The PERCENTILE_CONT/PERCENTILE_DISC ORDER BY column must be a numeric data type.
Explanation: The PERCENTILE_CONT/PERCENTILE_DISC ORDER BY column must have a numeric data type.
Generated By: Res modules
For Whom: End User.
Remedy: Resubmit the request with a valid numeric expression.

9802 The DictionaryCacheSegmentSize is too small for this request.
Explanation: The request for cache is made that exceeds the segment size for cache. A single request should not exceed
the segment size.
Generated By: MGC modules.
For Whom: Internal.
Remedy: Increase the DBS Control Record field DictionaryCacheSegmentSize. See Teradata Utilities Manual for information
on DBS Control fields. Simplify the table by reducing the number of columns or shortening or removing some of
the titles or defaults .

9803 Views/Macros having SEQUENCED qualifier may fail during its use.
Explanation: View or Macros having SEQUENCED qualifier may report an error during its use if SEQUENCED semantics
can not be converted to point-in-time semantics.
Generated By: parser.
For Whom: User.
Remedy: Nothing to be done. Such cases are not yet by the database.

9804 Response Row size or Constant Row size overflow.
Explanation: The user request generated a response or constant row of data that exceeded internal Teradata database
limitations.
NOTE: Although the size of spool files has been increased to 1 MB, response rows still have lower limits. The response row is limited to two 64k fields generated by the projection list and the order by clause. Constant rows are limited to approximately 1MB.
Generated By: Parser modules.
For Whom: End User.
Remedy: Change the SQL and/or reduce the data field sizes and/or number of fields being returned and resubmit the
request. Limit the projection list and order by clause to approximately 64k bytes of data each.

9805 User %FSTR is not authorized to use the VERYHOT temperature setting.
Explanation: The user tried to execute a statement that would manually set data to VERYHOT temperature but was not
authorized.
Generated By: SYN and RES modules.
For Whom: The DBA.
Remedy: Grant execute macro access to macro DBC.VHCTRL to the user that caused the error and resubmit the request.

9806 Invalid Restore of database TD_SYSFNLIN.
Explanation: The user requested an invalid restore of database TD_SYSFNLIB. A restore of the TD_SYSFNLIB is not
permitted.
Generated By: OPT Modules.
For Whom: User.
Remedy: The user must change the command to remove any invalid options. Then re-submit the rquest.

9807 Query caused a snapshot. It will be retried.
Explanation: This is a warning only, not an error. It informs the user that an automatic retry is being executed for the
query.
Generated By: PAR modules.
For Whom: End User.
Notes: The request is still processed despite the warning.
Remedy: This message is for information only.

Above are list of Teradata Errors or Failure Codes from Error 9761 To 9807 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.

 

Teradata SQL Error and Failure Codes from Error 9729 To 9756

9729 Session cannot modify a load operation.
Explanation: The LDI table is being loaded as a concurrent load isolated operation by a session. A CHECKPOINT can be
issued on the on-going load only if the session is the same session that issued the BEGIN ISOLATED LOADING statement.
Generated By: AMP Modules.
For Whom: End user.
Remedy: The command may be re-issued in the session that issued the BEGIN ISOLATED LOADING.

9730 Table %DBID.%TVMID is in load state.
Explanation: The LDI table is being loaded as a concurrent load isolated operation. The following conditions cause the
error to be reported: 1) A BEGIN ISOLATED LOADING statement is attempting to initiate load on the table. 2) A DML
statement with the NO ISOLATED LOADING is being executed on the table in this state.
Generated By: AMP Modules.
For Whom: End user.
Remedy: The command may be re-issued after the table completes the concurrent load operation.

9731 Load on the specified table is completed. Set session LDILoadGroup query band value to
NONE.
Explanation: A load session submitted a modification on the LDI table; however the load operation has already ended.
The session query band must have been set to NONE.
Generated By: AMP Modules.
For Whom: End user.
Remedy: The query band value for LDILoadGroup in the session must set to NONE as the tables in the session.s context
are no longer in concurrent load isolated operation.

9732 Invalid RowLoadID value in the row.
Explanation: Level three checking using Checktable verifies that the RowLoadID contains the correct insertion and deletion
load value. The load values must be within the CurrLoadID value for the table as recorded in DBC.TVM.CurrLoadID.
The insertion load value must be less than the deletion load value within the RowLoadID.
Generated By: Checktable.
For Whom: Site support representative.
Remedy: Contact your support representative.

9733 Operation not allowed: one or more tables is in isolated load operation.
Explanation: An ARCHIVE/DUMP command is issued on a LDI table (or the containing database) that is currently
being loaded as a concurrent load operation. The command cannot be executed while the load operation is in progress.
Generated By: Archive/Restore.
For Whom: End user.
Remedy: Resubmit the command after the on-going load operation is completed.

9736 Backup object was found that was not locked; no data dumped.
Explanation: The object was found during the dump that was not locked and did not have the Logging Online Archive
option on. This could happen if the object was added after the Logging Online Archive On and LOCK commands were run
and before the dump object list was created. No data rows are being dumped, just the table header and dictionary rows.
Generated By: Dump – AMP
For Whom: End User.
Notes: When the table is restored from this dump, it will be empty.
Remedy: If the data in the table must be backed up, dump the database again.

9737 Argument is either not byte-string or byte-string length is invalid.
Explanation: The input is either not a byte string or byte string is not 2, 4 or 6 bytes in length.
Generated By: OPT and EVL modules.
For Whom: EndUser.
Notes: This is a user error
Remedy: Make sure the input argument is byte-string with length of 2, 4 or 6 bytes.

9740 DBQL Express request sent with invalid LOB column type.
Explanation: The AMP DBQL software encountered a fault while initializing LOB field during an express request to
insert into a LOB column in DBQL table.
Generated By: InitExpLob() function in expdbql module.
For Whom: System administrator & Site support representative.
Remedy: This error should be reported to the site support representative including any snapshot dump for the error.
Some DBQL table’s LOB column data is not getting logged. This error is not user controllable. The remedy is that the caller
of InitExpLob() function should set proper lob type. Supported LOB types defined are BLOB, CLOBL (CLOB latin) and
CLOBU (CLOB Unicode)

9752 DBQL lock range must be between 5 and 32,767.
Explanation: For the WITH LOCK = n option of BEGIN QUERY LOGGING, the minimum value allowed is 5, and maximum
is 32767.
Generated By: opddbql.c
For Whom: End User.
Remedy: Specify a value in the correct range.

9756 Secure server not available.
Explanation: This error occurs when all the UDF secure servers are busy processing table functions and another udf is
trying to acquire the server that has entered a critical region.
Generated By: UDF subsystem
For Whom: End Users.
Remedy: Wait for table functions to finish first.

Above are list of Teradata Errors or Failure Codes from Error 9729 To 9756 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.

 

Teradata SQL Error and Failure Codes from Error 9705 To 9728

9705 A network disconnect during a LOB client-to-server transfer caused an abort.
Explanation: A session using Redrive or Recoverable Network Protocol was transferring a LOB from the client to the
database when a network disconnect occurred. The Gateway initiated an abort of the transaction.
Generated By: Dispatcher.
For Whom: End User.
Remedy: Resubmit the request and transaction.

9721 Left-over spool(Final Response) table found : transaction aborted.
Explanation: This error occurs if a left-over spool is a Final response spool, which is used by a transaction other than the
transaction for which it was created. The transaction attempting to use this left-over spool is aborted, and diagnostic information
about the left- over spool appears on the system-console screen.
Generated By: AMP
For Whom: Site Support Representative.
Notes: Developers researching the left-over spool problem will be interested in the console-screen output produced by
the logging of this error.
Remedy: Contact your Support Representative.

9722 Attempt to access a down Table or Index contains down region
Explanation: A statement has attempted to access a table or index that has been set down. It is not currently accessible
for SQL statements.
Generated By: AMP (STP, S2S, SUT).
For Whom: End User.
Remedy: Reset the down table or index status before resubmitting the SQL statement. Some of the ways to reset the
down status are: – ALTER TABLE SQL statement – Fast path DELETE ALL/ DROP table SQL statement – Rebuild the Table
– Restore the table from backup – Drop and recreate the index

9723 Table operator error on the AMP, details: %VSTR
Explanation: This message indicates a table operator processing error on the AMP.
Generated By: AMP
For Whom: End user or Field Engineer or the concerned site support representative.
Remedy: Check the table operator source code if the problem persists contact support personnel.

9724 An AMP is down and fallback sub-table data cannot be used in %VSTR.
Explanation: The query attempted to perform an operation on fallback table data that is not supported while an AMP is
down.
Generated By: AMP (STP).
For Whom: End User.
Remedy: Bring down AMPs back online and retry query.

9725 The same user is already logged on and running other BAR jobs.
Explanation: The restore job is rejected as same user is already running other BAR jobs.
Generated By: AMP
For Whom: End User.
Remedy: Logoff the sessions where same user is running other BAR jobs.

9726 DBQL AWT DPS cache fault isolated (count %s).
Explanation: The AMP DBQL software encountered a fault while using the awtDPS cache to collect AMP usage data
(Algorithm 3 primarily). The fault was isolated to allow the step to continue. DBQL capture of AMP request and step data
is impacted and the QryLog view DBQLStatus field (DBQLogTbl) will reflect that.
Generated By: AMP Worker Task (awtdps and other modules).
For Whom: System administrator & Site support representative.
Notes: This message is logged once per AMP and if faults continue on an AMP it is logged once more no sooner than 60
minutes after the first. The count value (faults isolated for this AMP) helps identify the extent of the problem. DBS Control
parameter DBQLSnapLimit controls snapshot dumps.
Remedy: This error should be reported to the site support representative including any snapshot dump for the error.
Some DBQL AMP usage data is not being collected. When the system is restarted the awtDPS cache is created new, the
same as a normal DBS TPA start and DBQL collection is no longer impacted. If this message reoccurs, report it. DBQL
Algorithm 1 may be selected in DBS Control general 64 until the issue with Algorithm 3 is resolved. Be aware that DBQL
usage data logged varies depending on the algorithm selected.

9727 DBQL AWT DPS cache failed assertion test, %s.
Explanation: The AMP DBQL software detected a problem in the awtDPS cache used to collect AMP usage data (Algorithm
3 primarily). The failure is indicated by the variable part of the message.
Generated By: AMP Worker Task (awtdps and other modules).
For Whom: System administrator & Site support representative.
Notes: This message may be logged under the DBQL awtDPS fault isolation code.
Remedy: This error should be reported to the site support representative.

9728 Retry later as currently a load operation is in progress on the table %DBID.%TVMID.
Explanation: The LDI table is being loaded as a concurrent load isolated operation.
Generated By: AMP Modules.
For Whom: End user.
Remedy: The command must be re-issued after the load operation is completed

Above are list of Teradata Errors or Failure Codes from Error 9705 To 9728 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.

 

Teradata SQL Error and Failure Codes from Error 9692 To 9704

9692 HASH BY/PARTITION BY expression not found in input SELECT list.
Explanation: A HASH BY or PARTITION BY expression must be part of the input SELECT list for the user defined table
operator.
Generated By: OPT modules.
For Whom: End User.
Remedy: Change HASH BY/PARTITION BY phrase or input SELECT list.

9693 NORMALIZE not allowed for system projected transaction time column.
Explanation: NORMALIZE not allowed for system projected transaction time column.
Generated By: OPT module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9694 MultiLoad utility does not support load operations on NORMALIZE tables.
Explanation: MultiLoad utility does not support load operations on NORMALIZE tables.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9695 SET REDRIVE FOR TRANSACTION is not supported in query band statement.
Explanation: The SET REDRIVE FOR TRANSACTION is not supported in query band statement. It is supported with
FOR SESSION option only.
Generated By: OPD
For Whom: User.
Remedy: Correct the query band statement and resubmit.

9696 Unwind parser stack and return to dispatcher during abort of IPE request.
Explanation: Unwind parser stack and return to previous dispatcher logmark when aborting an IPE request.
Generated By: Dispatcher, Parser modules.
For Whom: Internal only.
Remedy: This operation is internal to the database. When parser optimizes a request using IPE and the SQL request
receives an abort, dispatcher raises this event to signal parser to unwind the stack and return to the previous dispatcher
logmark.

9697 Updating ignore column(s) is not allowed on normalize table with current or sequenced validtime update.
Explanation: Updating ignore column(s) is not allowed on normalize table with current or sequenced validtime update.
Generated By: RES module.
For Whom: End User.
Remedy: Don’t update only the ignore column.
9698 Invalid DELETE in Fastload: %VSTR.
Explanation: FastLoad does not permit DELETE other than Nontemporal DELETE.
Generated By: resolver.
For Whom: Host Utility Fast Load.
Remedy: Correct the statement and resubmit the request.

9699 Only one expression is permitted in the WITHIN GROUP ORDER BY clause .
Explanation: The PERCENTILE_CONT/PERCENTILE_DISC functions support one expression in WITHIN GROUP
ORDER BY specification.
Generated By: Res modules
For Whom: End User.
Remedy: Resubmit the request with a valid ORDER BY expression.

9700 The PERCENTILE_CONT/PERCENTILE_DISC(expression) must be a numeric value between 0 and 1.
Explanation: The PERCENTILE_CONT/PERCENTILE_DISC expression must evaluate to a numeric value between 0
and 1.
Generated By: Res modules
For Whom: End User.
Remedy: Resubmit the request with a valid numeric expression.

9701 The system was restarted with redrive disabled due to a crash during startup.
Explanation: There was a crash during startup. Redrive has been disabled in order to prevent this crash from occurring
repeatedly and taking down the PE.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Contact your support representative.

9703 A table does not have Normalize definition.
Explanation: Normalize definition can not be dropped without defined it on a table.
Generated By: RES module.
For Whom: End User.
Remedy: Normalize definition can not be dropped without defined it on a table.

9704 A Dispatcher is late in responding to a TDWM internal message; no action needed.
Explanation: This is a TDWM informational message only. On each TDWM dashboard interval a message is sent to each
dispatcher requesting data. If a dispatcher does not respond before the next interval, this message is logged. As a result of a late dispatcher message, some rows may be missing through the TDWMExceptions API however all rows are logged to disk.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: This is an informational message only. The software handles the situation and no user response is needed. The
DBA may take note of the logged message in investigating system responses.

Above are list of Teradata Errors or Failure Codes from Error 9692 To 9704 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.

 

Teradata SQL Error and Failure Codes from Error 9679 To 9691

9679 SQL request cannot be prepared because query capture is in effect for this session.
Explanation: The BEGIN QUERY CAPTURE session currently does not support parameterized SQL requests with question-
mark parameter markers & non-parameterized SQL requests as part of Auto-Generated Key Retrieval (AGKR).
Generated By: parser.
For Whom: User.
Remedy: Do not submit parameterized SQL requests with question-mark parameter markers & non-parameterized SQL
requests as part of Auto-Generated Key Retrieval (AGKR) in BEGIN QUERY CAPTURE session.

9680 SQL request was not executed because query capture is in effect for this session.
Explanation: This is only a warning to indicate that the SQL request submitted within a BEGIN QUERY CAPTURE session
is not actually executed. The query capture is successfully done for the submitted SQL request.
Generated By: parser.
For Whom: User.
Remedy: Simply ignore, as this is the expected behaviour in BEGIN QUERY CAPTURE session. However, if the SQL
request needs to be executed then end the BEGIN QUERY CAPTURE session using END QUERY CAPTURE statement and
resubmit the SQL request.

9682 Invalid Normalize operation , MEETS only is not allowed.
Explanation: MEETS NORMALIZE operation is not supported on TD1410.
Generated By: SYN module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9683 The DBQL ObjectUsage logging is not enabled. The change percentage to skip statistics collection is determined based on dynamic AMP sampling, which can only detect the row count change.
Explanation: The DBQL ObjectUsage logging is not enabled. The change percentage to skip this statistics collection is
determined based on the dynamic AMP sampling which can only detect the row count change. Therefore, the system cannot
accurately determine the update and the combination of insert and delete counts on the target table.
Generated By: OPD modules.
For Whom: End User.
Notes: This warning is issued when the DBQL ObjectUsage logging is not enabled and statistics collection is skipped.
Remedy: Turn on ObjectUsage logging for the target database if more accuracy is needed.

9685 Statistics on this expression are not valid.
Explanation: The statistics expression refers to objects which no longer exists or matches with the original expression.
Generated By: OPT modules.
For Whom: End User.
Remedy: Revalidate the statistics by recreating the object referred in the expression or drop the invalid stats by dropping
all the statistics on the table and recollect the required statistics.

9686 The specified sampling percentage may not be optimal for some of the statistics.
Explanation: A user-specified sampling percentage value is not optimal and might cause estimation errors.
Generated By: OPD modules.
For Whom: End User.
Notes: This warning is issued when a user specified a sampling percentage which is not optimal.
Remedy: Use system-determined sampling percentage (recommended) or increase the user-specified sampling percentage.

9687 No active BEGIN QUERY CAPTURE to end.
Explanation: There is no active BEGIN QUERY CAPTURE session in progress to end. END QUERY CAPTURE statement
is used to end the scope of previously submitted BEGIN QUERY CAPTURE statement in the session.
Generated By: parser.
For Whom: User.
Remedy: Nothing to be done. This error is for information only that there is no currently active BEGIN QUERY CAPTURE
session in progress..

9688 Table operator’s execution error: %VSTR.
Explanation: Table operation’s execution error with the detailed message.
Generated By: Parser.
For Whom: System Support Representative.
Remedy: Contact your support representative.

9689 A CURSOR is not updatable when NORMALIZE clause is specified in the CURSOR select statement.
Explanation: A CURSOR is not updatable when NORMALIZE clause is specified in the CURSOR select statement.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9690 WITH clauses may not be specified in a SELECT NORMALIZE request.
Explanation: WITH clauses may not be specified in a SELECT NORMALIZE request.
Generated By: OPT module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9691 Invalid HASH BY/PARTITION BY constant.
Explanation: A HASH BY or PARTITION BY constant does not represent the position of a selected expression.
Generated By: OPT modules.
For Whom: End User.
Remedy: Change HASH BY/PARTITION BY phrase.

Above are list of Teradata Errors or Failure Codes from Error 9679 To 9691 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.

 
1 2 3 4 50