RE: implied run and commit on dbms_job
- From: "Singer, Phillip (P.W.)" <psinger1@xxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 9 Feb 2005 07:00:21 -0500
>=20
>Does anyone know of a document stating/mentioning the implied
>dbms_job.RUN that is called by oracle for a job when the time=20
>is reached
>for the job on the queue.
>=20
>This is because our developer only realized now that there is=20
>an implied
>commit on the dbms_job.run when the procedure/package called is not
>autonomous as stated in NOTE: 61730.1 on metalink.
>=20
>They are not believing us that oracle just calls dbms_job.run(job
>number) at the requested time and this has a build in commit they never
>considered before.
>=20
>Was discovered when they asked us to kill a job and was horrified to
>find that the work done in the job was commited.
>George
>=20
We had a job which ran just fine on a Sequent (NUMA-Q) using version
8.1.7. Then we migrated to 9.2.0 on Linux, and it had frequent
problems. We fixed it by making sure the job did an explicit commit no
matter what (originally, it was possible to find a branch with no
commit). This has led me to believe that the actual behavior is version
and platform dependent.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
