Glossary

Term Description
Application Mode Determines whether configuration data is cached. When set to PRODUCTION, configuration data is cached.
Application Resource Cache Timeout Time to cache translations in minutes before checking data source for updates. For value < 0, never check for updates.
Batch Size The maximum number of Cycle tasks that will process in the cycle grid
Cycle Group Size The number of cycle work items to group together and execute on a single thread in a cluster.
Cycle Period The number of seconds that the cycle agent will wait before checking for additional work.
Grid Task Submission Thread Pool Size The number of threads dedicated to submit tasks to grid.
jpa.showSql (Default – false)

Shows information in the application's log/console for all SQLs executed using JPA.

Note: It should be used only in a Non-Production environment.

Default Task Processor Threadpoolsize This thread pool is for processing of activities, scheduled valuation and scheduled computation on any entity that supports such processing. Also this thread pool executes resumable tasks, which are long running tasks in the grid that maintain intermediate state and report progress.
Update stats run

Specifies whether statistics on AsCycle should be updated during policy level of cycle processing.

Values:  Yes, No (default).  
Example: updatestats.run=Yes 	 
Update stats degree

It specifies the degree of parallelism applicable for Oracle. It is applicable when updatestats.run=Yes is set and the value should be set to an integer greater than or equal to 1.

If it is not set, then the table default value specified by the DEGREE clause in the CREATE TABLE or ALTER TABLE statement for AsCycle is used.

Example: updatestats.degree=32		
MEMORY_MAX_TARGET Specifies the maximum value to which a DBA can set the MEMORY_TARGET initialization parameter.
MEMORY_TARGET

Specifies the Oracle system-wide usable memory. The database tunes memory to the MEMORY_TARGET value, reducing or enlarging the SGA and PGA as needed.

Note: Settings of MEMORY_MAX_TARGET and MEMORY_TARGET affect each other.

In a text-based initialization parameter file, if MEMORY_MAX_TARGET is omitted and a value for MEMORY_TARGET is included, then the database automatically sets MEMORY_MAX_TARGET to the value of MEMORY_TARGET. If a line for MEMORY_TARGET is omitted and a value for MEMORY_MAX_TARGET is included, the MEMORY_TARGET parameter defaults to zero. After startup, the MEMORY_TARGET can be changed dynamically to a nonzero value, provided that it does not exceed the value of MEMORY_MAX_TARGET.

System session-cached-cursors The session_cached_cursors parameter is used to reduce the amount of parsing with SQL statements that use host variables. The session_cached_cursors parameter has a default value of 50, and increasing the value of session_cached_cursors requires a larger shared_pool_size to cache the cursors.
COMMIT_LOGGING COMMIT_LOGGING is an advanced parameter used to control how redo is batched by Log Writer. If COMMIT_LOGGING is altered after setting COMMIT_WAIT to FORCE_WAIT, then the FORCE_WAIT option is no longer valid.
COMMIT_WAIT

COMMIT_WAIT is an advanced parameter used to control when the redo for a commit is flushed to the redo logs.

If the parameter is set to FORCE_WAIT, the default behavior (immediate flushing of the redo log buffer with wait) is used. If this is a system setting, the session level and transaction level (COMMIT_WRITE) options will be ignored. If this is a session level setting, the transaction level options will be ignored. If COMMIT_WAIT is altered after it has been set, then the FORCE_WAIT option is no longer valid.

CURSOR_SHARING

Determines what kind of SQL statements can share the same cursors.

Values:

  • FORCE: Forces the statements that may differ in some literals, but are otherwise, identical to share a cursor unless the literals affect the meaning of the statement.
  • SIMILAR: Causes statements that may differ in some literals, but are otherwise identical to share a cursor unless the literals affect either the meaning of the statement or the degree to which the plan is optimized.
  • EXACT: Only allows statements with identical text to share the same cursor.
Number of processes

Specifies the maximum number of operating system user processes that can simultaneously connect to Oracle. Its value should allow for all background processes such as locks, job queue processes, and parallel execution processes.

The default values of the SESSIONS and TRANSACTIONS parameters are derived from this parameter. Therefore, if you change the value of PROCESSES, you should evaluate whether to adjust the values of those derived parameters.

Open cursors

Specifies the maximum number of open cursors (handles to private SQL areas) a session can have at once. You can use this parameter to prevent a session from opening an excessive number of cursors.

It is important to set the value of OPEN_CURSORS high enough to prevent the application from running out of open cursors. The number will vary from one application to another. Assuming that a session does not open the number of cursors specified by OPEN_CURSORS, there is no added overhead to setting this value higher than actually needed.

 

 

 

 

 

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us