TT-03233
Failed to wait for a SQL command to complete that was not compiled in write concurrency mode mode
Cause
The ttDbWriteConcurrencyModeSet built-in procedure could not acquire a lock. A common cause for this is that there is a long running SQL statement.
Action
Use the ttXactAdmin utility to check if there is SQL statement blocking the lock acquisition for the ttDbWriteConcurencyModeSet built-in procedure. If there is a SQL statement blocking the lock acquisition, wait for the SQL statement to finish executing. Alternatively, consider terminating the SQL statement. For more information about using the ttXactAdmin utility, see Using the ttXactAdmin utility in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
Additional Information
The enhanced write concurrency mode transition started and will continue until all SQL statements in transition are executed. The ttDbWriteConcurencyModeSet built-in procedure cannot wait because it could not acquire a lock.
TT-03233
Failed to wait for a SQL command to complete that was not compiled in write concurrency mode mode
Cause
The ttDbWriteConcurrencyModeSet built-in procedure could not acquire a lock. A common cause for this is that there is a long running SQL statement.
Action
Use the ttXactAdmin utility to check if there is SQL statement blocking the lock acquisition for the ttDbWriteConcurencyModeSet built-in procedure. If there is a SQL statement blocking the lock acquisition, wait for the SQL statement to finish executing. Alternatively, consider terminating the SQL statement. For more information about using the ttXactAdmin utility, see Using the ttXactAdmin utility in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
Additional Information
The enhanced write concurrency mode transition started and will continue until all SQL statements in transition are executed. The ttDbWriteConcurencyModeSet built-in procedure cannot wait because it could not acquire a lock.
TT-03233
Failed to wait for a SQL command to complete that was not compiled in write concurrency mode mode
Cause
The ttDbWriteConcurrencyModeSet built-in procedure could not acquire a lock. A common cause for this is that there is a long running SQL statement.
Action
Use the ttXactAdmin utility to check if there is SQL statement blocking the lock acquisition for the ttDbWriteConcurencyModeSet built-in procedure. If there is a SQL statement blocking the lock acquisition, wait for the SQL statement to finish executing. Alternatively, consider terminating the SQL statement. For more information about using the ttXactAdmin utility, see Using the ttXactAdmin utility in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
Additional Information
The enhanced write concurrency mode transition started and will continue until all SQL statements in transition are executed. The ttDbWriteConcurencyModeSet built-in procedure cannot wait because it could not acquire a lock.
