Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Informix User — — source: Usenet: comp.databases.informix
Hello,
Please advise:
We are having a very strange problem that is causing dbexport to fail.
DBEXPORT always fails when extracting a schema for a particular table.
The error message
is:
=================
table definition is OK ....(Not shown here )
revoke all on "informix".dx_accountSumm from "public";-284 - A subquery has returned not exactly one row.
======================
When looking at the systmaster.systabnames there are two records with
the same tablename, same owner name and same database. We have no idea
why or how. We are however able to update/insert records into this
table properly. The error occurs only during dbexport causing the
dbexport process to abort with finishing the rest of the tables. It
stops after exporting 87 out 115 tables.
Can I simply delete the record from systabnames that points to the
non-existent table using partnum.
Informix User wrote:
> When looking at the systmaster.systabnames there are two records with
> the same tablename, same owner name and same database. We have no idea
> why or how. We are however able to update/insert records into this
> table properly. The error occurs only during dbexport causing the
> dbexport process to abort with finishing the rest of the tables. It
> stops after exporting 87 out 115 tables.
>
> Can I simply delete the record from systabnames that points to the
> non-existent table using partnum.
I'd take it up with tech support -- such an action would almost certainly be
unsupported.
--
Ciao,
The Obnoxious One
"Ogni uomo mi guarda come se fossi una testa di cazzo"
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.