User`s guide

Additional Notes on Initialization Parameters
C-2 Oracle Database Installation and Administration Guide
value for this parameter is the current BS2000 user ID of the Oracle background
processes. You can specify a prefix for the trace and alert files in the following format:
BACKGROUND_DUMP_DEST=BDD
You can also specify a POSIX directory for this parameter, if you have enabled the
POSIX subsystem.
Note: This parameter is ignored by the new diagnosability
infrastructure introduced in Oracle Database 11g, which places trace
and core files in a location controlled by the
DIAGNOSTIC_DEST
initialization parameter
C.3.2 USER_DUMP_DEST
This parameter specifies the path name (directory or prefix) where the server writes
debugging trace files on behalf of a user process. The default value for this parameter
is the current BS2000 user ID of the Oracle Database processes.
You can specify a prefix for the trace files as follows:
USER_DUMP_DEST=UDD
You can also specify a POSIX directory for this parameter, if you have enabled the
POSIX subsystem.
Note: This parameter is ignored by the new diagnosability
infrastructure introduced in Oracle Database 11g, which places trace
and core files in a location controlled by the
DIAGNOSTIC_DEST
initialization parameter
C.3.3 AUDIT_FILE_DEST
This parameter specifies the path name (directory or prefix) into which the audit trail
is written when the
AUDIT_TRAIL initialization parameter is set to OS . Usually this
value is used as a prefix for BS2000 file names. You can also specify a POSIX directory
for this parameter, if you have enabled the POSIX subsystem. The default value for
this parameter is
SID . ADUMP. The name of the audit files is tsn-seqno . AUD , where
tsn is the task sequence number of the current task and seqno is a sequence number.
Bear in mind that regardless of whether database auditing is enabled, Oracle/BS2000
always records some database-related actions into the operating system audit file:
instance startup, shutdown and connections with administrator privileges.
C.3.4 DB_BLOCK_SIZE
This parameter can have one of the following values:
■ 2K, 4K, 6K, 8K, 16K, 32K, if you use BS2000 2K pubset format.
■ 4K, 8K, 16K, 32K, if you use BS2000 4K pubset format.
C.3.5 DB_FILE_MULTIBLOCK_READ_COUNT
The default value of this parameter is 64K/ DB_BLOCK_SIZE , which is also the
maximum value. Setting this parameter beyond this limit has no effect.