Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 E-mail Us
 Oracle Articles
New Oracle Articles

 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog

 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Oracle Support

 SQL Tuning

 Oracle UNIX
 Oracle Linux
 Remote s
 Remote plans
 Application Server

 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S


 Consulting Staff
 Consulting Prices
 Help Wanted!


 Oracle Posters
 Oracle Books

 Oracle Scripts

Don Burleson Blog 









Multi-Valued Parameters

Oracle RAC Cluster Tips by Burleson Consulting

This is an excerpt from the bestselling book Oracle Grid & Real Application Clusters.  To get immediate access to the code depot of working RAC scripts, buy it directly from the publisher and save more than 30%.

There are many parameters whose values can vary from one instance to another in the cluster. Table 8.3 shows the parameters that can have different values across the instances of the RAC system. Based on the resources available on a particular node and the tuning methodology desired for a specific instance, many of the values can be set up without affecting other instances. This gives a true independent environment for any given instance.




Specifies the number of database buffers in the buffer cache.


Specifies the number of I/Os that should be needed during a crash or instance recovery.


Specifies the number of seconds the database takes to perform crash recovery of a single instance.


Use ifile to embed another parameter file within the current parameter file. For example: ifile = common.ora


Lets you restrict parallel query operations to a limited number of instances.


Specifies the maximum number of processes that can be created for the execution of jobs.


Specifies the maximum number of concurrent user sessions allowed.

license_sessions_ warning 

Specifies a warning limit on the number of concurrent user sessions.


Uses a text string to specify the default location and root of the disk file or tape device when archiving redo log files.


Specifies the default filename format when archiving redo log files. (Oracle recommends keeping the same format on all instances.)


Value of True indicates that archiving is automatic.


Controls output generated by the archive log process.


Specifies the frequency of checkpoints in terms of the number of redo log file blocks that can exist between an incremental checkpoint and the last block written to the redo log. This number refers to physical operating system blocks, not database blocks.


Specifies the amount of time, in seconds, that has passed since the incremental checkpoint at the position where the last write to the redo log (sometimes called the tail of the log) occurred. This parameter also signifies that no buffer will remain dirty (in the cache) for more than integer seconds.


Specifies the maximum number of open connections globally for each database instance that can be migrated.


Used in conjunction with the instance_groups parameter, it lets you restrict parallel query operations to a limited number of instances.


Specifies the minimum percentage of parallel execution processes (of the value of parallel_max_servers) required for parallel execution.


Specifies the minimum number of parallel execution processes for the instance. This value is the number of parallel execution processes Oracle creates when the instance is started.


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.


Enables or disables global query rewriting for the database.


Determines the degree to which Oracle must enforce query rewriting.


Lets you specify the number of session cursors to cache. Repeated parse calls of the same SQL statement cause the session cursor for that statement to be moved into the session cursor cache.


Specifies the maximum number of concurrent transactions.

transactions_per_ rollback_segment

Specifies the number of concurrent transactions you expect each rollback segment to have to handle.

Table 8.3: Parameters that can vary from one instance to another instance

By using the SET clause of the ALTER SYSTEM statement or by using the OEM (Oracle Enterprise Manager), initialization parameter values can be changed for a given instance. Many of the changes can be made effective immediately. Optionally, they can be made persistent across reboot of the instance.


This is an excerpt from the bestselling book Oracle Grid & Real Application Clusters, Rampant TechPress, by Mike Ault and Madhu Tumma.

You can buy it direct from the publisher for 30%-off and get instant access to the code depot of Oracle tuning scripts.


Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster


Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational