Problem exporting data

I have a certain database. The data is allocated in a dbspace who needs about 8Gb. In this dbspace i have 4 chunks of 2Gb each one. I want to replicate this database in another disk. This database had a dbspace that has been erased. I have created another one (with the same name) and i have added 4 chunks of 2Gb each one. When i did the dbexport of the first one and did the dbimport... occurrs an error -131: not enough free space.... i have add another more chunk... and there is not problem. Someone knows why the same database needs about 2Gb more in each dbspace? thanks... and sorry for the mistakes... i cant speak a very good english.

do you have any triggers on the tables ? Is it inserting extra data as your loading the original ? On Tuesday 10 April 2007 12:33, Alberto Sánchez Bardanca wrote: > I have a certain database. The data is allocated in a dbspace who > needs about 8Gb. In this dbspace i have 4 chunks of 2Gb each one. I > want to replicate this database in another disk. This database had a > dbspace that has been erased. I have created another one (with the > same name) and i have added 4 chunks of 2Gb each one. > > When i did the dbexport of the first one and did the dbimport... > occurrs an error -131: not enough free space.... i have add another > more chunk... and there is not problem. > > Someone knows why the same database needs about 2Gb more in each > dbspace? thanks... and sorry for the mistakes... i cant speak a very > good english. > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list -- Mike Aubury Aubit Computing Ltd is registered in England and Wales, Number: 3112827 Registered Address : Murlain Business Centre, Union Street, Chester, CH1 1QP

On 10 abr, 13:59, Mike Aubury <i...@aubit.com> wrote: > do you have any triggers on the tables ? > Is it inserting extra data as your loading the original ? > > On Tuesday 10 April 2007 12:33,AlbertoSánchezBardanca wrote: > > > > > I have a certain database. The data is allocated in a dbspace who > > needs about 8Gb. In this dbspace i have 4 chunks of 2Gb each one. I > > want to replicate this database in another disk. This database had a > > dbspace that has been erased. I have created another one (with the > > same name) and i have added 4 chunks of 2Gb each one. > > > When i did the dbexport of the first one and did the dbimport... > > occurrs an error -131: not enough free space.... i have add another > > more chunk... and there is not problem. > > > Someone knows why the same database needs about 2Gb more in each > > dbspace? thanks... and sorry for the mistakes... i cant speak a very > > good english. > > > _______________________________________________ > > Informix-list mailing list > > Informix-l...@iiug.org > >http://www.iiug.org/mailman/listinfo/informix-list > > -- > Mike Aubury > > Aubit Computing Ltd is registered in England and Wales, Number: 3112827 > Registered Address : Murlain Business Centre, Union Street, Chester, CH1 1QP There's no tri triggers on the tables. It's not being inserted data while the loading.

