DBohner-(db)
Legendary Poster
Ugh,
I'm trying to find the pixie-dust to resolve all the problems with Mother of Earth... I feel like I am flailing...
9.0, Oracle 11g, Unix
I have this UBE that hangs at the end of the Initialize Section for an hour, then quickly races through the fifty-one records it pulls back...
I am schooled, I know that it is all Database Time - that dang Select Statement is Taking an Hour!
I re-submit the UBE with Logging turned on, after an hour I capture the SQL Statement and I switch gears, opening my SQL tool.
The first time I run the statement, exactly as copied from the log - it takes 45 minutes (fifteen minutes faster than the UBE). Each subsequent submission of the same SQL statement take only one of my life's breaths (I am short winded, can't you tell).
I run the UBE again - and it, again, takes an hour.
What the heck am I missing? I know there is an opportunity for a new index - but, shouldn't the blasted Oracle 'Optimizer' have figured that the EXACT same query keeps hitting the system? Why can I run it in under seconds through a query tool (Aqua) - while RUNUBE (as Oracle claims it) take an HOUR - EVERY TIME.
Where's the Magic Performance Button?
Suggestions (other than an iSeries, please)?
(db)
I'm trying to find the pixie-dust to resolve all the problems with Mother of Earth... I feel like I am flailing...
9.0, Oracle 11g, Unix
I have this UBE that hangs at the end of the Initialize Section for an hour, then quickly races through the fifty-one records it pulls back...
I am schooled, I know that it is all Database Time - that dang Select Statement is Taking an Hour!
I re-submit the UBE with Logging turned on, after an hour I capture the SQL Statement and I switch gears, opening my SQL tool.
The first time I run the statement, exactly as copied from the log - it takes 45 minutes (fifteen minutes faster than the UBE). Each subsequent submission of the same SQL statement take only one of my life's breaths (I am short winded, can't you tell).
I run the UBE again - and it, again, takes an hour.
What the heck am I missing? I know there is an opportunity for a new index - but, shouldn't the blasted Oracle 'Optimizer' have figured that the EXACT same query keeps hitting the system? Why can I run it in under seconds through a query tool (Aqua) - while RUNUBE (as Oracle claims it) take an HOUR - EVERY TIME.
Where's the Magic Performance Button?
Suggestions (other than an iSeries, please)?
(db)