Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

DBMS_SCHEDULER.CREATE_JOB Remove Implicit Commit

gdanbyJun 2 2016

There should be an option when creating a DBMS Scheduler job to create this as part of the transaction, so it can be rolled back if the transaction fails. DBMS_JOB worked like this and DBMS_SCHEDULER is so much better, except it's not transactional. I know there are workarounds, but these feel a bit messy. It makes migrating from DBMS_JOB to DBMS_SCHEDULER a harder task than it should be.

Comments

Klibby-Oracle
Hi Julie,

Per Oracle Client/Server interoperability the Oracle Client has to be at a minimum of 9.2.0.4 or higher to connect to an 11.2 RDBMS. Understand however that 9.2 has not been desupported for error correction for a while so if you run into new issues after upgrading to the 9.2.0.8 terminal patches the only other suggestion is to upgrade to 11g preferably 11.2.0.3

Edited by: klibby on May 1, 2012 11:53 AM
Julie Treger-Oracle
Thanks for the quick response!

Regards,
Julie
1 - 2

Post Details

Added on Jun 2 2016
38 comments
8,216 views