Handlng character sets in Weblogic

I have a Java application where we do Ajax calls to update screen items. The application is working fine in Eclipse/Tomcat. Where the Ajax call takes a parameter (send with EncodeURIComponent) dos a lookup in the Oracle database and returns a UTF-16 response. This works correctly in the Tomcat environment.
However, when running in the Weblogic environment the parameter that is being sent to the servlet arrives garbled. When I look in our debugging logs on Tomcat the string shows (in the ServletBase class) as a UTF-8 looking string. The same statement in the Weblogic environment shows question marks.
The code that initiates the Ajax request is:
var url = 'JobSearchServlet?clientdata=<%=cd.getId()%>&value=' + encodeURIComponent(param);
              req.open("POST", url, false);
              req.send(null);The code in the ServletBase class (an abstract class that extends HttpServlet) looks like this:
  request.setCharacterEncoding(SystemConfigUtil.getSetting(SystemConfigUtil.DEFAULT_ENCODING, "UTF-8"));
            IUser user = SessionUtil.getUser(request);
            if (_logger.isDebugEnabled())
                 _logger.debug(SystemConfigUtil.getSetting(SystemConfigUtil.DEFAULT_ENCODING, "UTF-8"));
                _logger.debug("ServletBase.processHttpRequest(" + this.getClass().getName() + ") beginning for user " + (user == null ? "guest" : user.getEmailAddress()) + ".");
                java.util.Enumeration theEnum = request.getParameterNames();
                while (theEnum.hasMoreElements())
                    String name = (String)theEnum.nextElement();
                    String []values = request.getParameterValues(name);
                    if (values.length == 1)
                        _logger.debug("  Parameter " + name + "=" + values[0]);
                    else
                        for (int i=0; i<values.length; i++)
                            _logger.debug("  Parameter " + name + "[" + i + "]=" + values);
The output in the debug log for this looks like:
UTF-8
[2010-06-24 08:45:51,955]:[DEBUG]:[com.towers.core.servlet.ServletBase] - ServletBase.processHttpRequest(com.towers.mafwk.servlet.reporting.JobSearchServlet) beginning for user null.
[2010-06-24 08:45:51,955]:[DEBUG]:[com.towers.core.servlet.ServletBase] - Parameter clientdata=A10168526710
[2010-06-24 08:45:51,955]:[DEBUG]:[com.towers.core.servlet.ServletBase] - Parameter value=?????? *<--------------------------- In Tomcat this shows what looks like a UTF-8 string*
[2010-06-24 08:45:51,965]:[DEBUG]:[com.towers.core.servlet.ServletBase] - About to call subclass processHttpRequest
I cannot figure out why this all works correctly on TomCat in my Windows XP environment but fails on the Weblogic environment in Windows Server 2003

Some more information:
Weblogic version 9.2
When receiving the message in the servlet, the parameter in the URL is translated using the code:
new String(myParam.getBytes("8859_1"),"UTF8")
The output of this is showing as ???? in the weblogic logs and as correct cyrillic strings in the Tomcat console.

