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

ORA-12731: invalid collation class in regular expression

1 Answers  

---

ORA-22283: filename contains characters that refer to parent directory

1 Answers  

---

TNS-12699: Native service internal error

1 Answers  

---

ORA-29817: non-supported option with disassociate statement

1 Answers  

---

ORA-39032: function string is not supported in string jobs

1 Answers  

---

PLS-00386: type mismatch found at 'string' between FETCH cursor and INTO variables

1 Answers  

---

PLS-00116: Duplicate where-clause in table expression

1 Answers  

---

TNS-01168: Cannot allocate memory

1 Answers  

---

ORA-14641: STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition

1 Answers  

---

ORA-12724: regular expression corrupt

1 Answers  

---

ORA-01876: year must be at least -4713

1 Answers  

---

ORA-04088: error during execution of trigger 'string.string'

1 Answers  

---