Principle: The 55-58% that obtains usable memory is OK.

2, area of PGA program overall situation

A, Sort_area_size is used at what sort takes memory

B, Hash_area_size is used at coming loose to arrange connection, bitmap index

These two parameter are to belong to PGA below blame MTS, do not belong to SGA, it is to be every Session alone distributive, go up in our server besides OS SGA, must consider principle of this two parts: OS uses memory SGA Session*(sort_area_size Hash_area_size 2M)<Total physics RAM had better

Example configuration

The principle that masters basically is, db_block_buffer normally can as far as possible big, shared_pool_size wants measurable, log_buffer arrives to hundreds of K greatly normally 1M is about the same

A, if 512M RAM

Proposal Shared_pool_size = 50M, db_block_buffer* Db_block_size = 200M

B, if 1G RAM

Proposal Shared_pool_size = 100M, db_block_buffer* Db_block_size = 400M

C, if 2G

Proposal Shared_pool_size = 200M, db_block_buffer *db_block_size = 800M

Parameter changes way

Oracle8i:

Basically be to pass modification Oracle to start parameter file to undertake relevant configuration

Parameter file position:

D:oRacleadminDB_Namepfileinit.ora

By above modification above parameter is worth can.

Oracle9i:

Two kinds of means: The first kind is modification Oracle after file of the parameter that start, found server parameter file again through this parameter file

The 2nd kind is to run Oracle to revise a command to undertake modification directly.

SQL>alter System Set Db_cache_size=200M Scope=spfile;

SQL>alter System Set Shared_pool_size=50M Scope=spfile;