The short f it is that you lost 15hours.
There is no way to "relabel" these 4k page into 16k.

Cheers
Serge


"Harish Reddy V. "
<db2udbdba-ezmlmshield-x57649109.[Email address protected] wrote on
02/27/2006 03:45:06 AM:

>
>
> Hi,
>
>
>
> I am in tricky situation now. Yesterday I have started loading data into
> one of the tables in our test DB. Loading activity has run for almost 15
> hours and loaded 512 million rows (suppose to load total of 525 million
> rows) and stopped throwing an error as below
>
>
>
> SQL0659N Maximum size of a table object has been exceeded.
> SQLSTATE=54032
>
>
>
> SQL2038N A database system error "-2044" occurred during processing.
>
>
>
> SQL3532I The Load utility is currently in the "LOAD" phase.
>
>
>
> Upon checking the tablespace I could clearly see that , the tablepsace
> in this DB is 4KB pagesize where in the source from where I have
> exported data in 16 KB . This could be one of culprit for this error.
>
>
>
> I request you all to look into this and help me out resolving this.
>
>
>
> 1) Is it possible to move containers from 4KB tablespace to 16 KB
> tablespace . If so how ??
>
> 2) In case if I am able to move this container to another tablespace
> with enough size, is it possible to restart load activity from where it
> has got failed ??
>
>
>
> My Environment : DB2 8.1.6 on solaris
>
>
>
> Appreciate an early respone on this.
>
>
>
> Regards
>
> Harish
>
>
>
> ---------------------------------------------------------------------
> PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
> website: http://www.LazyDBA.com
> To unsubscribe: http://www.lazydba.com/unsubscribe.html
>


DB2 & UDB email list listserv db2-l LazyDBA home page