Re: SQL*Loader rollback probs

Thanks for the suggestion, but this didn't work. It said that the bind size had to be at least 356 because that is the size of the bind array in bytes, not the number of records. I tried ROW=1, too and DIRECT=TRUE. That didn't work, either.
Thank you again,
Pam

Madhu Cherukuri wrote:
>
> Did you try with BINDSIZE parameter with the sqlload command?
> This can specify how much of data is commite after insert.
> Try specifying BINDSIZE=(low value may be 5 or 10)
> If u still get the error go with the least 1. this means it will commit
> after each record. For more info on BINDSIZE, refer to
> Oracle7 Server Utilities reference manual
> HTH
>
> Madhu Cherukuri <Madhu.Cherukuri_at_worldnet.att.net>
>
> Pam Richmond wrote in message <34CE1AEE.533A_at_cat.com>...
> >I have been using SQL*Loader to successfully import fixed-width flat
> >file data into an Oracle database. We modified the data recently, and
> >some blank fields were filled in with data. This seems to have caused
> >SQL*Loader to run out of storage for the rollback.
> >
> >I am using Personal Edition 7. The file is 11.5M. I'm using REPLACE
> >when I run SQL*Loader. I tried to change the maxextents, but it is
> >already set to 121, and it says I can't make it any larger than that.
> >
> >Following is the error:
> >926:Oci error while executing deleting (due to REPLACE keyword) from
> >table for table xyz
> >ORA-01562 failed to extend rollback segment (id=4)
> >ORA-01628 max # extents (121) reached for rollback segment RB3
> >
> >What can I do to fix this?
> >Thanks,
> >Pam Richmond
  Received on Thu Jan 29 1998 - 00:00:00 CST