Alex,
Thanks. I am on 8.1.7.4. So it is not automatic UNDO. I already split
thequery in two. Right now the question is if I should use temporary/permanent
table or PL/SQL table. I assume PL/SQL table will always be faster than
temporary table. We have dedicated server so I think it is using memory from
main memory and not affecting SGA. How do I keep track of how much memory is
being used? I want balance performance and memory. to make sure no
paging/swapping occurs. Thanks
Alex Gorbachev <gorbyx@xxxxxxxxx> wrote:
How do you know you was running out of space in rollback segment? ORA-1555?
Usually, SELECT fails with ORA-1555 not because rollback segment is
too small but because your undo retention period is too small. I
assume you use automatic undo management.
2006/7/5, A Joshi :
>
> Hi,
> I had a big query which was running out of rollback so after some tuning
> i had to break it down in to two. from the first query i store the result in
> a temporary table and then use it for second part. it is still slow. i did
> not use permament table since that could involve rollback/redo. but still i
> will try to check it. i am also thinking of pl/sql table but if that always
> remains in memory then it could impact memory or sga. pl/sql table uses pga
> or OS memory but if paging swapping occurs then it would impact sga too.
> Will it always be faster than temp or permanent table? Can some one give
> feedback if you had similar experience. Thanks for help.
>
>
> ________________________________
> Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates
> starting at 1¢/min.
>
>
--
Best regards,
Alex Gorbachev
http://blog.oracloid.com
---------------------------------
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates
starting at 1¢/min.
