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-13764: Value "string" is illegal as a result percentage.

1 Answers  

---

ORA-00069: cannot acquire lock -- table locks disabled for string

1 Answers  

---

ORA-02178: correct syntax is: SET TRANSACTION READ { ONLY | WRITE }

1 Answers  

---

ORA-14305: List value 'string' specified twice in partition 'string'

1 Answers  

---

ORA-22303: type "string"."string" not found

1 Answers  

---

PROT-00707: Cluster registry integrity check failed

1 Answers  

---

ORA-26711: remote table does not contain a primary key constraint

1 Answers  

---

RMAN-06068: recovery aborted because of missing datafiles

1 Answers  

---

ORA-29917: cannot lock a table which gets its rows from a collection operand

1 Answers  

---

SQL-02134: Invalid runtime context

1 Answers  

---

DRG-50947: ABOUT clause not allowed without a theme index

1 Answers  

---

ORA-39060: table(s) dropped because of conflict with master table

1 Answers  

---