Skip Headers

Oracle8i Server Installation and Database Administration Guide
Release 3 (8.1.7) for Fujitsu Siemens Computers BS2000/OSD

Part Number A95466-01
Go To Table Of Contents
Go To Index

Go to previous page Go to next page

Initialization Parameters and the
Parameter File

Every time SQL*DBA starts an Oracle Server instance, it uses a set of parameters which specify the characteristics of that particular instance's operation. These parameters are kept in a file, typically named sid.DBS.INIT.ORA.

This appendix shows the parameter file as it is delivered, and lists other parameters that you may need to change to customize the Oracle Server for your system, with their default values.

Please refer to the Oracle8i Reference manual for general descriptions of the parameters listed in this Appendix.

Example Parameter File

The $ORACL817.DEMO.DBS.INIT.ORA parameter file is created upon initial installation and can be edited as a text file.

Unsupported Parameters

A few initialization file parameters, described in the generic documentation are not supported by Oracle8 for BS2000/OSD. These are as follows:

Specifying these parameters in the initialization file will result in an Oracle Server error during startup; the workaround is to remove the offending lines.

Additional Notes on Initialization Parameters


The value of this parameter may be:


This value should always be set so that when multiplied by the value of DB_BLOCK_SIZE the result equals 32K. A result greater than 32K does not improve performance but only wastes buffer space.


If you plan to create a very large database, you should set this value to the maximum of 2044 before creating the database.


This parameter must be set to a number greater than 0 if distributed transactions occur on your instance.


The value of this parameter should always be set so that when multiplied by the value of SF_PBLKSIZE the result equals 32K.


Even if this parameter is set to TRUE, times for physical read/writes are not collected in all cases. This is because the current optimized input/output implementation makes it hard to provide realistic times.


This parameter can indicate a pubset (e.g. LOG_ARCHIVE_DEST=:PUB1:) in order to store all archived redo logs on special media.

Go to previous page Go to next page
Copyright © 2001 Oracle Corporation.

All Rights Reserved.
Go To Table Of Contents
Go To Index