Oracle 8.1.7.4 + JDBC Driver 10.2.0.3.0=invalid or unknown NLS parameter...

I'm having an issue trying to update the jdbc driver from 10.1.0.2.0 to 10.2.0.3.0 to access an Oracle 8.1.7.4 instance. Using this code I'm getting the following exception, any ideas how to fix it?
Thanks,
Johann
Connection c = null;
try {
     Driver dr = new oracle.jdbc.OracleDriver();
     DriverManager.registerDriver(dr);
     Properties props = new Properties();
     props.put("user", "congiromsr");
     props.put("password", "the password");
     String url = "jdbc:oracle:thin:@cholguaco:1533:lobo";
     c = dr.connect(url, props);
     System.out.println("The driver is "
               + c.getMetaData().getDriverVersion());
     System.out.println("The DBMS is "
               + c.getMetaData().getDatabaseProductVersion());
} catch (Exception e) {
     e.printStackTrace();
} finally {
     try {
          c.close();
     } catch (Exception ignore) {
java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-12705: invalid or unknown NLS parameter value specified
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:283)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:278)
     at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOauth(T4CTTIoauthenticate.java:791)
     at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:362)
     at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:439)
     at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
     at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
     at TestClass.main(TestClass.java:14)

JDBC drivers set NLS parameters based on your locale settings. There are three based parameters: language, territory and character set. Maybe in your case JDBC driver 10.2.0.3.0 sets one of them with value that is not supported in Oracle Database 8.1.7.4. Character set is the first candidate for this. JDBC drivers use only Unicode character sets - there are a few new of them in Oracle Database 10g. 8 and 9 versions of JDBC drivers use UTF8 which is Unicode version 3.0 but in 10g is added Al32UTF8 which is Unicode version 4.0.

