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

NNL-00511: Shows or sets the server's system query authority requirements

1 Answers  

---

ORA-00409: COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT

1 Answers  

---

DRG-10828: token string is longer than maximum length for column string

1 Answers  

---

RMAN-10007: error closing cursor

1 Answers  

---

ORA-38955: Source platform string not cross platform compliant

1 Answers  

---

ORA-26515: no master log available for 'string.string'

1 Answers  

---

ORA-31453: invalid value string for parameter, expecting: Y, N, or NULL

1 Answers  

---

ORA-36882: (XSSRF01) The second parameter of an AW single row function cannot be NULL.

1 Answers  

---

NNL-00351: Scheduled configuration save to occur in string

1 Answers  

---

PCB-00237: Declaration of "string" cannot have a level number greater than 48

1 Answers  

---

PCC-02023: Found end of file while scanning a PL/SQL statement

1 Answers  

---

ORA-06710: TLI Driver: send interrupt break message failed

1 Answers  

---