- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Continuation of Shared Memory thread
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
09-15-2005 03:03 AM
09-15-2005 03:03 AM
My Sybase DBA's say they are only interested in increasing the shmmax parameter in the kernel, right now it is setting at 536,870,912 and this was set when we had 2g of system memory and now we have 4gig of system memory. They say that I should reset it to the max of 4,294,967,296. Would this be OK to do and what is the meaning of Y below the Dyn, I still have to rebuild the kernel and reboot the system for the change to take place is this correct.
Parameter Current Dyn Planned
=============================================
shmmax 536870912 Y 536870912
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2005 03:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2005 03:14 AM
09-15-2005 03:14 AM
Re: Continuation of Shared Memory thread
kmtune -s shmmax=xxx
kmtune -u shmmax
Dynamically updates shmmax w/out rebuilding the kernel or rebooting.
Check it using
kmtune -l -q shmmax
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2005 03:19 AM
09-15-2005 03:19 AM
Re: Continuation of Shared Memory thread
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2005 03:22 AM
09-15-2005 03:22 AM
Re: Continuation of Shared Memory thread
Why shmmax has nothing to do with how much memory you have on the system. It only has to do how much shared memory you can allocte but if a database need 4 gig of shared memory there is something wrong with the database or the database is to big and you have to consider to go to another database like oracle. and keep in mind that you can't allocted all the memory for shared.
grtz. Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2005 03:22 AM
09-15-2005 03:22 AM
Re: Continuation of Shared Memory thread
This doesn't stop them from snagging all the memmory in the box - it just determines how large the largest single segment can be. This generally helps databases run more efficiently than having their managed memory areas cut up all over the place.
Hopefully though - they won't take this to mean that they can allocate 4G of shared memory, singly, or in pieces.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2005 03:30 AM
09-15-2005 03:30 AM