Oracle cursor help


I have a few Oracle tables that have gotten way too big.  Normal
DELETE/WHERE clauses consume too many resources.  I know enough
to know that cursors would be more efficient here but I don't
know enough to actually start using them.  Does anyone have an
example or two (or three) to bootstrap me?  What I'd essentially
want to do is loop through all rows, look at a few column settings,
and delete those that fall into certain categories (e.g., certain
dates being so old and certain status fields not being set to a
set value, etc.).  I can also limit the row set up front with a
pretty simple WHERE clause -- whatever is more efficient is what
I'm aiming for (it wasn't clear to me if limiting up front with
WHERE clauses defeated the efficiency of cursors ...)

--
Steve Sapovits  steves06@xxxxxxxxxxx
.

Relevant Pages

  • Re: Oracle cursor help
    ... DELETE/WHERE clauses consume too many resources. ... I can also limit the row set up front with a pretty simple WHERE clause -- whatever is more efficient is what I'm aiming for (it wasn't clear to me if limiting up front with WHERE clauses defeated the efficiency of cursors ...) ... Can you work with the parallel options (Oracle Enterprise Edition)? ...
    (perl.dbi.users)
  • Re: thread death callback to be called after fork
    ... Finalizers don't seem right--you have to manage them separately from the normal code to close resources, which is typically in ensure clauses. ... You might want some of the threads to survive into the fork. ... There probably isn't a pure ruby way to hack this in, because the threads are already dead in the fork as soon as the fork starts executing ruby code. ...
    (comp.lang.ruby)