Here are some important Oracle parameters and information in the context of use with SAP applications.
- Path for alert log and background trace files
- Defines the Oracle version whose features can be used to the greatest extent
- As a rule, it must not be reset to an earlier release (see Note SAP 598470).
- A value with three parts (such as 10.2.0) rather than five parts (such as 10.2.0.2.0) is recommended to avoid changing the parameter as part of a patch set installation.
- If an ORA-00201 error occurs when you try to convert the value with five parts 10.2.0.2.0 to 10.2.0, you can leave the value 10.2.0.2.0 (independent of the patch set used).
- Path and name of the control files that are used
- Defines how many days historic data is retained in the control files
- Historic data is required by RMAN, for example.
- May cause control files to increase in size (see Note 904490)
- Path under which core files are stored
- Size of an Oracle block
- Can be set to a value higher than 8K in well-founded individual cases after it has been approved by SAP Support (see Note 105047)
- Size of the Oracle data buffer (in bytes)
- Optimal size depends on the available memory (see Notes 789011 and 617416)
- Maximum number of Oracle data files
- Name of the database
- Number of DBWR processes
- Activation of internal control mechanisms and functions
- To set events in SPFILE, refer also to Note 596423.
- If many events are set, data sources such as V$PARAMETER, DBA_HIST_PARAMETER, or "SHOW PARAMETER" may supply an incomplete value. This is only a display problem. The values that are included in V$PARAMETER2 are the relevant values.
- Activation of file system functions (see Note 999524 and Note 793113)
- If you previously used a large file system cache (>= 2 * Oracle Buffer Pool), the performance may get worse after you activated the direct I/O if you set FILESYSTEMIO_OPTIONS to SETALL. Therefore, it is important that you enlarge the Oracle buffer pool to replace the file system cache that is no longer available.
- Optimized scheduling policy for Oracle processes on HP-UX.
- The privileges RTSCHED and RTPRIO must be assigned to the dba group to enable you to use the functions (see Note 1285599).
- Historic variant of LOG_ARCHIVE_DEST_1, which is not compatible with features such as the Flash Recovery Area and which should therefore no longer be used.
- Path/prefix for offline redo logs
- The syntax differs with an additional "LOCATION=" string of LOG_ARCHIVE_DEST; if this difference is ignored, ORA-16024 occurs concerning LOG_ARCHIVE_DEST_1.
- Name format of the offline redo logs
- To avoid the problems described in Note 132551, it must be explicitly set to WINDOWS at least.
- Minimum size of the Oracle redo buffer (in bytes)
- Oracle internally determines the buffer's actual size, so it is normal for "SHOW PARAMETER LOG_BUFFER" or a SELECT on V$PARAMETER to return values between 1MB and 16MB.
- Defines whether checkpoints are to be logged in the alert log
- Maximum size of Oracle trace files (in operating system blocks)
- A limitation is useful to avoid file system overflows and to reduce the duration of the dump generation.
- You can increase it temporarily if required.
- Maximum number of cursors opened in parallel by one session
- Determines how much data is to be read to determine the access plan.
- Level 2 (the default setting for Oracle 10g): Dynamic sampling is performed only if tables do not have any statistics.
- Level 6: As level 2 and includes dynamic sampling of 128 table blocks if literals are used and there are no bind variables.
- Adjusts the calculated index costs; when there is a value of 20 (percent), index costs are reduced by a factor of 5, for example.
- A value lower than 100 is advisable so that index accesses are preferred instead of full table scans.
- Defines size of the memory area for parallel query messages (in bytes)
- Defines the maximum number of parallel execution processes (see Note 651060)
- Based on the number of CPU Cores of the database server
- The number of CPU Cores generally corresponds to the default value for the Oracle parameter CPU_COUNT. If you are unsure in individual cases, you can use the value of the parameter CPU_COUNT (for example, in transaction DB26).
- If the database shares the server with other software (for example, SAP central instance, other Oracle instances), you can also select a lower value (for example, 8 CPU Cores, the SAP central instance and the Oracle database should share resources 50:50 -> PARALLEL_MAX_SERVERS = 8 * 0.5 * 10 = 40).
- Defines the number of parallel query processes that can be executed in parallel for each CPU
- Influences the DEFAULT level of parallel processing during a parallel execution (see Note 651060).
- Checks the available PGA memory (see Notes 789011 and 619876)
- Defines the maximum number of Oracle processes that exist in parallel
- The component relating to ABAP work processes is only relevant in systems with ABAP stacks. The component relating to J2EE server processes is only relevant in systems with Java stacks.
- <max-connections> indicates the maximum number of connections (also called pool size) of the J2EE system DataSource (sysDS.maximumConnections). You can set the value of this parameter using the VisualAdmin tool or other J2EE administration tools.
- Defines whether query transformations are also factored in when the access path is determined
- Enables access later on to objects that have already been dropped
- Not supported by SAP (see Note 105047)
- Defines whether TCP database access via OPS$ users is allowed (see Note 400241)
- Defines whether the system has to create replication information when the database is accessed
- Performance improves if it is deactivated
- Defines the maximum number of Oracle sessions that exist in parallel - must be configured larger than PROCESSES, since single processes can serve several sessions (for example, in the case of multiple database connections from work processes)
- Defines the size of the Oracle shared pool (see Notes 690241 and 789011)
- Specifies to what extent STAR transformations can be used
- Defines whether automatic undo management is used (see Note 600141)
- Defines the undo tablespace to be used (see Note 600141)
- Path for trace files of Oracle shadow processes
- Defines whether data of a B*TREE index can be transformed into a bitmap display during a database access.
- Determines whether bloom filters may be used during joins.
- Control use of NUMA optimizations.
- Control use of NUMA optimizations.
- Activates or deactivates individual CBO fixes
- To set _FIX_CONTROL, see Note 1455168.
- If many _FIX_CONTROL values are set, data sources such as V$PARAMETER, DBA_HIST_PARAMETER, or "SHOW PARAMETER" may supply an incomplete value. This is only a display problem. The values that are included in V$SYSTEM_FIX_CONTROL are the relevant values.
- Note 1454675 describes a problem whereby the _FIX_CONTROL values do not work despite being displayed correctly in V$PARAMETER.
- With a value of 10 and in connection with fix 6795880, the following is prevented: sporadic hanging during parsing
- This is a generic parameter that can be used for different purposes in certain cases.
- With Oracle 10.2.0.4 and fix 6904068, you use this parameter to introduce a break of 1/100 second between two "cursor: pin S" mutex requests instead of continually executing requests. This may help to avoid critical CPU bottlenecks.
- Controls whether index joins can be used or not; within an index join, two indices of a table are directly linked together.
- Controls whether the In Memory Undo feature (IMU) is used or not
- Defines whether Oracle takes the contents of the bind variables into account during parsing
- May cause various problems (Notes 755342, 723879) if not set to FALSE.
- Controls the cost calculation for IN lists
- If the parameter is set to OFF, long IN lists are evaluated very favorably.
- The CBO performs a reasonable cost calculation for IN lists using the value ALL.
- Therefore, you should always use the default value ALL (this means that you should not set the parameter). If the CBO takes incorrect decisions in individual cases, these incorrect decisions must be analyzed and corrected.
- Controls whether Cartesian merge joins are used.
- Controls whether join predicates may be used in a UNION ALL construct beyond the view boundaries.
- Controls rule-based CBO decision in connection with the FIRST_ROWS hint and ORDER BY (see Note 176754).
- Controls whether table prefetching is used (a value of zero means no table prefetching).