Focus on performance and high availability of IT infrastructure especially Database and OS.
Friday, March 28, 2014
Converting an Administrator-Managed Database to a Policy-Managed Database and Vice-Versa
(VERSION INFORMATION: Oracle GI & DB188.8.131.52; Red Hat 5u7)
Oracle RAC provides a new method to manage your clustered database. Traditionally, databases were administrator managed, where a DBA managed each instance of the database by defining specific instances to run on specific nodes in the cluster. To help implement dynamic grid configurations, Oracle RAC 11g release 2 (11.2) introduces policy-managed databases, where the DBA is required only to define the cardinality (number of database instances required). Oracle Clusterware manages the allocation of nodes to run the instances and Oracle RAC allocates the required redo threads and undotablespaces, as needed (when database uses OMFs).
Now, let convert ORCL database from the old administrator managed to policy-managed database.
Record the current configuration.
$ srvctlconfig database -d orcl
$ srvctlconfig service -d orcl
creating a server pool called tobi_cluster_pool with two node as maximum.
[oracle@red1 ~]$ srvctl modify service -d orcl -s dtptest.tobi.com -x true #set the DTP (Distributed Transaction Processing) option to true.
[oracle@red1 ~]$ srvctl status service -d orcl -s dtptest.tobi.com
Start the service
[oracle@red1 ~]$ srvctl start service -d orcl -s dtptest.tobi.com
NOTE: You cannot directly convert a policy-managed database to an administrator-managed database. Instead, you can remove the policy-managed configuration using the srvctl remove database and srvctl remove service commands, and then register the same database as an administrator-managed database
Change from policy to administrator managed database