[Q] dbexport, dbimport usage.
Hi, all
I'd installed informix on linux box. I curious about dbimport and dbexport.
How can I use dbexport and dbimport ? I just did dbexport store database.
But when I tried to dbimport from exported directory, I got error message.
'can't open sql script file'. what's mean error message ? how can i use
dbimport ?
Would you let know why use dbimport and dbexport ? is it for data backup or
schema backup ? I can't find document.
Thanks all.
--
+---------------+---------------------------------------------------------+
| .--. | |
| |o_o | | Name : Ssang-Gu Hwang |
| |:_/ | | E-mail : angra@maninet.co.kr |
| // \\ \\ | Tel : 02) 3289-3762 |
| (| | ) | FAX : 02) 3289-3477 |
| /'\\_ _/`\\ | Org : Maninetwork |
| \\___)=(___/ | |
+---------------+---------------------------------------------------------+
Hi Ssang-gu Hwang,
To begin with your last question, the function of this tools.
No, it is not for making back-ups, for that you should use ontape or
onbar (onarchive also workes but is not recommended due to it's complex
handling)
No, it also isn't for schema back-up for that you should use the
dbschema utility.
The main function of this tools is to download a whole database to ASCII
and to import it again. This way you can make a hardcopy of the data in
the dartabase. Normally this is used to reorganise a complete database
or to secure a database before a migration.
The usage of this tools you can find in the migration guide (I believe).
There are a few things you should know:
- Tools are not optimised for performance (however the first create the
table, fill the data
and afterwards the indices are created.)
- Normally these tools handle primary and foreign constraints well
- A dbimport can not berestarted (you must start all over again eveytime
a problem
occurs).
- On NT I know there are problems with BLOBS and BAAN IV hash-keys.
There are
corrupted. So don;t use this tools for this.
- If a table definition exceeds more than 64k (I've had it), the export
runs fine but the
import fails, due to the imitation of the 64k SQL buffer in IDS. You
should fix this by
splitting the definition in a craete and a alter tabel part.
- If you want to re-create the database with a different name you should
change the
directory name (if exported to disk) and the name of the .sql file in
this directory.
For the rest this utilities works fine. (But not recommend for databases
bigger than a few Gb).
I hope this has pointed some thing out...
Greetings,
Rob Prop
Database Consultant