apb.htm

Teach yourself Oracle8 in 21 day

<P><B>OBJECT_CACHE_MAX_SIZE_PERCENT [0%..OS Dependent] &lt;10%&gt; <BR>
</B>This parameter specifies the percentage of the optimal cache size beyond which
the Session object cache size can grow. </P>

<P><B>OBJECT_CACHE_OPTIMAL_PERCENT [10KB..OS Dependent] &lt;100KB&gt; <BR>
</B>This parameter specifies the optimal size of the Session object cache. </P>

<P><B>OPEN_CURSORS [1..OS limit] &lt;50&gt; <BR>
</B>This parameter specifies the maximum number of open cursors that a single user
process can have open at once. </P>

<P><B>OPEN_LINKS [0..255] &lt;4&gt; <BR>
</B>This parameter specifies the maximum number of concurrent open connections to
remote database processes per user process. This value should exceed the maximum
number of remote systems accessed within any single SQL statement. </P>

<P><B>PARTITION_VIEW_ENABLED [TRUE/FALSE] &lt;FALSE&gt; <BR>
</B>If set to <TT>TRUE</TT>, the optimizer skips unnecessary table accesses in a
partition view. </P>

<P><B>PLSQL_V2_COMPATIBILITY [TRUE/FALSE] &lt;FALSE&gt; <BR>
</B>This parameter sets the compatibility level for PL/SQL. </P>

<P><B>PROCESSES [6 to OS dependent] &lt;50&gt; <BR>
</B>This parameter specifies the maximum number of OS user processes that connect
to the Oracle instance. This number must take into account the background processes
and the login process that started the instance. Be sure to add an extra six processes
for the background processes. </P>

<P><B>REMOTE_DEPENDENCIES_MODE [TIMESTAMP/SIGNATURE] &lt;TIMESTAMP&gt; <BR>
</B>This parameter specifies how dependencies on remote stored procedures are to
be handled by the database. </P>

<P><B>REMOTE_LOGIN_PASSWORDFILE [NONE/SHARED/EXCLUSIVE] &lt;NONE&gt; <BR>
</B>This parameter specifies whether Oracle checks for a password file. A value of
<TT>NONE</TT> indicates that users are authenticated through the operating system.
A value of <TT>EXCLUSIVE</TT> indicates that the password file can be used only by
one database and can contain names other than <TT>SYS</TT> and <TT>INTERNAL</TT>.
Setting this parameter to <TT>SHARED</TT> allows more than one database to use this
password file, but only <TT>SYS</TT> and <TT>INTERNAL</TT> are recognized by this
password file. </P>

<P><B>REPLICATION_DEPENDENCY_TRACKING [TRUE/FALSE] &lt;TRUE&gt; <BR>
</B>This parameter specifies that dependency tracking for read/write operations to
the database is turned on. </P>

<P><B>RESOURCE_LIMIT [TRUE/FALSE] &lt;FALSE&gt; <BR>
</B>A value of <TT>FALSE</TT> disables the enforcement of resource limits such as
sessions, CPU time, and so on. This disables the enforcement of those limits regardless
of how they are set. </P>

<P><B>SESSIONS [number] &lt;1.1 * PROCESSES&gt; <BR>
</B>This parameter specifies the total number of user and system sessions. Because
recursive sessions might occur, this number should be set slightly higher than <TT>PROCESSES</TT>.
<TT>DDL_LOCKS</TT> is derived from this parameter. </P>

<P><B>SHADOW_CORE_DUMP [FULL/PARTIAL] &lt;FULL&gt; <BR>
</B>This parameter specifies whether the SGA is included in core dumps. </P>

<P><B>SNAPSHOT_REFRESH_INTERVAL [1..3600] &lt;60&gt; <BR>
</B>This parameter specifies the number of seconds between wake-ups for the instance's
snapshot refresh process. </P>

<P><B>SNAPSHOT_REFRESH_KEEP_CONNECTION [TRUE/FALSE] &lt;FALSE&gt; <BR>
</B>This parameter specifies whether the snapshot refresh process should keep remote
connections after the refresh. If set to <TT>FALSE</TT>, the remote database connections
are closed after the refreshes occur. </P>

<P><B>SNAPSHOT_REFRESH_PROCESS [0..10] &lt;0&gt; <BR>
</B>This parameter specifies the number of snapshot refresh processes per instance.
You must set this value to <TT>1</TT> or higher for automatic refreshes. One snapshot
refresh process is usually sufficient. </P>

<P><B>SINGLE_PROCESS [TRUE/FALSE] FALSE <BR>
</B>If <TT>SINGLE_PROCESS</TT> is set to <TT>TRUE</TT>, the database instance is
brought up in a single-user mode. A value of <TT>FALSE</TT> indicates that the database
is brought up in a multiprocess mode. </P>

<P><B>TEMPORARY_TABLE_LOCKS [0..OS dependent] &lt;SESSIONS&gt; <BR>
</B><TT>TEMPORARY_TABLE_LOCKS</TT> specifies the number of temporary tables that
can be created in the temporary segment space. A temporary table lock is required
whenever a sort occurs that cannot be held in memory (that is, the sort exceeds <TT>SORT_AREA_RETAINED_SIZE</TT>).
If your application contains a large number of <TT>ORDER BY</TT> clauses or if you
perform a large number of index sorts, you might want to increase this number. </P>

<P><B>TRANSACTIONS [number] &lt;1.1 * PROCESSES&gt; <BR>
</B>This parameter specifies the maximum number of concurrent transactions in the
instance. The default value is greater than <TT>PROCESSES</TT> to provide for recursive
transactions. A larger value increases the size of the SGA. If you increase the number
of transactions allowed in the system, you might also want to increase the number
of rollback segments available. </P>

<P><B>TRANSACTIONS_PER_ROLLBACK_SEGMENT [1..OS dependent] &lt;30&gt; <BR>
</B>This value specifies the maximum number of concurrent transactions allowed per
rollback segment. You can calculate the minimum number of rollback segments enabled
at startup with this formula:</P>
<PRE><FONT COLOR="#0066FF">Rollback Segments = TRANSACTIONS / TRANSACTIONS_PER_ROLLBACK_SEGMENT
</FONT></PRE>
<P>Performance can be improved if there is less contention on rollback segments.
In a heavily used system, you might want to reduce <TT>TRANSACTIONS_PER_ROLLBACK_SEGMENT</TT>
to decrease this contention. </P>

<P><B>USER_DUMP_DEST [valid path name] &lt;OS dependent&gt; <TT><BR>
</TT></B><TT>USER_DUMP_DEST</TT> specifies the path to where the debugging trace
files are written. </P>

<P><B>UTL_FILE_DIR [valid directory] <BR>
</B>This parameter specifies directories that are permitted for PL/SQL file I/O.
<H2><FONT COLOR="#000077">Recovery Manager</FONT></H2>
<P>These parameters are used in conjunction with the Recovery Manager. </P>

<P><B>BACKUP_DISK_IO_SLAVES [0..15] &lt;0&gt; <BR>
</B>This parameter defines the number of I/O slaves used by the Recovery Manager
to back up, copy, or restore. </P>

<P><B>BACKUP_TAPE_IO_SLAVES [TRUE/FALSE] &lt;FALSE&gt; <BR>
</B>This parameter specifies whether I/O slaves are used by the Recovery Manager
for tape operations. </P>

<P><B>DB_FILE_NAME_CONVERT [string] <BR>
</B>This parameter converts the filename of a new datafile on the primary database
to a filename on the standby database. </P>

<P><B>LOG_FILE_NAME_CONVERT [string] <BR>
</B>This parameter converts the filename of a new log file on the primary database
to a filename on the standby database. </P>

<P><B>TAPE_ASYNCH_IO [TRUE/FALSE] &lt;TRUE&gt; <BR>
</B>This parameter specifies that I/O to sequential devices are asynchronous. This
should be left enabled and not altered.
<H2><FONT COLOR="#000077">Multithreaded Server</FONT></H2>
<P>These parameters are used if you are using the multithreaded server process. </P>

<P><B>MTS_DISPATCHERS [&quot;protocol, number&quot;] &lt;NULL&gt; <BR>
</B>This parameter specifies the configuration of the dispatcher process(es) created
at startup time. The value of this parameter is a quoted string of two values separated
by a comma. The values are the network protocol and the number of dispatchers. Each
protocol requires a separate specification. This parameter can be specified multiple
times. Here is an example of two dispatcher definitions:</P>
<PRE><FONT COLOR="#0066FF">MTS_DISPATCHERS = &quot;tcp, 2&quot;
MTS_DISPATCHERS = &quot;ipx, 1&quot;
</FONT></PRE>
<P><B>MTS_LISTENER_ADDRESS [configuration] &lt;NULL&gt; <BR>
</B>This parameter specifies the configuration of the listener process addresses.
There must be a listener process address for each protocol used in the system. Addresses
are specified as the SQL*Net description of the connection address.</P>
<P>Because each connection is required to have its own address, this parameter might
be specified several times. Here is an example:</P>
<PRE><FONT COLOR="#0066FF">MTS_LISTENER_ADDRESS = &quot;(ADDRESS=(PROTOCOL=tcp)(HOST=hostname)(PORT=7002))&quot;
MTS_LISTENER_ADDRESS = &quot;(ADDRESS=(PROTOCOL=ipx)()())&quot;
</FONT></PRE>
<P><B>MTS_MAX_DISPATCHERS [OS dependent] &lt;5&gt; <BR>
</B>This parameter specifies the maximum number of dispatcher processes allowed to
run simultaneously. </P>

<P><B>MTS_MAX_SERVERS [OS dependent] &lt;20&gt; <BR>
</B>This parameter specifies the maximum number of shared server processes allowed
to run simultaneously. </P>

<P><B>MTS_MULTIPLE_LISTENERS [TRUE/FALSE] &lt;FALSE&gt; <BR>
</B>This parameter is obsolete. </P>

<P><B>MTS_RATE_LOG_SIZE [DEFAULTS/EVENT_LOOPS/MESSAGES/SERVER_BUFFERS/CLIENT_BUFFERS/TOTAL_BUFFERS/IN_CONNECTS/OUT_CONNECTS/RECONNECTS]
&lt;10&gt; </B><BR>
This parameter specifies the sample size used to calculate dispatcher-rate statistics.
</P>

<P><B>MTS_RATE_SCALE [DEFAULTS/EVENT_LOOPS/MESSAGES/SERVER_BUFFERS/CLIENT_BUFFERS/TOTAL_BUFFERS/IN_CONNECTS/OUT_CONNECTS/RECONNECTS]
&lt;misc&gt; </B><BR>
This parameter specifies the scale at which dispatcher-rate statistics are reported.
</P>

<P><B>MTS_SERVERS [OS dependent] &lt;0&gt; <BR>
</B>This parameter specifies the number of server processes created at instance startup.
</P>

<P><B>MTS_SERVICE [name] &lt;DB_NAME&gt; <BR>
</B>This parameter specifies the name of the service to be associated with the dispatcher.
Using this name in the <TT>CONNECT</TT> string allows users to connect using the
dispatcher. The name should be unique. Do not specify this name in quotes. It is
usually a good idea to make this name the same as the instance name. Because the
dispatcher is tried first, if it is not available, the <TT>CONNECT</TT> string can
still connect the user into the database through a normal database connection.
<H2><FONT COLOR="#000077">Distributed Option</FONT></H2>
<P>These parameters are meaningful only when you use the distributed option. </P>

<P><B>COMMIT_POINT_STRENGTH [0..255] &lt;OS dependent&gt; <BR>
</B>This value is used to determine the commit point site when executing a distributed
transaction. The site with the highest value for <TT>COMMIT_POINT_STRENGTH</TT> is
the commit point site. The site with the largest amount of critical data should be
the commit point site. </P>

<P><B>DISTRIBUTED_LOCK_TIMEOUT [1..unlimited] &lt;60 seconds&gt; <TT><BR>
</TT></B><TT>DISTRIBUTED_LOCK_TIMEOUT</TT> specifies, in seconds, how long distributed
transactions should wait for locked resources. </P>

<P><B>DISTRIBUTED_RECOVERY_CONNECTION_HOLD_TIME [1..1800] &lt;200 seconds&gt; <BR>
</B><TT>DISTRIBUTED_RECOVERY_CONNECTION_HOLD_TIME</TT> specifies, in seconds, how
long to hold a remote connection open after a distributed transaction fails. A larger
value holds the connection longer but also continues to use local resources even
though the connection might have been severed. Any value larger than 1,800 seconds
interferes with the reconnection and recovery background processes and will never
drop a failed connection. </P>

<P><B>DISTRIBUTED_TRANSACTIONS [0..TRANSACTIONS] &lt;OS dependent&gt; <BR>
</B><TT>DISTRIBUTED_TRANSACTIONS</TT> specifies the maximum number of distributed
transactions that the database can process concurrently. This value cannot exceed
the value of <TT>TRANSACTIONS</TT>. If you are having problems with distributed transactions
because network failures are causing many in-doubt transactions, you might want to
limit the number of distributed transactions.</P>

<P>If <TT>DISTRIBUTED_TRANSACTIONS</TT> is set to <TT>0</TT>, no distributed transactions
are allowed and the RECO process does not start at instance startup. </P>

<P><B>MAX_TRANSACTION_BRANCHES [1..32] &lt;8&gt; <BR>
</B>This parameter controls the number of branches in a distributed transaction.
</P>

<P><B>REMOTE_OS_AUTHENT [TRUE/FALSE] &lt;FALSE&gt;<BR>
</B>If this parameter is set to <TT>TRUE</TT>, it allows authentication to remote
systems with the value of <TT>OS_AUTHENT_PREFIX</TT>. </P>

<P><B>REMOTE_OS_ROLES [TRUE/FALSE] &lt;FALSE&gt; <BR>
</B>If this parameter is set to <TT>TRUE</TT>, it allows remote clients to have their
roles managed by the OS. If <TT>REMOTE_OS_ROLES</TT> is <TT>FALSE</TT>, roles are
managed and identified by the database for the remote system.
<H2><FONT COLOR="#000077">Parallel Server Parameters</FONT></H2>
<P>These parameters are used only in conjunction with the Oracle Parallel Server
option. </P>

<P><B>ALLOW_PARTIAL_SN_RESULTS [TRUE/FALSE] &lt;FALSE&gt; <BR>
</B>This parameter allows partial results to be returned on queries to global performance
tables even if a slave could not be allocated. </P>

<P><B>CACHE_SIZE_THRESHOLD [number] &lt;0.1 * DB_BLOCK_BUFFERS&gt; <BR>
</B>This parameter specifies the maximum size of a cached partition table split among
the caches of multiple instances. If the partition is larger than this value, the
table is not split among the caches. </P>

<P><B>DELAYED_LOGGING_BLOCK_CLEANOUTS [TRUE/FALSE] &lt;TRUE&gt; <BR>
</B>This parameter enables the delayed block cleanout feature. This can reduce OPS