If you think about what dbexport does it should help you to solve the
problem.

Basically dbexport does a dbschema of the database and writes the output to
dbname.sql
Then it does an unload of each table.

So, to dbexport only one table use dbschema -ss -d dbname -t tabname
tabname.sql
to unload the table use the sql statement unload to "tabname.unl" select *
from tabname

Then drop the table and recreate the table in the new dbspace using the
dbname.sql modofied to include the "in dbspace" clause
and then load the table using "load from "tabname.unl" insert into tabname

And I'll leave it to the UNIX specialists to explain how you get the unload
file onto a tape. My UNIX isn't quite up to that but I'm sure it is
possible.

Malcolm


----- Original Message -----
From: "Howard Jones" <howie_lfc@hotmail.com>
To: <informix-list@iiug.org>
Sent: Monday, November 24, 2003 3:26 PM
Subject: Dbexport


> Hello all,
>
> IDS 9.21.FC4
> HPUX11.0
>
> The customer has requested the archive data we have currently within a
> dbspace be moved to a seperate database within the live instance. Any
> ideas....I was planning on using dbexport to tape but I have just read
that
> a dbexport exports the whole database which is not feasable.
> So to recap I wish to create a new database and populate it with the
> excisting data from a dbspace.
>
>

sending to informix-list