Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
Subject: RE: Weird database hanging
Date: Fri, 14 Sep 2007 13:55:18 -0500
Message-ID: <302F06193D7F4D48ABC997408E786BD0026FC3B0@MSPM1BMSGM09.ent.core.medtronic.com>
In-Reply-To: <716f7a630709141119p6b28d084h1ee33adec81944ca@mail.gmail.com>
Thread-Topic: Weird database hanging
References: <716f7a630709141119p6b28d084h1ee33adec81944ca@mail.gmail.com>
From: "Elliott, Patrick" <patrick.elliott@medtronic.com>
To: <don@seiler.us>, "oracle-l" <oracle-l@freelists.org>
Sender: oracle-l-bounce@freelists.org
Errors-to: oracle-l-bounce@freelists.org
Precedence: normal
Reply-to: patrick.elliott@medtronic.com


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@freelists.org
[mailto:oracle-l-bounce@freelists.org] 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
--
http://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
--
http://www.freelists.org/webpage/oracle-l