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-27372: length of action and arguments exceeds platform limit string

1 Answers  

---

KUP-03001: fatal error during library cache pre-loading

1 Answers  

---

ORA-06564: object string does not exist

1 Answers  

---

ORA-28546: connection initialization failed, probable Net8 admin error

1 Answers  

---

ORA-32320: REFRESH FAST of "string"."string" unsupported after container table PMOPs

2 Answers  

---

ORA-32832: failure string trying to acquire administration lock

1 Answers  

---

ORA-38472: VARCHAR representation of the data item is too long.

1 Answers  

---

ORA-12402: invalid format string: string

1 Answers  

---

ORA-32824: schedule exists for source string and destination string

1 Answers  

---

RMAN-06214: %-15s string

1 Answers  

---

ORA-13110: cannot drop topology with associated topo_geometry tables

1 Answers  

---

ORA-35276: (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ]

1 Answers  

---