Re: Error Loading with HPL
Hi
Thanks to all who answered. Yes Sir, I were blind. One of the dbspaces of
the fragmentation strategy filled up. And HPL doesn't use the remainder,
fortunately.
Reinhard.
> -----Ursprüngliche Nachricht-----
> Von: Bogdan BOTEZ [mailto:bmbogdan@gmail.com]
> Gesendet am: Montag, 3. März 2008 08:46
> An: Habichtsberg, Reinhard
> Betreff: Re: Error Loading with HPL
>
> On Mon, Mar 3, 2008 at 9:29 AM, Habichtsberg, Reinhard
> <RHabichtsberg@arz-emmendingen.de> wrote:
> > Hi
> >
> > Solaris 10
> > IDS 9.40FC9W2
> >
> > we have to migrate some rather big tables (about
> 800.000.000 rows) from one
> > server to another. We unload the tables with HPL in flat
> files, copy them to
> > the other server and load them with HPL.
> >
> > The tables are fragmented. The table structure is
> identical on both servers.
> >
> > No problems occured with one of the tables, although even
> bigger. With
> > another the load alwway stopped with the messages:
> >
> > Fatal error getting stream buffer from server
> > Fatal error in server row processing - SQL error -271 ISAM
> error -131> >
> > Database Load Completed -- Processed 76156665 Records
> > Records Inserted-> 0
> > Detected Errors--> 0
> > Engine Rejected--> 0
> >
> > Repeating unload and copy had no effect.
> >
> > Since it's urgent to load the tables any help is highly
> appreciated.
> >
> > Reinhard.
>
> -271 Could not insert new row into the table.
>
> This problem has many possible causes, including a locked table or a
> full disk. Check the accompanying ISAM error code for more
> information.
>
>
> -131 ISAM error: no free disk space.
>
> Not enough contiguous free disk space is available to complete the
> current operation. For C-ISAM programs, if transaction logging is in
> use, roll back the current transaction. Make some disk space
> available,
> and run the program again. For SQL products, roll back the current
> transaction, if possible. Contact the system administrator about
> acquiring more disk space for databases.
>
>
> Probably related to extent management - did you moved the
> schema definition
> including adjusted extent size next size?
>
> Temporary dbspaces ok?
>
> Regards,
> Bogdan BOTEZ.
>