Answer / guest

Cause: The block header on the redo block indicated by the
accompanying error, is not reasonable.

Action: Do recovery with a good version of the log or do
time based recovery up to the indicated time. If this
happens when archiving, archiving of the problem log can be
skipped by clearing the log with the UNARCHIVED option. This
must be followed by a backup of every datafile to insure
recoverability of the database.

Please add more information about this Error

ORA-07741: slemop: $OPEN failure

1 Answers  

---

ORA-27058: file I/O question parameter is invalid

1 Answers  

---

ORA-29385: cannot create plan directive from string to string

1 Answers  

---

ORA-23534: missing column in materialized view container table "string"."string"

1 Answers  

---

IMP-00002: failed to open string for read

1 Answers  

---

DRG-50401: failed to retrieve fuzzy match candidates from db: string

1 Answers  

---

ORA-23476: cannot import from string to string

1 Answers  

---

ORA-24275: function 'string' parameter 'string' missing or invalid

1 Answers  

---

ORA-00205: error in identifying controlfile, check alert log for more info

2 Answers   TechValley,

---

ORA-08186: invalid timestamp specified

1 Answers  

---

KUP-04075: no read access to directory object string

1 Answers  

---

ORA-34279: (MXDCL37) CONCAT can only be used when defining a DIMENSION.

1 Answers  

---