Teradata SQL Error and Failure Codes from Error 3160 To 3175

3160 DBQL or TDWM Cache invalid or size exceeded
Explanation: This error occurs if something is wrong in allocating DBQL or TDWM cache to store rows of information,
or if the cache reference is invalid.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Verify system resource condition which is affecting DBQL or TDWM

3161 DBQL internal event
Explanation: This event is logged if DBQL cannot get resources at startup, if a timeout occurs while attempting to
BEGIN or END query logging or if messages to the AMPS become queued up (past about 80 per PE).
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Contact your support representative.

3167 Object Use Count Cache invalid or size exceeded
Explanation: This error occurs if something is wrong in allocating Object Use Count Cache to store object information, or
if the cache reference is invalid.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Verify system resource condition that is affecting Object Use Count.

3168 Object use count for one or more objects could not be updated due to some error on AMPs.
Explanation: This error occurs if Object Use Count is unable to perform because of an SYSERRORMSGKIND response
message received from the AMP as part of ExpObjUseCnt express request made by DisObjUseCnt task.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Contact your support representative. Check all AMPs are online and there are no deadlocks to lock a dictionary
row.

3169 Object Use Count internal event
Explanation: This error occurs if Object Use Count is unable to perform because of an internal error.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Contact your support representative. A system restart is needed to make the Object Use Count feature working.

3170 System is busy. Object use count feature should be disabled. Use count for one or more objects may not be captured in dictionary.
Explanation: This error occurs if Object Use Count is unable to perform because system is busy or Object Use Count feature
is slow because of some other reason.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Contact your support representative. Check there are no deadlocks to lock a dictionary row.

3171 Object use count feature is disabled because a lock on dictionary row could not be obtained.
Explanation: This error occurs if Object Use Count feature is unable to perform because a lock on dictionary row could
not been obtained after waiting for LOCKTIMEMAXTHRESHOLD (20 Min) time. This error can occur if dictionary is
locked down for a significant amount of time by some task or operations like Archive (i.e. Dump Restore) of the system.
Generated By: Dispatcher.
For Whom: System Support Representative.
Remedy: Contact your support representative.

3172 Cursor Positioning has a bad statement number.
Explanation: The statement number in the cursor positioning parcel is invalid. It is either 0 or bigger than the maximum
statement number for the request.
Generated By: Dispatcher.
For Whom: Applications.
Remedy: Provide a valid statement number in the cursor positioning parcel and resubmit.

3173 Row cursor positioning has a bad row number.
Explanation: The row number specified in the row position parcel is non-zero for a non-data returning statement or the
row number is bigger than the number of rows in the answer set.
Generated By: Dispatcher.
For Whom: Applications.
Remedy: Provide a valid row number in the row cursor positioning parcel and resubmit.

3174 LOB offset/character positioning has a bad value.
Explanation: If the LOB is a BLOB, the offset specified in the offset positioning parcel exceeds the size of the BLOB. If the
LOB is a CLOB, the character position specified in the parcel exceeds the total number of characters for the CLOB. Since
position 0 will point to the very first byte/character, the valid value to point to the last byte/character in the LOB will be
total byte length – 1 for BLOB and total character count – 1 for CLOB.
Generated By: Dispatcher.
For Whom: Applications.
Remedy: Provide a valid offset/character position in the offset/character cursor positioning parcel and resubmit.

3175 Cursor Positioning not supported.
Explanation: Currently, Teradata does not support cursor positioning for the following conditions: 1) It is a multi-statement
request. 2) Perform row positioning on a LOB in locator mode. 3) Perform offset positioning on non LOB data or LOB
in inline mode. 4) Perform row positioning on a select via primary index access.
Generated By: Dispatcher.
For Whom: Applications.

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