Teradata Database Errors

Teradata error 9128 The transaction exceeded the maximum number of rowhash locks allowed.

Teradata code 9128 The transaction exceeded the maximum number of rowhash locks allowed.

Error description

error explanation...

Explanation: This error is returned when a transaction has exceeded the number of rowhash locks allowed. The threshold on the number of rowhash locks allowed is defined in DBSControl via the General field ’MaxRowHashBlocksPercent’.

This is done so that one transaction does not fill up the lock table with rowhash locks. The number of control blocks/locks that can fit into an AMP lock table is defined by STDMAXLOCKBLOCKS which is currently ~51860.

Generated By: LOK subsystem.

For Whom: End user.

Remedy: Reduce the number of rowhash locks that the transaction is acquiring. An alternative is increase the General field ’MaxRowHashBlocksPercent’ value in DBSControl.

More information

Teradata error TDP0910 USER LOGON EXIT INTERFACE FAILED SYS=systemcode, USER=usercode

Teradata error SYS=systemcode, USER=usercode

Teradata error 232 EM_INVPCLAUTHRSP Invalid authrsp parcel.

Teradata error TDP2313 DEVICE devnum: UNABLE TO LOG ERROR, CODE(code), INFO(info)

Teradata error TDP2060 START POOL COMMAND IS TOO LONG

Teradata error 10608 Invalid administrative thread operation: %d

Teradata error TPT18146 Error %d allocating memory for Error List buffer

Teradata error 5 – 42 Messages

Teradata error TPT2075 Error: Failed to configure the Job Logger facility

Teradata error TDP1879 TDPSYNC: SPI#SESS COUNTER IS INVALID

Error category

errors 91*



Teradata Database Errors