Answer / guest

Cause: A media recovery session encountered a table that was
loaded by the direct loader without logging any redo
information. Some or all of the blocks in this table are now
marked as corrupt.

Action: The table must be dropped or truncated so that the
corrupted blocks can be reused. If a more recent backup of
the file is available, try to recover this file to eliminate
this error.

Please add more information about this Error

ORA-24960: the attribute string is greater than the maximum allowable length of number

1 Answers  

---

ORA-13757: "SQL Tuning Set" "string" is active.

1 Answers  

---

ORA-14025: PARTITION may not be specified for a materialized view or a materialized view log

1 Answers  

---

PLS-00484: redundant exceptions 'string' and 'string' must appear in same exception handler

1 Answers  

---

ORA-19728: data object number conflict between table string and partition string in table string

1 Answers  

---

---

ORA-13239: sdo_dimensionality not specified during n-d R-tree creation

1 Answers  

---

ORA-31165: cannot load object-relational XML attribute using direct path

1 Answers  

---

NNC-00428: invalid meta-data data item

1 Answers  

---

RMAN-06485: changed archivelog expired

1 Answers  

---

PCC-02201: Found syntax error

1 Answers  

---

ORA-31212: DBMS_LDAP: PL/SQL - Invalid LDAP mod_array.

1 Answers  

---

ORA-22316: input type is not a collection type

1 Answers  

---