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-28178: password not provided by proxy

1 Answers  

---

ORA-06959: Buffer I/O quota is too small

1 Answers  

---

ORA-39015: job is not running

1 Answers  

---

LSX-00210: value "~1S" out of range for type "~2S"

1 Answers  

---

DRG-12001: Please enter username:

1 Answers  

---

ORA-12901: default temporary tablespace must be of TEMPORARY type

1 Answers  

---

AMD-00104: Level "string" cannot be added to the hierarchy; parent and child parameters represent the same level

1 Answers  

---

TNS-00551: underlying transport connection failed

1 Answers  

---

ORA-16171: RECOVER...FINISH not allowed due to gap for thr string, seq string-string

1 Answers  

---

ORA-30934: 'string' (string node) cannot be inserted in parent 'string' (string node)

1 Answers  

---

ORA-21611: key length [string] is invalid

1 Answers  

---

ORA-16729: Validating the value of property string hits error string.

1 Answers  

---