| Optimisation of SQL [message #374778] |
Sat, 30 June 2001 14:39  |
neil mcbride
Messages: 1
Registered: June 2001
|
Junior Member |
|
|
What is the easiest method of tuning SQL so that it does not hit 'rollback segment' and 'snapshot too old' errors?
I am a heavy end-user of SQL without full DBA capabilities that cannot rely on prompt results from our own DBA's.
|
|
|
|
| Re: Optimisation of SQL [message #374808 is a reply to message #374778] |
Tue, 03 July 2001 18:55  |
andrew again
Messages: 2577
Registered: March 2000
|
Senior Member |
|
|
This message occurs when transactions taking place at the same time as your query (and which have priority over your queries) use all the space in the rollback segment. This means that you don't know when you'll hit the problem.
Get other users to commit/rollback frequently if they have large transactions.
Make your queries more efficient to get them completed quicker (add indexes?, optimize SQL).
Even if you on 8i, the following should help:
http://www.dlcwest.com/~jed/fastoracle/tuning_guidelines.shtml
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
