How to avoid Lock time-out occurs when different applications access the same table in database with different operations simultaneously? For example, unload and other DML operations occur simultaneously. (DBMR2123)

~ 0 min
2016-03-09 10:49

Locks are required for concurrency control between multiple transactions on the same database objects. Lock time-out will be occurring when multiple users access to one database objects simultaneously. Although it’s normal behavior, in order to ensure the consistency of the data in database. However, we still need the simultaneous access requirements can be met in some special conditions. But how to handle the specific requirements? Differnt needs have different handle methods mainly according to practical problems.

Below we make DBMR2123 as an example to elaborate:

When customer unloads data from table test, another application programs operate the same table test (delete, insert etc) at the meantime, Lock time-out will be occur. In order to avoid Lock time-out occur we can use the temporary table as a workaround.

Detailed operation as follows

Select * from test into temp_test;

Unload data from (select * from temp_test) to test_file;

It doesn’t influence the original table performance but need extend the deftablespace because temporary table regular specified on deftablespace currently.

 

Version: DBMaker 4.x\5.x DBMaker4.x\5.x

Product: Normal

Platform: Windows xp

Average rating 0 (0 Votes)

You cannot comment on this entry

Tags