In my environment I have two databases each in their own environment. I am trying load (a) to (b) and am having problems doing this. First off, the environments are not totally identical, the database chunks are not the same (b) has fewer chunks but is should still have enought space to hold database (a). I ran a dbexport on (a) and when I run a dbimport on (b) I get the following message.....
*** create database
330 - Cannot create or rename database.
100 - ISAM error: duplicate value for a record with unique key.
The environment where I am going still has the old database online (in onmonitor) is it possible to move one database to another environment? And if it is, why is this error coming up?
I realize I have not given much information but I will be the first to admit I am a UNIX admin, not an informix admin.
Let's say you have an IDS instance called "work_one".
work_one is made up of some dbspaces, some critical (rootdbs, physdbs, logdbs, and tempdbs) and some user defined (dbs1, dbs2, dbs3, etc ....).
All these dbspaces are created using "chunks" of raw space and these chunks are created from logical volumes.
The dbspace(s) contain the database tables and indexes.
When you drop a database, you're removing the contents of some dbspaces, like dbs1 and dbs2, but the empty dbs1 and dbs2 dbspaces remain and are ready to receive the dbimport.
Note: the SQL script generated by dbexport will have the source database dbspace(s) for indexes defined explicitly in the SQL script for each index. All these must be changed to the correct dbspace(s) that will be used for the target database.
The dbspace for the target database tables is defined using dbimport from the command line.
Thanks for that info, but then I have a question, what happens if both databases are named the same thing? Also, when I looked at the sql script (which is the database name) there is nothing in there listing what chuncks contain what information. I have a database named elitedbs and the chuncks under it are elitesec1-20 and none of those names are listed in the sql file.