Hi,
We have 3 jobs and in all 3 jobs target table is same. After successfully finished of each job, one record will insert in target table. Means total 3 records. But 3 jobs are different. Is there any possibility of locking the table while inserting 3 records at a time from 3 jobs.
please suggest!
Table Locking in Oracle
Moderators: chulett, rschirm, roy
Table Locking in Oracle
Kiran Kumar
...ALL IS WELL...
...ALL IS WELL...
Re: Table Locking in Oracle
I am confused.
All 3 jobs have the same target table. After each finishes you want to insert one record into the target table. Are these the same target table? Do the jobs already insert data into the target table when they are running?
What is the requirement to lock the table? Is this lock designed to stop something else happening at the same time?
Have you considered performing the insert through a package that controls the locking?
All 3 jobs have the same target table. After each finishes you want to insert one record into the target table. Are these the same target table? Do the jobs already insert data into the target table when they are running?
What is the requirement to lock the table? Is this lock designed to stop something else happening at the same time?
Have you considered performing the insert through a package that controls the locking?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
What I'm reading is a desire to take a table level lock for the duration of all three jobs running. Basically, the answer is no, because the three jobs will use separate connections (separate database user numbers), and they can't all own the same lock.
If you want to build transactions of this kind you need all the logic in one job.
If you want to build transactions of this kind you need all the logic in one job.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.