Parameter Descriptions

Most initialization parameter values are global (on a database-wide basis), not per user, unless otherwise specified.

For more information, see your system release bulletins or other operating system-specific Oracle documentation.

ALWAYS_ANTI_JOIN

AUDIT_TRAIL

The values TRUE and FALSE are also supported for backward compatibility. TRUE is equivalent to DB, and FALSE is equivalent to NONE.

The SQL AUDIT statements can set auditing options regardless of the setting of this parameter.

For more information, see the Oracle7 Server Administrator's Guide.

AUTO_MOUNTING

For more information, see the Trusted Oracle7 Server Administrator's Guide.

BACKGROUND_DUMP_DEST

An ALERT file in the directory specified by BACKGROUND_DUMP_DEST logs significant database events and messages. Anything that affects the database instance-wide or globally is recorded here. This file records all instance startups and shutdowns, messages to the operator console, and errors that cause trace files to be written. It also records every CREATE, ALTER, or DROP operation on a database, tablespace, or rollback segment.

The ALERT file is a normal text file. Its filename is operating system specific. For platforms that support multiple instances, it takes the form ALERT_sid.LOG. This file grows slowly, but without limit, so the DBA may wish to delete it periodically. The file may be deleted even when the database is running.

For more information, see the Oracle7 Server Administrator's Guide.

See your operating system-specific Oracle documentation for the default value.

BLANK_TRIMMING

CACHE_SIZE_THRESHOLD

Default value:	0.1*DB_BLOCK_BUFFERS
Multiple instances:	should have the same value

Specifies the maximum size of a cached partition of a table split among the caches of multiple instances. If the partition is larger than the value of this parameter, the table is not split among the instances' caches. The default value of this parameter is 1/10 the number of database blocks in the buffer cache.

For more information, see Oracle7 Parallel Server Concepts & Administration.

CHECKPOINT_PROCESS

Note: Adjust all calculations that depend on the number of background processes to allow for the CKPT process. For example, increase the value of the PROCESSES parameter by one, and increase the values of other parameters whose default values are derived from PROCESSES if you do not use their default values.

Additional Information: For more information, see SESSIONS .

CLEANUP_ROLLBACK_ENTRIES

For more information, see the Oracle7 Server Administrator's Guide.

CLOSE_CACHED_OPEN_CURSORS

A value of TRUE causes open cursors to be closed at each COMMIT or ROLLBACK. The cursor can then be reopened as needed. If cursors are rarely reused, setting the parameter to TRUE frees memory used by the cursor when the cursor is no longer in use.

COMMIT_POINT_STRENGTH

The commit point site stores information about the status of transactions. Other computers in a distributed transaction require this information, so it is desirable to have machines that are always available as commit point sites. Therefore, set COMMIT_POINT_STRENGTH to a higher value on your more available machines.

For more information about two-phase commit, see the Oracle7 Server Concepts and Oracle7 Server Distributed Systems, Volume I.

See also your operating system-specific Oracle documentation for the default value.

COMPATIBLE

When using the standby database and feature, this parameter must have the same value on the primary and standby databases, and the value must be 7.3.0.0.0 or higher.

This parameter allows you to immediately take advantage of the maintenance improvements of a new release in your production systems without testing the new functionality in your environment.

The default value is the earliest release with which compatibility can be guaranteed.

For more information, see Oracle7 Server Migration.

See also your operating system specific Oracle documentation for the default value.

COMPATIBLE_NO_RECOVERY

The default value is the earliest version with which compatibility can be guaranteed. In some cases, this version may be earlier than the version specifiable with the COMPATIBLE parameter.

For more information, see the Oracle7 Server Migration manual.

See also your operating system-specific Oracle documentation for the default value.

CONTROL_FILES

For more information, see the Oracle7 Server Administrator's Guide.

CPU_COUNT

Warning: On most platforms Oracle automatically sets the value of CPU_COUNT to the number of CPUs available to your Oracle instance. Do not change the value of CPU_COUNT.

If there is heavy contention for latches, change the value of LOG_SIMULTANEOUS_COPIES to twice the number of CPUs you have. Do not change the value of CPU_COUNT.

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for information about this parameter.

CURSOR_SPACE_FOR_TIME

Shared SQL areas are kept pinned in the shared pool when this parameter's value is TRUE. As a result, shared SQL areas are not aged out of the pool as long as there is an open cursor that references them. Because each active cursor's SQL area is present in memory, execution is faster. Because the shared SQL areas never leave memory while they are in use, however, you should set this parameter to TRUE only when the shared pool is large enough to hold all cursors simultaneously.

Setting this parameter to TRUE also retains the private SQL area allocated for each cursor between executes instead of discarding it after cursor execution. This saves cursor allocation and initialization time.

For more information, see the Oracle7 Server Concepts manual.

DB_BLOCK_BUFFERS

For more information, see Oracle7 Server Concepts.

See also your operating system-specific Oracle documentation for the default value.

DB_BLOCK_CHECKPOINT_BATCH

In general, DB_BLOCK_CHECKPOINT_BATCH should be set to a value that allows the checkpoint to complete before the next checkpoint log switch takes place. If a checkpoint log switch takes place every 20 minutes, then this parameter should be set to a value that allows check pointing to complete within 20 minutes.

Setting DB_BLOCK_CHECKPOINT_BATCH to zero causes the default value to be used. A value larger than the maximum can be specified, but its effect is the same as specifying the maximum.

For more information, see Oracle7 Server Concepts.

DB_BLOCK_CHECKSUM

Warning: Setting DB_BLOCK_CHECKSUM to TRUE can cause a performance overhead. Set this parameter to TRUE only under the advice of Oracle Support personnel to diagnose data corruption problems.

For more information, see the Oracle7 Server Administrator's Guide.

DB_BLOCK_LRU_EXTENDED_STATISTICS

