Oracle 10G Commit Not Visible

Question

I have a commit or concurrency issue I hope someone can shed some light on.
I'm building rows in a reporting table via several stored procedures and reporting on the results.
The final stored procedure uses the rows built by the initial stored procedures and occasionally, the rows initially created are not visible to the final stored procedure.
Is there a way to force Oracle to COMMIT the rows and WAIT so there are 100% visible to subsequent stored proccedures?
Thanks. (Oracle DB 10.2.0.3.0 Client 11.2.0.2)
In summary -
1> Proc #1 runs and builds summary rows
2> Proc #2 runs and builds summary rows
3> proc #3 runs and builds summary rows
4> proc #4 then does some totals on the results of the first 3 procs.
Sometimes the results of the first procs are not visible to proc#4 when it runs.
I have explicit commits at the end of the stored procedures. In theory I (or anyone else) should be able to see the results of each stored procedures as it runs but sometimes they are not. I have actually seen this happen by monitoring the rows in the reporting table coupled with DBMS_OUTPUT from the stored procs.
The reporting table can be active, accessed simultaneously by a 20? users at a time. It does seem timing sensitive, when I add some wait time in the app before calling each stored proc the number occurrences where rows are not found decrease. Similarly, when the numbers of users decrease the number of occurrences decrease.
proc1 summary_labor
cursor proc_cursor1 is select * from table1;
For c_row1 in proc1
Do some calculations
Insert a summary row into reporting table
end; -- For
COMMIT;
End Proc1

Answer 1

user7313584 wrote:
I have a commit or concurrency issue I hope someone can shed some light on.
I'm building rows in a reporting table via several stored procedures and reporting on the results.
The final stored procedure uses the rows built by the initial stored procedures and occasionally, the rows initially created are not visible to the final stored procedure.
Is there a way to force Oracle to COMMIT the rows and WAIT so there are 100% visible to subsequent stored proccedures?
Thanks. (Oracle DB 10.2.0.3.0 Client 11.2.0.2)
In summary -
1> Proc #1 runs and builds summary rows
2> Proc #2 runs and builds summary rows
3> proc #3 runs and builds summary rows
4> proc #4 then does some totals on the results of the first 3 procs.
Sometimes the results of the first procs are not visible to proc#4 when it runs.
I have explicit commits at the end of the stored procedures. In theory I (or anyone else) should be able to see the results of each stored procedures as it runs but sometimes they are not. I have actually seen this happen by monitoring the rows in the reporting table coupled with DBMS_OUTPUT from the stored procs.
The reporting table can be active, accessed simultaneously by a 20? users at a time. It does seem timing sensitive, when I add some wait time in the app before calling each stored proc the number occurrences where rows are not found decrease. Similarly, when the numbers of users decrease the number of occurrences decrease.So procedure 4 is dependant on the completion of procedures 1 thru 3. So what is causing procedure 4 to run before those others have completed? You need to ensure it doesn't run until such a time.
proc1 summary_labor
cursor proc_cursor1 is select * from table1;
For c_row1 in proc1
Do some calculations
Insert a summary row into reporting table
end; -- For
COMMIT;
End Proc1Horrible code.
Use a single INSERT ... SELECT ... statement to avoid context switching which is inevitably causing the code to run slowly.