Answer / guest

Cause: Supplemental logging was not turned on while there is
a logical standby database in the configuration. This could
happen either on the primary or on the logical standby that
is being switched over to be the primary.

Action: Check Data Guard broker log for more details. Issue
"ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY,
UNIQUE INDEX) COLUMNS" to add supplemental logging.

Please add more information about this Error

ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL

1 Answers  

---

ORA-24784: Transaction exists

1 Answers  

---

AMD-00127: dimension #string: RDBMS dimension column not specified

1 Answers  

---

ORA-36966: (XSRELTBL10) workspace object must be a dimension.

1 Answers  

---

DRG-50923: could not rewrite PL/SQL for execution

1 Answers  

---

DRG-52210: error while registering value for attribute: string

1 Answers  

---

NNC-00404: supplied buffer of size string is smaller than minimum size string

1 Answers  

---

ORA-31648: Timeout before master process string finished initialization.

1 Answers  

---

PLS-00123: program too large

1 Answers  

---

DRG-51801: failed to seek in file: %(1)

1 Answers  

---

AMD-00110: parameter string of "string" not valid

1 Answers  

---

ORA-00154: protocol error in transaction monitor

1 Answers  

---