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-02183: valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }

1 Answers  

---

NZE-29159: Unable to read library.

1 Answers  

---

ORA-12715: invalid character set specified

1 Answers  

---

ORA-31459: system triggers for DBMS_CDC_PUBLISH package are not installed

1 Answers  

---

ORA-15054: disk "string" does not belong to diskgroup "string"

1 Answers  

---

SQL-02142: Collection is NULL

1 Answers  

---

ORA-03203: concurrent update activity makes space analysis impossible

1 Answers  

---

RMAN-08000: channel string: copied datafile string

1 Answers  

---

PCB-00110: Unable to open temporary file "string"

1 Answers  

---

LPX-00237: invalid condition section keyword, must be INCLUDE or IGNORE

1 Answers  

---

ORA-30654: missing DEFAULT keyword

1 Answers  

---

ORA-40214: duplicate setting: string

1 Answers  

---