- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Problems with SAM and shared memory
Operating System - HP-UX
1752577
Members
4309
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-10-2010 01:07 PM
тАО02-10-2010 01:07 PM
Problems with SAM and shared memory
Hi,
Since I installed Progress RDBS on the HP-UX 11.23 server I'm getting this kind of errors when trying to start SAM while the Progress databases are up:
sam: FATAL ERROR: Unable to load library "/usr/obam/lib/libIDMawrt.1": Not enough space
OR
/usr/lib/dld.sl: Call to mmap() failed - TEXT //usr/obam/lib/libobam.1
/usr/lib/dld.sl: Not enough space
/usr/sbin/sam[220]: 4826 Abort(coredump).
As I could read on other threads it seems that this is related to the shared memory as long as the database servers are using it.
Yet, when using swapinfo it looks like I have enough memory as long as only 25% of the total is used.
I tried to change some kernel parameters but with no favorable result.
Any advice would be apreciated.
Thanks
Since I installed Progress RDBS on the HP-UX 11.23 server I'm getting this kind of errors when trying to start SAM while the Progress databases are up:
sam: FATAL ERROR: Unable to load library "/usr/obam/lib/libIDMawrt.1": Not enough space
OR
/usr/lib/dld.sl: Call to mmap() failed - TEXT //usr/obam/lib/libobam.1
/usr/lib/dld.sl: Not enough space
/usr/sbin/sam[220]: 4826 Abort(coredump).
As I could read on other threads it seems that this is related to the shared memory as long as the database servers are using it.
Yet, when using swapinfo it looks like I have enough memory as long as only 25% of the total is used.
I tried to change some kernel parameters but with no favorable result.
Any advice would be apreciated.
Thanks
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-10-2010 01:16 PM
тАО02-10-2010 01:16 PM
Re: Problems with SAM and shared memory
Hi:
You should look at both 'maxdsiz' (or 'maxdsiz_64bit' if the database is a 64-bit one) as well as the amount of swap space you have configured.
Swap space is required at least during process instantiation for reservation purposes. While a process may never actually use swap space, the kernel demands that enough exist in the event that process data needs to be swapped (paged).
Regards!
...JRF...
You should look at both 'maxdsiz' (or 'maxdsiz_64bit' if the database is a 64-bit one) as well as the amount of swap space you have configured.
Swap space is required at least during process instantiation for reservation purposes. While a process may never actually use swap space, the kernel demands that enough exist in the event that process data needs to be swapped (paged).
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-10-2010 01:55 PM
тАО02-10-2010 01:55 PM
Re: Problems with SAM and shared memory
The failure is telling you that there is not enough shared address space left in the Global areas to load the shared library. (I'll assume said library is 32-bit). This is not the same as virtual memory (swap) or real memory (RAM) -- it is virtual address space of a particular range which is shared across the system.
The Memory Windows white paper gives a reasonable overview of this though it was written for 11.0 [the concepts of the different address space layouts are still good]. If you're on IPF, the Adaptive Address Space white paper is what you want to read:
http://docs.hp.com/en/943/memwn1_4.pdf
http://docs.hp.com/en/8681/aas_white_paper.pdf
Barring being able to either run 64-bit Progress (which doesn't use IPC_SHARE32/MAP_ADDR32 or you're no better off) or using Memory Windows or MPAS to shift SAM or Progress to a different shared area, the only other solution I could think of here would be to run SAM first (and not close it) such that you consume the address space in advance [preventing the Progress DBs from consuming it] or reduce the database shared address space consumption.
The Memory Windows white paper gives a reasonable overview of this though it was written for 11.0 [the concepts of the different address space layouts are still good]. If you're on IPF, the Adaptive Address Space white paper is what you want to read:
http://docs.hp.com/en/943/memwn1_4.pdf
http://docs.hp.com/en/8681/aas_white_paper.pdf
Barring being able to either run 64-bit Progress (which doesn't use IPC_SHARE32/MAP_ADDR32 or you're no better off) or using Memory Windows or MPAS to shift SAM or Progress to a different shared area, the only other solution I could think of here would be to run SAM first (and not close it) such that you consume the address space in advance [preventing the Progress DBs from consuming it] or reduce the database shared address space consumption.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2010 02:43 AM
тАО02-11-2010 02:43 AM
Re: Problems with SAM and shared memory
>JRF: You should look at both 'maxdsiz'
Not hardly. As Don said, when you see "TEXT" it means shared memory, since TEXT isn't "swapped".
>Don: I'll assume said library is 32-bit.
No need to assume, this is a 32 bit dld from the error message. :-)
Not hardly. As Don said, when you see "TEXT" it means shared memory, since TEXT isn't "swapped".
>Don: I'll assume said library is 32-bit.
No need to assume, this is a 32 bit dld from the error message. :-)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP