Answer / guest

Cause: The file header block is internally inconsistent. The
beginning of the block has a header with a checksum and
other data for insuring the consistancy of the block. It is
possible that the last disk write did not operate correctly.
The most likely problem is that this is not a datafile for
any database.

Action: Have operating system make correct file available to
database. If the trace file dump indicates that only the
checksum is wrong, restore from a backup and do media recovery.

Please add more information about this Error

ORA-07626: smsget: sga already mapped

1 Answers  

---

NID-00416: Change of database name failed.

1 Answers  

---

ORA-12984: cannot drop partitioning column

1 Answers  

---

ORA-30457: 'string.string' cannot be refreshed because of unmnanaged NOT NULL columns in container

1 Answers  

---

ORA-14459: missing GLOBAL keyword

2 Answers  

---

DRG-51020: out of memory in fuzzy matcher

1 Answers  

---

NNL-00207: Scheduled reload check to occur in string

1 Answers  

---

ORA-12020: materialized view string is not registered

1 Answers  

---

ORA-29962: fatal error occurred in the execution of ODCIINDEXALTER routine

1 Answers  

---

QSM-02080: mv log must have primary key

1 Answers  

---

PCC-00099: Length cannot be given for types ROWID, DATE, or MLSLABEL

1 Answers  

---

ORA-19624: operation failed, retry possible

2 Answers  

---