There may be entire books written about character set issues in Oracle. In my experience,
if you didn't create the database with UTF-8 support and set the NLS_LANG environment
variable correctly in all the right locations (including Direct Connect clients), then it will not
be possible to get correct encoding in the database. There isn't anything Esri-specific to this,
however, it's just the way Oracle rolls.
- V
PS: I should note that UTF-8 isn't generally NVARCHAR2, it's VARCHAR2; Oracle generally
bumps up to AL32UTF16 once it gets into NVARCHAR2.