Teradata SQL Error and Failure Codes from Error 9881 To 9890

SQLServerF1_Header_Small

9881 Function ’%VSTR’ called with an invalid number or type of parameters
Explanation: The function was either called with an incorrect number of arguments or the data types could not be
implicitly converted to the types accepted by the function. This error can be returned for both embedded functions and
user-defined functions.
Generated By: Parser Modules.
For Whom: End User.
Remedy: If using an embedded function, reference the documentation for details on how to use it. For user-defined functions,
“show function” or “help function” will show the number and type of parameters accepted by the UDF.

9882 An old statistic with same set of columns is replaced with new statistic to honor the new userspecified column ordering during COLLECT STATISTICS processing.
Explanation: An old statistic with same set of columns is replaced with new statistic to honor the new user-specified column
ordering during COLLECT STATISTICS processing.
Generated By: OPT Modules.
For Whom: User.
Remedy: The user should drop the existing multicolumn stats, before collecting stats on same set of columns in a new
order.

9883 Specified table is already a Load Isolated table.
Explanation: An ALTER TABLE command is issued to alter the specified table to be a LDI table. However, the table is
already a load isolated table.
Generated By: Resolver modules.
For Whom: End user.
Remedy: Do not issue the command as it is a load isolated table already.

9884 Cannot add load isolation property for table with %VSTR defined on the table.
Explanation: An ALTER TABLE command is issued to alter the specified table to be a LDI table. The command cannot
be executed successfully if: 1) If the table has NUSI or USI defined 2) If the table has one or more join indexes that are already not marked as load isolated tables. For example a single table join index exists on the table being altered. 3) If the table has column partitions defined on it.
Generated By: Resolver modules.
For Whom: End user.
Remedy: If the table is a column partitioned table, then alter table cannot be used to make the table a LDI table. Otherwise,
drop the index or indexes and re-issue the command.

9885 Cannot drop load isolation property of the table with %VSTR defined on the table.
Explanation: An ALTER TABLE command is issued to alter the specified LDI table to be a non-LDI table. The command
cannot be executed successfully if: 1) If the table has NUSI or USI defined 2) If the table has one or more join indexes that
are already marked as load isolated tables. For example a single table join index exists on the table being altered.
Generated By: Resolver modules.
For Whom: End user.
Remedy: Drop the index or indexes and re-issue the command.

9886 Specified DML level is already set for the Load Isolated table.
Explanation: An ALTER TABLE command is issued on LDI table to alter the DML that must be load isolated. However,
the table already defines the specified DML level to be load isolated
Generated By: Resolver modules.
For Whom: End user.
Remedy: Check the DML level specified and change it to alter. If DML level is the required setting, do not issue the
ALTER table statement.

9887 No load is in progress for the specified load group value.
Explanation: There is no isolated load operation going on using the specified value for the reserved LDILoadGroup
Queryband. This error can occur for any of the following statements: 1) SET QUERY_BAND that specifies the incorrect
query_band value for LDILoadGroup 2) CHECKPOINT ISOLATED LOADING that specifies the incorrect query_band
value for LDILoadGroup. 3) END ISOLATED LOADING that specifies the incorrect query_band value for LDILoadGroup.
Generated By: Resolver modules.
For Whom: End user.
Remedy: Correct the query_band value that corresponds to the required load operation and re-issue the command.

9888 LDILoadGroup cannot be changed while associated load is in progress.
Explanation: The value for the reserved LDILoadGroup is being changed. However, a concurrent isolated load operation
is already in progress and it has not ended.
Generated By: Resolver modules.
For Whom: End user.
Remedy: After the on-going load operation is completed, correct the LDILoadGroup query_band value to NONE and
resubmit.

9889 Session currently loading other LDI tables.
Explanation: A BEGIN ISOLATED LOADING command is submitted in a session that is currently already a load session.
The session is performing a concurrent isolated load already.
Generated By: Resolver modules.
For Whom: End user.
Remedy: After the on-going load operation is completed, set the LDILoadGroup query_band value to NONE, issue the
SET QUERY_BAND command and then resubmit the BEGIN ISOLATED LOADING command.

9890 Table %DBID.%TVMID is not load isolated.
Explanation: There are multiple reasons for this error. 1) A BEGIN ISOLATED LOADING specifies a table that is either
not a LDI table or a LDI table on which concurrent isolated loading is disabled. 2) TD_ROWLOADID is specified on a non-
LDI table 3) ALTER TABLE with RELEASE DELETED ROWS option is submitted on a non-LDI table.
Generated By: Resolver modules.
For Whom: End user.
Remedy: Check the command for correct LDI table and resubmit the command.

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