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-13217: invalid parameters supplied in ALTER INDEX statement

1 Answers  

---

TNS-00308: Navigator: Failed to open log while rereading parameter data

1 Answers  

---

TNS-00087: * version - ask the process name to display its version number

1 Answers  

---

ORA-30939: Order violation: Element 'string' may not follow element 'string'

1 Answers  

---

RMAN-06727: could not locate datafilecopy string

1 Answers  

---

---

ORA-01196: file string is inconsistent due to a failed media recovery session

1 Answers  

---

ORA-36276: (XSCGMDLAGG06) Current operator does not need the weight variable.

1 Answers  

---

ORA-09217: sfsfs: failed to resize file

1 Answers  

---

ORA-06713: TLI Driver: error on connect

1 Answers  

---

ORA-29546: badly formed resource: string

1 Answers  

---

ORA-02057: 2PC: string: bad two-phase recovery state number string from string

1 Answers  

---

NNL-00897: Messages sent: number

1 Answers  

---