dbimport don't use all available dbspace

Hi all, On Linux Centos, with Informix 10.00.FC6 I've this dbspace situation [informix@test64-001 dev]$ onstat -d IBM Informix Dynamic Server Version 10.00.FC6 -- On-Line -- Up 4 days 00:03:36 -- 37900 Kbytes Dbspaces address number flags fchunk nchunks pgsize flags owner name 45068e78 1 0x60001 1 1 2048 N B informix rootdbs 460fa5c8 2 0x60001 2 1 2048 N B informix datidbs1 460faec8 3 0x42001 3 1 2048 N TB informix sortdbs 46132498 4 0x60001 4 1 2048 N B informix datidbs2 4 active, 2047 maximum Chunks address chunk/dbs offset size free bpages flags pathname 45069028 1 1 0 15000 5211 PO-B /informix/dev/rootdbs 460fa760 2 2 64 512000 453406 PO-B /informix/dev/datidbs1 460fb060 3 3 0 256000 255947 PO-B /informix/dev/sortdbs 46132630 4 4 0 512000 511947 PO-B /informix/dev/datidbs2 4 active, 32766 maximum NOTE: The values in the "size" and "free" columns for DBspace chunks are displayed in terms of "pgsize" of the DBspace to which they belong. Expanded chunk capacity mode: always [informix@test64-001 dev]$ I'm trying to make a dbimport of a database with the command [informix@test64-001 dev]$ dbimport <dbname> and the only dbspace consumed by the engine is the rootdbs that becomes completly full after few second with the error: ... *** execute sqlobj 261 - Cannot create file for table (edp.ma_d_inv). 131 - ISAM error: no free disk space [informix@test64-001 dev]$ So I've change the command in [informix@test64-001 dev]$ dbimport -d datidbs1 <dbname> The engine now use all the dbspace datidbs1 (1G) until this became full again, like onstat -d say IBM Informix Dynamic Server Version 10.00.FC6 -- On-Line -- Up 4 days 00:06:26 -- 46092 Kbytes Dbspaces address number flags fchunk nchunks pgsize flags owner name 45068e78 1 0x60001 1 1 2048 N B informix rootdbs 460fa5c8 2 0x60001 2 1 2048 N B informix datidbs1 460faec8 3 0x42001 3 1 2048 N TB informix sortdbs 46132498 4 0x60001 4 1 2048 N B informix datidbs2 4 active, 2047 maximum Chunks address chunk/dbs offset size free bpages flags pathname 45069028 1 1 0 15000 5211 PO-B /informix/dev/rootdbs 460fa760 2 2 64 512000 0 PO-B /informix/dev/datidbs1 460fb060 3 3 0 256000 255947 PO-B /informix/dev/sortdbs 46132630 4 4 0 512000 511947 PO-B /informix/dev/datidbs2 4 active, 32766 maximum NOTE: The values in the "size" and "free" columns for DBspace chunks are displayed in terms of "pgsize" of the DBspace to which they belong. Expanded chunk capacity mode: always [informix@test64-001 dev]$ but don't use the space in the other dbspaces (datidbs2 for example) How can i force the engine to use all the dbspaces presents and availables ? Thank for the advice. Danilo

