Re: Import failure

I had a similar situation.

Follow these steps:

1. Identify the rollback segments "RBS" tablespace(R01,R02....).
2. set the maximum extents for a particular rollback segment(R01,R02...) large enough(249 or higher.....depends on your requirement)
3. use the following command to set the rollback segment for the transaction. SET TRANSACTION USE ROLLBACK SEGMENT R02 ONLINE;
4. Then run the import. It should use the specified rollback segment with larger extent provided no other transaction is using that segment.

Let me know if this helped,
Chinna

Tim Witort <trwNOSPAM_at_NOSPAMmedicalert.org> wrote in article <340C48D0.1E71_at_NOSPAMmedicalert.org>...
> Oscar Ssentoogo wrote:
> >
> > Hi
> >
> > When importing a large text data file using SqlLdr, after about 35000
> > records (total 550000) there is a failure. Maximum Extents reached.
> >
> > How do I configure the database table to allow many more records to be
> > imported at a go. The table size should be able to accommodate upto
 about
> > 5 million records.
> > What are the most efficient storage parameters for such a table,
> > i.e. min / maxextents /next, tablespace size etc.
>
> If the extent failure is on your rollbacks,
> there is an import option to do periodic commits. This will
> allow the largest imports to work even with normal sized
> rollbacks.
>
> If the failure is on the table being imported, you need to
> size it correctly. There is a section in the Oracle Server
> Administrator's Guide on calculating table sizes. I also
> have a DOS program that will do it too if you're interested.
>
> -- TRW
> --
> |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> | Tim Witort || He is not silent. He is not |
> | trwATmedicalertDOTorg || whispering. We are not quiet |
> | || we are not listening. |
> | Pin: TZ, only one :^( || - Out of the Grey |
> |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>
  Received on Mon Sep 15 1997 - 00:00:00 CDT