Answer / guest

Cause: (1) The current export dump file was generated using
Beta-2 of Oracle8.0 AND (2) there was a File that appeared
as an an attribute of an ADT within a table's column AND (3)
the character set of the export server's database was
different than the character set of the import server's
database AND (4) when the filename or the aliasname of the
File increased in size when it was translated to the
character set of the import server. When all of these
conditions are true, translation of the strings could yield
corruption of the data in the column. Rather than proceeding
with the translation, import will leave the character
strings in the File in the old character set.

Action: After import completes, rename the directory aliases
and external filenames to match the real names used for the
target database.

Please add more information about this Error

ORA-12416: policy string not found

1 Answers  

---

ORA-29347: Tablespace name validation failed - failed to match tablespace 'string'

1 Answers  

---

ORA-13620: The task or object string is read-only and cannot be deleted or modified.

1 Answers  

---

PLS-01467: The value list of the IN predicate, if not a subquery, must contain only value_specifications

1 Answers  

---

ORA-30054: invalid upper limit snapshot expression

1 Answers  

---

---

ORA-06605: LU6.2 Driver: Unexpected line turnaround

1 Answers  

---

RMAN-06462: no backupsets found on device DISK that match specification

1 Answers  

---

ORA-13850: Tracing for client identifier string is not enabled

1 Answers  

---

ORA-29803: missing ANCILLARY keyword

1 Answers  

---

DRG-50904: weight string outside valid range 0.1 to 10.0

1 Answers  

---

ORA-03276: duplicate ALLOCATE EXTENT option specification

1 Answers  

---

QSM-02145: GROUP BY clause is present but no aggregate functions are used

1 Answers  

---