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.
Dennis Pimple — — source: Informix-list mailing list archive (1991-1998)
pinoy_ako (john@miso.wwa.com) wrote:
: Hi,
: We using NCR 3430 with AT&T Unix SvR4 2.03 and
: SE/R4gl 6.00.UE1G6.
: Our problem is that starting this afternoon, our program began to
: show the following error
: Program stopped at line ....
: -346 Could not update a row in table
: SYSTEM error number -2
: No such file or directory.
Check permissions on the *.dbs directory and the files within it. I
suspect root changed something. Make sure everything is owned by
informix and has group informix. Directory should be drwxrwx--- and
files should be -rw-rw----.
=======================================================================
Dennis J. Pimple dennisp@informix.com Opinions expressed
Senior Consultant -------------------- are mine, and do not
Informix Software Inc Voice: 303-850-0210 necessarily reflect
Denver Colorado USA Fax: 303-779-4025 those of my employer.
: I didn't recompile or change the program. I also didn't change
: the schema. I tried the following:
: 1. from dbaccess
: REPAIR TABLE [table name]
: 2. from shell prompt
: bcheck -s [table name ]*idx
: bcheck -s systables.idx
: bcheck -s sysindexes.idx
: Do I have a corrupt database? And how can I fix this?
: Pls. email or post. Thanks!
: John
: --
: - J -
--
=======================================================================
Dennis J. Pimple dennisp@informix.com Opinions expressed
Senior Consultant -------------------- are mine, and do not
Informix Software Inc Voice: 303-850-0210 necessarily reflect
Denver Colorado USA Fax: 303-779-4025 those of my employer.
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.