ORA-01102: Cannot Mount Database in EXCLUSIVE mode

When we are doing database refresh from Prod to Dev (lower environment), At that time we put the cluster database parameter to false. This parameter is spfile file specific, so we need to bounce the database.

After the refresh completed successfully, we are masteron steroids trying to start the node, at that time we are getting the below error.

High Cable Curls | Exercise Videos & Guides | Bodybuilding.com tren for sale The Intermediate Bodybuilding Program – RippedBody.com

ORA-01102: cannot mount database in EXCLUSIVE mode

Below is a step by step solution, that we are following.

Step1:- Check for cluster database parameter

SYS@DBsGuru1 > show parameter cluster_database;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
cluster_database                     boolean     FALSE
cluster_database_instances           integer     1

Step2: Check for cluster database instance.

This parameter specifies the number of instances we have. Change the value of this parameter to n of instance.

SYS@DBsGuru1 > show parameter cluster_database_instances;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
cluster_database_instances           integer     1

After cloning we need to turn on cluster database to True and cluster database instance to number(n) of the node. Like we have 2 node clusters here so we have to specify cluster database instance 2.

Step3: Change the cluster database and cluster database instance parameter value.

SYS@DBsGuru1 > alter system set cluster_database=TRUE scope=spfile sid='*';

System altered.

SYS@DBsGuru1 > alter system set cluster_database_instances=2 scope=spfile sid='*';

System altered.

Bounce all the instance, or you can bounce the database, as we have a test environment, we have bounced database here.
Make sure you have bounce instance according to your environment’s criticality.

Command to stop the database.

[oracle@DBsGuru1 trace]$ srvctl stop database -d TEST

Command to start database.

[oracle@DBsGuru1 trace]$ srvctl start database -d TEST

Command to check the status of database

[oracle@DBsGuru1 trace]$ srvctl status database -d TEST
Instance TEST1 is running on node DBsGuru1
Instance TEST2 is running on node DBsGuru2

This document is just for learning purpose and always validate in the LAB environment first before applying in the LIVE environment.

Hope so you like this article
Please share your valuable feedback/comments/subscribe and follow us below and don’t forget to click on the bell icon to get the most recent update. Click here to know more about our pursuit.


How useful was this post?

Click on a star to rate it!

Average rating / 5. Vote count:

No votes so far! Be the first to rate this post.

As you found this post useful...

Follow us on social media!

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?


Hello and welcome to DBsGuru,DBsGuru is a group of experienced DBA professionals and serves databases and their related community by providing technical blogs, projects, training. Technical blogs are the source of vast information not about databases but its related product like middleware, PL/SQL, replication methodology, and so on.Thanks for the visits!Share Learn Grow!