Problem with Oracle Rollback Segment Session I am facing a problem in Oracle, which after performing a procedure that performs INSERT or UPDATE with a millions amount of record in a table, not the next procedure "sees" the data in the table already inserted. My procedure is scheduled to perform commit 100 thousand lines. I also use cursors with bulk collection. 

I suspect the problem may be due to the area Rollback segment of the Session of Oracle, anyone know if there is any DML command to clear the area or give a flush on Rollback segment?
I suspect you're using multiple sessions and the other session cannot "see" the work performed because it is currently uncommitted.

The default Oracle transaction Isolation Level is Read Committed. This means that a  session will not be able to see the work a given session has done until it has explicitly committed the transaction. 

The Oracle Server Concepts Guide explains this in detail.