ROLLBACK SEGMENT ERROR

loveojha2 · Post by **loveojha2** » Thu Dec 22, 2005 11:49 pm

Are you using transaction size as 0 for target (Oracle).
Moreover you need not change Siebel, it's the problem with Oracle rollback segment.
Solns:

1. Increase the rollback segment size.
or
2. Experiment with transaction size other than 0 (but here you would need to be a bit careful since specifying transaction size means specifying commit frequency).

ray.wurlod · Post by **ray.wurlod** » Fri Dec 23, 2005 12:07 am

I think you'll find that the Oracle DBA has privilege to do ANYTHING - that's the definition of a DBA!

Bala R · Post by **Bala R** » Fri Dec 23, 2005 1:06 am

If your DBA still couldn't help you, then you could consider splitting your load into smaller segments. Load the data into sequential files and then you could bulk load them into Oracle. Thus overcoming the rollback segment constraints. If you think that would be useful search for posts by kcbland on this topic.
HTH

Poornagirija · Post by **Poornagirija** » Fri Dec 23, 2005 5:40 am

HI FOLKS,

We are using transaction size of 5000 but thats for commit rt?

Now we are discussing that with our DBA.

Hope the best.

Anyway thanks for your suggestion.

With regards,
Poornagirija.

chulett · Post by **chulett** » Fri Dec 23, 2005 7:56 am

Poornagirija wrote:We are using transaction size of 5000 but thats for commit rt?

Yes, but with a great big CAVEAT.

Make sure you are not using the 'Transaction Size' box on the General tab on the Input of the OCI stage, that's just there for 'backwards compatability' and to confuse people. It is ignored.

Check the value in the 'Transaction Handling' tab on the stage where it says 'Rows per transaction' - that one is the real one and the one that is your commit level. That's probably still at the default of zero.