topic Re: STOP REASON STRMS in Operating System - HP-UX

STOP REASON STRMS

Bill Slaughter — Fri, 23 Mar 2001 20:54:06 GMT

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

Re: STOP REASON STRMS

James A. Donovan — Fri, 23 Mar 2001 23:53:26 GMT

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?

Re: STOP REASON STRMS

Printaporn_1 — Mon, 26 Mar 2001 03:06:56 GMT

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.

Re: STOP REASON STRMS

Bill Slaughter — Mon, 26 Mar 2001 16:10:32 GMT

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?

Re: STOP REASON STRMS

James A. Donovan — Mon, 26 Mar 2001 18:58:50 GMT

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