Similar Messages

  • PHP 5/Oracle 9i: invalid or unknown NLS parameter value error - Windows XP

    Details:
    Apache/1.3.33 (Win32) PHP/5.0.2
    Windows XP Pro Service Pack 1
    Oracle 9i (located remotely on Sun Solaris)
    Errors:
    Warning: ocilogon() [function.ocilogon]: OCISessionBegin: ORA-12705: invalid or unknown NLS parameter value specified in c:\program files\apache group\Apache\htdocs\eng\class\class.oci8hook.php on line 154
    Warning: ocilogon() [function.ocilogon]: ociopen_server: ORA-12560: TNS:protocol adapter error in c:\program files\apache group\Apache\htdocs\eng\class\class.oci8hook.php on line 154
    Unable to connect to database
    Question:
    How do I set-up the NLS parameters on Windows XP to see a remoted Oracle 9i database?
    Summary:
    I do have Oracle client loaded on my Windows XP workstation, plus when I run phpinfo() on my local workstation, I do have Oracle support enhabled:
    oci8:
    OCI8 Support: enabled
    Revision: $Revision: 1.257 $
    Active Persistent Links: 0
    Active Links: -6
    Temporary Lob support: enabled
    Collections support: enabled
    Oracle:
    Oracle Support: enabled
    Any suggestions or help would be greatly appreciated. Thank you for reading this post.

    user12009184 wrote:
    can anyone help me to resolve the problem.=================================
    Patience, Grasshopper
    You posted this follow-up a mere 30 minutes after your previous post.
    This forum is not a chat line, and it is not paid support.
    No one is responsible for monitoring it and giving a quick response.
    Furthermore, it is a global forum. The person with the information you seek may very well live 20 time zones away from you and was going to bed just as you posted. He will not even see your post for several more hours.
    Your original post went up in the middle of the night for half the world.
    No one with the information you seek is deliberately withholding it until you sound sufficiently desperate.

  • Oracle 9.2.0.8 JDBC Driver Java 1.5

    Where can I find Oracle 9.2.0.8 JDBC Driver for use with Java 1.5 ?

    Hello,
    Can you provide a test case for such behaviour? And the versions of JDK used in those samples ....
    It would be easier if we isolate java 1.5 issues from ojdbc issues.
    Rick B.

  • Can weblogic server 5.1 version work with Oracle 9.2.0 thin JDBC driver?

    we have an applicaiton using weblogic 5.1 and Oracle database 8.1.6. Is that possible
    to upgrade databse version to Oracle 9i without weblogic upgrade? If yes, what
    JDBC driver should be used? Oracle 9.2.0 thin JDBC driver or weblogic jDriver?
    Is there any known issue with the JDBC driver under that architecture?
    Please help.

    Lei Zeng wrote:
    we have an applicaiton using weblogic 5.1 and Oracle database 8.1.6. Is that possible
    to upgrade databse version to Oracle 9i without weblogic upgrade? If yes, what
    JDBC driver should be used? Oracle 9.2.0 thin JDBC driver or weblogic jDriver?
    Is there any known issue with the JDBC driver under that architecture?
    Please help.Hi. Any weblogic server can be used with any JDBC driver. Just upgrade the
    JDBC driver to the latest/best one for Oracle9i, and make sure it's the first
    thing in the server's weblogic.classpath (not the java.classpath). I recommend the
    thin driver. Because it's all java, it is much more reliable. There is no known
    issue with standard JDBC with that or any other driver. Some non-standard Oracle
    calls which arer available from Oracle's driver classes are available through
    weblogic, and some are not.
    Joe Weinstein

  • Doubts: Oracle 9i Client -J2SDK1.4 - JDBC Driver

    Hi eXperts,
    I have installed Oracle 9i(9.2.0.1) client in my machine. Along with the Oracle 9i client, there are two JREs (versions 1.3.1 and 1.1.8) also installed. After installing the oracle 9i client, the SYSTEM�s environment variable �PATH� is updated with the �bin� directory of both JRE (C:\Program Files\Oracle\jre\1.3.1\bin;
    C:\Program Files\Oracle\jre\1.1.8\bin;) and �bin� director of Oracle home (C:\oracle\ora92\bin;)
    Already I have installed J2SDK 1.4.1_02. I have set the USER�s environment variable �PATH� to �C:\j2sdk1.4.1_02\bin;�
    My problem is:
    1.     Before installing oracle 9i client, I was working with J2SDK v1.4.1. After installing, I could not able to invoke the J2SDK 1.4.1; instead I�m invoking JRE 1.3.1. I want work with latest version of J2SDK (that is J2SDK1.4.1, the one I installed) at the same time without disturbing the Oracle 9i clients JREs. Because, I want use the Oracle client for JDBC connection to the database.
    2.     I have installed J2SDK1.4.1, I want connect with oracle 9i database from JAVA using JDBC driver. That means JDBC driver supporting J2SDK1.4. (With ojdbc14.jar, not with classes12.jar,). But, currently I�m using �classes12.jar� to connect with database, because my program invokes JRE1.3, not J2SDK1.4.
    3.     And one more doubt is that why Oracle 9i client comes with two JREs. JRE 1.3.1 is having backward compatibility; it should support JRE 1.1.8 features too. Why two JREs?
    Hope that any of you can solve my doubts.
    Thank & Regards,
    Vijay

    Hi Viravan,
    Yes of course, JRE 1.1.8 doesn�t have the forward compatibility with JRE 1.3. I would like to hear the words from you to clear and assure myself with the doubt that what is the purpose of inclusion of JRE1.1.8 along with the oracle 9i client?. I�m assuming that this is because of to use JRE 1.1.8 compatible JDBC drivers. Is it right?
    Because,
    For JDK1.1 � classes111.zip
    For JDK1.2 and JDK1.3 � classes12.zip and
    For JDK1.4 � ojdbc14.jar
    If that is the case why they haven�t included the JRE1.4 along with Oracle 9i client, because they were provided the ojdbc14.jar.
    If any OTHER REASON is there, please let me know. I�m suspecting that there may be some other reasons for the inclusion of JRE1.1.8. Looking forward your reply�
    Thanks for your support.
    Vijay

  • Servlets/ oracle jdbc driver

    i am trying to connect to my oracle database within a servlet. the driver i want to use is a oracle jdbc oci8 driver, but but unfortuntately i always get an unsatisfied link error (this only happens in servlets)
    the errormessage i get is:
    java.lang.UnsatisfiedLinkError: no ocijdbc8 in java.library.path
    at org.apache.jserv.JServServletManager.load_init(JServServletManager.java:589)
    at org.apache.jserv.JServServletManager.loadServlet(JServServletManager.java:498)
    at org.apache.jserv.JServConnection.processRequest(JServConnection.java:269)
    at org.apache.jserv.JServConnection.run(JServConnection.java:188)
    at java.lang.Thread.run(Thread.java:484)
    can anyone help me?
    thx, laurenz
    null

    make sure your servlet engine platform has an oracle client installed matching the jdbc driver version being used.
    You must also properly configure your servlet engine to access the jdbc oci driver's executables.

  • Distribute JDBC driver with our application

    we are not an oracle customer, but we develop an application that has a component that leverages the JDBC driver to connect to the Oracle database. is it ok to distribute the JDBC driver with this application component? i don't see anything in the licensing policy that prevents us from doing so. do we need to be a member of the oracle partner network at a certain level?
    thx.

    we are not an oracle customer, but we develop an application that has a component that leverages the JDBC driver to connect to the Oracle database. is it ok to distribute the JDBC driver with this application component? i don't see anything in the licensing policy that prevents us from doing so. do we need to be a member of the oracle partner network at a certain level?
    You were REQUIRED to accept the license agreement prior to downloading the JDBC driver software. It is expected that you will actually READ the license agreement prior to accepting it.
    Oracle Database 12c Release 1 JDBC Driver Downloads
    You must accept the OTN License Agreement to download this software.
    That license agreement CLEARLY answers your question so you should re-read it. You are bound by ALL of the terms but this is copied directly from that link:
    License Rights
    We grant you a nonexclusive, nontransferable limited license to use the programs: (a) for purposes of developing, testing, prototyping and running applications you have developed for your own internal data processing operations; (b) to distribute the programs with applications you have developed to your customers provided that each such licensee agrees to license terms consistent with the terms of this Agreement, you do not charge your end users any additional fees for the use of the programs, and your end users may only use the programs to run your applications for their own business operations; and (c) to use the programs to provide third party demonstrations and training. You are not permitted to use the programs for any purpose other than as permitted under this Agreement. If you want to use the programs for any purpose other than as expressly permitted under this agreement you must contact us, or an Oracle reseller, to obtain the appropriate license. We may audit your use and distribution of the programs. Program documentation is either shipped with the programs, or documentation may accessed online at http://www.oracle.com/technetwork/indexes/documentation/index.html.
    Item (b) above begins with 'to distribute the programs . . .'
    Yes - you can distribute the JDBC driver as long as you abide by that license agreement in its entirety (not just the quote I provided).
    Any and all questions need to be directed to Oracle as noted in the License Agreement. No one on the forums can speak for Oracle.

  • New version of jdbc driver

    Hi JDBC Dev. Team,
    I heard a rumour recently that Oracle are going to employ programmers from Sun to rewrite the JDBC implementation - is this true?
    Also, when will the JDBC implementation be reduced to an acceptable size (<500Kb)?
    regards,
    Alexander
    null

    Pity that the rumour has no foundation. Thanks for the quick response though. I appreciate that.
    As for the size, well, from the very start Oracle has made mention of the fact that their JDBC driver was small enough to be downloaded by an applet (see original JDBC documentation which apparently hasn't been updated in lieu of the new MEGA sized JDBC driver).
    I, of course, want to use it with applets/applications as I am a firm believer that HTML interfaces are insufficient and that people will return to Java GUI's. Given that Java has a fantastic GUI API it is logical that people will want to make use of it in the future. I do, that's for sure. However, it is not an option to download a 1.7 Mb JDBC driver in an applet - it is really rather exhorbitant! Would be interesting to hear what ORacle themselves think of their JDBC driver.
    Anyway, I will either have to use RMI/CORBA or someone else's JDBC driver...
    thanks for your response,
    alexander

  • JDBC Driver to Support nvarchar/nchar/ntext

    I downloaded the jdbcKona driver for MS SQL Server 7/2000 from
    the "Download Center". This page claims that this driver
    supports the international data types (nvarchar, nchar, and
    ntext) on SQL Server 7/2000.
    http://www.weblogic.com/docs51/techstart/install_jmsq4.html
    The examples provided in this download were very old (12/19/2001)
    and none of them showed anything dealing with these international
    types so I wonder if this driver truly does support these data
    types or if I somehow downloaded the wrong driver?
    I'd be interested in seeing some examples of how to use these
    international types to store various languages in the database.
    Something along the lines of performing this query (but doing
    so via JDBC where the text within the single quotation marks
    is a parameter that could be English, French, etc.) would be
    great:
    select address from names where name = N'&#1073;&#1091;&#1081;&#1085;&#1086;'
    Thanks.

    Grace wrote:
    Okay, that kind of makes sense, but are you saying that if I
    have this table:
    NAMES
    name nvarchar(50)
    address nvarchar(100)
    and I have a prepared statement like this:
    dbstatement = dbconnection.prepareStatement(
    "insert into address values ( ?, ? )" );
    that this set of JDBC:
    dbstatement.setString( 1, "&#1073;&#1091;&#1081;&#1085;&#1086;" );
    dbstatement.setString( 2, "123 &#1087;&#1086;&#1079;&#1074;&#1086;&#1083;&#1103;&#1077;&#1090;"
    ResultSet rs = dbStatement.executeQuery();
    would work the same way as this set of JDBC:
    dbstatement.setString( 1, "Alfred" );
    dbstatement.setString( 2, "123 West Main Street" );
    ResultSet rs = dbStatement.executeQuery();
    This does not appear to be the case. When I try this, I get a
    SQLException: string or binary data would be truncated. If I
    modify the query so that it doesn't throw any errors I see
    garbage text inserted into the database.
    Are you aware of any examples of this?No JDBC driver will change or interpret the content of any string parameter values. Is
    that syntax supposed to be understood by your DBMS? I think you need to create
    whatever string you want to send, as a Java String with the unicode characters you want,
    then set the parameter(s) with the value. Eg:
    String myFirst = "\u1073\u1091\u1081\u1085\u1086"; // note Java syntax for unicode characters...
    dbStatement.setString(1, myFirst );
    Also, the SQL you are doing is an insert, not a query, so use executeUpdate(). ExecuteQuery()
    will throw an exception.
    Joe
    >
    >
    Joseph Weinstein <[email protected]> wrote:
    Grace wrote:
    I downloaded the jdbcKona driver for MS SQL Server 7/2000 from
    the "Download Center". This page claims that this driver
    supports the international data types (nvarchar, nchar, and
    ntext) on SQL Server 7/2000.
    http://www.weblogic.com/docs51/techstart/install_jmsq4.html
    The examples provided in this download were very old (12/19/2001)
    and none of them showed anything dealing with these international
    types so I wonder if this driver truly does support these data
    types or if I somehow downloaded the wrong driver?
    I'd be interested in seeing some examples of how to use these
    international types to store various languages in the database.
    Something along the lines of performing this query (but doing
    so via JDBC where the text within the single quotation marks
    is a parameter that could be English, French, etc.) would be
    great:
    select address from names where name = N'&#1073;&#1091;&#1081;&#1085;&#1086;'The driver support of nvarchar etc. means that it will transmit string
    values,
    such as PreparedStatement parameters, with the "N'" prefix, and all java
    (16-bit) characters as unicode. This way, the DBMS will not strip the
    characters
    with a varchar map. The driver doe not alter the static contents of SQL
    that
    the application sends. It would be the DBMS that would interpret (or
    not)
    the SQL such as you posed above.
    Joe

  • Problem with Java 5 and Oracle 10g JDBC driver

    Hi All,
    Currently we upgrade our web application to Java 5 and Oracle 10.2 JDBC driver. And we encountered a bug, when the user entered the information through UI and data didn't store into database (Oracle 9i). The problem is that this bug is not happend so often maybe once a day and this did not happen before we upgraded to Java 5 and Oracle 10.2 JDBC driver. Does anyone encounter the same problem ? Is this Java 5 problem or Oracle JDBC driver problem ?
    Thanks,

    sounds like a database problem...
    Are you using a driver version that's supported for your database engine?
    What else did you change? We once ran into a major bug in our application that had for 5 years been masked by performance problems in our hardware and infrastructure.
    Once those were resolved the bug showed itself and caused tens of thousands of records to be erroneously inserted into our database every day.
    It's certainly NOT a problem with your JVM (if it's a decent one, like the Sun implementation).
    So it's either your database, your driver, your network (dropping packets???), or your application.
    The upgrade may just have exposed something that was already there.

  • Unable to load oracle.jdbc.driver.OracleDriver class

    i want to connect my java application with oracle database but i m getting an error -"class not found exception oracle.jdbc.driver.OracleDriver " which is written in Class.forName() to register the driver for DriverManager.
    plz help me..

    This is an old class, not included with the JDK anymore. It was made obsolete by
    DataSource which is a connection pool and not a single connection.

  • How can I access the oracle/sql server jdbc driver class files from my cust

    I have a war file in which I have custom DataSource i.e mypackage.Datasource class. Its basically the need of my application. In this class we connect to datasource and link some of our programming artifacts .
    I have deployed the oracle jdbc driver and deploy my application as ear with datasources.xml in the meta inf file. Inspite of that my code fails to load the jdbc driver classes.
    Here is the extract of the code :
            Class.forName("oracle.jdbc.OracleDriver").newInstance();
             String url = "jdbc:oracle:thin:@dataserver:1521:orcl";
            Connection conn = DriverManager.getConnection(url, "weblims3", "labware");
            if(conn != null){
              out.println("the connection to the database have been achieved");
            out.println("conn object achived= " + conn);
    Class.forname fails in this case. I can see the ojdbc5.jar the driver jar in usr\sap\CE1\J00\j2ee\cluster\bin\ext\ojdbc5  . I even put the ojdbc.jar in web-inf/lib and application lib but does not help at all. Hope I have explained my problem clearly.
    I deployed the jdbc driver in the name of ojdbc5 .
    I am stuck here. It will be great help if anyone can help me in this. Thanks in advance.

    Bent,
    You can access the database from your Java portlet, just like from any other Java/JSP environment. Yes, you can use JDBC, as well as BC4J.
    The Discussion Forum portlet was built using BC4J, take a look at it's source to see how it was done.
    Also, check out Re: BC4J Java portlet anyone?, it contains a lot of useful information too.
    Peter

  • Help - Could not load 'oracle.jdbc.driver.OracleDriver ...

    I'm using oci8 to connect to the Oracle database.
    URL: jdbc:oracle:oci8:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(PORT=1527)(HOST=testhost)))(CONNECT_DATA=(SID=fnoe2pa)))
    When I tried to start the weblogic server, I got the following errors:
    Can you suggest what I should do next (step-wise)??? Thanks, Bobby
    <Sleeping in createResource()>
    ####<15/08/2002 14:09:43> <Error> <JDBC> <qawebmethods> <myserver>
    <main> <system> <> <001060> <Cannot startup connection pool
    "pool/test_myapp" weblogic.common.ResourceException:
    Could not load 'oracle.jdbc.driver.OracleDriver
    If this is a type-4 JDBC driver, it could occur if the JDBC
    driver is not in the system CLASSPATH.
    If this is a type-2 JDBC driver, it may also indicate that
    the Driver native layers(DBMS client lib or driver DLL)
    have not been installed properly on your system
    or in your PATH environment variable.
    This is most likely caused by one of the following:
    1. The native layer SO, SL, or DLL could not be found.
    2. The file permissions on the native layer SO, SL, or DLL
    have not been set properly.
    3. The native layer SO, SL, or DLL exists, but is either
    invalid or corrupted.
    For more information, read the installation documentation
    for your JDBC Driver, available from:
    http://e-docs.bea.com
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:212)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
         at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:705)
         at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
         at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:650)
         at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
         at $Proxy31.updateDeployments(Unknown Source)
         at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
         at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
         at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
         at $Proxy42.start(Unknown Source)
         at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
         at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
         at weblogic.management.Admin.finish(Admin.java:644)
         at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
         at weblogic.Server.main(Server.java:35)
    >
    ####<15/08/2002 14:09:43> <Info> <JDBC> <qawebmethods> <myserver>
    <main> <system> <> <001082> <Creating Data Source named
    jdbc/test_myapp for pool pool/test_myapp>
    ####<15/08/2002 14:09:43> <Info> <JDBC> <qawebmethods> <myserver>
    <main> <system> <> <001070> <Checking existence of connection pool
    pool/test_myapp requested by user system>
    ####<15/08/2002 14:09:43> <Error> <JDBC> <qawebmethods> <myserver>
    <main> <system> <> <001059> <Error during Data Source creation:
    weblogic.common.ResourceException: DataSource(jdbc/test_myapp) can't
    be created with non-existent Pool (connection or multi)
    (pool/test_myapp)>
    ####<15/08/2002 14:09:50> <Info> <EJB> <qawebmethods> <myserver>
    <main> <system> <> <010008> <EJB Deploying file: myapp-ejb.jar>
    ####<15/08/2002 14:09:50> <Warning> <J2EE> <qawebmethods> <myserver>
    <main> <system> <> <160007> <You are running WebLogic Server with J2EE
    1.3 features enabled. The implementation of specific J2EE 1.3 features
    (EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0)
    in BEA WebLogic Server 6.1 is of a non-final version of the
    appropriate specification. It is subject to change in future releases
    once the specification becomes finalized. This may cause application
    code developed for BEA WebLogic Server 6.1 that uses the new features
    of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in
    future releases of BEA WebLogic Server.>
    ####<15/08/2002 14:09:59> <Error> <J2EE> <qawebmethods> <myserver>
    <main> <system> <> <160001> <Error deploying application myapp-ejb:
    Unable to deploy EJB: Counter from myapp-ejb.jar:
    The DataSource with the JNDI name: jdbc/test_myapp could not be
    located. Please ensure that the DataSource has been deployed
    successfully and that the JNDI name in your EJB Deployment descriptor
    is correct.
    >
    ####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101053> <[HTTP myserver] Loading web app: myapp>
    ####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101059> <[myserver] Loading myapp from WAR file:
    C:\bea\wlserver6.1\.\config\mydomain\applications\.wlnotdelete\wlap31483\myapp.war>
    ####<15/08/2002 14:09:59> <Warning> <J2EE> <qawebmethods> <myserver>
    <main> <system> <> <160007> <You are running WebLogic Server with J2EE
    1.3 features enabled. The implementation of specific J2EE 1.3 features
    (EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0)
    in BEA WebLogic Server 6.1 is of a non-final version of the
    appropriate specification. It is subject to change in future releases
    once the specification becomes finalized. This may cause application
    code developed for BEA WebLogic Server 6.1 that uses the new features
    of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in
    future releases of BEA WebLogic Server.>
    ####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101031>
    <[WebAppServletContext(1412030,myapp,/myapp)] extracting classfiles to
    C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\wlap31483\WEB-INF\_tmp_war_myapp:>
    ####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101032>
    <[WebAppServletContext(1412030,myapp,/myapp)] extracted classfiles
    successfully...>
    ####<15/08/2002 14:10:04> <Info> <HTTP Session> <qawebmethods>
    <myserver> <main> <system> <> <100037> <Creating SessionContext of
    type: memory for webapp: /myapp>
    ####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101047>
    <[WebAppServletContext(1412030,myapp,/myapp)] registering classpath
    servlet with initArgs 'null'>
    ####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101047>
    <[WebAppServletContext(1412030,myapp,/myapp)] registering getior
    servlet with initArgs 'null'>
    ####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101047>
    <[WebAppServletContext(1412030,myapp,/myapp)] registering tunneling
    servlets with initArgs 'wl-dispatch-policy=direct'>
    ####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101047>
    <[WebAppServletContext(1412030,myapp,/myapp)] registering JSPServlet
    with initArgs '[JspConfig:
    verbose=true,packagePrefix=jsp_servlet,-compiler=javac,compileFlags=,workingDir=C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\wlap31483\WEB-INF\_tmp_war_myapp,pageCheckSeconds=1,superclass=null,keepgenerated=false,precompileContinue=false,compilerSupportsEncoding=true,encoding=null,defaultfilename=index.jsp,compilerclass=null,noTryBlocks=false]'>
    ####<15/08/2002 14:10:04> <Debug> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101097> <Registering ServletContext:
    "myapp:/myapp">
    ####<15/08/2002 14:10:04> <Info> <J2EE> <qawebmethods> <myserver>
    <main> <system> <> <160003> <Deployed : myapp>
    ####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
    <main> <system> <> <101133> <Initializing WEB server myserver>
    ####<15/08/2002 14:10:04> <Notice> <Management> <qawebmethods>
    <myserver> <main> <system> <> <141052> <Application Poller started for
    development server.>
    ####<15/08/2002 14:10:04> <Notice> <WebLogicServer> <qawebmethods>
    <myserver> <ListenThread> <system> <> <000202> <ListenThread listening
    on port 7001>
    ####<15/08/2002 14:10:04> <Info> <NT Performance Pack> <qawebmethods>
    <myserver> <ListenThread> <system> <> <000000> <NATIVE: NTSocketMuxer
    was built on Nov 1 2001 16:39:28
    >
    ####<15/08/2002 14:10:04> <Notice> <WebLogicServer> <qawebmethods>
    <myserver> <SSLListenThread> <system> <> <000202> <SSLListenThread
    listening on port 7002>
    ####<15/08/2002 14:10:05> <Notice> <Management> <qawebmethods>
    <myserver> <main> <system> <> <141030> <Starting discovery of Managed
    Server... This feature is on by default, you may turn this off by
    passing -Dweblogic.management.discover=false>
    ####<15/08/2002 14:10:05> <Notice> <WebLogicServer> <qawebmethods>
    <myserver> <main> <system> <> <000331> <Started WebLogic Admin Server
    "myserver" for domain "mydomain" running in Development Mode>
    ####<15/08/2002 14:10:11> <Info> <NT Performance Pack> <qawebmethods>
    <myserver> <ExecuteThread: '14' for queue: 'default'> <> <> <000000>
    <Allocating: '2' NT reader threads>
    ####<15/08/2002 14:10:13> <Info> <HTTP> <qawebmethods> <myserver>
    <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
    <> <101047> <[WebAppServletContext(5367844,console,/console)] actions:
    init>
    ####<15/08/2002 14:10:18> <Info> <HTTP> <qawebmethods> <myserver>
    <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
    <> <101047> <[WebAppServletContext(5367844,console,/console)]
    FileServlet: init>
    ####<15/08/2002 14:10:18> <Info> <HTTP> <qawebmethods> <myserver>
    <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
    <> <101047> <[WebAppServletContext(5367844,console,/console)]
    FileServlet: Using standard I/O>

    "thorick" <[email protected]> wrote in message news:<[email protected]>...
    Most likely, the OCI libraries could not be loaded.
    Before continuing down this path, is there any reason
    why you want to use an OCI based Driver as opposed to the
    all Java Oracle thin driver ?There is indeed a valid reason for my choice.
    I am currently connecting to the Oracle "Rdb" 7.0 database (located on
    VMS) - not Oracle Oracle.
    The SQL Service software we're currently using is version 7.1. This
    version works well with the OCI8 driver (when connecting to the
    database from Windows NT). This version of SQL Service however does
    NOT work for the THIN driver (unless we upgrade the SQL Service to
    version 7.1.5.5 - which we're not prepared to do so because it is not
    stable enough from our previous test/trials). SQLSRV Version 7.1.5.5
    works for THIN driver but it will result in uncommitted
    transactions/unresolved connection/stopping of listener issues and
    there is a need to restart the service from time to time. Oracle has
    since confirmed that this is a bug that they have yet to resolve...
    So we have to stick to OCI8 (THICK) for the time being. I would really
    appreciate it very much if you can tell me the various OCI libraries
    that I need to load (in terms of WebLogic Server config file settings
    etc..).
    By the way I have already installed the Oracle 8 client software on
    the NT server (where WebLogic Server is) and I have also set up the
    relevant SID (using the Net8 Assistant) that points to the Oracle Rdb
    database on the VMS. I have also tried using SQL*Plus to connect to
    the database and I can connect properly to the database. But WebLogic
    simply doesn't seem to load the software.
    Help...
    Regards,
    Bobby Brown, writing from Australia.

  • Insert data 32K into a column of type LONG using the oracle server side jdbc driver

    Hi,
    I need to insert data of more than 32k into a
    column of type LONG.
    I use the following code:
    String s = "larger then 32K";
    PreparedStatement pstmt = dbcon.prepareStatement(
    "INSERT INTO TEST (LO) VALUES (?)");
    pstmt.setCharacterStream(1, new StringReader(s), s.length());
    pstmt.executeUpdate();
    dbcon.commit();
    If I use the "standard" oracle thin client driver from classes_12.zip ("jdbc:oracle:thin:@kn7:1521:kn7a") every thing is working fine. But if I use the oracle server side jdbc driver ("jdbc:default:connection:") I get the exception java.sql.SQLException:
    Datasize larger then max. datasize for this type: oracle.jdbc.kprb.KprbDBStatement@50f4f46c
    even if the string s exceeds a length of 32767 bytes.
    I'm afraid it has something to do with the 32K limitation in PL/SQL but in fact we do not use any PL/SQL code in this case.
    What can we do? Using LOB's is not an option because we have client software written in 3rd party 4gl language that is unable to handle LOB's.
    Any idea would be appreciated.
    Thomas Stiegler
    null

    In rdbms 8.1.7 "relnotes" folder, there is a "Readme_JDBC.txt" file (on win nt) stating
    Known Problems/Limitations In This Release
    <entries 1 through 3 omiited for brevity >
    4. The Server-side Internal Driver has the following limitation:
    - Data access for LONG and LONG RAW types is limited to 32K of
    data.

  • Oracle JDBC Driver 10.2.0.1.0 DataBaseMetaData Incorrect For Unary FKs

    Friends,
    My firm (which is not a MetaLink subscriber) has discovered a bug in the Oracle 10g JDBC Driver (10.2.0.1.0). The bug affects unary associations, namely cases in which the foreign key of a table points to that very table's primary key.
    In such cases, method DatabaseMetaData.getExportedKeys (which is designed to return all foreign keys that reference a specified table) fails to return the foreign key reference. The method works correctly as long as the foreign key "points to" a different table. Example:
    ResultSet lResultSetForeignKeys = aDatabaseMetaData.getExportedKeys(<foo>)
    while (lResultSetForeignKeys.next())
    // NOTHING RETURNED
    In this case, the ResultSet contains no elements.
    We discovered this problem testing the same logic against a cross-section of commercial databases. All other DBMS drivers produce the correct result except for the Oracle drivers.
    If some brave soul would convert this into a MetaLink TAR we'd sure appreaciate it, and if possible we'd love to be in the loop regarding the progress on this issue. My e-mail ID is [email protected], and I'm working on behalf of Corticon Technologies, Inc.
    Sincerely,
    David Lynch
    General Manager, SOTA

    My understanding is that to be a MetaLink subscriber you have to be an Oracle customer or subscribe for Oracle support services. Since Oracle is only one of the many databases we support, and because our sole objective with Oracle is compatibility testing, it's unlikely that we will become subscribers unless it's essentially free.
    Oracle is tangential (not core) to our own offerings, so we don't have a pressing need for support. Is there some avenue for people in our shoes?

Maybe you are looking for