Answer / guest

Cause: The indicated error caused two-pass instance or crash
recovery to fail. Recovery was retried with an alternate
(slower) method to avoid the error.

Action: Correct the cause of the indicated error (also
recorded) so that future instance or crash recovery can
succeed with the two-pass algorithm. This usually requires
making more main memory available to the recovery process.

Please add more information about this Error

ORA-01225: thread number string is greater than MAXINSTANCES string

1 Answers  

---

ORA-30461: 'string.string' cannot be refreshed because it is marked DISABLED

1 Answers  

---

ORA-06780: TLI Driver: recv error code failed

1 Answers  

---

ORA-30015: previously offlined undo tablespace 'string' is still pending

1 Answers  

---

ORA-12494: cannot insert or delete a level, category, or release category

1 Answers  

---

---

ORA-38761: thread string redo log sequence number string could not be accessed

1 Answers  

---

ORA-01198: must specify size for log file if RESETLOGS

1 Answers  

---

RMAN-08515: archive log filename=string thread=string sequence=string

1 Answers  

---

ORA-09873: TASDEF_OPEN: open error when opening tasdef@.dbf file.

1 Answers  

---

ORA-24047: invalid agent name string, agent name should be of the form NAME

1 Answers  

---

LFI-00151: Error on inserting into hash table in function string

1 Answers  

---

QSM-02001: clustered mv container table

1 Answers  

---