Move data from Oracle to Sybase - String problem - oracle

Question

In our DTS package we copy data from Oracle from column VARCHAR2(50 CHAR) (Unicode) to Sybase column VARCHAR(50) (Nonunicode). Source is Oracle DB where we select data from sql query.
Next one is Data conversion where we transform data to STRING[DT_STR] 50 (CODE PAGE 1250). Finally are data inserted to Sybase table column Varchar(50). But after running we see only empty columns, no original values.
Where can be the error?
Update 1
If i execute SELECT ##VERSION on the Sybase server i got the following information:
Adaptive Server Enterprise/15.7/EBF 21520 SMP SP102 /P/ia64/HP-UX B.11.31/ase157sp101/3445/64-bit/FBO/Sat Jul 13 05:47:31 2013
And i am using OLEDB Provider to connect to Sybase destination

Answer 1

Use ADO.Net instead of OLEDB
Based on your comments, it looks like you are using OLEDB Provider to connect to Sybase. The prefered way to connect to Sybase is using ADO.Net providers not OLEDB.
Sybase OLEDB Provider issues
With a small search on the web you can realize that Sybase OLEDB provider may cause several issue when used in SSIS, as example:
Error while extracting data from Sybase using OLE DB in SSIS
After reinstall SYBASE oledb provider it does not appear in SSIS connection manager
Sybase ADO.NET
ADO.Net is the proper way to connect to sybase from SSIS.
In the following official documentation they mentioned that:
Adaptive Server ADO.NET Data Provider can be integrated into SQL Server Integration Services (SSIS), allowing for native access to ADO.NET Data Provider functions.
With the integration, you can use Adaptive Server as an:
ADO.NET Connection Manager
ADO.NET Source data flow component
ADO.NET Destination data flow component
Also in the official download page, they didn't mentioned OLEDB provider but they mentioned ADO.NET
Step by step guide to use Sybase ADO.Net data provider
You can check the following link:
Import and Export from SQL Server to Sybase DB using SSIS
Workaround
If ADO.Net didn't work, check that the issue is not caused by some unicode characters that are not supported in Sybase destination.
Try adding a script component, add an Output column of type DT_STR, and use the following code:
Row.outColumn = Encoding.GetEncoding("Windows-1250").GetString(Encoding.GetEncoding("Windows-1250").GetBytes(Row.inColumn))
And map outColumn to the destination.