Similar Messages

  • Need suggestion on Multi currency and Unicode character set use in ABAP

    Hi All,
    Need suggestion. In one of the requirement I saw 'multi-currency and Unicode character set experience in FICO'.
    Can you please elaborate me how ABAPers are invlolved in multi currency as I think this is FICO fuctional area.
    And also what is Unicode character set exp.? Please give me some document of you have any.
    Thanks
    Sreedevi
    Moderator message - This isn't the place to prepare for interviews - thread locked
    Edited by: Rob Burbank on Sep 17, 2009 4:45 PM

    Use the default parser.
    By default, WebLogic Server is configured to use the default parser and transformer to parse and transform XML documents. The default parser and transformer are those included in the JDK 5.0.
    The built-in WebLogic Server DOM factory implementation class is com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl.
    The DocumentBuilderFactory.newInstance method returns the built-in parser.
    DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();

  • Foreign character sets in a database

    I am developing a site where people in many countries (mainly
    Scandinavian) can log on and update their pages. The information,
    (including passwords and usernames) is stored in an access
    database. I am using Access because I have no knowledge of PHP /
    SQL, and the site is unlikely to exceed the limitations of Access
    for a few years.
    Does Access change the format of text, or do I have to set up
    some special encoding? I find that if I type in the username and
    password using an english keyboard, when the original was set up
    using a foreign keyboard I cannot log in. The reverse also applies.
    I am using CS3 in default mode - using utf8. Should I be using
    Westren European encoding, or is Access the fly in the ointment?
    Or is it likely to be another problem.
    Howard Walker

    Hello,
    Specifying the character set for a WebLogic webservice (see:
    http://edocs.bea.com/wls/docs81/webserv/i18n.html#1069629) is one of the
    many enhancements made since the 6.1 release. If possible, the best
    solution for your webservice development would be to upgrade.
    Bruce
    "özkan Demir" wrote:
    >
    Hi all;
    I am developing RPC style webservices on weblogic server 6.1 with service pack
    2.
    I have a problem about character sets. I have to turkish language so that the
    character sets must be ISO-8859-9. But the soap messages are default UTF-8 so
    that turkish characters becomes undetermined.
    Is there a way that I can send soap messages in ISO-8859-9 character set or what
    do I have to solve the problem of turkish characters between the client and the
    server applications with webservices...Please Help!
    Thanks

  • Character sets in RTF messages not working with RTFEditorKit

    I'm using RTFEditorKit.read() to get the text from an RTF document. The text is written in Russian and starts with the following
    {\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\froman\fprq2\fcharset204{\*\fname
    Times New Roman;}Times New Roman CYR;}{\f1\fswiss\fprq2\fcharset0 Arial;}}
    {\colortbl ;\red0\green0\blue128;\red0\green0\blue0;}
    \viewkind4\uc1\pard\tx360\cf1\f0\fs20\'c1\'ee\'eb\'fc\'f8\'e8\'ed\'f1\'f2\'e2\'eeThe reader sets the translation table based on the \ansi\ at the start of the document, which simply maps all bytes to themselves. The initial text, which should be '&#1041;&#1086;&#1083;&#1100;&#1096;&#1080;&#1085;&#1089;&#1090;&#1074;&#1086;', is then converted as latin-1. The 'fcharset204', which is CP1251, is completely ignored, and there's a lovely line in the RTFReader class
    /* TODO: per-font font encodings ( \fcharset control word ) ? */Does anyone know how to extract non latin1 text from RTF or what other tools can be used to extract text from RTF.
    Thanks
    Antony

    Hello,
    Specifying the character set for a WebLogic webservice (see:
    http://edocs.bea.com/wls/docs81/webserv/i18n.html#1069629) is one of the
    many enhancements made since the 6.1 release. If possible, the best
    solution for your webservice development would be to upgrade.
    Bruce
    "özkan Demir" wrote:
    >
    Hi all;
    I am developing RPC style webservices on weblogic server 6.1 with service pack
    2.
    I have a problem about character sets. I have to turkish language so that the
    character sets must be ISO-8859-9. But the soap messages are default UTF-8 so
    that turkish characters becomes undetermined.
    Is there a way that I can send soap messages in ISO-8859-9 character set or what
    do I have to solve the problem of turkish characters between the client and the
    server applications with webservices...Please Help!
    Thanks

  • Character sets and conversions

    Hi all,
    were facing a quite complex problem, for which I'am not even able to specify were it is going wrong or what needs configuring, partly for lack of experience and partly for combining different tecnical areas from which I'm only responible for some of them.
    So I'll sketch breefly the situation, and hopefully you might give me some guidelines or hints as to where to look at.
    The setup : web application (so clients access by use of browser) on Weblogic- Linux platform, Tuxedo on Iseries , and as far as I understand some DB internally to Iseries where data is stored.
    Data is entered in the DB by use of some data-entry application that comes with the iSeries.
    The problem: consulting data by use of the web-aplication , some characters dont show up correctly , e.g. @ in email addresses, e's with accents, ...
    For the chain being "browser <-> WL <-> Tuxedo <-> DB" , the problem might be different points. But from trace beeing activated , we could see that the response going out of tuxedo to WL is not correct...
    Any hint as to what to look for, what can configuration is important, would be welcome ...
    Some sub-questions:
    - I understand Tuxedo is always "installed" in English , with no other option. This means that f.e. logs are in English.
    But can/need to define some character set?
    - Between Tuxedo <-> DB you can use som conversion tables ?
    Any help would be apreciated , were quite lost ..

    Hi,
    Given that you are running Tuxedo on iSeries, I'm guessing you are running Tuxedo 6.5 as the port for the current Tuxedo release on iSeries hasn't been released yet. Tuxedo 6.5 does not directly support multi-byte character strings. The two common buffer formats for string data in Tuxedo are STRING which doesn't support multi-byte characters, or CARRAY which does support multi-byte characters as a CARRAY is essentially a blob. Do you know what buffer type the Tuxedo application is using to send data to WebLogic Server?
    In Tuxedo 9.0 and later, direct support for multi-byte strings was added in the form of the MBSTRING buffer type. This buffer type supports multi-byte strings with a variety of character sets and encodings.
    Regards,
    Todd Little
    Oracle Tuxedo Chief Archiitect

  • UTF/Japanese character set and my application

    Blankfellaws...
    a simple query about the internationalization of an enterprise application..
    I have a considerably large application running as 4 layers.. namely..
    1) presentation layer - I have a servlet here
    2) business layer - I have an EJB container here with EJBs
    3) messaging layer - I have either Weblogic JMS here in which case it is an
    application server or I will have MQSeries in which case it will be a
    different machine all together
    4) adapter layer - something like a connector layer with some specific or
    rather customized modules which can talk to enterprise repositories
    The Database has few messages in UTF format.. and they are Japanese
    characters
    My requirement : I need thos messages to be picked up from the database by
    the business layer and passed on to the client screen which is a web browser
    through the presentation layer.
    What are the various points to be noted to get this done?
    Where and all I need to set the character set and what should be the ideal
    character set to be used to support maximum characters?
    Are there anything specifically to be done in my application code regarding
    this?
    Are these just the matter of setting the character sets in the application
    servers / web servers / web browsers?
    Please enlighten me on these areas as am into something similar to this and
    trying to figure out what's wrong in my current application. When the data
    comes to the screen through my application, it looks corrupted. But the asme
    message when read through a simple servlet, displays them without a problem.
    Am confused!!
    Thanks in advance
    Manesh

    Hello Manesh,
    For the database I would recommend using UTF-8.
    As for the character problems, could you elaborate which version of WebLogic
    are you using and what is the nature of the problem.
    If your problem is that of displaying the characters from the db and are
    using JSP, you could try putting
    <%@ page language="java" contentType="text/html; charset=UTF-8"%> on the
    first line,
    or if a servlet .... response.setContentType("text/html; charset=UTF-8");
    Also to automatically select the correct charset by the browser, you will
    have to include
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> in the
    jsp.
    You could replace the "UTF-8" with other charsets you are using.
    I hope this helps...
    David.
    "m a n E s h" <[email protected]> wrote in message
    news:[email protected]...
    Blankfellaws...
    a simple query about the internationalization of an enterpriseapplication..
    >
    I have a considerably large application running as 4 layers.. namely..
    1) presentation layer - I have a servlet here
    2) business layer - I have an EJB container here with EJBs
    3) messaging layer - I have either Weblogic JMS here in which case it isan
    application server or I will have MQSeries in which case it will be a
    different machine all together
    4) adapter layer - something like a connector layer with some specific or
    rather customized modules which can talk to enterprise repositories
    The Database has few messages in UTF format.. and they are Japanese
    characters
    My requirement : I need thos messages to be picked up from the database by
    the business layer and passed on to the client screen which is a webbrowser
    through the presentation layer.
    What are the various points to be noted to get this done?
    Where and all I need to set the character set and what should be the ideal
    character set to be used to support maximum characters?
    Are there anything specifically to be done in my application coderegarding
    this?
    Are these just the matter of setting the character sets in the application
    servers / web servers / web browsers?
    Please enlighten me on these areas as am into something similar to thisand
    trying to figure out what's wrong in my current application. When the data
    comes to the screen through my application, it looks corrupted. But theasme
    message when read through a simple servlet, displays them without aproblem.
    Am confused!!
    Thanks in advance
    Manesh

  • Can a db with character set UTF8 be restored to AL32UTF8?

    Hello Everyone,
    Good Day.
    Our present production and non-production databases are configured with NLS_CHARACTERSET as UTF8. However, as we are in the process of migrating to a new server, we intend to configure the new databases with NLS_CHARACTERSET as AL32UTF8 (which is the recommended option as per our research. Moreover, came to know that for Weblogic schemas and repositories to work, NLS_CHARACTERSET must be AL32UTF8).
    As we would be restoring from a backup to the new instance created on the new server, kindly help us understand if any issues might arise while restoring due to both being different charactersets?
    Warm Regards,
    Vikram.

    Hi Robin,
    Thank you for the update. Our DB is too huge and contains many schemas to try for a data pump. Hence we had planned for a restoration which might be simpler task with lesser downtime.
    Perhaps, one option would be to create the instances with UTF character set itself and then change it once the migration activity has been completed.
    Also, could you please throw some light on the two character sets as to which one is better and why?
    Warm Regards,
    Vikram.

  • Switching Character Sets in JDeveloper

    Hi, we have developed a number of Portlets on JDev 10.1.2 but used the default encoding of cp1252. When looking back on my course notes I saw that the course instructor had recommended that we set the default project encoding to UTF-8. What are the implications of using the default encoding? We have coded our portlets to use resource bundles in order that we can make them multi-lingual at some point in the future. Is UTF-8 essential for this and if so, should we take the hit now to re-encode ( on trying it, I got errors about malformed input values, mostly hyphens and apostorphes) or will it be a painless process if we do it later on?
    Thanks for any feedback.

    Hello,
    Specifying the character set for a WebLogic webservice (see:
    http://edocs.bea.com/wls/docs81/webserv/i18n.html#1069629) is one of the
    many enhancements made since the 6.1 release. If possible, the best
    solution for your webservice development would be to upgrade.
    Bruce
    "özkan Demir" wrote:
    >
    Hi all;
    I am developing RPC style webservices on weblogic server 6.1 with service pack
    2.
    I have a problem about character sets. I have to turkish language so that the
    character sets must be ISO-8859-9. But the soap messages are default UTF-8 so
    that turkish characters becomes undetermined.
    Is there a way that I can send soap messages in ISO-8859-9 character set or what
    do I have to solve the problem of turkish characters between the client and the
    server applications with webservices...Please Help!
    Thanks

  • Problem with character set - Reports 11.1.1.4

    Hi!
    I have a problem with Oracle Reports 11g regarding character set configuration. The default character set WE8ISO8859P1 works, so PDF reports have a regular display except for Eastern European (EE) letters which are replaced by "¿" sign.
    So, when I set any other character set in reports.sh, which would be a normal step to get EE letters, I'm always getting Greek Alphabet in PDF reports. Why Greek Alphabet?
    The character sets I tried to use are: EE8ISO8859P2, UTF8 and AL32UTF8.
    I changed uifont.ali and included PDF Subset with all four Arial font variants and, of course, I placed all fonts in fonts folder which is pointed by REPORTS_FONT_DIRECTORY.
    In Reports Builder everything works fine, but when I have to deploy the report to the Reports Services, the problem occurs.
    Also, when I've tried to execute PDF report using In-Process Reports Server (rep_wls_reports_hostnameasinst1) instead of AS Instance Reports Server (RptSvr_hostnameasinst1, which is a regular server), I'm getting Greek Alphabet in PDF reports even if the default character set is WE8ISO8859P1 in reports.sh. What is wrong with it? Where is Greek Alphabet configured?
    The production environment is 64-bit Oracle Linux 5.6 with Weblogic 10.3.4 and Forms&Reports 11.1.1.4. Forms works fine with character set EE8ISO8859P2 defined in default.env file.
    Thanks in advance!
    Regards,
    Dejan

    Thank you, Denis!
    Doc 300416.1 was very useful but Note 356221.1 - A Practical Methodology on Porting Reports from Windows to Unix with Different Font is actually crucial for configuring Reports on Linux.
    Also, there is a bug in 11.1.1.3 and 11.1.1.4, which can be fixed using the patch ( Note 1138405.1 - PDF Reports With Font Subsetting Raises Error "Bad /Bbox" on 64-Bit Linux ).
    Kind regards!

  • Validate on allowed character set

    Hi,
       I want to validate the Character set. Means, Now my User Interface taking all characters which are possible through key board like Japanese or Chinese characters. But I want to validate the character set.
      As per my knowledge , we need to check the characters manually by writing the logic to compare the each and every characters  but it is laborious job and creates performance problems also. Is there any alternative way?
    Is it possible to do it with WebDynpro  inbuilt functionality?
    Thanks and Best Regards,
    Vijay

    What kind of validation did you having in mind.  Web Dynpro ABAP will automatically convert all characters to the character set of the ABAP Logon Language.  I probably don't need to tell you, but the ultimate answer to any character set problems is to run a Unicode System and then all characters are supported. 
    Although this weblog is BSP specific, you might find some of the discussion useful:
    [/people/thomas.jung3/blog/2004/07/13/bsp-150-a-developer146s-journal-part-vii--dealing-with-multiple-languages-english-german-spanish-thai-and-polish|/people/thomas.jung3/blog/2004/07/13/bsp-150-a-developer146s-journal-part-vii--dealing-with-multiple-languages-english-german-spanish-thai-and-polish]
    You might be able to use SCP_TRANSLATE_CHARS or one of the other SCP function modules to do some sort of mass validation.

  • Problems with oracle character set

    Hi,
    We use weblogic SP2 and a oracle oci driver to connect to a database. When we tried to store a text file within the database, we found that all the '£' signs in the file are converted to question marks.
    Looking at the NLS_DATABASE_PARAMETERS table in the database suggests that we are using AL32UTF8 as the character set. I have since tried setting the NLS_LANG variable on the application server to use the same character set but this doesn't seem to solve the problem.
    Any experts out there know how I can fix this problem?
    Thanks!

    Hi Yash,
    Can u tell me how to insert values in a nchar/nvarchar column in
    Indian language scripts?
    I have set database characterset to 'IN8ISCII'? But while
    inserting values in the table I am getting error as characterset
    mismatch'
    I have tried it using UTF8 chracterset also??
    As fa as your problem is concerened, I think u have to set the
    nls_ characterset value$ in props$ table
    and same for nls_nchar_characterset column also..
    Thanks in advance
    Manoj mehta

  • Java.sql.SQLException: Non supported character set: oracle-character-set-860

    Hi,
    I am working on resultset.updateRow() and found some problem.
    I've tried the same jsp page on 2 WebLogic server
    one is on a Solaris Platfoem and another is on a NT platform
    On NT Platform it seems to be OK and update the database successfully.
    On Solaris, on error message on WebLogic log but error found in the JDBC log
    java.sql.SQLException: Non supported character set: oracle-character-set-860
    P.S. both jsp page connection to the same database server Oracle 8
    The testing JSP page:
    <%@ page language="java" import="java.sql.*, oracle.jdbc.driver.*,
    java.util.*, javax.sql.*" %>
    <html>
    <head>
    <title>Weblogic Oracle Testing - Store Procedure</title>
    <meta http-equiv="Content-Type" content="text/html; charset=big5">
    </head>
    Oracle Connection Testing
    <br>
    <body bgcolor="#FFFFFF">
    <%
    Connection conn = null;
    Statement stmt = null;
    ResultSet rs = null;
    String sql;
    Driver myDriver =
    (Driver)Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
    try {
    conn=DriverManager.getConnection("jdbc:oracle:thin:sa/z0y1z2y3@oradev01:1521
    :DEV01a");
    DatabaseMetaData DBMetaData = conn.getMetaData();
    boolean support1 =
    DBMetaData.supportsResultSetType(ResultSet.TYPE_SCROLL_SENSITIVE);
    boolean support2 =
    DBMetaData.supportsResultSetType(ResultSet.CONCUR_UPDATABLE);
    %>
    <p><%=support1%></p>
    <p><%=support2%></p>
    <%
    //create a statement
    stmt = conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,
    ResultSet.CONCUR_UPDATABLE);
    //execute a query
    rs = stmt.executeQuery("SELECT tbl_web_trx_hdr.* FROM tbl_web_trx_hdr");
    int concurrency = rs.getConcurrency();
    int type = rs.getType();
    %>
    <p>concurrency: <%=concurrency%></p>
    <p>type: <%=type%></p>
    <%
    rs.moveToInsertRow();
    rs.updateString("org_idx", "CCC");
    rs.updateString("trx_num", "ABC2");
    rs.updateDate("trx_dte", java.sql.Date.valueOf("2001-06-01"));
    rs.updateString("description", "123");
    rs.insertRow();
    rs.updateRow();
    } catch (SQLException e)
    { System.out.println("SQLMessage: " + e.getMessage());
    finally
    { rs.close();
    stmt.close();
    conn.close(); }
    %>
    </body>
    </html>
    Please help
    regards,
    Fannie

    yupp finally i got the solution. . .
    I was using connection from tomcat connection pooling.
    Hence, even though i was setting the classes12.jar and nls_charset12.jar in the classpath and compiling, -In runtime tomcat was using its own classes in the common/lib folder. . .(which might not support oracle-character-set-178.)
    So just added this jars into the common/lib of tomcat instead of web-inf/lib of my project
    and things began working. . .
    Thanks for the hint jshell. . .

  • ORA-12712 error while changing nls character set to AL32UTF8

    Hi,
    It is strongly recommend to use database character set AL32UTF8 when ever a database is going to used with our XML capabilities. The database character set in the installed DB is WE8MSWIN1252. For making use of XML DB features, I need to change it to AL32UTF8. But, when I try doing this, I'm getting ORA-12712: new character set must be a superset of old character set. Is there a way to solve this issue?
    Thanks in advance,
    Divya.

    Hi,
    a change from we8mswin1252 to al32utf8 is not directly possible. This is because al32utf is not a binary superset of we8mswin1252.
    There are 2 options:
    - use full export and import
    - Use of the Alter in a sort of restricted way
    The method you can choose depends on the characters in the database, is it only ASCII then the second one can work, in other cases the first one is needed.
    It is all described in the Support Note 260192.1, "Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode)". Get it from the support/metalink site.
    You can also read the chapters about this issue in the Globalization Guide: [url http://download.oracle.com/docs/cd/E11882_01/server.112/e10729/ch11charsetmig.htm#g1011430]Change characterset.
    Herald ten Dam
    http://htendam.wordpress.com

  • Oracle 8.1.5 install on Linux Redhat 6.0: character set (and other) problem(s)

    I am trying to install Oracle 8i on Linux and it does not work : once the install is finished, I have a message saying that "Character Set not found".
    I am runing a french version of Linux (fr-latin 1) and I try to install Oracle with French and English as languages
    An other problem about this install : Oracle does not seem to recognize that I have 6,9 Giga for it to install, and says that I have not enough space for the install...
    And at the end of the install, it takes for ages (about 15mns) during which nothing seems to happen. On one machine I got out of this phase, but on the other I never saw it finish, it looks as if the computer crashed. Is that normal?
    I went through all the initialization phases, set the correct environment variables...
    thanks
    Solange
    null

    I've been dealing with the same problems in the english version but could bypass thiss by doing the folowing.
    -Just ignore the disk space stuff
    -Ignore the charset message, also
    -When creating a database, choose custom and then select the WE8ISO8859P1 char set. It worked for portuguese, must work for french also.
    -Everyone here recommended, and I do the same, leave the database creation for later, not during instalation.
    Good Luck!

  • The ADO NET Source was unable to process the data. ORA-64203: Destination buffer too small to hold CLOB data after character set conversion.

     We developed a SSIS Package to pull the data From Oracle source to Sql Server 2012. Here we used ADO.Net source to pull the records from Source but getting the below error after pulling some 40K records.
      [ADO NET Source [2]] Error: The ADO NET Source was unable to process the data. ORA-64203: Destination buffer too small to hold CLOB data after character set conversion.
    [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. 
     The PrimeOutput method on ADO NET Source returned error code 0xC02090F5. 
     The component returned a failure code when the pipeline engine called PrimeOutput(). 
    The meaning of the failure code is defined by the component, 
    but the error is fatal and the pipeline stopped executing. 
     There may be error messages posted before this with more 
    information about the failure.
    Anything that we can do to fix this?

    Hi,
      Tried both....
      * Having schema type as Nvarchar(max). - Getting the same error.
      * Instead of ADO.Net Source used OLEDB Source with driver as " Oracle Provide for OLE DB" Getting error as below.
           [OLE DB Source [478]] Error: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.
           [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.  The PrimeOutput method on OLE DB Source returned error code 0xC0202009.  The component returned a failure
    code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.  There may be error messages posted before this with more information about the
    failure.
    Additional Info:
       * Here the Source task is getting failed not the conversion or destination task.
    Thanks,
    Loganathan A.

Maybe you are looking for