error -206 dbschema dbexport
Posted in 1999
Topics: Migration, Import/Export & Data Conversion
Hi,
we can't use dbexport or dbschema (always get the message
"The specified table informix.sysroleauth is not in the
database. (Error -206)"). Do you have any idea how to solve
this problem?
Regards,
Frank
oncheck -cc command.
In article <386875B5.65B3E20A@lindedaten.de>,
Frank Linde <frank@lindedaten.de> wrote:
> Hi,
>
> we can't use dbexport or dbschema (always get the message
> "The specified table informix.sysroleauth is not in the
> database. (Error -206)"). Do you have any idea how to solve
> this problem?
>
> Regards,
> Frank
>
Sent via Deja.com http://www.deja.com/
Before you buy.
Frank Linde wrote:
>
> Hi,
>
> we can't use dbexport or dbschema (always get the message
> "The specified table informix.sysroleauth is not in the
> database. (Error -206)"). Do you have any idea how to solve
> this problem?
Create a new database containing the same tables, copy the data from the
current tables to the corresponding table in the new database, drop the
original database, rename the new database.
If you do not have a schema for the database but have only a few tables you
can do the schema creation by hand. However, if you have many tables you
can get my utility myschema (from the IIUG Software Repository in the
package utils2_ak) and comment out the if block at the end of the
print_userauths() function in print_userauths.ec (it begins with the comment:
/* Grant role code. */) so that the program does not look for the
sysroleauth table then compile and run it against your database to get a
current schema.
Also note that I have posted another package, utils4_ak, which contains a
set of awk scripts to post process dbschema/myschema output to create load,
unload, drop, copy, dbcopy, etc. SQL and/or shell scripts that would reduce
your typing load to move the data to a new safe database schema if you are
not comfortable creating such scripts yourself.
Myschema and all of the programs in utils2_ak can be compiled with either
ESQL-C V7.xx, SDK 2.xx (ie ESQL-C 9.2x), or C4GL V7.xx.
Art S. Kagel