oracle ~ $ ulimit -u 2047 oracle ~ $ ulimit -n 1024 This is a big gaffe. According to Puschitz those values should be set in the .bash_profile to 16384 and 63536, respectively. Mea culpa on completely missing these in the setup. I've since set them in the ~oracle/.bash_profile as well as /etc/security/limits.conf. Only problem now is that it'll require a database bounce to take effect, although we have one scheduled for Sunday. Don. On 9/14/07, Elliott, Patrick <patrick.elliott@xxxxxxxxxxxxx> wrote: > > Take a look at the UNIX resource limits (ulimit) set for the oracle > user. It probably couldn't spawn any more processes. The init.ora > parameter might be an issue, but usually you get a more descriptive > error message when you max out init.ora processes. > > > Pat > > -----Original Message----- > From: oracle-l-bounce@xxxxxxxxxxxxx > [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Don Seiler > Sent: Friday, September 14, 2007 1:20 PM > To: oracle-l > Subject: Weird database hanging > > Running 10gR2 (10.2.0.2) on RHEL4 on 4 64-bit dual-core box. Earlier > today users complained en masse about not being able to connect to the > database. I got to a term and found that even trying to log in locally > as sysdba was hanging. > > The alert log had this: > Fri Sep 14 11:23:36 2007 > kkjcre1p: unable to spawn jobq slave process Fri Sep 14 11:23:36 2007 > Errors in file /u00/app/oracle/admin/foo/bdump/foo_cjq0_11519.trc: > Fri Sep 14 11:25:46 2007 > kkjcre1p: unable to spawn jobq slave process Fri Sep 14 11:25:46 2007 > Errors in file /u00/app/oracle/admin/foo/bdump/foo_cjq0_11519.trc: > Fri Sep 14 11:26:49 2007 > PMON failed to acquire latch, see PMON dump > > I hit the Google but before I came back, my login was ready and things > seemed back to normal. Checking back in the alert log I saw a lot of > these: > > WARNING: inbound connection timed out (ORA-3136) > > I'm assuming those are just symptoms of the original cause, and I've > already found suggestions for treating timeouts in sqlnet.ora and > listener.ora. > > The trace files mentioned have lines such as: > > Waited for process J000 to initialize for 60 seconds > > repeated for 70, 80, 90 seconds, etc. > > So in summary, there was hanging for everyone, it seemed to clear itself > up. One post on Google suggested that the PROCESSES init parameter > might be too low. Any other possibilities? > > -- > Don Seiler > oracle: http://ora.seiler.us > ultimate: http://www.mufc.us > -- > //www.freelists.org/webpage/oracle-l > > > > ___________________________________________________________________________________________________ > CONFIDENTIALITY AND PRIVACY NOTICE > Information transmitted by this email is proprietary to Medtronic and is > intended for use only by the individual or entity to which it is addressed, > and may contain information that is private, privileged, confidential or > exempt from disclosure under applicable law. If you are not the intended > recipient or it appears that this mail has been forwarded to you without > proper authority, you are notified that any use or dissemination of this > information in any manner is strictly prohibited. In such cases, please > delete this mail from your records. > > To view this notice in other languages you can either select the following > link or manually copy and paste the link into the address bar of a web > browser: http://emaildisclaimer.medtronic.com > -- Don Seiler oracle: http://ora.seiler.us ultimate: http://www.mufc.us -- //www.freelists.org/webpage/oracle-l