| Table of Contents |
|---|
What is this error?
| Code Block |
|---|
Session-1 iSQL> AUTOCOMMIT OFF; iSQL> UPDATE T1 SET C1 = C1 + 1; Session-2 iSQL> DROP INDEX IDX33; (IDX33 is relate with T1 table) [ERR-11075 : The transaction exceeds lock timeout specified by user.] |
This error occurs when a session executing a DDL tries to put a lock on a table is already locked by other session.
This error can also occur when a replication transaction tries to put a lock on a table that is already locked by a local transaction. (In this case, you can find the error message in $ALTIBASE_HOME/trc/altibase_rp.log)
How to confirm this condition?
Users will need to validate to make sure that in fact there is a lock on the target table by another session.
To learn more about how to check session conditions, please review this content.
How to resolve this case?
There are two ways to resolve this problem.
First, terminate session that has a lock on the target table. (See this page.)
Second option is simply to wait for a while. Lock can be unlocked when users explicitly execute a commit or rollback.