ORA-16674: standby database type has changed

 If a database created as Physical Standby is converted to a Logical Standby database while the Broker configuration is enabled, you may receive an error as follows.

ORA-16674: standby database type has changed

To fix this error, remove the relevant database from Broker, then add it again.

The process is as follows.

Step1:

Find out the Data Guard Broker Configuration

Step2:

Convert Physical Standby database to Logical Standby

Convert Physical Standby database named “Logical2” to Logical Standby with SQL commands. You may want to read the article “Convert Physical Standby Database to Logical Standby Database” for this process.

Check if its converted correctly:

Step3:

Check Data Guard Broker Configuration

Step4:

Try to Enable Logical2 Database

Step5:

REMOVE Logical2 database from configuration

Routing is removed from prmyFS Far Sync, which sends Redos to logical2.
Try to remove again.
After switchover, database is removed from physclFS Far Sync.
Try to remove again.
Check if its removed.

Step6:

Add the database to the configuration

Step7:

Configure RedoRoutes parameters

Step8:

ENABLE database in configuration

Step9:

Check if everything is correct

 

Comments

Popular posts from this blog

Step by Step: How to troubleshoot a slow running query in Oracle

Register Archive log file manually in standby Database

How to check UNDO tablespace usage and who is using more undo