1846418 Members
3018 Online
110256 Solutions
New Discussion

STOP REASON STRMS

 
Bill Slaughter
Occasional Contributor

STOP REASON STRMS

Background:
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
4 REPLIES 4
James A. Donovan
Honored Contributor

Re: STOP REASON STRMS

How many connections do you have between your web server and database server at any given time? What is the value of your tcp_conn_request_max tuneable?

# 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?
Remember, wherever you go, there you are...
Printaporn_1
Esteemed Contributor

Re: STOP REASON STRMS

Hi,

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.
enjoy any little thing in my life
Bill Slaughter
Occasional Contributor

Re: STOP REASON STRMS

Thanks for your answer, we added 2 CPU's this weekend and we are not starving for CPU anymore, we still have the bad resonse problem and maybe this is why.

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?



James A. Donovan
Honored Contributor

Re: STOP REASON STRMS

That particular TCP tuneable should take effect immediately. You can set it on reboot by placing the following in the /etc/rc.config.d/nddconf file.

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

Remember, wherever you go, there you are...