I hava a database that I want to move from one Informix server to
another. They both reside on the same machine with the same Informix
version.

SunOS 5.8 sparc Ultra-80
IBM Informix Dynamic Server Version 9.40.UC5

I set up my initial Informix environment and exported data from the
original IDS database via dbexport -q -o <dir> -ss <dbname>.

I changed to the new Informix environment and then attempted to import
data from that output directory into the new IDS database via dbimport
-q -i <dir> -d <DfltDbSpace> <dbname>. However, I received the
following output:

*** prepare sqlobj
329 - Database not found or no system permission.

111 - ISAM error: no record found.

After the failed dbimport, I found that the database was created in the
new IDS. I ran a database comparison via Server Studio and found that
all of the database tables had been created, but 5 synonyms were not
created and 340 routines were not created.

Has anyone seem a similar situation? Did you get a resolution to the
problem?

Thanks,
Gary Andrus

The database that the synonyms are pointing to does not exist in the
new instance.

When a dbimport fails, anything already created stays behind. I get
this problem a few times a year when I forget to change the synonyms to
include the instance name.

One fix is to edit the sql script in the export directory, find the
synonyms and correct them, then re-import the database. (dropping the
incomplete previous database first!!)

OR

Export the other required database(s) and load it into the second
instance before importing the original database.

HTH

Nog wrote:
> The database that the synonyms are pointing to does not exist in the
> new instance.
>
> When a dbimport fails, anything already created stays behind. I get
> this problem a few times a year when I forget to change the synonyms to
> include the instance name.
>
> One fix is to edit the sql script in the export directory, find the
> synonyms and correct them, then re-import the database. (dropping the
> incomplete previous database first!!)
>
> OR
>
> Export the other required database(s) and load it into the second
> instance before importing the original database.
>
> HTH

Nog,

I had looked for several different databases that I thought may be
causing the problem (via grep) but couldn't figure it out. After
reading your suggestion I did the obvious thing and looked at the
definition of the 5 synonyms. Sure enough, it was another database
that I hadn't been looking for and it was in all 5 synonyms.

Thanks for the help,
Gary

Hi Gary, many times I had that problem, it is because you're trying to
make
a DBIMPORT of a large database and your informix parameters are not
enough
to get that amount of information.

In my case, I used to do the import using:

$ dbimport databasename -d dbspaceofdata -lU

With the "-lU" parameter, it makes a load of the database in
"transactional
mode" in one step, but many times it shows me the same "prepare
sqlobj..."
error if it was a big database due to the lack of enough logs to
support that amount
of information. Now, to avoid that error I use 2 steps:

$ dbimport databasename -d dbspaceofdata

$ ontape -s -U databasename

Good Luck

--------------------------------------------------------------------------------------------------------


Gary Andrus ha escrito:

> I hava a database that I want to move from one Informix server to
> another. They both reside on the same machine with the same Informix
> version.
>
> SunOS 5.8 sparc Ultra-80
> IBM Informix Dynamic Server Version 9.40.UC5
>
> I set up my initial Informix environment and exported data from the
> original IDS database via dbexport -q -o <dir> -ss <dbname>.
>
> I changed to the new Informix environment and then attempted to import
> data from that output directory into the new IDS database via dbimport
> -q -i <dir> -d <DfltDbSpace> <dbname>. However, I received the
> following output:
>
> *** prepare sqlobj
> 329 - Database not found or no system permission.
>
> 111 - ISAM error: no record found.
>
> After the failed dbimport, I found that the database was created in the
> new IDS. I ran a database comparison via Server Studio and found that
> all of the database tables had been created, but 5 synonyms were not
> created and 340 routines were not created.
>
> Has anyone seem a similar situation? Did you get a resolution to the
> problem?
>
> Thanks,
> Gary Andrus