| Oracle® Database Administrator's Reference 10g Release 2 (10.2) for hp OpenVMS Part Number B25416-04 |
|
|
PDF · Mobi · ePub |
| Oracle® Database Administrator's Reference 10g Release 2 (10.2) for hp OpenVMS Part Number B25416-04 |
|
|
PDF · Mobi · ePub |
This appendix provides information about Oracle Database 10g logical names and utilities, and the default and recommended values for various initialization parameters. Refer to Oracle Database Administrator's Guide for general information about all the initialization parameters.
This appendix contains the following topics:
During installation, several logical names are set up. These assignments are referenced through the ORA_ROOT:[BIN]ORA_DB_LOGICALS.COM file that is referenced whenever you start up, upgrade, link, or relink Oracle Database 10g or other Oracle products.
This section contains the following topics:
If you do not set quotas for the background processes, then Oracle Database 10g uses built-in formulas to determine how to set the quota logical names.
Table D-1 shows each quota logical name, the minimum and maximum values that you can use if you are setting the logical names, and the current formula.
Table D-1 Components of Quota Logical Names
| Calculation Component | Value or Formula |
|---|---|
|
|
2.5 MB |
|
|
Process private storage + room for expansion. 20 MB |
|
|
30 MB size of P0 image |
|
|
Size of page tables needed to map SGA |
|
|
|
|
|
If backing file used:
Without backing file used: 4 * (
|
|
|
If backing file used: ( ( (
Without backing file used:
( ( |
See Also:
Section 5.5.3, "Process Quotas" for more information about modifying Oracle process quotas through logical namesIn Oracle Database 10g, the MTS Dispatcher requires larger BIOLM and ASTLM process quotas than in past releases.
For each number of anticipated MTS Dispatcher connections, both BIOLM and ASTLM must be set to 100 + 5 x number_of_simultaneous_connections. For example, if it is required that the MTS Dispatcher should handle 100 connections, then set both BIOLM and ASTLM to 100 + (5 * 100) = 600. When determining the maximum number of connections, you must consider both inbound and outbound connections. Outbound connections could be made while establishing database links or links to LDAP servers. Failure to set these quotas results in the MTS Dispatcher becoming blocked in a mutex wait state. Therefore, it is better to estimate the highest number of connections possible.
Both quotas may be controlled by setting the system-wide PQL$_BIOLM and PQL$_ASTLM values. They may also be controlled by adding instance-specific or process-specific logical names to ORA_ROOT:[BIN]ORA_DB_LOGICALS.COM.
The process-specific logicals for these are ORA_sid_Dxxx_PQL$_BIOLM and ORA_sid_Dxxx_PQL$_ASTLM.
The instance-wide logicals for these are ORA_sid_PQL$_BIOLM and ORA_sid_Dxxx_PQL$_ASTLM.
Both logical names must be set in the system logical name table. For example, to configure one dispatcher for 100 connections, add the following command to ORA_ROOT:[BIN]ORA_DB_LOGICALS.COM:
"$DEFINE/SYSTEM ORA_your_sid_name_D000_PQL$_BIOLM 600
Note:
For more information on setting the BIOLM and ASTLM values, refer to Metalink Note 156484.1.All parameters used in INIT.ORA require an equal sign (=). For example, DB_BLOCK_SIZE = 8192 is correct.
This section contains the following topics:
Identifies the directory where the trace files created by the detached Oracle Database 10g processes are sent.
None
ORA_ROOT:[ADMIN.dbname.BDUMP]
None
Identifies size (in bytes) of Oracle Database 10g database blocks and the database buffers in the SGA.
A binary multiple of 512 bytes (which is the OpenVMS I/O block size). The maximum value is 32768.
8192
None
Specifies a default text string to indicate the location and name of the disk file when archiving log files. Archiving directly to tape is not supported.
Any valid disk file name.
ORA_ARCHIVE
None
Specifies a default file name format for archived redo log files. LOG_ARCHIVE_FORMAT is appended to the string specified in the LOG_ARCHIVE_DEST parameter.
The redo log file format specifications can contain variables that are substituted with a unique archived redo log file name.
See Also:
Oracle Database Administrator's GuideAny valid file name format.
ARCH%T_%S_%R.ARC
None
Determines whether or not the SGA pages will be paged into each user's working set at connect time. This parameter can be manipulated to reduce page faults.
Define this parameter as TRUE if the current system load has not produced a high rate of page faults.
FALSE
None
Determines the size of the shared pool. The shared pool contains shared cursors and stored procedures.
Larger values of this parameter improve performance in multiuser systems. Smaller values use less memory. This parameter's minimum is 300 KB and its maximum is determined by the size of the SGA. Although there are no SGA size limitations, the minimum value is 30 MB.
160 MB
None
Identifies the size of real memory (in bytes) that will be available for sorting processes
The amount of real memory that you can reasonably expect to have available for sorting. For example, on a system with 256 MB of real memory, with 1/8 available to sort processes and 4 sorts occurring at the same time, you may set this parameter to 256/8/4 = 8 MB.
Generally, a large size improves the efficiency of large sort operations only. In most cases, however, the default works for most database operations.
None
|
 Copyright © 2008, Oracle. All rights reserved. Legal Notices |
|