Creating services with srvctl

In a RAC environment we can create services and run these services on a specific RAC instance/node (or a set of instances/nodes). This makes it possible for the applications to connect to specific instances. In this article I would explain how we create a service and make it run on the instance(s) of our choice, and make it automatically failover to another instance/node if current instance node goes down.

How to Add and Remove database to CRS or Oracle Restart

In RAC or Oracle Restart environment we can use “srvctl” command to add resources to CRS for automatic management of the resources. In this article I would explain how we remove and add a database resource to CRS in RAC environment. Same process can be used for single instance database in Oracle Restart environment. These steps are needed to be executed as RDBMS software owner “oracle”. Starting 12c, single letter options (-d, -i, etc.) can still be used, but probably these would be made obsolete in coming releases because full length option (-db, -instance etc.) have been introduced and I will use these full length options here.

CRS-0245: User doesn't have enough privilege to perform the operation

Reason of CRS-0245 is that you are executing “srvctl” command to perform a task that is not authorized for current logged in user. For example, I was trying to remove a RAC database from CRS using srvctl and I faced this error because I was executing this command as “grid” user whereas I was supposed to execute this command as “oracle” user that is RDBMS software owner.

PRKO-3141 : Database could not be removed because it was running

If we use “srvctl” command to remove a database from CRS (in case of RAC) or Oracle Restart (in case of single server GI installation), we might face this error if database is currently  running. To successfully remove a database from CRS using srvctl, either shutdown the database (all instances), or alternatively you can use “–f” (for versions bellow 12c) or “-force” (for 12 and above) option.

OEM Target Status Pending – OEM Metric Collection Error

Oracle Enterprise Manager Cloud Control is a very handy tool to monitor database servers. Sometimes it happens that Cloud Control does not show the actual status of a target. If status of your database is either “Pending” or “Metric Collection Error”, you can try following trouble shooting steps to resolve the problem. Similar steps may also be followed if targets other than database targets face same issue.