Rollback segment too small error [message #415525] |
Tue, 28 July 2009 03:25 |
deepbans
Messages: 32 Registered: February 2009
|
Member |
|
|
HI,
I am running a SQL query which contains n number of join including 2-3 outer join.Almost all the tables in my query are transactional table.
At the time query executes,The records in the tables are updated and SCN number of the records is changed and its also not available in the rollback segments.Then,its throwing ORA-01555
rollback segment too small error.
We have tuned the query from our side and we cant modify anything from DBA side part
Can you please suggest something to overcome this error?
Thanks & Regards.
|
|
|
|
Re: Rollback segment too small error [message #415541 is a reply to message #415532] |
Tue, 28 July 2009 03:43 |
deepbans
Messages: 32 Registered: February 2009
|
Member |
|
|
Thanks.
1.we are not putting anything in loop.
2.Sometime data is very huge.Can we opt for global temporary table.
But I think there will be chances of occurrence of error at the time of insertion in table. Is there anything through which we can skip that record or data block which is causing issue.
3.Can you pls explain little how order by clause going to help in this?
Regards.
|
|
|
|
Re: Rollback segment too small error [message #415545 is a reply to message #415544] |
Tue, 28 July 2009 03:56 |
deepbans
Messages: 32 Registered: February 2009
|
Member |
|
|
1.Can you please tell me how can we skip particular record in a query and directly fetch the record succeeding that record.
2.our record size is very high sometime its more than 10 MB.
and "order by" will reduce the performance.
Regards,
Deepa
|
|
|
|
|
|
Re: Rollback segment too small error [message #415650 is a reply to message #415525] |
Tue, 28 July 2009 09:23 |
|
BlackSwan
Messages: 26766 Registered: January 2009 Location: SoCal
|
Senior Member |
|
|
>But we dont know which records are causing issue.
The SQL reporting the ORA-01555 error is the victim, not culprit.
The root cause of the problem is some other session is doing DML against same table as victim SQL & also doing COMMIT.
Possible solutions include
1) do not do DML while victim query runs
2) do not do COMMIT until after victim SQL completes
3) make RBS larger (no guarentee this always works)
visit http://asktom.oracle.com & do KEYWORD search on ORA-01555
[Updated on: Tue, 28 July 2009 09:24] Report message to a moderator
|
|
|
|