topic Re: 32 bits app in a 64 bits platform in Operating System - HP-UX

32 bits app in a 64 bits platform

Ricardo R Peirano — Tue, 13 Jul 2004 11:43:16 GMT

Hi
I have a lot of 32 bit db2 instances running in my server, plus a 32 bits WebSphere server and in the last week a had some errors randomly into some of these instances when iÂ´m taking an online backup, like the following:

SQL1084C Shared memory segments cannot be allocated. SQLSTATE=57019

My questions are:
Is the 64 bits HPUX 11.11 emulating a 32 bits HPUX memory management for 32 bits applications?
If I have a 32 bit application running in a 64 bit hpux 11.11, Have I got a memory limit in 1.75 Gb from quadrant 3 and 4 for this applications?
Is the solution just memory windows or may be another one?

Regards

Ricar

Re: 32 bits app in a 64 bits platform

A. Clay Stephenson — Tue, 13 Jul 2004 11:52:36 GMT

Your applications compiled/linked as 32-bit are still limited by the same 32-bit virtual address space limits --- even in 64-bit land.

Your options are:
1) Recompile/relink as 64-bit
2) Use memory windows -- you still have the same limititations but each group of 32-bit applications gets its own 4GB VAS rather than being a 4GB VAS shared by all 32-bit applications.

Re: 32 bits app in a 64 bits platform

Cheryl Griffin — Tue, 13 Jul 2004 12:09:14 GMT

There is a few 32-64 bit memory explanations at http://devrsrc1.external.hp.com/STK/hpux_faq.html#G18

Re: 32 bits app in a 64 bits platform

Jeff Schussele — Tue, 13 Jul 2004 12:17:44 GMT

Hi Ricardo,

Just remember that IF you put these 2 apps into separate memory windows, resources cannot be shared between them.
This means if they interact to any extent then memory windows aren't the way to go.

Rgds,
Jeff

Re: 32 bits app in a 64 bits platform

Sundar_7 — Tue, 13 Jul 2004 12:20:06 GMT

Hi Ricar,

Yes that is right. 32 bit applications running in 64 bit 11.X will still have the 1.75 GB limitations.

I am not sure if this is possible with db2 or not but I believe if you change the executable type from EXEC_MAGIC to SHMEM_MAGIC then the shared memory limit can be raised upto 2.75 GB.

Or else your best bet would be to use memory windows

-- Sundar