Answer / guest

Cause: The Data Guard broker detected a stale sequence value
during its bootstrap or health check operations. The
sequence value is changed each time a role change occurs. A
database that is unavailable to participate in the role
change operation will end up with a stale sequence number.
Should the broker for that database attempt to re-join the
broker configuration, the broker will determine that it
missed a role change and will disable its management of that
database. The broker permanently disables the database since
it may no longer be a viable standby for the new primary.

Action: Examine the broker configuration for databases that
were permanently disabled and which may require reinstantiation.

Please add more information about this Error

RMAN-06198: %-24s string bytes

1 Answers  

---

ORA-12622: TNS:event notifications are not homogeneous

1 Answers  

---

ORA-02377: invalid resource limit

1 Answers  

---

PCC-02414: This attribute does not exist in the specified Object

1 Answers  

---

PLS-00151: Expression or Variable is an illegal type to PLS/QL: string

1 Answers  

---

RMAN-06530: CHANGE ... KEEP not supported for backup set which contains archive logs

1 Answers  

---

ORA-12171: TNS:could not resolve connect identifier: string

1 Answers  

---

ORA-38760: This database instance failed to turn on flashback database

1 Answers  

---

ORA-01955: DEFAULT ROLE 'string' not granted to user

1 Answers  

---

ORA-13624: The task string is executing and cannot be deleted or modified.

1 Answers  

---

ORA-14511: cannot perform operation on a partitioned object

1 Answers  

---

PCC-00124: COMMON_NAME option is specified too late

1 Answers  

---