Oracle Database Parameters [In

1) Every database has an alert log file, to which it logs messages about significant events such as startup and shutdown

1)

background_dump_dest = c:\oracle\admin\COIN\bdump

Every database has an alert log file, to which it logs messages about significant events such as startup, shutdown, log switches, and so forth. Any serious errors are also logged to this file. The background_dump_dest parameter controls the location of the alert log file.

2) The core_dump_dest parameter controls the directory used for the core dump files.

3) The user_dump_dest parameter controls the directory used for trace files created by database users for debugging purposes.

3)

user_dump_dest = c:\oracle\admin\COIN\udump

The user_dump_dest parameter controls the directory used for trace files created by database users for debugging purposes.

4) The db_files parameter controls the amount of memory that Oracle allocates for managing database files.

4)

db_files = 20

The db_files parameter controls the amount of memory that Oracle allocates for managing database files.

5) The compatable parameter allows you to have Oracle mimick the behavior of a previous release of the software.

5)

 
compatible = 8.1.5

The compatable parameter allows you to have Oracle mimick the behavior of a previous release of the software.

6)

6) The process parameter controls the number of server processes that can connect to the instance. This effectively limits the number of database users. This value includes lock processes (LCKn) and job queue processes (SNPn). So if your instance has one lock process, and one job queue process, that leaves room for 28 user processes.

processes =30

The process parameter controls the number of server processes that can connect to the instance. This effectively limits the number of database users. This value includes lock processes (LCKn) and job queue processes (SNPn). So if your instance has one lock process, and one job queue process, that leaves room for 28 user processes.

7)

7) This is a setting that Oracle recommends for all new development

optimizer_mode =choose

This is a setting that Oracle recommends for all new development. It enables the use of the cost-based optimizer, as opposed to the rule-based optimizer. The cost-based optimizer makes decisions about how to execute a query based on its estimate of the actual work that needs to be done. All of Oracle's development efforts are going into enhancing the cost-based optimizer.