Someone asked me how to differentiate whether RAC is Admin or Policy managed after it is created.
First, we should look at the definition:
Administrator-managed: Database administrators define the servers on which databases resource run, and place resources manually as needed. This is the management strategy used in previous releases.
Policy managed: Database administrators specify in which server pool (excluding generic or free) the database resource will run. Oracle Clusterware is responsible for placing the database resource on a server.
Http://docs.oracle.com/cd/E11882_01/install.112/e10813/srvpool.htm#RILIN1065)
That is to say, 11g RAC first has a Server Pool by default, if you do not need to customize the settings. All the services of RAC are managed according to the Default policy, which is called Admin management.
If you need to customize some services or configure them according to your own business logic, you must first define a server pool and then modify the database configuration information.
-------------------------------------- Split line --------------------------------------
Install Oracle 11gR2 (x64) in CentOS 6.4)
Steps for installing Oracle 11gR2 in vmwarevm
Install Oracle 11g XE R2 In Debian
Notes on installing Oracle 11g R2 in Oracle Linux 6.3
-------------------------------------- Split line --------------------------------------
How to check whether Admin managed:
[Grid @ rac1 bin] $ GRID_HOME/bin/srvctl config database-d mydb
Database unique name: mydb
Database name: mydb
Oracle home:/opt/app/oracle/product/11.2.0/dbhome_1
Oracle user: oracle
Spfile: + DATA/mydb/spfilemydb. ora
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools: mydb
Database instances: mydb1
Disk Groups: DATA
Services: Database is administrator managed
This indicates that the RAC is Managed by Admin.
To modify Admin Managed, add a service to RAC. The syntax is as follows:
Srvctl add service-d <db_unique_name>-s <service_name>
-R "<preferred_list>" [-a "<available_list>"] [-P {BASIC | NONE | PRECONNECT}]
-G <server_pool> [-c {UNIFORM | SINGLETON}]
[-K <net_num>]
[-L [PRIMARY] [, PHYSICAL_STANDBY] [, LOGICAL_STANDBY] [, SNAPSHOT_STANDBY]
[-Y {AUTOMATIC | MANUAL}]
[-Q {TRUE | FALSE}]
[-X {TRUE | FALSE}]
[-J {SHORT | LONG}]
[-B {NONE | SERVICE_TIME | THROUGHPUT}]
[-E {NONE | SESSION | SELECT}]
[-M {NONE | BASIC}]
[-Z <failover_retries>]
[-W <failover_delay>]
These options are not always used, but you should be familiar with them. Basically, only the database management option is generally used-l,-u. If TAF is used,-c,-e,-s,-m,-w, etc.
The following example shows how to add a Service
[Grid @ rac1 bin] $ GRID_HOME/bin/srvctl add serverpool-g mypool-l 2-u 2
Add the database to the custom Server Pool:
[Grid @ rac1 bin] $ GRID_HOME/bin/srvctl modify database-d mydb-g mypool
Check the new Policy of mydb RAC.
[Grid @ rac1 bin] $ GRID_HOME/bin/srvctl config database-d mydb
Database unique name: mydb
Database name: mydb
Oracle home:/opt/app/oracle/product/11.2.0/dbhome_1
Oracle user: oracle
Spfile: + DATA/mydb/spfilemydb. ora
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools: mypool
Database instances:
Disk Groups: DATA
Services: Database is policy managed
The database has used the Policy management option.
Note:
You do not need to customize Policy management if you do not need it. Admin management is compatible with 11g RAC and earlier versions and is more common.