...
| Code Block | ||
|---|---|---|
| ||
[2014/08/28 13:00:14] [FAQINTERNAL:Thread-1398925664] [FAQINTERNAL:Level-2] ERR-11075(errno=0) The transaction has exceeded the lock timeout specified by the user. [2014/08/28 13:00:14] [FAQINTERNAL:Thread-1398925664] [FAQINTERNAL:Level-3] INSERT INTO SYS.TB_TEST1 VALUES ( 1000001, , , , , , , , , 2014-08-28 13:00:09.960371 ); (TID : 35456) |
Cause
...
This error occurs when trying to acquire a lock on an object, but the object is already locked and the lock cannot be acquired.
...
- Occur when executing DDL
Generally, it is recommended to perform DDL in idle time. If the service is not stopped, X LOCK acquisition may fail instantaneously. If an error occurs, try performing DDL several times. If the same error still occurs, check whether the target table is busy or there is a long-run query (a query that takes a long time to execute or a query that has not been committed), and execute DDL again after taking action. - Occur when performing a change transaction in memory
If the above error occurs due to LOCK_ESCALATION_MEMORY_SIZE, there is a high possibility of a large amount of change transactions.
Make sure not to make a large number of change operations. It is recommended that the number of records to be changed is reduced by using conditional clauses and limit clauses and divided into multiple times to perform change transactions. - Occur when executing SELECT FOR UPDATE statement
Repeat the SELECT FOR UPDATE statement until it succeeds.
Find uncommitted transactions and commit or rollback.
Increase the time of the WAIT option. Occur in a replication environment
When designing for replication, consideration should be given to avoiding simultaneous changes on both servers for the same record.
When this error occurs, it may cause a problem with the data integrity of both servers, so the data must be checked.
Reference
...
...