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-22881: dangling REF

1 Answers  

---

ORA-07564: sldext: wildcard in filename or extension

1 Answers  

---

RMAN-03034: LEVEL number is invalid. LEVEL must be between string and string

1 Answers  

---

ORA-02043: must end current transaction before executing string

1 Answers  

---

ORA-31162: element or attribute "string" has no SQLType specified

1 Answers  

---

SQL*Loader-00129: Invalid number of rows for direct path column array

1 Answers  

---

ORA-08264: ora_addr: cannot close nameserver

1 Answers  

---

ORA-04055: Aborted: "string" formed a non-REF mutually-dependent cycle with "string".

1 Answers  

---

ORA-13276: internal error [string] in coordinate transformation

1 Answers  

---

ORA-29375: sum of values string for level string, plan string exceeds string

1 Answers  

---

PLS-01468: The first argument of the like-predicate must be a column of type character string

1 Answers  

---

DRG-50704: Net8 listener is not running or cannot start external procedures

1 Answers  

---