In 11gR2
NOTE : This is in a Policy Managed configuration
Adding a database service
Since this is Policy Managed database in the RACSP Server Pool, I added a service with the appropriate parameters. The SINGLETON cardinality means that it will run on only one instance. (See the previous post for the service MY_RAC_SVC with the cardinliaty UNIFORM).
Let's verify the alert.log entry.
The SCOPE specification of the ALTER SYSTEM limits the service to only this instance. (Note : MY_RAC_SVC had already been added to RACDB_2 earlier).
Removing a database service
Now, let's remove a database service
I need to first stop the service.
I can now remove the service.
Now, only the new service is listed.
Modifying the cardinality of a service
The service has been modified from SINGLETON (single instance) to UNIFORM (all instances).
Verifying this on node 2.
The service has been enabled on RACDB_2 as well now.
.
.
.
NOTE : This is in a Policy Managed configuration
Adding a database service
[root@node1 ~]# su - oracle -sh-3.2$ srvctl add service -d RACDB -s NEW_SVC -g RACSP -c SINGLETON -sh-3.2$ srvctl config service -d RACDB -s NEW_SVC Service name: NEW_SVC Service is enabled Server pool: RACSP Cardinality: SINGLETON Disconnect: false Service role: PRIMARY Management policy: AUTOMATIC DTP transaction: false AQ HA notifications: false Failover type: NONE Failover method: NONE TAF failover retries: 0 TAF failover delay: 0 Connection Load Balancing Goal: LONG Runtime Load Balancing Goal: NONE TAF policy specification: NONE Edition: Service is enabled on nodes: Service is disabled on nodes: -sh-3.2$ -sh-3.2$ srvctl start service -d RACDB -s NEW_SVC -sh-3.2$
Since this is Policy Managed database in the RACSP Server Pool, I added a service with the appropriate parameters. The SINGLETON cardinality means that it will run on only one instance. (See the previous post for the service MY_RAC_SVC with the cardinliaty UNIFORM).
Let's verify the alert.log entry.
-sh-3.2$ cd /u01/app/oracle/diag/rdbms/racdb/RACDB_1 -sh-3.2$ cd trace -sh-3.2$ tail alert_RACDB_1.log Begin automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK" Tue Jul 15 22:01:20 2014 End automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK" Tue Jul 15 22:06:45 2014 db_recovery_file_dest_size of 4000 MB is 22.25% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Tue Jul 15 22:11:10 2014 ALTER SYSTEM SET service_names='MY_RAC_SVC','NEW_SVC' SCOPE=MEMORY SID='RACDB_1'; -sh-3.2$
The SCOPE specification of the ALTER SYSTEM limits the service to only this instance. (Note : MY_RAC_SVC had already been added to RACDB_2 earlier).
Removing a database service
Now, let's remove a database service
-sh-3.2$ srvctl config service -d RACDB -s MY_RAC_SVC Service name: MY_RAC_SVC Service is enabled Server pool: RACSP Cardinality: UNIFORM Disconnect: false Service role: PRIMARY Management policy: AUTOMATIC DTP transaction: false AQ HA notifications: false Failover type: NONE Failover method: NONE TAF failover retries: 0 TAF failover delay: 0 Connection Load Balancing Goal: LONG Runtime Load Balancing Goal: NONE TAF policy specification: NONE Edition: Service is enabled on nodes: Service is disabled on nodes: -sh-3.2$ srvctl remove service -d RACDB -s MY_RAC_SVC PRCR-1025 : Resource ora.racdb.my_rac_svc.svc is still running
I need to first stop the service.
-sh-3.2$ srvctl stop service -d RACDB -s MY_RAC_SVC -sh-3.2$ -sh-3.2$ srvctl config service -d RACDB -s MY_RAC_SVC Service name: MY_RAC_SVC Service is enabled Server pool: RACSP Cardinality: UNIFORM Disconnect: false Service role: PRIMARY Management policy: AUTOMATIC DTP transaction: false AQ HA notifications: false Failover type: NONE Failover method: NONE TAF failover retries: 0 TAF failover delay: 0 Connection Load Balancing Goal: LONG Runtime Load Balancing Goal: NONE TAF policy specification: NONE Edition: Service is enabled on nodes: Service is disabled on nodes: -sh-3.2$ tail alert_RACDB_1.log End automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK" Tue Jul 15 22:06:45 2014 db_recovery_file_dest_size of 4000 MB is 22.25% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Tue Jul 15 22:11:10 2014 ALTER SYSTEM SET service_names='MY_RAC_SVC','NEW_SVC' SCOPE=MEMORY SID='RACDB_1'; Tue Jul 15 22:17:48 2014 ALTER SYSTEM SET service_names='NEW_SVC' SCOPE=MEMORY SID='RACDB_1'; -sh-3.2$
I can now remove the service.
-sh-3.2$ srvctl remove service -d RACDB -s MY_RAC_SVC -sh-3.2$ srvctl config service -d RACDB Service name: NEW_SVC Service is enabled Server pool: RACSP Cardinality: SINGLETON Disconnect: false Service role: PRIMARY Management policy: AUTOMATIC DTP transaction: false AQ HA notifications: false Failover type: NONE Failover method: NONE TAF failover retries: 0 TAF failover delay: 0 Connection Load Balancing Goal: LONG Runtime Load Balancing Goal: NONE TAF policy specification: NONE Edition: Service is enabled on nodes: Service is disabled on nodes: -sh-3.2$
Now, only the new service is listed.
Modifying the cardinality of a service
-sh-3.2$ srvctl modify service -d RACDB -s NEW_SVC -c UNIFORM -sh-3.2$ srvctl config service -d RACDB -s NEW_SVC Service name: NEW_SVC Service is enabled Server pool: RACSP Cardinality: UNIFORM Disconnect: false Service role: PRIMARY Management policy: AUTOMATIC DTP transaction: false AQ HA notifications: false Failover type: NONE Failover method: NONE TAF failover retries: 0 TAF failover delay: 0 Connection Load Balancing Goal: LONG Runtime Load Balancing Goal: NONE TAF policy specification: NONE Edition: Service is enabled on nodes: Service is disabled on nodes: -sh-3.2$ -sh-3.2$ srvctl start service -d RACDB -s NEW_SVC
The service has been modified from SINGLETON (single instance) to UNIFORM (all instances).
Verifying this on node 2.
-sh-3.2$ pwd /u01/app/oracle/diag/rdbms/racdb/RACDB_2/trace -sh-3.2$ tail -2 alert_RACDB_2.log Tue Jul 15 22:27:36 2014 ALTER SYSTEM SET service_names='NEW_SVC' SCOPE=MEMORY SID='RACDB_2'; -sh-3.2$
The service has been enabled on RACDB_2 as well now.
.
.
.
No comments:
Post a Comment