Thanx for reply.
We are using Oracle DB. We are using DBD::Oracle driver and data type of column where these data is stores id NVARCHAR. 
Oracle NLS_NCHAR enviroment variable is AL16UTF16.

Japanese character are inserted into Sybase DB table by some other tachnology and DBI is used for sybase conenctivity.My script is fetching from Sybase table.But not Japanese character are stored into variable.So first I need to know why not actual Japanese character are fetched
?
Post this what should be done to store these Japanese character into Oracle?. 

Thanx,
Prafull

You need to check five things:

1. In what encoding is the data stored in the Sybase database?
2. Does your script Encode::decode the data from the proper encoding?
3. In what encoding is the data stored in the Oracle database?
4. Does your script Encode::encode the data to the proper encoding?
5. Does your script output to the console in the encoding that the console uses?

In Sybase Japanese data columns are encoded in Shift-JIS encoding.

We are retrieving this data using DBI.
use DBI qw(:sql_types);

 if ( @row = $dbFOX_sth->fetchrow_array ) {
                 ( $sInstrumentNameJ, $sInstrumentShortJ )    = @row;

When we print this data in unix console it comes as junk.

After we get this value in a variable we pass this to a stored proc which inserts data in Oracle Nvarchar2 data type field.

Here it comes as inverted ?.

Please advise.

What is the charset of the Sybase server?
Are the strings stored in univarchar() or in varchar() columns?

If the charset is not set to utf8, and if the columns are not univarchar(), then you need to either have the client code (DBI/DBD::Sybase) use the utf8 charset when fetching the data, or use the same charset as the dataserver.

If the data is stored in univarchar() columns then you should set your client charset to utf8.

DBD::Sybase 1.12 should have better support for unicode/utf8 characters, btw.

Michael