Hello, Danilo. Dbimport executes an sql script, according to the database name you are importing. Notice that there is a folder with your database name, and inside it, there is a [database_name].sql file. If you need to make adjustments for indexes, the only way is to manually change your sql script, before importing. Via dbimport command, you can only set the main dbspace for your database, not any index related. Hope it helps. Regards. Atenciosamente, Alexandre Marini [http://mcsoftware.com.br/mc_conteudo/assinaturas/logoassinatura.png] [http://mcsoftware.com.br/mc_conteudo/assinaturas/arquiteturalogo.png] ________________________________ De: ids-bounces@iiug.org <ids-bounces@iiug.org> em nome de DANILO BREMBILLA <dbrembilla@robur.it> Enviado: segunda-feira, 10 de outubro de 2016 08:53:06 Para: ids@iiug.org Assunto: dbimport don't use all available dbspace [37956] Hi all, On Linux Centos, with Informix 10.00.FC6 I've this dbspace situation [informix@test64-001 dev]$ onstat -d IBM Informix Dynamic Server Version 10.00.FC6 -- On-Line -- Up 4 days 00:03:36 -- 37900 Kbytes Dbspaces address number flags fchunk nchunks pgsize flags owner name 45068e78 1 0x60001 1 1 2048 N B informix rootdbs 460fa5c8 2 0x60001 2 1 2048 N B informix datidbs1 460faec8 3 0x42001 3 1 2048 N TB informix sortdbs 46132498 4 0x60001 4 1 2048 N B informix datidbs2 4 active, 2047 maximum Chunks address chunk/dbs offset size free bpages flags pathname 45069028 1 1 0 15000 5211 PO-B /informix/dev/rootdbs 460fa760 2 2 64 512000 453406 PO-B /informix/dev/datidbs1 460fb060 3 3 0 256000 255947 PO-B /informix/dev/sortdbs 46132630 4 4 0 512000 511947 PO-B /informix/dev/datidbs2 4 active, 32766 maximum NOTE: The values in the "size" and "free" columns for DBspace chunks are displayed in terms of "pgsize" of the DBspace to which they belong. Expanded chunk capacity mode: always [informix@test64-001 dev]$ I'm trying to make a dbimport of a database with the command [informix@test64-001 dev]$ dbimport <dbname> and the only dbspace consumed by the engine is the rootdbs that becomes completly full after few second with the error: .... *** execute sqlobj 261 - Cannot create file for table (edp.ma_d_inv). 131 - ISAM error: no free disk space [informix@test64-001 dev]$ So I've change the command in [informix@test64-001 dev]$ dbimport -d datidbs1 <dbname> The engine now use all the dbspace datidbs1 (1G) until this became full again, like onstat -d say IBM Informix Dynamic Server Version 10.00.FC6 -- On-Line -- Up 4 days 00:06:26 -- 46092 Kbytes Dbspaces address number flags fchunk nchunks pgsize flags owner name 45068e78 1 0x60001 1 1 2048 N B informix rootdbs 460fa5c8 2 0x60001 2 1 2048 N B informix datidbs1 460faec8 3 0x42001 3 1 2048 N TB informix sortdbs 46132498 4 0x60001 4 1 2048 N B informix datidbs2 4 active, 2047 maximum Chunks address chunk/dbs offset size free bpages flags pathname 45069028 1 1 0 15000 5211 PO-B /informix/dev/rootdbs 460fa760 2 2 64 512000 0 PO-B /informix/dev/datidbs1 460fb060 3 3 0 256000 255947 PO-B /informix/dev/sortdbs 46132630 4 4 0 512000 511947 PO-B /informix/dev/datidbs2 4 active, 32766 maximum NOTE: The values in the "size" and "free" columns for DBspace chunks are displayed in terms of "pgsize" of the DBspace to which they belong. Expanded chunk capacity mode: always [informix@test64-001 dev]$ but don't use the space in the other dbspaces (datidbs2 for example) How can i force the engine to use all the dbspaces presents and availables ? Thank for the advice. Danilo ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

OK, you have two problems: 1 - You probably did not use the -ss flag when you ran dbexport so the correct dbspaces for the tables and indexes are not included in the schema file. That's OK if you want to load the database into different dbspaces than the original one(s). 2 - You did not originally include the -d <dbspacename> option to the dbimport so the new database was created in the rootdbs which is the default location unless you have the AUTOLOCATE ONCONFIG parameter set to a different dbspace. 3 - If you want some of the tables and/or indexes to go into datidbs2 and some into datidbs1 then you will have to edit the edp.sql schema file in the edp.dbs directory and add IN <dbspacename> clauses to those objects that should go into a different dbspace than the one named in the -d datidbs1 option. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Mon, Oct 10, 2016 at 7:53 AM, DANILO BREMBILLA <dbrembilla@robur.it> wrote: > Hi all, > On Linux Centos, with Informix 10.00.FC6 I've this dbspace situation > > [informix@test64-001 dev]$ onstat -d > > IBM Informix Dynamic Server Version 10.00.FC6 -- On-Line -- Up 4 days > 00:03:36 > -- 37900 Kbytes> > Dbspaces > address number flags fchunk nchunks pgsize flags owner name > 45068e78 1 0x60001 1 1 2048 N B informix rootdbs > 460fa5c8 2 0x60001 2 1 2048 N B informix datidbs1 > 460faec8 3 0x42001 3 1 2048 N TB informix sortdbs > 46132498 4 0x60001 4 1 2048 N B informix datidbs2 > 4 active, 2047 maximum > > Chunks > address chunk/dbs offset size free bpages flags pathname > 45069028 1 1 0 15000 5211 PO-B /informix/dev/rootdbs > 460fa760 2 2 64 512000 453406 PO-B /informix/dev/datidbs1 > 460fb060 3 3 0 256000 255947 PO-B /informix/dev/sortdbs > 46132630 4 4 0 512000 511947 PO-B /informix/dev/datidbs2 > 4 active, 32766 maximum > > NOTE: The values in the "size" and "free" columns for DBspace chunks are > > displayed in terms of "pgsize" of the DBspace to which they belong. > > Expanded chunk capacity mode: always > > [informix@test64-001 dev]$ > > I'm trying to make a dbimport of a database with the command > [informix@test64-001 dev]$ dbimport <dbname> > and the only dbspace consumed by the engine is the rootdbs that becomes > completly full after few second with the error: > > .... > *** execute sqlobj > 261 - Cannot create file for table (edp.ma_d_inv). > 131 - ISAM error: no free disk space > [informix@test64-001 dev]$ > > So I've change the command in > > [informix@test64-001 dev]$ dbimport -d datidbs1 <dbname> > > The engine now use all the dbspace datidbs1 (1G) until this became full > again, > like onstat -d say > > IBM Informix Dynamic Server Version 10.00.FC6 -- On-Line -- Up 4 days > 00:06:26 > -- 46092 Kbytes> > Dbspaces > address number flags fchunk nchunks pgsize flags owner name > 45068e78 1 0x60001 1 1 2048 N B informix rootdbs > 460fa5c8 2 0x60001 2 1 2048 N B informix datidbs1 > 460faec8 3 0x42001 3 1 2048 N TB informix sortdbs > 46132498 4 0x60001 4 1 2048 N B informix datidbs2 > 4 active, 2047 maximum > > Chunks > address chunk/dbs offset size free bpages flags pathname > 45069028 1 1 0 15000 5211 PO-B /informix/dev/rootdbs > 460fa760 2 2 64 512000 0 PO-B /informix/dev/datidbs1 > 460fb060 3 3 0 256000 255947 PO-B /informix/dev/sortdbs > 46132630 4 4 0 512000 511947 PO-B /informix/dev/datidbs2 > 4 active, 32766 maximum > > NOTE: The values in the "size" and "free" columns for DBspace chunks are > > displayed in terms of "pgsize" of the DBspace to which they belong. > > Expanded chunk capacity mode: always > [informix@test64-001 dev]$ > > but don't use the space in the other dbspaces (datidbs2 for example) > How can i force the engine to use all the dbspaces presents and availables > ? > > Thank for the advice. > Danilo > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --001a1130cfa675517d053e8208af