Re: 65MB per Oracle Connection?

I did not know that open_cursors are allocated on a per session basis. My understanding is that it is the maximum number of non-committed cursors (including updates, inserts, deletes and selects) that any one process can have. I'll try decreasing the number and give it a try!

Thanks

Matt Kolenda
Sybrand Bakker <postbus_at_sybrandb.demon.nl> wrote in message news:959924278.8321.0.pluto.d4ee154e_at_news.demon.nl...
> Your open_cursors is way too big (and memory is allocated on beforehand
 *per
> session*), 500 or 1000 should be more than sufficient.
> Also your shared pool is too big.
>
> Hth,
>
> Sybrand Bakker, Oracle DBA
>
> Matt Kolenda <mkolenda_at_netabacus.com> schreef in berichtnieuws
> sjdgu2mi5ri149_at_corp.supernews.com...
> > I am running Oracle on NT 4 SP5. Every dedicated server process takes
 65MB
> > of memory! Does anyone know why so much memory is being allocated per
> > process? Any help would be appreciated! Here is the error message I
 get:
> >
> > ORA-04030: out of process memory when trying to allocate 62500000 bytes
> > (session heap,First curdef allocation)
> >
> >
> > Thanks
> >
> > Matt
> >
> > Here are my init.ora parameters:
> > db_name = PC06
> > instance_name = PC06
> > service_names = PC06.NETABACUS
> > db_files = 1024
> > open_cursors=999999999
> > control_files = ("D:\Oracle\oradata\PC06\control01.ctl",
> > "D:\Oracle\oradata\PC06\control02.ctl")
> > db_file_multiblock_read_count = 8
> > db_block_buffers = 600
> > shared_pool_size = 80000000
> > log_checkpoint_interval = 10000
> > log_checkpoint_timeout = 1800
> > processes = 50
> > parallel_max_servers = 5
> > log_buffer = 32768
> > #audit_trail = true # if you want auditing
> > #timed_statistics = true # if you want timed statistics
> > max_dump_file_size = 10240 # limit trace file size to 5M each
> > # Global Naming -- enforce that a dblink has same name as the db it
 connects
> > to
> > global_names = true
> > # 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.
> > # oracle_trace_enable = true
> > oracle_trace_collection_name = ""
> > # define directories to store trace and alert files
> > background_dump_dest = D:\Oracle\admin\PC06\bdump
> > user_dump_dest = D:\Oracle\admin\PC06\udump
> > db_block_size = 4096
> > remote_login_passwordfile = exclusive
> > os_authent_prefix = ""
> > distributed_transactions = 10
> > compatible = 8.1.0
> > sort_area_size = 66560
> >
> >
> >
> >
>
>
>
Received on Fri Jun 02 2000 - 00:00:00 CDT