Skip to content

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

  • by

PRKO-3141 or PRKO-03141

Tried to remove a RAC database from the cluster, but it failed with PRKO-3141.

[oracle@primary01 ~]$ srvctl remove database -d orclcdb
PRKO-3141 : Database orclcdb could not be removed because it was running

PRKO-3141 (or PRKO-03141) means that the database you want to remove is still running, so you cannot remove it at this moment.

Solution

There're 2 ways to solve PRKO-03141.

1. Stop DB then Remove

The formal way to solve the problem is to stop the database before removing it.

[oracle@primary01 ~]$ srvctl stop database -d orclcdb
[oracle@primary01 ~]$ srvctl status database -d orclcdb
Instance ORCLCDB1 is not running on node primary01
Instance ORCLCDB2 is not running on node primary02

Then we can safely remove it.

[oracle@primary01 ~]$ srvctl remove database -d orclcdb
Remove the database orclcdb? (y/[n]) y

2. Remove DB Forcibly

If you don't care the database status and any other dependencies, you can forcibly delete it from the cluster by adding a parameter -f.

[oracle@primary01 ~]$ srvctl remove database -d orclcdb -f

Although the database has been removed from the cluster, it's still running and accessible, which makes the situation really weird. Is there any use case for this?

Leave a Reply

Your email address will not be published. Required fields are marked *