Page 1 of 1
Posted: Wed Jul 20, 2005 10:44 pm
by ranga1970
I think this is an Database issue; Roll back segment problem arises when you are trying to commit large volumes of data, or Abort occured and you are trying roll back the data, contact your DBA and try to reduce your commit level
thanks
Posted: Wed Jul 20, 2005 10:55 pm
by pavithra_12
Hi,
we have also set the reduced the commit level but still the problem persist. Is there any way to design the server job to overcome this error.
Regards
Pavithra
Posted: Wed Jul 20, 2005 11:19 pm
by ranga1970
whats the commit level?
How about asking your DBA to Increase the RBS?
Whats the record size?
Posted: Thu Jul 21, 2005 12:57 am
by ray.wurlod
This is NOT a DataStage problem. Nor does it have anything to do with the fact that you're performing lookups to hashed files.
You are trying to send too large a transaction to Oracle.
Possible solutions are to have you Oracle DBA enlarge the rollback segment so that it can handle the size of transaction you are sending, or to send smaller transactions (smaller rows per transaction).
The rollback segment keeps the "before image" records, in case you elect to roll back the transaction. Discuss with your Oracle DBA.
Posted: Thu Jul 21, 2005 3:56 am
by pavithra_12
Hi,
Thanxs for the valuble suggestion. Please let me know whether including Link Partioner and Link Collector stages can this error can be over come.
or Is there any other way in creating a Server Job for the same that can split the huge volume of data and process the same and load it in to the data mart.
Regards
Pavithra