Where are your logs? >From: "Alberto S'nchez Bardanca" <Bardanca@gmail.com> >To: informix-list@iiug.org >Subject: Re: Problem exporting data >Date: 10 Apr 2007 05:06:33 -0700 >MIME-Version: 1.0 >Received: from perform.iiug.org ([216.177.38.211]) by >bay0-mc1-f11.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Tue, >10 Apr 2007 05:11:14 -0700 >Received: from localhost (localhost [127.0.0.1])by perform.iiug.org >(Postfix) with ESMTP id 2FF69A104;Tue, 10 Apr 2007 08:10:42 -0400 (EDT) >Received: from perform.iiug.org ([127.0.0.1])by localhost (perform.iiug.org >[127.0.0.1]) (amavisd-new, port 10024)with ESMTP id e5rmScBPWjD0; Tue, 10 >Apr 2007 08:10:29 -0400 (EDT) >Received: by perform.iiug.org (Postfix, from userid 60001)id BADDFA180; >Tue, 10 Apr 2007 08:10:29 -0400 (EDT) >Received: from perform.iiug.org (localhost [127.0.0.1])by perform.iiug.org >(Postfix) with ESMTP id 7FEC6A15C;Tue, 10 Apr 2007 08:10:16 -0400 (EDT) >X-Message-Info: >LsUYwwHHNt3Xa+F4a5U3Sw3fMkIkWdZkWoev6nnCWuQvAVKeFIFwtIwbk0IXQS4p >X-Virus-Scanned: amavisd-new at iiug.org >Path: >nnrp.xmission!xmission!ucberkeley!news-hog.berkeley.edu!newshub.stanford.edu!postnews.google.com!q75g2000hsh.googlegroups.com!not-for-mail >Newsgroups: comp.databases.informix >Organization: http://groups.google.com >Lines: 37 >References: ><1176204820.438992.30980@y5g2000hsa.googlegroups.com><mailman.542.1176206434.10648.informix-list@iiug.org> >NNTP-Posting-Host: 194.140.82.250 >X-Trace: posting.google.com 1176206793 18038 127.0.0.1 (10 Apr 2007 >12:06:33GMT) >X-Complaints-To: groups-abuse@google.com >NNTP-Posting-Date: Tue, 10 Apr 2007 12:06:33 +0000 (UTC) >User-Agent: G2/1.0 >X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; >es-ES;rv:1.8.1.3) Gecko/20070309Firefox/2.0.0.3,gzip(gfe),gzip(gfe) >X-HTTP-Via: 1.1 rubicon:3128 (Squid/2.4.STABLE3) >Complaints-To: groups-abuse@google.com >Injection-Info: q75g2000hsh.googlegroups.com; >posting-host=194.140.82.250;posting-account=KIHrJQ0AAAC9jf4DKPUmxlNjpG5IKmEb >Xref: nnrp.xmission comp.databases.informix:196650 >X-BeenThere: informix-list@iiug.org >X-Mailman-Version: 2.1.6 >Precedence: list >List-Id: "comp.databases.informix" <informix-list.iiug.org> >List-Unsubscribe: ><http://www.iiug.org/mailman/listinfo/informix-list>,<mailto:informix-list-request@iiug.org?subject=unsubscribe>; >List-Archive: <http://www.iiug.org/pipermail/informix-list>; >List-Post: <mailto:informix-list@iiug.org> >List-Help: <mailto:informix-list-request@iiug.org?subject=help> >List-Subscribe: ><http://www.iiug.org/mailman/listinfo/informix-list>,<mailto:informix-list-request@iiug.org?subject=subscribe>; >Errors-To: informix-list-bounces@iiug.org >Return-Path: informix-list-bounces@iiug.org >X-OriginalArrivalTime: 10 Apr 2007 12:11:14.0717 (UTC) >FILETIME=[55F3C4D0:01C77B69] > >On 10 abr, 13:59, Mike Aubury <i...@aubit.com> wrote: > > do you have any triggers on the tables ? > > Is it inserting extra data as your loading the original ? > > > > On Tuesday 10 April 2007 12:33,AlbertoS'nchezBardanca wrote: > > > > > > > > > I have a certain database. The data is allocated in a dbspace who > > > needs about 8Gb. In this dbspace i have 4 chunks of 2Gb each one. I > > > want to replicate this database in another disk. This database had a > > > dbspace that has been erased. I have created another one (with the > > > same name) and i have added 4 chunks of 2Gb each one. > > > > > When i did the dbexport of the first one and did the dbimport... > > > occurrs an error -131: not enough free space.... i have add another > > > more chunk... and there is not problem. > > > > > Someone knows why the same database needs about 2Gb more in each > > > dbspace? thanks... and sorry for the mistakes... i cant speak a very > > > good english. > > > > > _______________________________________________ > > > Informix-list mailing list > > > Informix-l...@iiug.org > > >http://www.iiug.org/mailman/listinfo/informix-list > > > > -- > > Mike Aubury > > > > Aubit Computing Ltd is registered in England and Wales, Number: 3112827 > > Registered Address : Murlain Business Centre, Union Street, Chester, CH1 >1QP > >There's no tri triggers on the tables. >It's not being inserted data while the loading. > >_______________________________________________ >Informix-list mailing list >Informix-list@iiug.org >http://www.iiug.org/mailman/listinfo/informix-list _________________________________________________________________ Need a break? Find your escape route with Live Search Maps. http://maps.live.com/?icid=hmtag3

Alberto S'nchez Bardanca wrote: >I have a certain database. The data is allocated in a dbspace who >needs about 8Gb. In this dbspace i have 4 chunks of 2Gb each one. I >want to replicate this database in another disk. This database had a >dbspace that has been erased. I have created another one (with the >same name) and i have added 4 chunks of 2Gb each one. > >When i did the dbexport of the first one and did the dbimport... >occurrs an error -131: not enough free space.... i have add another >more chunk... and there is not problem. > >Someone knows why the same database needs about 2Gb more in each >dbspace? thanks... and sorry for the mistakes... i cant speak a very >good english. > >_______________________________________________ >Informix-list mailing list >Informix-list@iiug.org >http://www.iiug.org/mailman/listinfo/informix-list > > > > Check below parameters in your onconfig file: DBSPACETEMP >>> Did you setup any tmpdbs? DUMPDIR >>> Where the "/tmp" define here? and whats the available size of this file system?

Alberto Sánchez Bardanca написа: > I have a certain database. The data is allocated in a dbspace who > needs about 8Gb. In this dbspace i have 4 chunks of 2Gb each one. I > want to replicate this database in another disk. This database had a > dbspace that has been erased. I have created another one (with the > same name) and i have added 4 chunks of 2Gb each one. > > When i did the dbexport of the first one and did the dbimport... > occurrs an error -131: not enough free space.... i have add another > more chunk... and there is not problem. > > Someone knows why the same database needs about 2Gb more in each > dbspace? thanks... and sorry for the mistakes... i cant speak a very > good english. > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list > > > Hi to avoid that problem use dbexport with "-ss" option. Dimitar Bachvarov

