Database Administration (MOSC)

MOSC Banner

Commit in pl/sql procedure returning control too soon?

edited Jan 9, 2014 10:37AM in Database Administration (MOSC) 7 commentsAnswered ✓
 Hi, I have DEV DBA, who wrote a pl/sql stored procedure that contains 

FOR 
    inserts into a single table (inserts a list of school id's)
LOOP 
COMMIT;
dbms_scheduler.create_program...
dbms_scheduler.DEFINE_PROGRAM_ARGUMENT...
DBMS_SCHEDULER.create_job...  --creates and runs a job that does stuff to each school id in the list that was inserted in the table in the above for loop

However, the DEV DBA says that the job is working for all the schools except for the first one.  They think that the commit is in the background and the procedure control continued on and created and executed the job before the commit finished, thereby missing the first school.  This behavior only seems to happen with large data on an under-powered box (its under stress). But, still, the commit should completely finish before continuing in the code - right?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center