HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Shared Memory usage per database instance.
Operating System - HP-UX
1833569
Members
4453
Online
110061
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
Forums
Discussions
Discussions
Discussions
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
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
03-20-2001 08:46 AM
03-20-2001 08:46 AM
Shared Memory usage per database instance.
From the following output, I want to know exactly which Oracle database instance is using wich Shared Memory Segment.
It just gives the user names who owns the Shared Memory Segement. So if we have ten different database instances under the same user, it would be difficult to figure out shared memory usage per each database instance.
# ipcs -mob
Shared Memory:
T ID KEY MODE OWNER GROUP NATTCH SEGSZ
m 537 0x441806fc --rw-r--rw- root sys 0 13812
m 3093 0x491806fc --rw-r--rw- root sys 0 16344
m 26 0x411806fc --rw-r--rw- root sys 1 4508024
m 23 0xe0da3354 --rw-r----- ora816 dba 6 36040704
m 20504 0xa122aef0 --rw-r----- ora816 dba 6 81096704
m 11803 0x6a7dfce7 --rw-r----- oracle dba 6 8290304
m 12304 0x55fef118 --rw-r----- oracle dba 7 5439488
IPC status from /dev/kmem as of Mon Mar 19 11:09:21 2001
Thanks.
It just gives the user names who owns the Shared Memory Segement. So if we have ten different database instances under the same user, it would be difficult to figure out shared memory usage per each database instance.
# ipcs -mob
Shared Memory:
T ID KEY MODE OWNER GROUP NATTCH SEGSZ
m 537 0x441806fc --rw-r--rw- root sys 0 13812
m 3093 0x491806fc --rw-r--rw- root sys 0 16344
m 26 0x411806fc --rw-r--rw- root sys 1 4508024
m 23 0xe0da3354 --rw-r----- ora816 dba 6 36040704
m 20504 0xa122aef0 --rw-r----- ora816 dba 6 81096704
m 11803 0x6a7dfce7 --rw-r----- oracle dba 6 8290304
m 12304 0x55fef118 --rw-r----- oracle dba 7 5439488
IPC status from /dev/kmem as of Mon Mar 19 11:09:21 2001
Thanks.
Everyday Learning.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2001 09:03 AM
03-20-2001 09:03 AM
Re: Shared Memory usage per database instance.
The last column shows the segment size of the shared memory allocated. This number is equivalent to your database's SGA size. So all you need to do is know the size of each SGA of each database and you'll know what shared memory segment belongs to each database.
Remember, wherever you go, there you are...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2001 09:08 AM
03-20-2001 09:08 AM
Re: Shared Memory usage per database instance.
From the output you supplied, the only way would be to get the size of the SGA from oracle
svrmgrl (or sqlplus if 8i)
connect internal
show sga
and tie that up to the segment size. That assumes however that no two instances have the same SGA size and that all instances occupy a single shared memory segment.
Another possible way is to use ipcs -am. This will give you a CTIME (Time segment created) column which could be cross referenced with the time that the database was started. This is not foolproof though.
You could also arrange for each instance to be run under a different UNIX user account.
Regards,
John
svrmgrl (or sqlplus if 8i)
connect internal
show sga
and tie that up to the segment size. That assumes however that no two instances have the same SGA size and that all instances occupy a single shared memory segment.
Another possible way is to use ipcs -am. This will give you a CTIME (Time segment created) column which could be cross referenced with the time that the database was started. This is not foolproof though.
You could also arrange for each instance to be run under a different UNIX user account.
Regards,
John
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP