apb.htm

Teach yourself Oracle8 in 21 day

pinging. </P>

<P><B>FREEZE_DB_FOR_FAST_INSTANCE_RECOVERY [TRUE/FALSE] <BR>
</B>This parameter specifies that the entire database freeze in order to speed recovery.
</P>

<P><B>GC_DEFER_TIME [integer] &lt;0&gt; <BR>
</B>This parameter specifies the time the server waits (in hundredths of a second)
before responding to a forced-write request for hot blocks. </P>

<P><B>GC_DB_LOCKS [0..unlimited] &lt;0&gt; <BR>
</B>This parameter specifies the number of PCM locks allocated. The value of <TT>GC_DB_LOCKS</TT>
should be at least one greater than the sum of the locks specified with the parameter
<TT>GC_FILES_TO_LOCKS</TT>. </P>

<P><B>GC_FILES_TO_LOCKS [file_number=locks:filename=locks] &lt;NULL&gt; <BR>
</B>This parameter supplies a list of filenames, each specifying how many locks should
be allocated for that file. Optionally, the number of blocks and the value <TT>EACH</TT>
can be added to further specify the allocation of the locks. </P>

<P><B>GC_LCK_PROCS [0..10] &lt;1&gt; <BR>
</B>This parameter specifies the number of lock processes (LCK0 to LCK9) to create
for the instance. The default value of <TT>1</TT> is usually sufficient unless an
unusually high number of locks are occurring. </P>

<P><B>GC_RELEASABLE_LOCKS [0..DB_BLOCK_BUFFERS] &lt;DB_BLOCK_BUFFERS&gt; <BR>
</B>This parameter allocates space for fine-grain locking. </P>

<P><B>GC_ROLLBACK_LOCKS [number] &lt;20&gt; <BR>
</B>This parameter specifies the number of distributed locks available for each rollback
segment. The default value is usually sufficient. </P>

<P><B>GC_ROLLBACK_SEGMENTS [number] &lt;20&gt; <TT><BR>
</TT></B><TT>GC_ROLLBACK_SEGMENTS</TT> specifies the maximum number of rollback segments
systemwide. This includes all instances in the parallel server system, including
the <TT>SYSTEM</TT> rollback segment. </P>

<P><B>GC_SAVE_ROLLBACK_LOCKS [number] &lt;20&gt; <BR>
</B>This parameter specifies the number of distributed locks reserved for deferred
rollback segments. These deferred rollback segments contain rollback entries for
segments taken offline. </P>

<P><B>GC_SEGMENTS [number] &lt;10&gt; <BR>
</B>This parameter specifies the maximum number of segments that might have space-management
activities simultaneously performed by different instances. </P>

<P><B>GC_TABLESPACES [number] &lt;5&gt; <BR>
</B>This parameter specifies the maximum number of tablespaces that can be simultaneously
brought online or offline. </P>

<P><B>INSTANCE_GROUPS [string] <BR>
</B>This parameter assigns the current instance to this instance group. </P>

<P><B>INSTANCE_NUMBER [1..OS dependent] &lt;Lowest Available Number&gt; <BR>
</B>This parameter specifies a unique number that maps the instance to a group of
free space lists. </P>

<P><B>LM_LOCKS [512..Limited by Instance Size] &lt;12000&gt; <BR>
</B>This parameter specifies the number of locks that are configured for the lock
manager. </P>

<P><B>LM_PROCS [36..PROCESSES+instances+safety factor] &lt;64+instances&gt; <BR>
</B>This parameter represents the number of the <TT>PROCESSES</TT> parameter plus
the number of instances. </P>

<P><B>LM_RESS [256..Limited by Instance Size] &lt;6000&gt; <BR>
</B>This parameter controls the number of resources that can be locked by each lock-manager
process. <BR>
</P>

<P><B>LOCK_NAME_SPACE [string] <BR>
</B>This parameter specifies the name space that the distributed lock manager (DLM)
uses to generate lock names. </P>

<P><B>MAX_COMMIT_PROPAGATION_DELAY [0..90000] &lt;90000&gt; <BR>
</B>This parameter specifies the maximum amount of time that can pass before the
SCN (System Change Number) is changed by the DBWR. This value helps in certain conditions
where the SCN might not be refreshed often enough because of a high load from multiple
instances.</P>

<P><B>OPEN_LINKS_PER_INSTANCE [0..UB4MAXVAL] &lt;4&gt; <BR>
</B>This parameter specifies the maximum number of migratable open connections. </P>

<P><B>OPS_ADMIN_GROUP [group name] &lt;all instances&gt; <BR>
</B>This parameter allows instances to be grouped for monitoring and administration.
</P>

<P><B>PARALLEL_DEFAULT_MAX_INSTANCES [0..instances] &lt;OS dependent&gt; <BR>
</B>This parameter specifies the default number of instances to spit a table among
for parallel query processing. This value is used if the <TT>INSTANCES DEFAULT</TT>
is specified in the table/cluster definition. </P>

<P><B>PARALLEL_INSTANCE_GROUP [string] &lt;group&gt; <BR>
</B>This parameter specifies the parallel instance group to be used for spawning
parallel query slaves. </P>

<P><B>PARALLEL_SERVER [TRUE/FALSE] &lt;FALSE&gt; <BR>
</B>Setting this to <TT>TRUE</TT> enables the Parallel Server option. </P>

<P><B>PARALLEL_TRANSACTION_RESOURCE_TIMEOUT [0..OS Dependent] &lt;300&gt; <BR>
</B>This parameter specifies the maximum amount of time (seconds) that can pass before
a session executing a parallel operation will time-out while waiting on a resource
held by another session. THREAD [0..max threads] &lt;0&gt; This parameter specifies
the number of the redo thread to be used by this instance. Any number can be used,
but the value must be unique within the cluster.
<H2><FONT COLOR="#000077">Security</FONT></H2>
<P>These parameters help set up system security; manipulate them to obtain the best
mix of efficiency and security. </P>

<P><B>AUDIT_FILE_DEST [dir_name] &lt;$ORACLE_HOME/RDBMS/AUDIT&gt; <BR>
</B>This parameter specifies the directory where audit files are stored. </P>

<P><B>AUDIT_TRAIL [NONE,DB,OS] <BR>
</B>The <TT>AUDIT_TRAIL</TT> parameter enables auditing to the table <TT>SYS$AUD$</TT>.
Auditing causes a record of database and user activity to be logged. Because auditing
causes overhead, it limits performance. The amount of overhead and the effect on
performance is determined by what and how much is audited. Once <TT>AUDIT_TRAIL</TT>
is enabled, auditing is turned on by the Oracle command <TT>AUDIT</TT>. </P>

<P><B>O7_DICTIONARY_ACCESSIBILITY [TRUE/FALSE] &lt;TRUE&gt; <BR>
</B>If set to <TT>TRUE</TT> (default), access to the <TT>SYS</TT> schema is allowed.
This is Oracle7 behavior. </P>

<P><B>OS_AUTHENT_PREFIX [] &lt;OPS$&gt; <BR>
</B>This is the value concatenated to the beginning of the user's OS login account
to give a default Oracle account name. The default value of <TT>OPS$</TT> is OS dependent
and is provided for backward compatibility with previous Oracle versions. Typically,
you use the default or set the value to <TT>&quot;&quot;</TT> (<TT>NULL</TT>) to
eliminate prefixes altogether. </P>

<P><B>OS_ROLES [TRUE/FALSE] &lt;FALSE&gt; <BR>
</B>Setting this parameter to <TT>TRUE</TT> allows the OS to have control over the
username's roles. If set to <TT>FALSE</TT>, the username's roles are controlled by
the database. </P>

<P><B>SQL92_SECURITY [TRUE/FALSE] &lt;FALSE&gt; <BR>
</B>This parameter specifies whether the table-level <TT>SELECT</TT> privileges are
needed to execute an update or delete that reference's table-column values. </P>

<P><B>TRANSACTION_AUDITING [TRUE/FALSE] &lt;TRUE&gt; <BR>
</B>This parameter specifies that additional transaction information is included
in a special redo record.
<H2><FONT COLOR="#000077">Trusted Oracle7</FONT></H2>
<P>The following parameters apply to the Trusted Oracle7 option. </P>

<P><B>AUTO_MOUNTING [TRUE/FALSE] &lt;TRUE&gt; <BR>
</B>When set to <TT>TRUE</TT>, this parameter specifies that a secondary database
is mounted by the primary database whenever a user connected to the primary database
requests data from the secondary database. </P>

<P><B>DB_MOUNT_MODE [NORMAL/READ_COMPATIBLE] &lt;NORMAL&gt; <BR>
</B>This parameter specifies the access mode to which the database is mounted at
instance startup. A value of <TT>NORMAL</TT> starts the database in normal read-write
mode; <TT>READ_COMPATIBLE</TT> starts the database in read-write mode with the added
feature of supporting concurrent mounting by one or more read-secure instances. </P>

<P><B>LABEL_CACHE_SIZE [number&gt; 50] &lt;50&gt; <BR>
</B>This parameter specifies the cache size for dynamic comparison of labels. This
number should be greater than the label-category combinations in the OS and should
never be less than 50. </P>

<P><B>MLS_LABEL_FORMAT [valid label format] &lt;sen&gt; <BR>
</B>This parameter specifies the format used to display labels. The default value
<TT>sen</TT> specifies sensitive. </P>

<P><B>OPEN_MOUNTS [0..255] &lt;5&gt; <BR>
</B>This parameter specifies the maximum number of databases that an instance can
simultaneously mount in OS MAC mode. This value should be large enough to handle
all the primary and secondary databases you might mount.
<H2><FONT COLOR="#000077">National Language Support</FONT></H2>
<P>The following parameters are used in the configuration of National Language Support
features. </P>

<P><B>NLS_CURRENCY [character string] &lt;derived from NLS_TERRITORY&gt; <BR>
</B>This parameter specifies the string to use as the local currency symbol for the
<TT>L</TT> number format element. </P>

<P><B>NLS_DATE_FORMAT [format mask] &lt;derived from NLS_TERRITORY&gt; <BR>
</B>This parameter defines the default date format to use with the <TT>TO_CHAR</TT>
and <TT>TO_DATE</TT> functions. The value of this parameter is any valid date format
mask. Here is an example:</P>
<PRE><FONT COLOR="#0066FF">NLS_DATE_FORMAT = `DD/MM/YYYY'
</FONT></PRE>
<P><B>NLS_DATE_LANGUAGE [NLS_LANGUAGE value] &lt;value for NLS_LANGUAGE&gt; <BR>
</B>This parameter determines the language to use for the day and month names and
date abbreviations (<TT>AM</TT>, <TT>PM</TT>, <TT>AD</TT>, <TT>BC</TT>). </P>

<P><B>NLS_ISO_CURRENCY [valid NLS_TERRITORY value] &lt;derived from NLS_TERRITORY&gt;
<BR>
</B>This parameter defines the string to use as the international currency symbol
for the <TT>C</TT> number format element. </P>

<P><B>NLS_LANGUAGE [NLS_LANGUAGE value] &lt;OS dependent&gt; <BR>
</B>This parameter defines the default language of the database. This specifies the
language to use for messages, the language of day and month names, symbols to be
used for AD, BC, A.M. and P.M., and the default sorting mechanisms. </P>

<P><B>NLS_NUMERIC_CHARACTERS [two characters] &lt;derived from NLS_TERRITORY&gt;
<BR>
</B>This parameter defines the characters to be used as the group separator and decimal.
The group separator is used to separate the integer groups (that is, hundreds, thousands,
millions, and so on). The decimal separator is used to distinguish between the integer
and decimal portion of the number. Any two characters can be used but they must be
different. The parameter is specified by two characters within single quotes. To
set the group separator to <TT>,</TT> (comma) and the decimal separator to <TT>.</TT>
(period), use the following statement:</P>
<PRE><FONT COLOR="#0066FF">NLS_NUMERIC_CHARACTERS = `,.'
</FONT></PRE>
<P><B>NLS_SORT [BINARY or named linguistic sort] &lt;derived from NLS_LANGUAGE&gt;
<BR>
</B>If this parameter is set to <TT>BINARY</TT>, the collating sequence for <TT>ORDER_BY</TT>
is based on the numeric values of the characters. A linguistic sort decides the order
based on the defined linguistic sort. A binary sort is much more efficient and uses
much less overhead. </P>

<P><B>NLS_TERRITORY [territory name] &lt;OS dependent&gt; <BR>
</B>This parameter specifies the name of the territory whose conventions are used
for day and week numbering. The parameter also provides defaults for other NLS parameters.</P>
<CENTER>
<P>
<HR>
<A HREF="../apa/apa.htm"><IMG SRC="../buttonart/previous.gif" WIDTH="128" HEIGHT="28"
ALIGN="BOTTOM" ALT="Previous chapter" BORDER="0"></A><A HREF="../apc/apc.htm"><IMG
SRC="../buttonart/next.gif" WIDTH="128" HEIGHT="28" ALIGN="BOTTOM" ALT="Next chapter"
BORDER="0"></A><A HREF="../index.htm"><IMG SRC="../buttonart/contents.gif" WIDTH="128"
HEIGHT="28" ALIGN="BOTTOM" ALT="Contents" BORDER="0"></A> <BR>
<BR>
<BR>
<IMG SRC="../buttonart/corp.gif" WIDTH="284" HEIGHT="45" ALIGN="BOTTOM" ALT="Macmillan Computer Publishing USA"
BORDER="0"></P>

<P>&#169; <A HREF="../copy.htm">Copyright</A>, Macmillan Computer Publishing. All
rights reserved.
</CENTER>


</BODY>

</HTML>