> Hi > to avoid that problem use dbexport with "-ss" option. ok, i have listened that solution before, i did it. But... what is the problem, why could the database needs 2 more Gb ? >> DBSPACETEMP >>> Did you setup any tmpdbs? >> DUMPDIR >>> Where the "/tmp" define here? and whats the About tempdbs, the temp_dbs in the new place (the databases are located in different machines) is bigger than the older one. The DUMPDIR has the same configuration in both. The logs have about the same size in both (i have changed that at first) and are located in different dbspaces.... Thanks for all to everybody.

rather than inserting a row, i suspect the reason for the out of space error is probably occurring when the engine tries to add another extent and there is not enough space in the dbsapce to add the extent. if you use the -ss option you should pick up the extent sizes of your current database which should resolve this issue. On Apr 10, 3:23 pm, "Alberto Sánchez Bardanca" <Barda...@gmail.com> wrote: > > Hi > > to avoid that problem use dbexport with "-ss" option. > > ok, i have listened that solution before, i did it. But... what is the > problem, why could the database needs 2 more Gb ? > > >> DBSPACETEMP >>> Did you setup any tmpdbs? > >> DUMPDIR >>> Where the "/tmp" define here? and whats the > > About tempdbs, the temp_dbs in the new place (the databases are > located in different machines) is bigger than the older one. The > DUMPDIR has the same configuration in both. > > The logs have about the same size in both (i have changed that at > first) and are located in different dbspaces.... > > Thanks for all to everybody.

Alberto S'nchez Bardanca wrote: >> Hi >> to avoid that problem use dbexport with "-ss" option. > ok, i have listened that solution before, i did it. But... what is the > problem, why could the database needs 2 more Gb ? > > >>> DBSPACETEMP >>> Did you setup any tmpdbs? >>> DUMPDIR >>> Where the "/tmp" define here? and whats the > About tempdbs, the temp_dbs in the new place (the databases are > located in different machines) is bigger than the older one. The > DUMPDIR has the same configuration in both. > > The logs have about the same size in both (i have changed that at > first) and are located in different dbspaces.... > > Thanks for all to everybody. > Several IDS versions ago data and indexes were always placed in the same tablespace - they shared the same extents. In the later versions of IDS you can control whether index should be in its own tablespace (called a detached index) or share the tablespace with the table data. Modern versions of IDS creates detached indexes as default. Since tablespaces grow in extent size, you will typically get a larger overhead with detached indexes. My guess is that the old table has attached indexes and the copy has detached indexes. Use oncheck or sysmaster database to find out how the two tables and indexes are created.

Alberto Sánchez Bardanca написа: >> Hi >> to avoid that problem use dbexport with "-ss" option. >> > ok, i have listened that solution before, i did it. But... what is the > problem, why could the database needs 2 more Gb ? > > > >>> DBSPACETEMP >>> Did you setup any tmpdbs? >>> DUMPDIR >>> Where the "/tmp" define here? and whats the >>> > About tempdbs, the temp_dbs in the new place (the databases are > located in different machines) is bigger than the older one. The > DUMPDIR has the same configuration in both. > > The logs have about the same size in both (i have changed that at > first) and are located in different dbspaces.... > > Thanks for all to everybody. > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list > > > Hi, If you don't use -ss option IDS estimate extent size as ((row count) * (row size)). And if developer set big row size, but real data are not too big new extent size estimated by dbimport somtime is huge :-) . Dimitar Bachvarov

We had a similar problem to this a few years ago. I think we were using IDS 9.4 at the time. But our problem was due to not having extent sizes set and allowing IDS to set the extent sizes. In those situations IDS assumed the maximum length for a varchar when calculating row size as part of extent size calculations. So a 1.5Gbyte database needed 8Gbytes after migration. Are you sure that you are getting extent sizes in the .sql file produced by dbexport - a grep for extent in the .sql file should suffice. Regards Malcolm -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of Claus Samuelsen Sent: 11 April 2007 07:18 To: informix-list@iiug.org Subject: Re: Problem exporting data Alberto Sánchez Bardanca wrote: >> Hi >> to avoid that problem use dbexport with "-ss" option. > ok, i have listened that solution before, i did it. But... what is the > problem, why could the database needs 2 more Gb ? > > >>> DBSPACETEMP >>> Did you setup any tmpdbs? >>> DUMPDIR >>> Where the "/tmp" define here? and whats the > About tempdbs, the temp_dbs in the new place (the databases are > located in different machines) is bigger than the older one. The > DUMPDIR has the same configuration in both. > > The logs have about the same size in both (i have changed that at > first) and are located in different dbspaces.... > > Thanks for all to everybody. > Several IDS versions ago data and indexes were always placed in the same tablespace - they shared the same extents. In the later versions of IDS you can control whether index should be in its own tablespace (called a detached index) or share the tablespace with the table data. Modern versions of IDS creates detached indexes as default. Since tablespaces grow in extent size, you will typically get a larger overhead with detached indexes. My guess is that the old table has attached indexes and the copy has detached indexes. Use oncheck or sysmaster database to find out how the two tables and indexes are created. _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list