| Oracle Scheduler locks packages [message #316816] |
Mon, 28 April 2008 07:53  |
yamon
Messages: 22
Registered: July 2006
|
Junior Member |
|
|
I am moving Windows schedules into Oracle Scheduler and created the new procedures in a package, to keep the procedures together. I have noticed that when a procedure in the package is running via the scheduler, I cannot alter any of the other procedures in the package, as the package appears to be locked.
Therefore, for large procedures, is it recommended that all scheduler rocedures be stand alone procedures? And therefore, if the old Windows schedules (batch files calling sql scripts) reference packaged procedures, do these packaged procedures need to be re-created as stand-alone procedures?
Thanks,
Yamon
|
|
|
|
| Re: Oracle Scheduler locks packages [message #316859 is a reply to message #316816] |
Mon, 28 April 2008 10:49  |
ThomasG
Messages: 3212
Registered: April 2005
Location: Heilbronn, Germany
|
Senior Member |
|
|
The real question here is: Why are you changing the packages all the time?
There should only be a need to change packages during upgrades of the application, when jobs shouldn't be running anyway.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
