GAURAVGUPTA9
13th November 2002, 10:46
hi all
i am facing a problem of database errors. i want to ask how can we know the maximum size of rollback segment for a database require.
wot is its criteria?
regards
Gaurav
Djie-En
13th November 2002, 11:00
Hi,
What kind and version of database are you using?
And what kind of error?
GN
GAURAVGUPTA9
13th November 2002, 11:24
hi
we are using oracle 8i and the error no is ORA1555. rollback segment error. i have got the rollback segment doubled. but still i am getting the same error.
Regards
Gaurav
patvdv
13th November 2002, 11:51
It's very hard to judge the required size of a rollback segment for a busy process. A much better approach is to make sure you run this process off-peak hours, preferably with no users connected. We have discussed this issue several times before so please do a search for old threads on the same topic.
Djie-En
13th November 2002, 11:52
Hi,
Our oracle-version is 8.1.7: We created a tablespacesize of 5 Gb. for RBS. We made 8 RollBackSegments of 250 Mb./each Optimal size. So there is space of about 3 Gb. for extents. The RollBackSegments will autom. shrink to 250 Mb.
But we have faced problems with some sessions, which created an error 1555. After Baan had reprogrammed them, the error did not occur anymore. So it maybe the session which is not programmed well.
GN
NPRao
13th November 2002, 23:31
Gaurav,
Please refer to the thread you started on this topic sometime ago -
error 2555 (very urgent) (http://www.baanboard.com/baanboard/showthread.php?s=&threadid=5943&highlight=prepared)
Do you have any more specific Q on this topic for others to understand the issue ?
victor_cleto
14th November 2002, 18:56
Gaurav, what is your current SP level and Baan version?
For BaanIV, in between SP4 and SP6 (can't remember exactly) Baan did a major change in several sessions to fix ora 1555 by implementing commits for each hundred rows or so.
Before you make a global change by starting to increase your rolback segs., check the session solutions in the Baan support website, this may be a specific [bad] coding problem.