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

QSM-02058: set operator in mv and compatibility mode is less than 9.0

1 Answers  

---

NNL-00223: Statistic counters are next logged in string

1 Answers  

---

ORA-37044: (XSACQUIRE_OLDGEN) Cannot acquire object workspace object without resync.

1 Answers  

---

ORA-22978: only simple attribute name is allowed in the WITH OBJECT OID clause

1 Answers  

---

ORA-02351: internal error: string

1 Answers  

---

---

ORA-06917: CMX: error in data read (too many bytes read)

1 Answers  

---

ORA-02474: Fixed hash area extents used (string) exceeds maximum allowed (string)

1 Answers  

---

ORA-07256: sptrap: cannot set up signal handler to catch exceptions.

1 Answers  

---

DRG-11833: Request-URI Too Big

1 Answers  

---

ORA-32161: Cannot perform piecewise fetch

1 Answers  

---

SQL*Loader-00941: Error during describe of table string

1 Answers  

---

ORA-24123: feature string is not yet implemented

1 Answers  

---