Try to truss your ls -ltr or other commands which get stuck - if you get stuck in a system call, this should show it (of course the truss itself may take a while to get started). Top would open up lots of /proc filesystem files, so you may have a file descriptor allocation issue ... or some bug related to OS spinlock contention (mpstat would show increase in smtx column) -- Tanel Poder Consulting, Training: http://blog.tanelpoder.com Expert Oracle Exadata book: http://www.apress.com/9781430233923 On Wed, Sep 14, 2011 at 5:08 PM, Sanjay Mishra <smishra_97@xxxxxxxxx> wrote: > Rodd > > I tried with regular file system. This also happen when lots other command > is slow and not with ls only. Even running Top command takes forever to come > while uptime works fine. sar -u also works fine. So there is something > associated for some command which need some extra resource (Not sure what > like ls -ltr vs ls or grep) are very slow and so attribute to outside > application connection to Database freezing. > > SA pointing everything to Oracle as there are more that 2000 Oracle > Connection which anyway stays when everythig is running fine also during > other part of the day. > > Sanjay > From: Rodd Holman <rodd.holman@xxxxxxxxx> > To: oracle-l@xxxxxxxxxxxxx > Sent: Wednesday, September 14, 2011 9:39 AM > Subject: Re: Oracle/Solaris > What file system are you using? Could it be something in the zfs > indexing. Since a standard ls works, and smaller directories work for > sorted output, this sounds more like journaling or indexing. I'm not an > SA, so there may be more technical ways to say this, but have them look > at your file system settings and the indexing and journaling parameters > on the server. > > -- //www.freelists.org/webpage/oracle-l