not enough rollback segment

[admin]

Xiong,

Heres the steps forwarded by our DBAs:

1. Take problem rollback segments offline (not SYSTEM rollback segment). 2. Drop the tablespace containing problem RBS. 3. Recreate the tablespace. 4. Recreate all the RBS and keep them of the same size. If need be increase the INTIAL_EXTENT, NEXT_EXTENT and MAX_EXTENT parameters. 5. Put them on line.


----- Forwarded by Nowell Henry/NYLIC on 08/07/01 10:16 AM -----
|--------+----------------------->
| | "Li, Xiong |
| | (Corporate |
| | Manukau)" |
| | |
| | |
| | 08/06/01 |
| | 05:54 PM |
| | Please |
| | respond to |
| | datastage-use|
| | rs |
| | |
|--------+----------------------->
>---------------------------------------------------------------------------|
| |
| To: "datastage-users@oliver.com" |
| cc: |
| Subject: not enough rollback segment |
>---------------------------------------------------------------------------|




Hi, all

My overnight job aborted last week along with the message:

ProcessFSEBITClassification.CLARITY: ORA-01555: snapshot too old: rollback segment number 6 with name "RBS5" too small.

It seems that the rollback segment is not enough, my oracle DBA thought The RBS are large enough for an OLTP system along with the amount of RBS. So I changed ORAOCI8 stage "Transaction Size" from 2000 to 100, then it worked OK.

This morning, it aborted again, with the same problem. What can I do now? reduce Transaction Size again, or add more rollback segment? Can anybody give me a recommendation?

Thanks in advance

Xiong

DISCLAIMER: This electronic message together with any attachments is confidential. If you are not the intended recipient, do not copy, disclose or use the contents in any way. Please also advise us by return e-mail that you have received the message and then please destroy. Carter Holt Harvey is not responsible for any changes made to this message and / or any attachments after sending by Carter Holt Harvey. We use virus scanning software but exclude all liability for viruses or anything similar in this email or any attachment.