Ansicht
Dokumentation

OS-dependent parameters: init.ora
Tip-No.: 573 ( INFO573 )

Short text

OS-dependent parameters: init.ora
Tip-No.: 573

Symptom

Database performance.

Cause

Changing disk/file system configuration.

Solution

**********************************************************************
* Operating System-dependent init.ora parameters *
**********************************************************************

1. General OS-dependent parameters

All parameters that set up paths/files must be modified depending
on the operating system. These parameters may be affected by changes
to the disk/file system configuration.


Parameter Sap-ERecommendation

-------------------------------------------------------------

init_sql_files
control_files Mirror in data directories
log_archive_dest ?/saparch soft-link to own disk
background_dump_dest ?/saptrace/background
user_dump_dest ?/saptrace/usertrace

In ?/saptrace/background, the database traces and the alert_.log
are written.


Comments:

- control_files is a purely mirror parameter. Recommendation:
A control file should be held in ORACLE_HOME/dbs as default.
- init_sql_files is only used when first creating the DB.
- log_archive_dest
The DB must be in ARCHIVELOG mode and log_archiv_start must have the
value "True". The parameter indicates where the archive process writes
the Offline-Redo-Logs to. In addition to the path name, the beginning
of the name of the archive file must be specified.
e.g. Log_archive_dest = /usr/ora/C11/saparch/C11arch
ecreatesin ?/saparch dthe fles
C11arch





2. UNIX-specific parameters

Parameter Default SAP-Recommendation

------------------------------------------------------

db_writers 1 = ANo. of disks + 1, to which the DB
didats is distribute





3. VMS-specific parameters

Comments:

- control_files:
In VMS, 2 logicals are created at installation, that point to "one"
control-file. The control file not actual physically mirrored in this
way, as is incorrectly claimed in some ORACLE documentation manuals.