Answer / guest

Cause: Due to a problem in 8.0.2 Export, national character
data in NCHAR and NVARCHAR2 columns was incorrectly assumed
to be in the export server's data base character set and was
converted to the export client's data base character set.
This conversion would only be correct if the export server's
data base character set was the same as the export server's
national character set and the export client's data base
character set was the same as the export client's national
character set. All other combinations would likely be
incorrect. This export dump file was generated by 8.0.2
Export and the export client and server characater sets did
not fit that criteria.

Action: Examine the national character data. If incorrect,
update the data with correct data.

Please add more information about this Error

ORA-16721: unable to set LOG_ARCHIVE_DEST_n parameters

1 Answers  

---

ORA-33625: (FRASSIGN02) You cannot use the APPEND keyword with concat dimension workspace object.

1 Answers  

---

PCB-00401: Character string not properly terminated

1 Answers  

---

ORA-32031: illegal reference of a query name in WITH clause

2 Answers  

---

ORA-16793: Logical Standby Database Guard is unexpectedly OFF

1 Answers  

---

SQL*Loader-00515: Error getting CPU time

1 Answers  

---

ORA-32813: propagation schedule string already exists

1 Answers  

---

ORA-28277: LDAP search, while authenticating global user with passwords, failed.

1 Answers  

---

ORA-27050: function called with invalid FIB/IOV structure

1 Answers  

---

TNS-02501: Authentication: no more roles

1 Answers  

---

ORA-31201: DBMS_LDAP: generic error: string

1 Answers  

---

ORA-32834: Messaging Gateway agent user has not been set

1 Answers  

---