When compiling statistics for the X$KCBRBH table, set this parameter to the maximum size you want to use to evaluate the buffer cache. It should be set to zero otherwise. (Although you can set this value very high, it is not practical to set it to a size beyond your system's memory capacity.)

For more information, see the Oracle7 Server Administrator's Guide.

DB_BLOCK_LRU_LATCHES

DB_BLOCK_LRU_STATISTICS

Set this parameter to TRUE when you want to compile statistics for the X$KCBCBH table; otherwise, leave it set to FALSE. This parameter is a tuning tool and should be set to FALSE during normal operation.

For more information, see Oracle7 Server Administrator's Guide and Oracle7 Server Tuning.

DB_BLOCK_SIZE

This parameter affects the maximum value of the FREELISTS storage parameter for tables and indexes.

For more information block size, see Oracle7 Server Concepts.

See also your operating system-specific Oracle documentation for the default value.

DB_DOMAIN

For example, this parameter allows one department to create a database without worrying that it might have the same name as a database created by another department. If one sales department's DB_DOMAIN = "JAPAN.ACME.COM", then their "SALES" database (SALES.JAPAN.ACME.COM) is uniquely distinguished from another database with DB_NAME = "SALES" but with DB_DOMAIN = "US.ACME.COM".

The following characters are valid in a database domain name:

• alphabetic characters

• numbers

• underscore (_)

• sharp (#)

DB_FILES

Reduce the value only if you need SGA space and do not anticipate having more database files.

DB_FILES is similar to the MAXDATAFILES argument for the CREATE DATABASE statement, which sets the absolute maximum number of datafiles at database creation. An instance cannot mount a database unless DB_FILES is equal to or greater than MAXDATAFILES for that database. Greater values are only useful for instances that mount different databases at different times.

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the default value.

DB_FILE_MULTIBLOCK_READ_COUNT

The actual maximums vary by operating system; they are always less than the operating system's maximum I/O size expressed as Oracle blocks (max_IO_size/DB_BLOCK_SIZE), and can never be larger than DB_BLOCK_BUFFERS/4.

For information on the optimizer, see Oracle7 Server Tuning.

See also your operating system-specific Oracle documentation for the default value.

DB_FILE_SIMULTANEOUS_WRITES

If the operating system supports only one write per device and cannot combine writes to adjacent blocks, then the value should be 1. Though the value has no maximum because DBWR writes blocks in groups, it is not useful to use a value larger than 24.

For more information, see Oracle7 Server Concepts.

See also your operating system-specific Oracle documentation for the default value.

DB_FILE_STANDBY_NAME_CONVERT

Set the value of this parameter to two strings: the first string is the pattern found in the data file names on the primary database; the second string is the pattern found in the data file names on the standby database.

DB_MOUNT_MODE

For more information, see the Trusted Oracle7 Server Administrator's Guide.

DB_NAME

If not specified, a database name must appear on either the STARTUP or the ALTER DATABASE MOUNT command line.

The following are valid characters in a database name:

• alphabetic characters

• numbers

• underscore (_)

• sharp (#)

• dollar symbol ($)

Lowercase characters are not treated with special significance. They are considered the same as their uppercase counterparts.

For more information, see the Oracle7 Server Administrator's Guide.

DBLINK_ENCRYPT_LOGIN

For more information, see the Oracle7 Server Administrator's Guide.

DELAYED_LOGGING_BLOCK_CLEANOUTS

When Oracle commits a transaction, each block that the transaction changed is not immediately marked with the commit time. This is done later, upon demand--when the block is read or updated. This is called block cleanout.

When block cleanout is done during an update to a current block, the cleanout changes and the redo records are piggybacked with those of the update. In previous releases, when block cleanout was needed during a read to a current block, extra cleanout redo records were generated and the block was dirtied. This has been changed.

As of release 7.3, when a transaction commits, all blocks changed by the transaction are cleaned out immediately. This cleanout performed at commit time is a "fast version" which does not generate redo log records (delayed logging) and does not repin the block. Most blocks will be cleaned out in this way, with the exception of blocks changed by long running transactions.

During queries, therefore, the data block's transaction information is normally up-to-date and the frequency of needing block cleanout is much reduced. Regular block cleanouts are still needed when querying a block where the transactions are still truly active, or when querying a block which was not cleaned out during commit.

Note: As of Oracle Server release 7.3, performing a SELECT COUNT (*) no longer does a block cleanout.

During changes (INSERT, DELETE, UPDATE), the cleanout redo log records are generated and piggyback with the redo of the changes.

DISCRETE_TRANSACTIONS_ENABLED

For more information about supplied packages, see the Oracle7 Server Application Developer's Guide.

DISTRIBUTED_LOCK_TIMEOUT

For more information on data concurrency, see Oracle7 Server Concepts and Oracle7 Server Distributed Systems, Volume I.

DISTRIBUTED_RECOVERY_CONNECTION_HOLD_TIME

For more information, see the Oracle7 Server Administrator's Guide and Oracle7 Server Distributed Systems, Volume I.

DISTRIBUTED_TRANSACTIONS

If network failures are occurring at an abnormally high rate, causing many in-doubt transactions, you may want to decrease this parameter's value temporarily. This limits the number of concurrent distributed transactions, which then reduces the number of in-doubt transactions. Thus, the amount of blocked data and possible heuristic decision making (because of in-doubt transactions) is reduced.

If DISTRIBUTED_TRANSACTIONS is set to 0, no distributed transactions are allowed for the database. The recoverer (RECO) process also does not start when the instance starts up.

For more information, see the Oracle7 Server Administrator's Guide and Oracle7 Server Distributed Systems, Volume I.

See also your operating system-specific Oracle documentation for the default value.

DML_LOCKS

The default value assumes an average of 4 tables referenced per transaction. For some systems, this value may not be enough.

If the value is set to 0, enqueues are disabled and performance is slightly increased. However, you cannot use DROP TABLE, CREATE INDEX, or explicit lock statements such as LOCK TABLE IN EXCLUSIVE MODE. If the value is set to 0 on one instance, it must be set to 0 on all instances of an Oracle Parallel Server.

For more information on data concurrency, see Oracle7 Server Concepts and Oracle7 Server Distributed Systems, Volume I.

ENQUEUE_RESOURCES

Enqueues are platform-specific locking mechanisms. An enqueue allows the user to store a value in the lock, that is, the mode in which the lock is requested. The operating system lock manager keeps track of the resources locked. If a process cannot be granted the lock because it is incompatible with the mode requested and the lock is requested with wait, the operating system puts the requesting process on a wait queue which is serviced FIFO (first-in, first-out).

One difference between enqueues and latches is that in latches there is no ordered queue of waiters as there is in enqueues. Latch waiters may either use timers to wake up and retry or spin (only in multiprocessors). Since all waiters are concurrently retrying (depending on the scheduler), anyone might get the latch and conceivably the first one to try might be the last one to get the latch.

ENQUEUE_RESOURCES sets the number of resources that can be locked by the lock manager. The default value of ENQUEUE_RESOURCES is derived from the SESSIONS parameter and should be adequate, as long as DML_LOCKS + 20 is less than ENQUEUE_RESOURCES. For three or fewer sessions, the default value is 20. For 4 to 10 sessions, the default value is ((SESSIONS - 3) * 5) + 20; and for more than 10 sessions, it is ((SESSIONS - 10) * 2) + 55.

If you explicitly set ENQUEUE_RESOURCES to a value higher than DML_LOCKS + 20, then the value you provide is used.

If there are many tables, the value may be increased. Allow one per resource (regardless of the number of sessions or cursors using that resource), not one per lock.

For more information on data concurrency, see Oracle7 Server Concepts and Oracle7 Server Distributed Systems, Volume I.

EVENT

EVENT is used to debug the system. This parameter should not usually be altered except at the direction of Oracle technical support personnel.

FIXED_DATE

For more information on datatypes, see Oracle7 Server Concepts.

GC_DB_LOCKS

Default value:	0
Range of values:	1 - unlimited (depending on available memory and operating system)
OK to change?	yes
Multiple instances:	must have identical values

The total number of PCM locks covering data blocks cached in the multiple SGAs of a parallel server.

The value of GC_DB_LOCKS must be greater (by at least 1) than the sum of the locks specified with the GC_FILES_TO_LOCKS initialization parameter.

GC_DB_LOCKS is always rounded up to the next prime number to ensure that PCM locks are available for datafiles not specified in GC_FILES_TO_LOCKS. For example, if GC_DB_LOCKS has a value of 1000, then 1009 PCM locks are available. New datafiles added while the parallel server is running are covered by the extra nine PCM locks.

This parameter has no effect on an instance running in exclusive mode.

For more information, see Oracle7 Parallel Server Concepts & Administration.

GC_DEFAULT_LOCKS

For more information, see Oracle7 Parallel Server Concepts & Administration.

GC_FILES_TO_LOCKS

Default value:	NULL
OK to change?	yes
Multiple instances:	must have identical values

This parameter controls the mapping of PCM locks to datafiles. To avoid performance problems, you should always change GC_FILES_TO_LOCKS when the size of datafiles change or new datafiles are added. This requires that you shutdown and restart your parallel server.

GC_FILES_TO_LOCKS has the following syntax:

GC_FILES_TO_LOCKS = "{file_list=lock_count[!blocks][EACH]}[:]..." 

where file_list is one or more datafiles listed by their file numbers, or ranges of file numbers, with comma separators:

filenumber[-filenumber][,filenumber[-filenumber]]... 

and lock_count is the number of PCM locks assigned to file_list. A colon (:) separates each clause that assigns a number of PCM locks to file_list.

The optional parameter blocks, with the "!" separator, specifies the number of contiguous blocks covered by one lock, if it covers multiple blocks; the default value is 1. EACH specifies that each datafile in file_list is assigned a separate set of lock_count PCM locks. Spaces are not allowed within the quotation marks.

If the number of PCM locks specified for file_list is less than the actual number of data blocks in the datafiles, then some PCM locks will cover more datablocks than specified by lock_count!blocksEACH.

The value of the GC_DB_LOCKS parameter must be greater (by at least 1) than the sum of lock_count for all datafiles specified. The excess PCM locks are assigned to any datafiles not specified in GC_FILES_TO_LOCKS.

To find the correspondence between filenames and file numbers, query the data dictionary view DBA_DATA_FILES.

This parameter has no effect on an instance running in exclusive mode.

For more information, see Oracle7 Parallel Server Concepts & Administration.

GC_LCK_PROCS

Default value:	1 (ignored when the database is mounted in exclusive mode)
Range of values:	1 - 10, or 0 for a single instance running in exclusive mode
OK to change?	yes (1 is usually sufficient)
Multiple instances:	must have identical values

The number of background lock processes (LCK0 through LCK9) for an instance in a parallel server. The default of 1 is normally sufficient, but you can increase the value if the distributed lock request rate saturates the lock processes. (Lock requests are asynchronous, but a request is blocked until it knows if the lock can be granted.)

Increase the value of the PROCESSES parameter by one for each LCKn process, and increase the values of other parameters whose default values are derived from PROCESSES if you do not use their defaults.

This parameter has no effect on an instance running in exclusive mode.

For more information, see Oracle7 Parallel Server Concepts & Administration.

GC_RELEASABLE_LOCKS

For more information, see Oracle7 Parallel Server Concepts & Administration.

GC_ROLLBACK_LOCKS

Default value:	20
OK to change?	yes
Multiple instances:	must have identical values

For each rollback segment, the number of distributed locks available for simultaneously modified rollback segment blocks. The default is adequate for most applications.

These distributed locks are acquired in exclusive mode by the instance that acquires the rollback segment. They are used to force the instance to write rollback segment blocks to disk when another instance needs a read-consistent version of a block.

This parameter has no effect on an instance running in exclusive mode.

For more information, see Oracle7 Parallel Server Concepts & Administration.

GC_ROLLBACK_SEGMENTS

Default value:	20
OK to change?	yes
Multiple instances:	must have identical values

The maximum number of rollback segments system wide. Set this parameter to the total number of rollback segments acquired by all instances in a parallel server, including the SYSTEM rollback segment. To allow for additional instances in the future, or additional rollback segments for the current instances, you can set it to a higher value.

Each rollback segment requires one distributed lock, specified by this parameter, in addition to the number specified by the GC_ROLLBACK_LOCKS parameter. The total number of distributed locks for rollback segments is:

(GC_ROLLBACK_SEGMENTS * (GC_ROLLBACK_LOCKS + 1 )) 

This parameter has no effect on an instance running in exclusive mode.

For more information, see Oracle7 Parallel Server Concepts & Administration.

GC_SAVE_ROLLBACK_LOCKS

Default value:	20
OK to change?	yes
Multiple instances:	must have identical values

This initialization parameter reserves distributed locks for deferred rollback segments, which contain rollback entries for transactions in tablespaces that were taken offline.

The default is adequate for one or two instances but should be increased to 10 per instance for more instances if you need to take tablespaces offline while Oracle is running in parallel mode.

This parameter has no effect on an instance running in exclusive mode.

For more information, see Oracle7 Parallel Server Concepts & Administration.

GC_SEGMENTS

Default value:	10
OK to change?	yes
Multiple instances:	must have identical values

The maximum number of segments system wide that may have space management activities performed simultaneously by different instances. The default is adequate for most applications. If tables acquire new extents frequently, you can increase the value to two or three times the number of tables that different instances extend simultaneously.

Each segment that undergoes simultaneous space management in a parallel server requires approximately nine distributed locks dedicated to coordinating space management activities. The total number of distributed locks reserved by this parameter is therefore approximately (9 * GC_SEGMENTS).

This parameter has no effect on an instance running in exclusive mode.

For more information, see Oracle7 Parallel Server Concepts & Administration.

GC_TABLESPACES

Default value:	5
OK to change?	yes
Multiple instances:	must have identical values

The maximum number of tablespaces in a parallel server that can be brought from offline to online (or vice versa) concurrently.

For more information, see Oracle7 Parallel Server Concepts & Administration.

GLOBAL_NAMES

For more information, see the Oracle7 Server Administrator's Guide.

HASH_AREA_SIZE

You can change the value of this parameter without shutting down your Oracle instance by using the ALTER SESSION command.

HASH_JOIN_ENABLED

You can change the value of this parameter without shutting down your Oracle instance by using the ALTER SESSION command.

HASH_MULTIBLOCK_IO_COUNT

The value of DB_BLOCK_SIZE multiplied by the value of HASH_MULTIBLOCK_IO_COUNT should be less than 64 KB.

This parameter strongly affects performance because it controls the number of partitions into which the input is divided. If you change the parameter value, make sure that the following formula remains true:

R / M < Po2(M/C)

R = sizeof(left input to the join)

M = HASH_AREA_SIZE * 0.9

Po2(n) = largest power of 2 that is smaller than n

C = HASH_MULTIBLOCK_IO_COUNT * DB_BLOCK_SIZE

IFILE

IFILE = COMMON.ORA

You can have up to three levels of nesting. In this example, the file COMMON.ORA could contain a second IFILE parameter for the file COMMON2.ORA, which could contain a third IFILE parameter for the file GCPARMS.ORA. You can also include multiple parameter files in one parameter file by listing IFILE several times with different values:

IFILE = DBPARMS.ORA

IFILE = GCPARMS.ORA

IFILE = LOGPARMS.ORA

For more information, see the Oracle7 Server Administrator's Guide.

INIT_SQL_FILES

INSTANCE_NUMBER

Default value:	lowest available number (depends on instance startup order and on the INSTANCE_NUMBER values assigned to other instances)
Range of values:	1 - O/S dependent
OK to change?	yes (can be specified in both parallel and exclusive modes)
Multiple instances:	if specified, instances must have different values

This parameter can be specified in parallel mode or exclusive mode. It specifies a unique number that maps the instance to one group of free space lists for each table created with storage option FREELIST GROUPS.

The INSTANCE option of the ALTER TABLE ALLOCATE EXTENT statement assigns an extent to a particular group of free lists. If you set INSTANCE_NUMBER to the value specified for the INSTANCE option, the instance uses that extent for inserts and updates that expand rows.

For more information, see Oracle7 Parallel Server Concepts & Administration.

JOB_QUEUE_INTERVAL

This parameter replaces the SNAPSHOT_REFRESH_INTERVAL parameter.

JOB_QUEUE_PROCESSES

This parameter replaces the SNAPSHOT_REFRESH_PROCESS parameter.

LABEL_CACHE_SIZE

For more information, see the Trusted Oracle7 Server Administrator's Guide.

LICENSE_MAX_SESSIONS

A zero value indicates that concurrent usage (session) licensing is not enforced. If you set this parameter to a non-zero number, you may also want to set LICENSE_SESSIONS_WARNING.

Concurrent usage licensing and user licensing should not both be enabled. Either LICENSE_MAX_SESSIONS or LICENSE_MAX_USERS should always be zero.

Multiple instances can have different values, but the total for all instances mounting a database should be less than or equal to the total number of sessions licensed for that database.

For more information, see the Oracle7 Server Administrator's Guide.

LICENSE_MAX_USERS

Concurrent usage (session) licensing and user licensing should not both be enabled. Either LICENSE_MAX_SESSIONS or LICENSE_MAX_USERS, or both, should be zero.

If different instances specify different values for this parameter, the value of the first instance to mount the database takes precedence.

For more information, see the Oracle7 Server Administrator's Guide.

LICENSE_SESSIONS_WARNING

If this parameter is set to zero, no warning is given when approaching the concurrent usage (session) limit. If you set this parameter to a nonzero number, you should also set LICENSE_MAX_SESSIONS.

For more information, see the Oracle7 Server Administrator's Guide.

LOG_ARCHIVE_BUFFER_SIZE

This parameter, with LOG_ARCHIVE_BUFFERS, can tune archiving so that it runs as fast as necessary, but not so fast that it reduces system performance.

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system specific Oracle documentation for the default value.

LOG_ARCHIVE_BUFFERS

This parameter, with LOG_ARCHIVE_BUFFER_SIZE, can tune archiving so that it runs as fast as necessary, but not so fast that it reduces system performance.

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the default value.

LOG_ARCHIVE_DEST

To override the destination that this parameter specifies, either specify a different destination for manual archiving or use the Server Manager command ARCHIVE LOG START filespec for automatic archiving, where filespec is the new archive destination.

For more information, see the Oracle7 Server Administrator's Guide.

See your Oracler operating system-specific documentation for the default value and for an example of how to specify the destination path or filename using LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT.

LOG_ARCHIVE_FORMAT

%s log sequence number

%t thread number

Using uppercase letters (for example, %S) for the variables causes the value to be a fixed length padded to the left with zeros.

The following is an example of specifying the archive redo log filename format:

LOG_ARCHIVE_FORMAT = "LOG%s_%t.ARC"

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the default value and range of values.

LOG_ARCHIVE_START

In ARCHIVELOG mode, if all online redo log files fill without being archived, an error message is issued, and instance operations are suspended until the necessary archiving is performed. This delay is more likely if you use manual archiving. You can reduce its likelihood by increasing the number of online redo log files.

To use ARCHIVELOG mode while creating a database, set this parameter to TRUE. Normally, a database is created in NOARCHIVELOG mode and then altered to ARCHIVELOG mode after creation.

For more information, see the Oracle7 Server Administrator's Guide.

LOG_BLOCK_CHECKSUM

Any logs written with the COMPATIBILITY parameter set to 7.2.0 or higher will not be readable by earlier releases. This compatibility restriction exists even if checksumming is not enabled.

Warning: Setting LOG_BLOCK_CHECKSUM to TRUE can cause a performance overhead. Set this parameter to TRUE only under the advice of Oracle Support personnel to diagnose data corruption problems.

LOG_BUFFER

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the default value and range of values.

LOG_CHECKPOINT_INTERVAL

The number of times DBWR has been notified to do a checkpoint for a given instance is shown in the cache statistic dbwr checkpoints, which is displayed in the System Statistics Monitor of the Server Manager. Additional cache statistics include background checkpoints started and background checkpoints completed.

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the default value.

LOG_CHECKPOINT_TIMEOUT

Note: A checkpoint scheduled to occur because of this parameter is delayed until the completion of the previous checkpoint if the previous checkpoint has not yet completed.

For more information, see the Oracle7 Server Administrator's Guide.

LOG_CHECKPOINTS_TO_ALERT

For more information, see the Oracle7 Server Concepts manual.

LOG_ENTRY_PREBUILD_THRESHOLD

For multiple-processor systems, it is sometimes beneficial to increase this parameter. Single-processor systems should keep the value at 0.

For systems experiencing latch contention that have fast processors and efficient memory-to-memory copy algorithms, increasing this value will prebuild log entries and reduce the time that the copy latch is held.

Do not increase this value for systems experiencing memory contention.

LOG_FILES

For more information, see the Oracle7 Server Administrator's Guide.

LOG_FILE_STANDBY_NAME_CONVERT

Set the value of this parameter to two strings: the first string is the pattern found in the log file names on the primary database; the second string is the pattern found in the log file names on the standby database.

LOG_SIMULTANEOUS_COPIES

If this parameter is set to 0, redo copy latches are turned off, and the parameters LOG_ENTRY_PREBUILD_THRESHOLD and LOG_SMALL_ENTRY_MAX_SIZE are ignored.

You can change the value of this parameter without shutting down your Oracle instance by using the ALTER SESSION command.

For more information, see the Oracle7 Server Administrator's Guide.

LOG_SMALL_ENTRY_MAX_SIZE

If the redo entry is copied on the redo allocation latch, the user process releases the latch after the copy. If the redo entry is larger than this parameter, the user process releases the latch after allocating space in the buffer and getting a redo copy latch.

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the default value and range of values.

MAX_COMMIT_PROPAGATION_DELAY

Default:	90000
Range of values:	0 - 90000
OK to change?	no
Multiple instances:	must have identical values

This initialization parameter should not be changed except under a limited set of circumstances specific to the Parallel Server. This parameter indicates the maximum amount of time allowed before the System Change Number (SCN) held in the SGA of an instance is refreshed by LGWR. It determines if the local SCN should be refreshed from the lock value when getting the snapshot SCN for a query. Units are in hundredths of seconds. Under very unusual circumstances involving rapid updates and queries of the same data from different instances, the SCN may not be refreshed in a timely manner. The default value of 90,000 hundredths of a second, or fifteen minutes, is an upper bound that allows the preferred existing high performance mechanism to remain in place.

Change this parameter only when it is absolutely necessary to see the most current version of the database when doing a query.

For more information, see Oracle7 Parallel Server Concepts & Administration.

MAX_DUMP_FILE_SIZE

Oracle silently restricts the maximum value for this parameter to approximately 4,000,000 physical blocks. If the user exceeds this value then MAX_DUMP_FILE_SIZE is set to 4,000,000 physical blocks, which is the maximum Oracle can provide.

For example, if your logical file system block size is 512 bytes and you do not want to exceed 5 MB for the trace file size, you would set the MAX_DUMP_FILE_SIZE to 10,000.

For more information, see the Oracle7 Server Administrator's Guide.

MAX_ENABLED_ROLES

The actual number of roles a user can enable is 2 + the value of MAX_ENABLED_ROLES, because each user has two additional roles, public, and the user's own role. For example, if MAX_ENABLED_ROLES is set to 5, user scott can have 7 roles enabled, the five enabled by MAX_ENABLED_ROLES plus public and scott.

For more information, see the Oracle7 Server Administrator's Guide.

MAX_ROLLBACK_SEGMENTS

For more information, see the Oracle7 Server Administrator's Guide.

MAX_TRANSACTION_BRANCHES

The previously fixed maximum number of branches limited the number of servers or server groups involved in a distributed transaction to 8 per Oracle instance. With the MAX_TRANSACTION_BRANCHES parameter, the maximum number of branches can be increased to 32, allowing for 32 servers or server groups per Oracle instance to work on one distributed transaction.

Setting MAX_TRANSACTION_BRANCHES to a lower value reduces shared pool memory usage slightly according to the following equation:

MAX_TRANSACTION_BRANCHES * DISTRIBUTED_TRANSACTIONS * 72 bytes

MLS_LABEL_FORMAT

For more information, see the Oracle7 Server Administrator's Guide.

MTS_DISPATCHERS

The configuration string for each group of dispatcher processes includes the network protocol for that group and the number of dispatcher processes in the group (one or more). Each network protocol that you use on your system requires a separate specification.

You can specify multiple network protocols in a single parameter or in multiple parameters. For example, if you are using TCP/IP and DECNet to connect to the server, you could either specify both in one parameter, as follows:

MTS_DISPATCHERS = ("tcp, 1", "decnet, 4")

or specify two parameters, as follows:

MTS_DISPATCHERS = "tcp, 1"

MTS_DISPATCHERS = "decnet, 4"

In these examples the first configuration string specifies one dispatcher process for the TCP/IP protocol and the second configuration string specifies four dispatcher processes for the DECNet protocol.

Note: If you have multiple MTS_DISPATCHERS parameters, they must be adjacent to each other in your initialization file.

For more information, see the Oracle7 Server Administrator's Guide. See also the Oracle Network Manager Administrator's Guide.

MTS_LISTENER_ADDRESS

Warning: Each address must be specified with its own parameter. (This differs from the SQL*Net syntax.) For example, if you use TCP/IP as well as DECNet, you would provide specifications similar to the following in your initialization file:

			MTS_LISTENER_ADDRESS =    \ 

			   "(ADDRESS=(PROTOCOL=tcp)(HOST=myhost)(PORT=7002))"

			MTS_LISTENER_ADDRESS =    \ 

			   "(ADDRESS=(PROTOCOL=decnet)(NODE=name)(OBJECT=mts))"

Note: If you have multiple MTS_LISTENER_ADDRESS parameters, they must be adjacent to each other in your initialization file.

Address specifications for the Listener process are operating system specific and network protocol specific.

For more information, see the Oracle7 Server Administrator's Guide.

See your operating system-specific Oracle documentation and SQL*Net documentation for a description of how to specify addresses for the protocols on your system.

MTS_MAX_DISPATCHERS

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the default value and range of values.

MTS_MAX_SERVERS

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the default value and range of values.

MTS_MULTIPLE_LISTENERS

MTS_MULTIPLE_LISTENERS = TRUE

MTS_LISTENER_ADDRESS =

	(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(PORT=5000)(HOST=zeus))\

	(ADDRESS=(PROTOCOL=decnet)(OBJECT=outa)(NODE=zeus))

MTS_SERVERS

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the default value and range of values.

MTS_SERVICE

The name you specify must be unique. It should not be enclosed in quotation marks. It is a good idea for this name to be the same as the instance name. That way, if the dispatcher is unavailable for any reason, the CONNECT string will still connect the user to the database.

If not specified, MTS_SERVICE defaults to the value specified by DB_NAME. If DB_NAME also is not specified, the Oracle7 Server returns an error at startup indicating that the value for this parameter is missing.

For more information, see the Oracle7 Server Administrator's Guide. See also the Oracle Network Manager Administrator's Guide.

NLS_CALENDAR

NLS_CALENDAR can have one of the following values:

• Arabic Hijrah

• Gregorian

• Japanese Imperial

• Persian

• ROC (Republic of China)

• Thai Buddha

SELECT SYSDATE FROM DUAL;

SYSDATE

--------

07-02-17 

NLS_CURRENCY

For example, the following query uses the L format element to return the default local currency symbol for the territory FRANCE:

SELECT TO_CHAR(TOTAL, 'L099') "TOTAL"

   FROM ORDERS WHERE CUSTNO = 586;

 TOTAL

-------

  F635

For more information, see the Oracle7 Server Administrator's Guide.

NLS_DATE_FORMAT

NLS_DATE_FORMAT = "MM/DD/YYYY"

The value of this parameter is stored in the tokenized internal date format. Each format element occupies two bytes, and each string occupies the number of bytes in the string plus a terminator byte. Also, the entire format mask has a two-byte terminator. For example, "MM/DD/YY" occupies 12 bytes internally because there are three format elements, two one-byte strings (the two slashes), and the two-byte terminator for the format mask. The tokenized format for the value of this parameter cannot exceed 24 bytes.

For more information, see the Oracle7 Server Administrator's Guide.

NLS_DATE_LANGUAGE

For more information, see the Oracle7 Server Administrator's Guide.

NLS_ISO_CURRENCY

SELECT TO_CHAR(TOTAL, 'C099') "TOTAL"

   FROM ORDERS WHERE CUSTNO = 586;

 TOTAL

-------

FRF635

The value of this parameter can be any valid territory specified in NLS_TERRITORY.

For more information, see the Oracle7 Server Administrator's Guide.

NLS_LANGUAGE

NLS_LANGUAGE = FRENCH

Examples of supported languages are American, French, and Japanese.

This parameter determines the default values of the parameters NLS_DATE_LANGUAGE and NLS_SORT. For a complete list of languages, see "Supported Languages" .

For more information, see the Oracle7 Server Administrator's Guide.

See also your country release notes and operating system-specific Oracle documentation.

NLS_NUMERIC_CHARACTERS

Any character can be the decimal or group separator. The two characters specified must be single-byte, and both characters must be different from each other each other. The characters cannot be any numeric character or any of the following characters: plus ( + ), hyphen ( - ), less than sign ( < ), greater than sign ( > ).

The characters are specified in the following format:

NLS_NUMERIC_CHARACTERS = "<decimal_character><group_separator>"

For example, if you wish to specify a comma as the decimal character and a space as the group separator, you would set this parameter as follows:

NLS_NUMERIC_CHARACTERS = ", "

The default value of this parameter is determined by NLS_TERRITORY.

Note: When the decimal character is not a period ( . ) or when the group separator is used, numeric literals must appear in quotation marks. For example, with the value of NLS_NUMERIC_CHARACTERS above, the following SQL statement requires quotation marks around the numeric literals:

INSERT INTO SIZES ( ITEMID, PRICE, WIDTH )

   VALUES ( 618, '45,50', TO_NUMBER('1 234,11', '9G999D99'));

For more information, see the Oracle7 Server Administrator's Guide.

NLS_SORT

If the value is a named linguistic sort, sorting is based on the order of the defined linguistic sort. Most languages supported by the NLS_LANGUAGE parameter also support a linguistic sort with the same name.

Note: Setting NLS_SORT to anything other than BINARY causes a sort to use a full table scan, regardless of the path chosen by the optimzer.

You must use the NLS_SORT operator with comparison operations if you want the linguistic sort behavior.

The default value of this parameter depends on the value of the NLS_LANGUAGE parameter.

For a list of supported linguistic definitions and extended definitions, see 4 - 38.

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the sorting rules used by the linguistic sorting mechanisms.

NLS_TERRITORY

This parameter determines the default values for the following parameters: NLS_CURRENCY, NLS_ISO_CURRENCY, NLS_DATE_FORMAT, and NLS_NUMERIC_CHARACTERS.

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the territory-dependent default values for these parameters.

OPEN_CURSORS

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the range of values.

OPEN_LINKS

This parameter refers only to connections used for distributed transactions. Direct connections to a remote database specified as an application connects are not counted.

If set to 0, then no distributed transactions are allowed.

For more information, see the Oracle7 Server Administrator's Guide and Oracle7 Server Distributed Systems, Volume I.

OPEN_MOUNTS

For more information, see the Trusted Oracle7 Server Administrator's Guide.

OPTIMIZER_MODE

You can set the goal for cost-based optimization by setting this parameter to FIRST_ROWS or ALL_ROWS. FIRST_ROWS causes the optimizer to choose execution plans that minimize response time. ALL_ROWS causes the optimizer to choose execution plans that minimize total execution time. The goal of cost-based optimization can also be set within a session by using ALTER SESSION SET OPTIMIZER_MODE. See Oracle7 Server SQL Reference for more information about the ALTER SESSION command.

For more information about tuning SQL statements, see Oracle7 Server Tuning.

For more information about the optimizer, see Oracle7 Server Concepts and Oracle7 Server Tuning.

OPTIMIZER_PERCENT_PARALLEL

You can change the value of this parameter without shutting down your Oracle instance by using the ALTER SESSION command. Low values favor indexes, and high values favor table scans.

Cost-based optimization will always be used for any query that references an object with a nonzero degree of parallelism. For such queries a RULE hint or optimizer mode or goal will be ignored. Use of a FIRST_ROWS hint or optimizer mode will override a nonzero setting of OPTIMIZER_PERCENT_PARALLEL.

ORACLE_TRACE_COLLECTION_NAME

ORACLE_TRACE_COLLECTION_PATH

ORACLE_TRACE_COLLECTION_SIZE

ORACLE_TRACE_ENABLE

ORACLE_TRACE_FACILITY_NAME

ORACLE_TRACE_FACILITY_PATH

OS_AUTHENT_PREFIX

Note: The text of the OS_AUTHENT_PREFIX parameter is case sensitive with some operating systems.

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation.

OS_ROLES

If OS_ROLES is equal to TRUE, the operating system completely manages the role grants for all database usernames. Any revokes of roles granted by the operating system are ignored, and any previously granted roles are ignored.

The default value, FALSE, causes roles to be identified and managed by the database.

For more information, see the Oracle7 Server Administrator's Guide.

PARALLEL_DEFAULT_MAX_INSTANCES

For more information, see Oracle7 Parallel Server Concepts & Administration.

PARALLEL_DEFAULT_MAX_SCANS

PARALLEL_DEFAULT_SCANSIZE

PARALLEL_MAX_SERVERS

For more information, see Oracle7 Parallel Server Concepts & Administration.

PARALLEL_MIN_PERCENT

PARALLEL_MIN_SERVERS

For more information, see Oracle7 Parallel Server Concepts & Administration.

PARALLEL_SERVER_IDLE_TIME

PARTITION_VIEW_ENABLED

You can change the value of this parameter without shutting down your Oracle instance by using the ALTER SESSION command.

PRE_PAGE_SGA

PROCESSES

The default values of DB_FILE_MULTIBLOCK_READ_COUNT and SESSIONS are derived from PROCESSES. If you alter the value of PROCESSES, you may want to adjust the values of these derived parameters.

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the range of values.

RECOVERY_PARALLELISM

For more information, see Oracle7 Parallel Server Concepts & Administration.

REMOTE_DEPENDENCIES_MODE

If this parameter is set to TIMESTAMP, which is the default setting, the client running the procedure compares the timestamp recorded on the server side procedure with the current timestamp of the local procedure and executes the procedure only if the timestamps match.

If the parameter is set to SIGNATURE, the procedure is allowed to execute as long as the signatures are considered safe. This allows client PL/SQL applications to be run without recompilation.

REMOTE_LOGIN_PASSWORDFILE

For more information about secure connections for privileged users, see the Oracle7 Server Administrator's Guide.

REMOTE_OS_AUTHENT

For more information, see the Oracle7 Server Administrator's Guide.

REMOTE_OS_ROLES

For more information, see the Oracle7 Server Administrator's Guide.

RESOURCE_LIMIT

For more information, see the Oracle7 Server Administrator's Guide.

ROLLBACK_SEGMENTS

Note: Never name the SYSTEM rollback segment as a value for the ROLLBACK_SEGMENTS parameter.

This parameter has the following syntax:

ROLLBACK_SEGMENTS = (rbseg_name [, rbseg_name] ... )

Although this parameter usually specifies private rollback segments, it can also specify public rollback segments if they are not already in use.

Different instances in an Oracle7 Parallel Server cannot name the same rollback segment for any of the ROLLBACK_SEGMENTS. Query the data dictionary view DBA_ROLLBACK_SEGS to find the name, segment ID number, and status of each rollback segment in the database.

For more information, see the Oracle7 Server Administrator's Guide.

ROW_CACHE_CURSORS

For more information about memory structure and processes, see Oracle7 Server Concepts.

ROW_LOCKING

For information about tuning SQL statements, see the Oracle7 Server Tuning manual.

SEQUENCE_CACHE_ENTRIES

Each entry requires approximately 110 bytes in the SGA for an Oracle7 Parallel Server.

Sequences created with the NOCACHE option do not reside in this cache. They must be written through to the data dictionary on every use.

For more information about managing schema objects, see Oracle7 Server Administrator's Guide and Oracle7 Server Application Developer's Guide.

SEQUENCE_CACHE_HASH_BUCKETS

SERIALIZABLE

Setting SERIALIZABLE to TRUE provides ANSI degree three consistency at a considerable cost in concurrency.

For more information about data concurrency, see the Oracle7 Server Tuning manual.

SESSION_CACHED_CURSORS

SESSIONS

The default values of ENQUEUE_RESOURCES and TRANSACTIONS are derived from SESSIONS. If you alter the value of SESSIONS, you may want to adjust the values of ENQUEUE_RESOURCES and TRANSACTIONS.

With the multi-threaded server, you should adjust the value of SESSIONS to approximately 1.1 * (total number of connections).

For more information memory structures and processes, see the Oracle7 Server Concepts manual.

SHARED_POOL_SIZE

For more information, see the Oracle7 Server Administrator's Guide.

SHARED_POOL_RESERVED_MIN_ALLOC

The default value is adequate for most systems. If you increase the value, then the Oracle Server will allow fewer allocations from the reserved list and will request more memory from the shared pool list.

SHARED_POOL_RESERVED_SIZE

The default value of 0 represents no reserved shared pool area.

Ideally, this parameter should be large enough to satisfy any request scanning for memory on the reserved list without flushing objects from the shared pool. The amount of operating system memory, however, may constrain the size of the shared pool. In general, you should set SHARED_POOL_RESERVED_SIZE to 10% of SHARED_POOL_SIZE. For most systems, this value will be sufficient if you have already tuned the shared pool.

SNAPSHOT_REFRESH_PROCESS

For more information on managing table snapshots, see Oracle7 Server Distributed Systems, Volume II.

SNAPSHOT_REFRESH_INTERVAL

For more information on managing table snapshots, see Oracle7 Server Distributed Systems, Volume II.

SORT_AREA_RETAINED_SIZE

If a sort requires more memory, a temporary segment is allocated and the sort becomes an external (disk) sort. The maximum amount of memory to use for the sort is then specified by SORT_AREA_SIZE instead of by this parameter.

Larger values permit more sorts to be performed in memory. However, multiple sort spaces of this size may be allocated. Usually, only one or two sorts occur at one time, even for complex queries. In some cases, though, additional concurrent sorts are required. Each sort occurs in its own memory area, as specified by SORT_AREA_RETAINED_SIZE.

For more information, see Oracle7 Server Concepts.

SORT_AREA_SIZE

Increasing SORT_AREA_SIZE size improves the efficiency of large sorts. Multiple allocations never exist; there is only one memory area of SORT_AREA_SIZE for each user process at any time.

The default is usually adequate for most database operations. Only if very large indexes are created might you want to adjust this parameter. For example, if one process is doing all database access, as in a full database import, then an increased value for this parameter may speed the import, particularly the CREATE INDEX statements.

For more information, see Oracle7 Server Concepts.

See also your operating system specific Oracle documentation for the default value on your system.

SORT_DIRECT_WRITES

When set to the default value of AUTO, and if the value of SORT_AREA_SIZE is greater than ten times the buffer size, SORT_DIRECT_WRITES automatically configures the SORT_WRITE_BUFFER_SIZE and SORT_WRITE_BUFFERS parameters. When SORT_DIRECT_WRITES is in AUTO mode, SORT_WRITE_BUFFERS and SORT_WRITE_BUFFER_SIZE have no effect.

When SORT_DIRECT_WRITES is set to TRUE, each sort allocates additional buffers in memory to write directly to disk.

When SORT_DIRECT_WRITES is set to FALSE, the sorts that write to disk write through the buffer cache.

For more information, see Oracle7 Server Tuning.

SORT_READ_FAC

                              (avg_seek_time + avg_latency + blk_transfer_time)
sort_read_fac  = --------------------------------------------
                                                      blk_transfer_time

See also your operating system-specific Oracle documentation for the default value.

SORT_SPACEMAP_SIZE

[(total_sort_bytes) / (sort_area_size)] + 64

where total_sort_bytes is

(number_of_records) * [sum_of_average_column_sizes + (2 * number_of_col)]

Here, columns include the SELECT list for the ORDER BY, the SELECT list for the GROUP BY, and the key list for CREATE INDEX. Also include 10 bytes for ROWID for CREATE INDEX and GROUP BY or ORDER BY columns not mentioned in the SELECT list for these cases.

For more information on memory structures and processes, see the Oracle7 Server Concepts.

See also your operating system-specific Oracle documentation for the default value.

SORT_WRITE_BUFFER_SIZE

SORT_WRITE_BUFFERS

SQL_TRACE

You can change the value of this parameter without shutting down your Oracle instance by using the ALTER SESSION command.

For more information about performance diagnostic tools, see Oracle7 Server Tuning.

See also the Oracle7 Server SQL Reference manual.

SQL92_SECURITY

TEMPORARY_TABLE_LOCKS

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the range of values.

THREAD

The number of the redo thread that is to be used by the instance. Any available redo thread number can be used, but an instance cannot use the same thread number as another instance. Also, an instance cannot start when its redo thread is disabled. A value of zero causes an available, enabled public thread to be chosen. An instance cannot mount a database if the thread is used by another instance or if the thread is disabled.

Redo threads are specified with the THREAD option of the ALTER DATABASE ADD LOGFILE command. Redo threads are enabled with the ALTER DATABASE ENABLE [PUBLIC] THREAD command. The PUBLIC keyword signifies that the redo thread may be used by any instance.

Thread 1 is the default thread in exclusive mode. An instance running in exclusive mode can specify THREAD to use the redo log files in a thread other than thread 1.

For more information, see Oracle7 Parallel Server Concepts & Administrationand Oracle7 Server SQL Reference.

TIMED_STATISTICS

For more information about performance diagnostic tools, see Oracle7 Server Tuning.

TRANSACTIONS

For more information about memory structures and processes, see Oracle7 Server Concepts and the Oracle7 Server Administrator's Guide.

TRANSACTIONS_PER_ROLLBACK_SEGMENT

More rollback segments can be acquired if they are named in the parameter ROLLBACK_SEGMENTS.

For more information, see the Oracle7 Server Administrator's Guide.

See also your operating system-specific Oracle documentation for the range of values.

USER_DUMP_DEST

For example, this directory might be set to C:\ORACLE\UTRC on MS-DOS; to /oracle/utrc on UNIX; or to DISK$UR3:[ORACLE.UTRC] on VMS.

For more information about performance diagnostic tools, see Oracle7 Server Tuning.

See also your operating system-specific Oracle documentation for the range of values.

UTL_FILE_DIR

Note that all users may read or write all files specified in the UTL_FILE_DIR parameter(s). This means that all PL/SQL users must be trusted with the information in the directories specified in the UTL_FILE_DIR parameters.