I created a procedure to remove up to 2.4 million records out of a 13+ million record table with bulk binds and forall. Figured that would be the fastest way. While doing this delete, other processes were accessing the table, but not the rows that were being deleted. Things went fine.
Eventually, records that were being deleted were being updated, then the probelms started. The job that did the big delete was killed in favor of deleteing the records in smaller batches. However, whenever I try to delete or update some of the records that were affected, the process hangs, like it's waiting on a commit or rollback from a previous transaction. I have bounced the db and this is still occuring. Is there a way to check if the blocks are indeed waiting for a commit or rollback and provide that as needed? Thank you -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
