bbh@whizz.uucp (Bud Hovell) (11/29/89)
We have a problem here that is driving me nuts! :-<
It seems that when we invoke isql (by the user at the command line or in a
shell script), it sometimes works fine, and sometime just bombs out with a
message of "Unknown error".
This happens just at the point after the Informix notice appears and when
the menu would be expected to appear. Seems to relate to the isql invocation
itself, and not to choice of options, dbname, etc. Dosn't matter which
options or database we use.
When this happens at night during one of the many scripted updates we run
under cron, it dumps ~2 Meg of junk into my cronlog, and hogs resources
until I manually kill the process.
There seems to be no particular pattern to the erratic bahavior. I have
re-installed both the kernal and the SQL software, and neither seems to
have make any change.
In the margin of my manual is a note from a conversation I had long
ago with tech support. The tech made the comment that this feature is
"awkward to use". Is "awkward" the approved newspeak euphomism for "fragile"
or "unreliable"? [I failed, at the time, to ask the nice person what he was
really trying to say.]
What is also peculiar is that we have NOT always had this problem - seems
to be cropping up just in the past two months. It doesn't seem to have
anything to do with the size of the database. We *think* we have permissions
and ownerships right, and there are no other mystery problems with the db
software.
We are running version 2.10.00B of Informix SQL on a 3B1, unix 3.51a os.
Any help would be most gratefully appreciated. 'Getting to be deperation time
on this problem.
Bud
________________________________________________________________________
UUCP: ...{tektronix|sun}!nosun!whizz!bbh (Just another pilgrim :-)
MOTD: "Lead, follow, or get out of the way!" - Ted Turnerchris@vision.UUCP (Chris Davies) (12/04/89)
In article <955@whizz.uucp> bbh@whizz (Bud Hovell) writes:
-> It seems that when we invoke isql (by the user at the command line or in a
-> shell script), it sometimes works fine, and sometime just bombs out with a
-> message of "Unknown error".
Yup. I can get it too. It happens to me when I haven't set up the various
shell variables
INFORMIXDIR=... (default: /usr/informix)
PATH=$PATH:$INFORMIXDIR/bin (required)
DBPATH=... (optional)
export INFORMIXDIR PATH DBPATH (required - sort of :-)
to point to things on our system (examples are for Bourne shell, "/bin/sh").
-> When this happens at night during one of the many scripted updates we run
-> under cron, it dumps ~2 Meg of junk into my cronlog, and hogs resources
-> until I manually kill the process.
I could believe this. Perhaps you need to set these variables in your scripts?
I would NOT recommend you set them in your cron file.
-> What is also peculiar is that we have NOT always had this problem - seems
-> to be cropping up just in the past two months. It doesn't seem to have
-> anything to do with the size of the database. We *think* we have permissions
-> and ownerships right, and there are no other mystery problems with the db
-> software.
Er. Um. :-( Oh well, you probably know all of this, but I've posted this
anyway, so that it might be of help to others (whenever...).
Chris
--
VISIONWARE LTD | UK: chris@vision.uucp JANET: chris%vision.uucp@ukc
Leeds Business Park | US: chris@vware.mn.org OTHER: chris@vision.co.uk
Bruntcliffe Lane | BANGNET: ...{backbone}!ukc!vision!chris
Morley, LEEDS LS27 0JG | VOICE: +44 532 529292
England | FAX: +44 532 526614 TELEX: 556283 SYSTIM G
--------------- "VisionWare: The home of DOS/UNIX integration" ---------------