|
Sr. |
PARAMETER |
DESCRIPTION |
|
1 |
active_instance_count | Designates one instance in a two-instance cluster as the primary instance, and the other as the secondary instance. This parameter has no functionality in a cluster with more than two instances. |
|
2 |
archive_lag_target | Specifies a log switch after a user-specified time period elapses. |
|
3 |
cluster_database | Specifies whether or not Oracle Database 10gRACis enabled. |
|
4 |
cluster_database_ instances | Equal to the number of instances. Oracle uses the value of this parameter to compute the default value of the large_pool_size parameter when the parallel_automatic_tuning parameter is set to true. |
|
5 |
cluster_interconnects | Specifies the additional cluster interconnects available for use inRACenvironment. Oracle uses information from this parameter to distribute traffic among the various interfaces. |
|
6 |
compatible | This parameter specifies the release with which the Oracle server must maintain compatibility. |
|
7 |
control_files | Specifies one or more names of control files. |
|
8 |
db_block_size | Specifies the size (bytes) of Oracle database blocks. |
|
9 |
db_domain | In a distributed database system, db_domain specifies the logical location of the database within the network structure. |
|
10 |
db_files | Specifies the maximum number of database files that can be opened for this database. |
|
11 |
db_name | Specifies a database identifier. It must correspond to the name specified in the create database statement. |
|
12 |
dml_locks (if 0, same on all) | They can be different if the dml_locks are positive. |
|
13 |
gc_files_to_locks | Controls the mapping of pre-release 9.0.1 parallel cache management (PCM) locks to data files. |
|
14 |
license_max_users | Specifies the maximum number of users you can create in the database. |
|
15 |
max_commit_ propagation_delay | Specifies the maximum amount of time allowed until the system change number (SCN), held in theSGAof an instance, and is refreshed by the log writer process (LGWR). It determines whether the local SCN should be refreshed from the lock value when getting the snapshot SCN for a query. Units are in hundredths of seconds. |
|
16 |
parallel_execution_ message_size | Specifies the size of messages for parallel execution. |
|
17 |
parallel_max_servers | Specifies the maximum number of parallel execution processes and parallel recovery processes for an instance. |
|
18 |
remote_login_ passwordfile | Specifies whether Oracle checks for a password file and how many databases can use the password file. |
|
19 |
row_locking | Specifies whether row locks are acquired during update operations. |
|
20 |
spfile | The value of this parameter is the name of the current server parameter file (SPFILE) in use. This parameter can be defined in a client side PFILE to indicate the name of the server parameter file to use. |
|
21 |
trace_enabled | Controls tracing of the execution history, or code path; Oracle Support Services uses this information for debugging. When trace_enabled is set to true, Oracle records information in specific files when errors occur. |
|
22 |
undo_management | Specifies which undo space management mode the system should use. When set toAUTO, the instance starts in automatic undo management mode. In manual undo management mode, undo space is allocated externally as rollback segments. |
|
23 |
undo_retention | Specifies (seconds) the amount of committed undo information to retain in the database. You can use undo_retention to satisfy queries that require old undo information in order to rollback changes to produce older images of data blocks. You can set the value at instance startup. |
Archive for the ‘RAC’ Category
10 g RAC installation
Posted by Sanjay on January 16, 2011
Posted in RAC | Leave a Comment »
Oracle 11g RAC installation.
Posted by Sanjay on January 10, 2011
Oracle 11g RAC installation.
Posted in RAC | Leave a Comment »
