HP-UX Error: 12 - Oracle9i on HP-UX 11i

[Alzhy]

HP-UX Error: 12: Not enough space

Anyone encountered this before?

max_mem_window = 0
maxdsiz_64bit 1073741824

[TwoProc]

The error code for that is "Not enough core".

What are you doing at this point? Relinking ?

Two possibles:
a) you're not using the ansi C compiler - you're using the one that shipped with the system.
b) your stacksize is too small on the system.
what is the value of maxssiz and maxssiz_64bit ?

See if you can review and make bigger.

[Steven E. Protter]

memory windows are how 32 bit systems get access to more contiguous memory. If this is a 64 bit system with 64 bit oracle memory windows should not be necessary.

maxdsiz_64bit might want to up that some, but that depends on a lot of things. What kind of system, how much memory, etc.

Might find some guidance at metalink.oracle.com

SEP

[Deoncia Grayson_1]

I agree with SEP, you might seriously want to consider tuning maxdsiz_64bit a bit higher if your server allows it, this link might be of interest to you as well...

http://support.businessobjects.com/library/kbase/articles/c2010558.asp

[Alzhy]

What's the biggest danger of bumping up maxdsiz_64bit to say 2GB or even 4GB? Will it put serious memory pressures on our server - which already averages close to 90% memory utilisation?

[Nobody's Hero]

We have maxdsiz_64 set to 2 GB running 64bit OS and Oracle.

Dont seem to have any memory issues. In fact, changing that parm to 2Gig helped and allowed the DBA's to start more instances.

[Steven E. Protter]

Nelson,

You have the best picture, overall of the memory situation.

Increasing the parameter will allow for larger memory chucks to be allocated. If the system is under pressure, it might simply need more memory.

Ideas:
* Check the oracle sga and see if its unreasonable.
* Additional memory.
* Thorough performance analysis(see attachments).

SEP

[Alzhy]

SEP:

* Check the oracle sga and see if its unreasonable.

Good question.. until now I've actually never ever seen a really good SGA sizing formula. AFAIK - the SGA merry go round is a trial and error method - that is a constant monitoring of cache hit and other "ratios" and continue lowering or increasing SGA components until you hit a "sweet spot"

BTW, I think our problem is simpy maxdsiz_64bit param simply set too low -- even low by Oralce on HP-UX 11i standards..

Thanks y'all!