Re: oracle processes exceeding 2000

We have a similar problem (Sun Solaris 2.6, Oracle 8.1.5 EE). If the IIS of the web server terminates a session it is marked killed but is never removed.

Workaround: kill the dispatcher processes that are listed in v$circuit by "kill -9 PID". They are restarted automatically. Reason: the process is waiting for something of the dispatcher.

Only drawback: all sessions that have their circuit served by that dispatcher dies.

Martin

sreedhar wrote:
>
> we have a sun e4500 machine, with 4gigs RAM. only one instance of
> oracle runs on this machine with no other applications. for some reason
> due to haevy traffic we are running out of sessions. currently the
> processes parameter is set to 1600. but we need more number of oracle
> sessions to cater to the kind of traffic we are getting. but i get the
> the following errors when i increase the processes parameter
>
> ORA-27145: insufficient resources for requested number of processes
> ORA-27300: OS system dependent operation:semids_per_proc failed with
> status: 0
> ORA-27301: OS failure message: Error 0
> ORA-27302: failure occurred at: sskgpwcr2
> ORA-27303: additional information: semids = 170, maxprocs = 2200
>
> we have 4GB of RAM.
> the following are the init.ora parameters
>
> instance_name = SREE
>
> service_names = SREE
>
> control_files = ('/sreedhar/SREE_cf1.ora','/sreedhar/SREE_cf2.ora')
>
> db_file_multiblock_read_count = 64
>
> db_block_buffers = 32768
>
> shared_pool_size = 524288000
>
> java_pool_size = 167772160
>
> log_checkpoint_interval = 10000
> log_checkpoint_timeout = 1800
>
> processes = 2200
> #processes = 256
>
> log_buffer = 163840
>
> # audit_trail = false # if you want auditing
> # timed_statistics = false # if you want timed statistics
> max_dump_file_size = 10000 # limit trace file size to 5M each
>
> ##### For archiving if enabled #####
> #log_archive_start = true
> #log_archive_dest = /oracle8i/d097/oradata/SREE/arch
> #log_archive_format = mavp_%t_%s.arc
> # If using private rollback segments, place lines of the following
> # form in each of your instance-specific init.ora files:
> #rollback_segments = (rsa01, rsa02, rsa03, rsa04, rsa05, rsa06, rsa07,
> rsa08, rsa09, rsa10, rsa11, rsa12)
>
> # Global Naming -- enforce that a dblink has same name as the db it
> connects to
> # global_names = false
>
> # Uncomment the following line if you wish to enable the Oracle Trace
> product
> # to trace server activity. This enables scheduling of server
> collections
> # from the Oracle Enterprise Manager Console.
> # Also, if the oracle_trace_collection_name parameter is non-null,
> # every session will write to the named collection, as well as enabling
> you
> # to schedule future collections from the console.
> os_authent_prefix = ""
>
> # The following parameters are needed for the Advanced Replication
> Option
> job_queue_processes = 0
> job_queue_interval = 60
> distributed_transactions = 10
> open_links = 4
>
> sort_area_size=262144
> sort_area_retained_size=65536
>
> #mts_dispatchers = "(PROTOCOL=TCP)
> (PRE=oracle.aurora.server.SGiopServer)"
> # Uncomment the following line when your listener is configured for SSL
> # (listener.ora and sqlnet.ora)
> mts_dispatchers = "(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))(DIS=1)(SES=254)
> (CON=254)(TIC=15)(POO=NO)(MUL=NO)(LIS=(ADDRESS_LIST=(ADDRESS
> =(PROTOCOL=IPC)(KEY=PNPKEY))(ADDRESS=(PROTOCOL=TCP)(HOST=127.0.0.1)
> (PORT=1521))(ADDRESS=(PROTOCOL=IPC)(KEY=SREE))))(PRE=oracle.auror
> a.server.SGiopServer)"
>
> #mts_service = SREE
> #mts_max_servers = 20
> mts_servers = 1
> compatible = "8.1.0"
>
> OPEN_CURSORS = 6144
>
> shared memory segments
> **********************
> set shmsys:shminfo_shmmax=4294967295
> set shmsys:shminfo_shmmni=100
> set shmsys:shminfo_shmmin=1
> set shmsys:shminfo_shmseg=64
> set semsys:seminfo_semmns=4800
> set semsys:seminfo_semmni=5120
>
> thanks a lot for your help.
>
> --
> Sreedhar
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Wed Apr 26 2000 - 00:00:00 CDT