NetNews Usenet Archive 1992 #18/NN_1992_18.iso/spool/comp/database/informix/1765

Internet Message Format | 1992-08-21 | 1.7 KB

Path: sparky!uunet!dtix!darwin.sura.net!europa.asd.contel.com!emory!hector.cc.bellcore.com
From: [e-mail] (saccente,warren j)
Newsgroups: comp.databases.informix
Subject: Online 4.10 Dbexport/Dbimport
Message-ID: <[e-mail]>
Date: 21 Aug 92 15:23:13 GMT
Sender: [e-mail]
Reply-To: [e-mail] (saccente,warren j)
Lines: 29
X-Informix-List-ID: <list.1389>

Paul Mahoney writes:

> I need to move databases about. Unfortunately dbexport does not
> record table extent/next extent sizes or the lock mode when it
> creates the sql necessary to recreate the exported database.
>
> Has anyone got tools which do it right? When I asked Informix they
> said no.

We are struggling with the same issues right now.  I've been working on
an awk script to changes the DBNAME.sql file such that it will put in the lock
modes and extent sizes and change the file so that it will work with isql
rather than dbimport.  I haven't spoken with Informix about this yet - but I
suspect that they would consider the extent size issue as a feature rather
than a flaw - and under most circumstances they are right.  dbimport will
figure out an extent size such that all data to be loaded will fit into the
first extent.  This is usually good - two cases where it is not good is
(1) if you don't have enough available contiguous dbspace to put the entire
table in one extent and (2) if you want the extent size to be less than 16K
(we create our tables as 8K extents because we have many very small tables -
our databases almost double in size when we export and import them).

Does anyone know if either of these situation exist post-4.0 or are
these flaws/features fixed?

Thanks,

Warren J. Saccente
Bellcore