ORA-29702: error occurred in Cluster Group Service operation (Bug 31561819)

If you ever upgrade your database running on a RAC cluster (including Exadata) to version 19c and then rollback your operation back to previous version and you encountered error "ORA-29702: error occurred in Cluster Group Service operation" while starting your database.

Additionally you can start the database with another name but not the same database which has been upgraded and now being rollback. 

This is due to Bug 31561819 and it's related to specifically with RAC cluster.

Mentioned bug exists from version 12.1.0.2 to 19.8.0 and later included in patch set itself. So if you need to fix this problem you would need to apply this patch.

As a workaround none is mentioned in oracle support but there is one:

Workaround : Perform the cold restart services of the your cluster.

crsctl stop crs (on all nodes sequentially)

crsctl start crs (on all nodes sequentially)


Once restart of cluster services is done, try starting the database back and it should work as in our case. If you still faces the problem reach out to oracle support or apply the patch.


References:

Bug 31561819 - Incompatible maxmembers at CRSD Level Causing Database Instance Not Able to Start (Doc ID 31561819.8)

Master Note for Database Error ORA-29702 (Doc ID 1544273.1)



Comments

Post a Comment

Popular posts from this blog

How to Solve - "WAIT FOR EMON PROCESS NTFNS"

Event Monitor Process in short called as EMON is generally used by oracle to send notification. Often applications uses Database Change Notification process also called as DBCN to be aware of changes in the database, based on these notifications they take further actions. Often clients subscribe to the database and notifications are send as callback to them. In some cases you will notice database sessions are showing wait event "WAIT FOR EMON PROCESS NTFNS" and it can even make your database un-responsive. One observation can be these processes are taking more CPU (may not in be in all cases). As stated EMON process deals with database notification and it's spawn and gets down itself and Administrators have no control on theses processes. Anyone can go through oracle documents to read more EMON functioning process.  EMON uses oracle advanced queues and database queue notifications into them and EMON process these notifications to clients based on their subscriptions. In s
Read more

Query Regression - "OR" Transformation Oracle 19c

Recently while upgrading Oracle Database from version 12.1 to 19.10 found there were couple of queries which was running slow post upgrade. Usually these type of behavior is seen while upgrading to newer version and oracle provide various ways to fix them. The difference between good and bad plan was an introduction of  "MERGE JOIN CARTESIAN" (aka MJC) and that's in where regressed query in 19c taking most of the time. MJC sometimes works for queries but in this case it was clearly not helping.  We had following options here:     1. Copy the profile from 12c to 19c database and it worked, but the problem was not just to specific query but with many similar query. This means profile option is not very attractive in this case.     2. We also tried running query with OFE 12.1 to use the same optimizer features as previous version and query behaves well. Though this option can't be placed as we need to use 19c OFE and can be placed only for testing purpose.           alte
Read more

ORA - 12537: TNS: connection closed

Often when active clone to be done to create a new environment, we land up into couple of issues. I will discuss about one issues during this process. Action : Create a new database on different machine from a source. Error : ORA - 12537: TNS: connection closed In order to duplicate the environment was using below rman log /tmp/duplicate.log connect target sys/<password>@<source tns alias> connect auxiliary sys/<password>@<target tns alias> run{ allocate channel ch1 device type disk; allocate channel ch2 device type disk; allocate channel ch3 device type disk; allocate channel ch4 device type disk; allocate auxiliary channel ax1 device type disk; allocate auxiliary channel ax2 device type disk; allocate auxiliary channel ax3 device type disk; allocate auxiliary channel ax4 device type disk; DUPLICATE TARGET DATABASE TO <TARGET_DBNAME> FROM ACTIVE DATABASE NOFILENAMECHECK; } While making connection to Auxiliary database received mentioned error ORA - 12537:
Read more