'dbms_lock.allocate_unique'
Hi,
My customer plans to make use of the 'dbms_lock' package to manually apply locks to certain tables. Unfortunately, when he uses the 'allocate_unique' procedure to associate a number (handle) with the named lock he does not know how long he will need that lock for. He therefore sets parameter 'expiration_specs' to a large number.
Subsequently, when he has finished with that lock, he calls 'dbms_lock.allocate_unique' with the same lock name but setting parameter 'expiration_specs' to 0. This seems to have the effect of disassociating the generated number from the lock name, thus enabling the normal mechanism to tidy up the 'dbms_lock_allocated' table, but I have 2 questions:
My customer plans to make use of the 'dbms_lock' package to manually apply locks to certain tables. Unfortunately, when he uses the 'allocate_unique' procedure to associate a number (handle) with the named lock he does not know how long he will need that lock for. He therefore sets parameter 'expiration_specs' to a large number.
Subsequently, when he has finished with that lock, he calls 'dbms_lock.allocate_unique' with the same lock name but setting parameter 'expiration_specs' to 0. This seems to have the effect of disassociating the generated number from the lock name, thus enabling the normal mechanism to tidy up the 'dbms_lock_allocated' table, but I have 2 questions:
0