Answer / guest

Cause: While converting the specified file from one platform
to another, some corrupt blocks were discovered in the
specified file. Details about the corruption have been
written to a server trace file.

Action: If these corrupt blocks are unexpected, you may be
able to use Block Media Recovery at the source database to
fix the problem, then re-convert the files.

Please add more information about this Error

ORA-31656: cannot use TABLESPACE_EXPR filter with transportable mode

1 Answers  

---

ORA-23382: materialized view repgroup "string"."string" is not registered at site string

1 Answers  

---

PLS-00049: bad bind variable 'string'

1 Answers  

---

ORA-19618: cannot name files after restoreValidate has been called

1 Answers  

---

ORA-23374: object group "string"."string" already exists

1 Answers  

---

RMAN-08104: input backupset count=string stamp=string creation_time=string

1 Answers  

---

TNS-01004: reload [<listener_name>] : reload the parameter files and SIDs

1 Answers  

---

ORA-30463: 'string' is not a detail table of any summary

1 Answers  

---

LSX-00214: too many occurrences of particle "~1S", maximum is ~2d

1 Answers  

---

ORA-38768: resizing datafile string failed

1 Answers  

---

NNL-00550: flush [<server_list>] : flush one or more servers' cache(s)

1 Answers  

---

ORA-01658: unable to create INITIAL extent for segment in tablespace string

1 Answers  

---