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
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.

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 *