Re: Oracle 7.2.2.3, Solaris 2.4, Bus Errors, and I/O Errors

From: <tdrudy_at_ix.netcom.com>
Date: 1997/01/30
Message-ID: <32F1470F.26F1@ix.netcom.com>#1/1

Wayne,

        Sounds like a lot of things...wish I had it here.

	Suggest:
		- do a recursive du (look up in the man page) and pipe

it to more: look at every file, . and regular, in all your subdirs in /opt

• take a look at /var/lp and /vaar/spool
• upgrading to Solaris 2.5 or 2.5.1: 2.4 was intended as an interim OS.
• go into /lost&found, and /tmp, and absolutely rm everything by destroying the directories and then recreating them. You could have large junk files which will NOT show on an ls.
• in /opt, try using an ls -la just to check for junk dot files. long shot.
• cannot understand the out of inodes error: that's pretty infrequent. Solaris reserves 30% of swap for the superuser only, even when the total says 100% used. What does your swap space (/) look like using df -k?
• what else do you have in /opt? what size hard disk on the 20? send me your file structure from df -k.

        If I had my Sun here, I could help you a bit more :) Email me if nothing else works. We can fix this.

                        Tom

Wayne Yingling wrote:
>
> Using Solaris 2.4 on a 20 with Oracle. Oracle has been running on this
> machine for over a year. Typically it has been pretty reliable - Until the
> new year.
>
> Lately we are receiving messages that file systems are full when they are not.
>
> We receive messages that the /opt filesystem is out of inodes when df -e
> indicates that there are over 400,000 free.
> And any executable we run from /opt returns a bus error.
> If we change directories into /opt we randomly receive "No device or Bad
> Address" messages when navigating into subdirectories.
>
> When these messages begin, Oracle returns "EOF on communication channel"
> errors when trying to connect remote through SQLNet V2. Oracle/Solaris
> returns "Bus error" messages when trying to connect from the server itself.
>
> After a reboot the messages go away then return 2 to 8 hours later. It seems
> to be Oracle usage related but no pattern has been established.
>
> Any thoughts ?
> Is it Oracle ? Solaris ? Hardware ?
>
> Thanks
> Wayne
Received on Thu Jan 30 1997 - 00:00:00 CST