- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- STOP REASON STRMS
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
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
03-23-2001 12:54 PM
03-23-2001 12:54 PM
STOP REASON STRMS
R380 - Oracle Web Server (V3 and V4) running on an R380
K580 - Oracle Database Server (V 8.0.5.1)
Problem:
We are experiencing a CPU load and I see alot of database background processes with a stop reason of STRMS, some are PRI.
Is there some tuneable Kernal parameter that can help this STRMS stop reason?
Our K580 is (at times) 100% CPU and the R380 never gets to 50%
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2001 03:53 PM
03-23-2001 03:53 PM
Re: STOP REASON STRMS
# ndd -get /dev/tcp tcp_conn_request_max
If it's the default of 20 and you are establishing a lot of connections, try increasing it to something like 200.
Are you using MTS for your Oracle listener? If so what are your init.ora parameters set to for MTS?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2001 07:06 PM
03-25-2001 07:06 PM
Re: STOP REASON STRMS
I use to face this kind of problem before with my oracle workflow process , the situation is
oracle sparwn many process , and with all wait at stream.
the solution come from Oracle by they have option to run the process w/o parallel.
That mean it will not sprawn too many processes.
the processing time reduce from 29hrs to 6sec !!!
please consider finding info from Oracle site also.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2001 08:10 AM
03-26-2001 08:10 AM
Re: STOP REASON STRMS
ndd -get /dev/tcp tcp_conn_request_max
returns the default 20
I increased it today durring our stress test.
It seemd to be in effect immed? or do I need to bounce listeners?
can we set that at reboot in a config file?
ndd.conf?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2001 10:58 AM
03-26-2001 10:58 AM
Re: STOP REASON STRMS
TRANSPORT_NAME[1]=tcp
NDD_NAME[1]=tcp_conn_request_max
NDD_VALUE[1]=200 (or whatever value you find appropriate).
You can find much more information on TCP stack tuning from http://www.rvs.uni-hannover.de/people/voeckler/tune/EN/tune.html
For Oracle tuning, hopefully you have support and access to Metalink, where you can find a lot of good info on tuning Oracle. http://metalink.oracle.com