RE: dbexport/dbimport question

There is a potential problem with some releases of dbexport -ss in that it produces IN clauses for indexes but not for tables. That can present problems if you are changing the basic locations of any of the dbspaces. You can get round it by not using dbexport -ss but then you will have a problem with data and serial constraint tables interleaving. If you can do it use dbexport -ss and manually edit all IN clauses and all extent size settings. -----Original Message----- From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] On Behalf Of Brian McLaughlin Sent: 03 May 2005 21:15 To: informix-list@iiug.org Subject: dbexport/dbimport question In the continuing story of our preparation to migrate to a new version our business software, I've set up our "practice" server with Informix 9.4. I'm using dbexport/dbimport to load our data, because we've changed the dbspaces a bit -- taking advantage now of large chunks, consolidating some spaces, etc. dbexport on our business server produced a hair over 9GB. When I look at the .sql file dbexport generated, most of the create table statements do not specify a dbspace. I believe that means that when this is dbimported, those tables are created in rootdbs? Rootdbs on the dbexported server is only 30MB. Rootdbs on the imported server is 512MB. Yet, on the dbimport, rootdbs filled up, and the import aborted. I can pretty easily edit the .sql file to include an "IN mydbs" after each create table statement, but my question is... where are these tables residing now if there is no dbspace specified in the dbexport results? Brian McLaughlin Administrative Computing George Fox University (503) 554-2587 sending to informix-list sending to informix-list