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-32773: operation not supported for smallfile tablespace string

1 Answers  

---

ORA-13363: no valid ETYPE in the geometry

1 Answers  

---

SQL*Loader-00274: At least 2 read buffers have to be specified.

1 Answers  

---

ORA-39004: invalid state

1 Answers  

---

DRG-11715: attempt to add a BT relation between 2 KB categories string and string

1 Answers  

---

ORA-06043: NETDNT: message send failure

1 Answers  

---

ORA-28140: Invalid column specified

1 Answers  

---

ORA-00750: database has been previously mounted and dismounted

2 Answers  

---

PCB-00312: Keyword WORK required here by ANSI

1 Answers  

---

NNL-00241: Processing of modification requests is currently enabled

1 Answers  

---

ORA-24190: length of payload exceeds string

1 Answers  

---

ORA-30735: cannot create multiple subtables of the same type under a supertable

1 Answers  

---