1) dbexport -o /usr2/informix mumble1
This creates a mumble1.exp
If I use another instance, I can get
dbimport mumble1 to work just fine.
dbimport -i /usr2/informix mumcopy
dbimport -i /usr2/informix/mumble1.exp mumcopy
Both give me
"Cannot open sql script file"
Now, according to the "OnLine Administrator's Guide, v5.0"
p7-9 "You can give the database a new name if you use the
-i option". Of course, it doesn't give an example of how to
do that.
OnLine v5.05 uc2 AIX V3.2.5, RS6000
TIA
--
No opinions, just FAX!
Uhh... I mean FACTS!
>This creates a mumble1.exp
I have done exactly this procedure using a shell script, where I do the
dbexport, then rename the nnn.exp directory, as well as the nnn.sql script in
the nnn.exp directory, subsequent to this I import the database.
I can let you have the script if you wish
>1) dbexport -o /usr2/informix mumble1
>This creates a mumble1.exp
>If I use another instance, I can get
>dbimport mumble1 to work just fine.
>dbimport -i /usr2/informix mumcopy
>dbimport -i /usr2/informix/mumble1.exp mumcopy
>Both give me
>"Cannot open sql script file"
Patrick,
Those who know me will know that I'm not renowned for the subtlety of
my solutions... :)
I usually approach this with a much more blunt approach: I mv the .exp
directory to the new name and then mv the .sql script in the .exp
directory to the new name. Then: no problem...
HTH!
--
Cheers,
Billy
-----------------------------------------------------------------------------
INCLUDE "Disclaimer.4gh" -- my opinions are
INCLUDE "FlamesToDevNull.4gh" -- flamers, eat my shorts!
INCLUDE "CaveatEmptor.4gh" -- take my advice at your own risk
INCLUDE "ThirtySomething.4gh" -- header file for this class
-- Written by : Billy Wheeler, Date: today
-- Copyright (c) 1995, The West Solutions Group