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

NNO-00318: overriding next statistic counter reset, resetting in number seconds

1 Answers  

---

ORA-15101: no action specified

1 Answers  

---

ORA-00400: invalid release value string for parameter string

1 Answers  

---

ORA-24791: invalid transaction start flags

1 Answers  

---

ORA-28293: No matched Kerberos Principal found in any user entry

1 Answers  

---

---

RMAN-08180: channel string: restore complete, elapsed time: string

1 Answers  

---

ORA-23496: can not change disabled status for "string" and "string"

1 Answers  

---

ORA-13838: invalid ADDRESS value

1 Answers  

---

ORA-00353: log corruption near block string change string time string

1 Answers  

---

ORA-30727: duplicate referential constraint for a REF column

1 Answers  

---

NZE-28758: memory release failure

1 Answers  

---

LSX-00008: feature "~s" is not implemented

1 Answers  

---