Answer / guest

Cause: In the act of failover or switchover, the database
resource guard may detect that reinstantiation of the
database is necessary due to the impending role change. This
occurs when the database resource guard recognizes a
situation in which the the database in question cannot be a
viable standby database for the new primary database.

Action: Reinstantiate (or flashback) the database indicated
by the broker and then re-enable broker management of that
database in the broker configuration.

Please add more information about this Error

NNL-00346: Save_config_on_stop is now ON

1 Answers  

---

ORA-04044: procedure, function, package, or type is not allowed here

1 Answers  

---

ORA-19562: file string is empty

1 Answers  

---

ORA-32407: cannot exclude new values when materialized view log includes new values

1 Answers  

---

ORA-04081: trigger 'string' already exists

1 Answers  

---

ORA-02087: object locked by another process in same transaction

1 Answers  

---

ORA-39315: illegal swap() call: only applys after clone/sync_code

1 Answers  

---

ORA-00977: duplicate auditing option

1 Answers  

---

EXP-00053: unable to execute QUERY on table string because the table has inner nested tables

1 Answers  

---

ORA-30158: The OCIFileWrite causes the file to exceed the maximum allowed size

1 Answers  

---

ORA-01641: tablespace 'string' is not online - cannot add data file

1 Answers  

---

RMAN-06411: backup copies setting out of range (1-4): number

1 Answers  

---