GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Oracle Performance & Memory Leak
Operating System - HP-UX
1850380
Members
2514
Online
104054
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
08-20-2003 12:46 PM
08-20-2003 12:46 PM
Hi,
Running Oracle 8.1.7.4 on HP/UX 11.0, I am experiencing problem with Oracle releasing the memory after the processe(s) are halted.
Before starting the database, the memory usage is 16% of 1.5 Gb of total memory. After starting the database it increases to 25% usage, and max at 95% during an import. Importing a single table takes several hours and the memory usage remains at 72% after halting the processes and shutting down the database, a problem that is only resolved by rebooting.
Thanks for any suggestion in resolving this problem.
Don. O.
Running Oracle 8.1.7.4 on HP/UX 11.0, I am experiencing problem with Oracle releasing the memory after the processe(s) are halted.
Before starting the database, the memory usage is 16% of 1.5 Gb of total memory. After starting the database it increases to 25% usage, and max at 95% during an import. Importing a single table takes several hours and the memory usage remains at 72% after halting the processes and shutting down the database, a problem that is only resolved by rebooting.
Thanks for any suggestion in resolving this problem.
Don. O.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2003 12:53 PM
08-20-2003 12:53 PM
Solution
Hi Don,
You really need to fire up glance or it's GUI version gpm & see what's using the memory.
It's very possible that the disk buffer cache is using up loads of memory. Default for the kernel parameter dbc_max_pct is 50% & *heavy* disk access - as in a huge import - could gobble up every bit of that 50% & it won't be released by the buffer until an application requests it.
HTH,
Jeff
You really need to fire up glance or it's GUI version gpm & see what's using the memory.
It's very possible that the disk buffer cache is using up loads of memory. Default for the kernel parameter dbc_max_pct is 50% & *heavy* disk access - as in a huge import - could gobble up every bit of that 50% & it won't be released by the buffer until an application requests it.
HTH,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2003 04:13 PM
08-20-2003 04:13 PM
Re: Oracle Performance & Memory Leak
I agree with previous response. The buffer cache will most likely be the culrpit.
Set dbc_max_pct to 15, regen the kernel and reboot. Then periodically monitor the memory usage using /usr/contrib/Q4/bin/kmeminfo..
I'm sure you will determine where the memory is going.
Tim.
Set dbc_max_pct to 15, regen the kernel and reboot. Then periodically monitor the memory usage using /usr/contrib/Q4/bin/kmeminfo.
I'm sure you will determine where the memory is going.
Tim.
Yesterday is history, tomorrow is a mystery, today is a gift. That's why it's called the present.
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 2026 Hewlett Packard Enterprise Development LP