Answer / guest

Cause: An attempt to do media recovery using a backup
controlfile found that one of the files is marked read only.
Read only files do not normally need to be recovered, but
recovery with a backup controlfile must recover all online
files.

Action: If the file really is read only, take it offline
before the recovery, and bring the read only tablespace
online after the database is open. If the file does need
recovery use a controlfile from the time the file was
read-write. If the correct controlfile is not available, use
CREATE CONTROLFILE to make one.

Please add more information about this Error

DRG-51804: failed to write to file: %(1)

1 Answers  

---

LSX-00161: disallowed type substitution between "~S" and "~S"

1 Answers  

---

ORA-22297: warning: Open LOBs exist at transaction commit time

1 Answers  

---

TNS-00285: Avg Connect Time (secs) : number

1 Answers  

---

ORA-32134: Cannot assign LOBs

1 Answers  

---

ORA-07617: $FORMAT_CLASS failed translating the binary label to a string

1 Answers  

---

ORA-03286: ALLOCATE EXTENT not valid for HASH CLUSTERS

1 Answers  

---

NZE-29042: Read buffer is not empty.

1 Answers  

---

DRG-10525: missing REBUILD keyword

1 Answers  

---

ORA-08206: ora_addr: cannot translate address file name

1 Answers  

---

SQL*Loader-00106: Invalid discard file name on command line

1 Answers  

---

IMG-00604: unable to access destination image data

1 Answers  

---