9891 Concurrent load operations are disabled in session.
Explanation: A SET QUERY_BAND command is submitted to set the query band value for LDILoadGroup from a session
that disables load operations.
Generated By: Resolver modules.
For Whom: End user.
Remedy: Enable load operations in the session and re-submit the command.
9892 Specified load isolated operations are disabled on %DBID.%TVMID.
Explanation: A WITH ISOLATED LOADING option is specified in a DML statement and the LDI target table does not
have the DML level enabled for load isolation.
Generated By: Resolver modules.
For Whom: End user.
Remedy: Enable load operations on the table and resubmit the command. Or perform the DML as a nonconcurrent LDI
modification.
9893 Invalid operation on load isolated table.
Explanation: The DMLs within a transaction for a given LDI table must all be nonconcurrent load isolated or all must be
concurrent load isolated DMLs. The specified command violates this rule.
Generated By: Parser modules.
For Whom: End user.
Remedy: Correct the command and resubmit or perform after the on-going operation is completed.
9894 Cannot define a %VSTR for a load isolated table.
Explanation: A load isolated table does not support permanent journals, compressed join index or hash index.
Generated By: Parser modules.
For Whom: End user.
Remedy: Modify the command as applicable to execute successfully. For example, remove the permanent journaling
option. Do not create a compressed join index or hash index on a LDI table.
9895 Cannot define load isolation on a table with permanent journal defined.
Explanation: A load isolated table does not support permanent journals. An alter table command is issued to make a
non-LDI table with permanent journal defined to a LDI table.
Generated By: Parser modules.
For Whom: End user.
Remedy: Remove permanent journaling option to convert the non-LDI table to LDI table Or create a new table without
journaling option from the existing table using CREATE TABLE AS.
9896 Load operation cannot occur as CurrLoadID reached the upper limit.
Explanation: Each concurrent isolated load operation increments the CurrLoadID by 2. The increment is causing the
upper limit of 0x7FFFFFFE to be exceeded and cannot be executed.
Generated By: Parser modules.
For Whom: End user.
Remedy: Perform ALTER TABLE using the RESET LOAD IDENTITY option and then perform the load operation.
9897 MLoad target table may not contain secondary indexes with load identity.
Explanation: MLoad command is issued on a LDI table that defines a NUSI with load identity.
Generated By: Parser modules.
For Whom: End user.
Remedy: Drop the NUS with load identity and resubmit the MLOAD command. Create the index after MLOAD is successful.
Alternatively, see if MLOADX may be used instead that supports all NUSI and USI on LDI tables.
9898 Table %DBID.%TVMID cannot be loaded as the %FSTR table is already in a different load operation.
Explanation: A child and parent LDI tables may not be loaded simultaneously in separate load operations.
Generated By: Parser modules.
For Whom: End user.
Remedy: Either load both the parent and child tables in the same load operation or perform them one after the other.
9900 Duplicate names specified in custom clause.
Explanation: Custom clause for server object must not have duplicate name.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Remove the duplicate name in custom clause and resubmit.
9901 Specified server already exists.
Explanation: The user attempted to create the server. A Server exists with that name. This error occurs on a CREATE
SERVER statement.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Choose a new name for the server and resubmit the request.
9902 Specified ’%VSTR’ option does not exist.
Explanation: The user attempted to alter the server.Specified server attribute option does not exist.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.
Above are list of Teradata Errors or Failure Codes from Error 9891 To 9902 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.