Re: SQL ERROR ==> 461: File Open Error

Walt Hultgren {rmy}, to All on 17 Nov 93: > From: walt@mathcs.emory.edu (Walt Hultgren {rmy}) > Date: 16 Nov 1993 13:37:56 -0500 > You may not like this next part: It suddenly started working, but we > don't know why. At least, I don't. I was watching over the sysadmin's > shoulder, but not closely. He checked a few mounts, and we did some other > looking around. I don't think anything was changed. All of the file > systems involved are local. None are even exported. Don't you _hate_ when that happens... > Anyway, as I recall the session, all he did was su to root, create a > database (which went OK!), then return to his personal login. After that, > everything worked fine. We currently have a rather convoluted OS and > network set-up here, so I figured maybe there's some problem with that. > Our environment will be much more simplified soon, so we let it go. And I think that may be the answer. Some versions of Unix only allow the super user to take the last slot in certain system tables. The open file and inode tables are the likely culprits here. If the symptom is repeatable (note that it will be load dependent), try reconfiguring those table sizes in the kernel. Cheers, -- jra Ashworth & Associates * jra@mechanic.fidonet.org -- Internet: jra@f8649.n3603.z1.FIDONET.ORG UUCP: ...!myrddin!mechanic!8649!jra NOTE: Of course I know it all! I don't? Damn!