Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Weird database hanging

Re: Weird database hanging

From: Don Seiler <>
Date: Thu, 20 Sep 2007 08:57:47 -0500
Message-ID: <>

Just an update that last night we set Oracle up with up to 20 GB of hugepages on RHEL4. This morning we saw another hang. A new twist now is that I can log in locally but not over the listener.

Oracle Support keeps telling us to fix application code, I've pretty much had it. This all worked fine for years on our 32-bit box with 1.5gb SGA. Now on a 64-bit box with 16gb SGA it can't seem to walk and chew gum at the same time.


On 9/18/07, Alex Gorbachev <> wrote:
> Could you paste content of /proc/meminfo?
> I'm not sure not using huge pages can cause such behavior but 16 GB
> SGA without huge pages on Linux is a killer. Normally, memory is
> managed in small 4k blocks. Each process has it's own page table where
> for each page it has location, permissions, and etc. For shared
> memory, each process will have its own entry in page table but only
> when it first accesses it. What can happen with large SGA, default
> page size and many Oracle processes - page table can actually occupy
> more space than SGA in addition to overhead of on-the-fly allocation
> of entries in page table.
> That being said, I'm not sure if that's relevant to your case.
> If you get qualified support engineer than s/he could hopefully see a
> clue there.
> Another option could be to OS trace the processes with high activity
> during the hang but I'd be careful on production. On the other hand -
> it's not working anyway at those times. :)
> On 9/18/07, Don Seiler <> wrote:
> > 5. We are not using huge pages. My SA says he'll set it up, since it
> > can't hurt now. I'm reading the Puschitz tuning page about it now. I
> > suppose shrinking the SGA or shared pool is always an option.
> >
> > One other difference between old and new servers is that I have
> > enabled the default degree of parallelism on our "warehouse" tables
> > and indexes, and set NOPARALLEL on our frontend objects. On our old
> > hardware it was kind of random which tables or indexes had it enabled
> > and what degree was set. Also our parallel_max_servers is 32, where
> > before it was 8. I don't think it would hurt to bring it down again.
> --
> Alex Gorbachev, Oracle DBA Brewer, The Pythian Group
> BAAG party -

Don Seiler
Received on Thu Sep 20 2007 - 08:57:47 CDT

Original text of this message