Why are you using such an old version of Java? Where are you decoding it? Can you not simply pass "UTF-8" as a parameter to your reading methods?
posted 10 years ago
Reason is: Input is from web browser then the transaction reaches weblogic where the japanese character is converting into UTF-8. from web logic the UTF-8 converted japanese character reached websphere Business integration(WBI 4.3 with jdk1.4), then its inserting into Oracle table through insert query.
The issue is, Oracle Apps or fornt end is unable to get this japanese character inserted by WBI. Oracle team asking to insert as it is in Japanese character.