"RAC" requires a unique set of important parameter lists in a RAC environment

The setting of database parameters in a RAC environment requires more attention. Most parameters in a RAC environment require the same settings for each node instance, but individual parameters are unique to each instance and need to be set separately.

1. Parameters that need to be set to the same value
What parameters need to be set to the same value in multiple instances of the RAC environment? Initialization parameters that are critical when creating a database and initialization parameters that affect specific database operations must have the same value.
For example, the following parameters require a uniform setting in each instance of the RAC Environment:
Active_instance_count
Archive_lag_target
Cluster_database
Control_files
Db_block_size
Db_domain
Db_files
Db_name
Db_recovery_file_dest
Db_recovery_file_dest_size
Db_unique_name
Max_commit_propagation_delay
Trace_enabled
Undo_management

2. Parameters that need to be set to different values
In a RAC environment, in order to differentiate between different instances and manage different instances, the following parameters require specific settings based on the specific instance.
THREAD
Rollback_segments
Instance_name
Instance_number
Undo_tablespace

3. View the parameter files in the RAC environment
Another effective way to obtain a parameter that is adjusted according to a specific instance is to obtain it by looking at the database's parameter file.
Take a parameter file on a RAC node as an example for reference.
[Email protected]> Create pfile= '/home/oracle/initracdb1.ora ' from SPFile;

File created.

[Email protected]> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0-production
With the partitioning, Real application Clusters, OLAP, Data Mining
and Real Application Testing options
[email protected]/home/oracle$ cat Initracdb1.ora
racdb1.__db_cache_size=41943040
racdb2.__db_cache_size=37748736
racdb1.__java_pool_size=4194304
racdb2.__java_pool_size=4194304
racdb1.__large_pool_size=4194304
racdb2.__large_pool_size=4194304
racdb1.__shared_pool_size=109051904
racdb2.__shared_pool_size=113246208
Racdb1.__streams_pool_size=0
Racdb2.__streams_pool_size=0
*.audit_file_dest= '/oracle/app/oracle/admin/racdb/adump '
*.background_dump_dest= '/oracle/app/oracle/admin/racdb/bdump '
*.cluster_database_instances=2
*.cluster_database=true
*.compatible= ' 10.2.0.1.0 '
*.control_files= ' +dgdata/racdb/controlfile/current.256.733087241 ', ' +dgfla/racdb/controlfile/ current.256.733087241 '
*.core_dump_dest= '/oracle/app/oracle/admin/racdb/cdump '
*.db_block_size=8192
*.db_create_file_dest= ' +dgdata '
*.db_domain= "
*.db_file_multiblock_read_count=16
*.db_name= ' racdb '
*.db_recovery_file_dest= ' +dgfla '
*.db_recovery_file_dest_size=21474836480
racdb2.instance_number=2
Racdb1.instance_number=1
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
*.remote_listener= ' listeners_racdb '
*.remote_login_passwordfile= ' Exclusive '
*.sga_target=167772160
racdb2.thread=2
Racdb1.thread=1
*.undo_management= ' AUTO '
Racdb2.undo_tablespace= ' UNDOTBS2 '
Racdb1.undo_tablespace= ' UNDOTBS1 '
*.user_dump_dest= '/oracle/app/oracle/admin/racdb/udump '

4. Summary
In order to meet the management requirements on different node instances of Oracle RAC, the correctness of parameter settings on each instance is particularly important, and it is recommended to have an in-depth understanding of commonly used important parameters.

Ext.: http://blog.itpub.net/519536/viewspace-681283/

RAC requires a unique set of important parameter lists in a RAC environment