- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Mem Checking Help
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
08-14-2001 04:46 AM
08-14-2001 04:46 AM
I have problem on database crash with possible cause of memory (physical) or user process overflow (according to Oracle). While none is identified, i.e. no message indicates OS problem and memory bad, as well as database processes bad, I would see if hp guru have any thought.
dmesg, ipcs, glance, swapinfo are what I have used.
Thanks.
Steven
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2001 04:58 AM
08-14-2001 04:58 AM
SolutionFrom a software (O/S) perspective, you are using the right tools to assess memory utilization.
IF you want to satisfy yourself that your physical memory is good you can view its configuration and error levels with the Support Tools Manager (STM):
# echo "selclass qualifier memory;info;wait;infolog"|cstm > /tmp/meminfo
Remember that single-bit errors are automatically corrected, and should not impact application software. A growing number of single bit errors is a warning to get a memory sim replaced, however.
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2001 04:58 AM
08-14-2001 04:58 AM
Re: Mem Checking Help
SAM-->performance monitor-->system properties-->meory gives the physical memory and swap info
If the database showing process over flow check the nproc in kernel parameter, orcale recommends 4096.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2001 05:49 AM
08-14-2001 05:49 AM
Re: Mem Checking Help
To determine the actual physical memory available on the system.
1. dmesg | grep Physical
(if it hasn't been too long since the machine reboot).
2. /usr/sam/lbin/getmem
(This command has to be run by root, gives the output in MB)
If you are looking for the actual location of the symm and their sizes, one of the easiest ways without reboot the system is to use cstm/mstm/xsm.
-HTH
I am RU
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2001 05:58 AM
08-14-2001 05:58 AM
Re: Mem Checking Help
You can use this C-program which shows you the available memory of you K server.
PJA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2001 06:23 AM
08-14-2001 06:23 AM
Re: Mem Checking Help
For deeper inspection, can you help finding any problem on ninode in kernel parameters? The sar -v result is:
-----------------------
#sar -v 5 5
HP-UX B.10.20 C 9000/879 08/14/01
10:08:50 text-sz ov proc-sz ov inod-sz ov file-sz ov
10:08:55 N/A N/A 197/3620 0 3894/4418 0 814/6779 0
10:09:00 N/A N/A 197/3620 0 3893/4418 0 814/6779 0
10:09:05 N/A N/A 197/3620 0 3895/4418 0 814/6779 0
10:09:10 N/A N/A 197/3620 0 3888/4418 0 814/6779 0
10:09:15 N/A N/A 198/3620 0 3894/4418 0 817/6779 0
---------------------
I see inod-sz is close. Do I have to adjust it from kernel?
Thanks a lot.
Steven
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2001 09:20 AM
08-14-2001 09:20 AM
Re: Mem Checking Help
You can change the kernel parameters is multiple ways. One of the ways is use SAM to change the kernel parameter. Mind you this change will require a reboot of the system.
To find out more information about the various configurable kernel parameters you can look at
http://docs.hp.com/hpux/onlinedocs/os/KCparams.OverviewAll.html
-HTH
I am RU
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2001 07:11 PM
08-14-2001 07:11 PM
Re: Mem Checking Help
The sar -v output you are looking at has only 2 useful values, proc-sz and file-sz. The inode-sz entry is a measure of the cache usage and should normally be 100% after a few hours following a reboot.
The most common parameters that need changing for database servers are:
nproc
nfile
maxdsiz
maxuprc
There are application-specific values such as semaphores but these are usually very explicit from the database manufacturer. Start by doubling nproc, nfile and maxdsiz. maxuprc won't need to be changed unless you have dozens of users logging in as the same username.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2001 01:02 AM
08-15-2001 01:02 AM
Re: Mem Checking Help
When running oracle it helps to check the values of
dynamic cache
dbc_max_pct
Shared memory related values
shmmax
shmmni
shmseg
also check the value of semaphores
SEMMNS
SEMMNI
...BPK...