dbms_lock usage
Want to use dbms_lock as a semaphore to sequence processing across a cluster of Web Logic application servers. Each transaction will have a non-unique key that will be used as the lock handle name, so there will be alot of different handle names being locked. The lock will allow transactions with the same key to be processed in a FIFO order since dbms_lock is a FIFO locking mechanism. What considerations should be taken to ensure that the database is not harmed using this approach (creating alot of handle names - about 2 million per day or 83,000 per hour)? Are
0