JVM freeze with oci driver?

An application that was working ok with oracle's thin driver started freezing with no obvious pattern when I switched to oci (9i on sunOS) - it can run a minute or days between freezes. There are multiple independent threads, and all of them freeze when this happens. Kill -3 does not produce a thread dump. Any ideas?

PS - running "java -server -Xms128m -Xmx128m" with:
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21)
Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode)

Similar Messages

  • BUG: retrieving NCHAR value using ViewObject returns "???" with OCI driver

    Hi,
    after upgrading JDeveloper to 10.1.3.1 we cannot use OCI JDBC drivers, because they don't work correctly - characters, that do not exist in database character set (EE8ISO8859P2 in our case) are converted to "?". Thin driver works well. We need to use OCI, because we had some issues with RAC with thin driver.
    Test case is easy: create table with NCHAR column, populate with unicode data, create ViewObject to select from this table and it will work only with THIN and not with OCI driver. This worked well with 10.1.3.0. When I tried to directly connect to DB and select that table using java.sql.Statement, it worked with both drivers, that's why I suspect the mechanics inside ADF BC.
    I logged a SR for this in Metalink, but try this way as well, for someone else could hit the same problem.
    Thanks for any help,
    Viliam

    Hi,
    after upgrading JDeveloper to 10.1.3.1 we cannot use OCI JDBC drivers, because they don't work correctly - characters, that do not exist in database character set (EE8ISO8859P2 in our case) are converted to "?". Thin driver works well. We need to use OCI, because we had some issues with RAC with thin driver.
    Test case is easy: create table with NCHAR column, populate with unicode data, create ViewObject to select from this table and it will work only with THIN and not with OCI driver. This worked well with 10.1.3.0. When I tried to directly connect to DB and select that table using java.sql.Statement, it worked with both drivers, that's why I suspect the mechanics inside ADF BC.
    I logged a SR for this in Metalink, but try this way as well, for someone else could hit the same problem.
    Thanks for any help,
    Viliam

  • Is it possible to working in Java Stored Procedures with OCI driver?

    Hello ALL.
    Could you help me...
    Is it possible to working in Java Stored Procedures with OCI driver?
    I want to try to do some workaround...
    I need to work with following parametrs from Java Stored Procedures:
    DriverManager.registerDriver (new oracle.jdbc.OracleDriver());
    String url = null;
    url = "jdbc:oracle:oci:@TEST";
    conn = DriverManager.getConnection (url,"scott","tiger");
    Is it possible?
    I tried but I have errors...
    Please, help me!
    Thanks

    You cannot call OCI functions directly from PL/SQL. You could, of course, write an external procedure that made OCI calls, though you could also write an external procedure in Java. I'm guessing the documentation is trying to convey this same information-- you would need an external procedure that used OCI if you wanted to use the old-school interfaces for LONG and LOB data types. If you converted to using LOBs rather than LONGs, you could do everything in PL/SQL.
    Justin

  • ORA-24327 with OCI driver

    Hi,
    We noticed that when we use the OCI driver for Oracle 8.1.7, we cannot have
    an initial connection pool size greater than 249. On the 250th one, there is
    a DBMS exception (ORA-24327) and weblogic says that it cannot create the
    connection.
    If we move to the Thin driver, there is no longer this restriction and we've
    tried it with success with more than 550 connections.
    Anyone know any limitation about the OCI driver and if there is any
    parameter on the OCI driver side or on the DB side to tune so that we can
    have more than 249 connections in our pool ?
    FI, we have the following configuration (in config.xml) :
    <JDBCConnectionPool CapacityIncrement="5"
    Name="imJDBCConnectionPool" Targets="imadmin"
    DriverName="weblogic.jdbc.oci.Driver" URL="jdbc:weblogic:oracle"
    InitialCapacity="270" MaxCapacity="270"
    TestTableName="dual" RefreshMinutes="40"
    ShrinkingEnabled="false" ShrinkPeriodMinutes="15"
    Properties="user=im;password=im;server=im09"/>
    and we have the following TNSNAMES.ORA :
    IM09.IM =
    (DESCRIPTION =
    (failover = on)
    (ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domaina-1)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domainb-1)(PORT = 1521))
    (CONNECT_DATA = (SERVICE_NAME = IM09.im)(SERVER = shared))
    and SQLNET.ORA (to resolve the IM domain name) :
    NAMES.DEFAULT_DOMAIN=IM
    Thanks
    -Vincent

    Vincent Massol wrote:
    >
    "Slava Imeshev" <[email protected]> wrote in message
    news:[email protected]...
    Hi Vincent,
    Just for curiosity sake, what are you doing with 250 connections?
    It's not in the Cactus area, is it? :-)
    grin ;-)
    No, I'm currently working for a customer, doing some lab performance tests.
    We wanted to use the OCI driver for the TAF feature of OPS (transparent
    application failover) but found that the Thin driver is performing so much
    better that we have switched to using it along with the multipool feature of
    WebLogic. Hi. Beware of 'TAF'. Note that all cursors will be defunct on failover,
    so any JDBC statement or ResultSet in progress at the time of failover will
    be lost. (IE: not at all transparent).
    Joe
    We haven't done any failover test yet so we don't know yet how the
    multipool (with a 'load-balancing' strategy) perform upon failover of one
    instance. If it's ok we'll keep using the thin driver. If not, we'll switch
    back to OCI drivers and try the TAF feature.
    Also, I don't think we really need that big number of connections. It seems
    we had some other performance issue which the DB which was making us use
    lots of connections on the WL side. With the thin driver we're only using
    about 39-100 connections maximum with a thread count of 40 (that's because a
    given message does up to 3 SQL statements per transaction (and a connection
    is only effectively released in the pool after the commit)).
    I've introduced Cactus on the project, of course, but only for the unit
    tests (I'm also using Mock Objects) ... :-)
    Regards,
    -Vincent
    Regards,
    Slava Imeshev
    "Vincent Massol" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    We noticed that when we use the OCI driver for Oracle 8.1.7, we cannothave
    an initial connection pool size greater than 249. On the 250th one,
    there
    is
    a DBMS exception (ORA-24327) and weblogic says that it cannot create the
    connection.
    If we move to the Thin driver, there is no longer this restriction andwe've
    tried it with success with more than 550 connections.
    Anyone know any limitation about the OCI driver and if there is any
    parameter on the OCI driver side or on the DB side to tune so that we
    can
    have more than 249 connections in our pool ?
    FI, we have the following configuration (in config.xml) :
    <JDBCConnectionPool CapacityIncrement="5"
    Name="imJDBCConnectionPool" Targets="imadmin"
    DriverName="weblogic.jdbc.oci.Driver" URL="jdbc:weblogic:oracle"
    InitialCapacity="270" MaxCapacity="270"
    TestTableName="dual" RefreshMinutes="40"
    ShrinkingEnabled="false" ShrinkPeriodMinutes="15"
    Properties="user=im;password=im;server=im09"/>
    and we have the following TNSNAMES.ORA :
    IM09.IM =
    (DESCRIPTION =
    (failover = on)
    (ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domaina-1)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = sf1-domainb-1)(PORT = 1521))
    (CONNECT_DATA = (SERVICE_NAME = IM09.im)(SERVER = shared))
    and SQLNET.ORA (to resolve the IM domain name) :
    NAMES.DEFAULT_DOMAIN=IM
    Thanks
    -Vincent
    B.E.A. is now hiring! (12/14/01) If interested send a resume to [email protected]
    DIRECTOR OF PRODUCT PLANS AND STRATEGY San Francisco, CA
    E-SALES BUSINESS DEVELOPMENT REPRESENTATIVE Dallas, TX
    SOFTWARE ENGINEER (DBA) Liberty Corner, NJ
    SENIOR WEB DEVELOPER San Jose, CA
    SOFTWARE ENGINEER (ALL LEVELS), CARY, NORTH CAROLINA San Jose, CA
    SR. PRODUCT MANAGER Bellevue, WA
    SR. WEB DESIGNER San Jose, CA
    Channel Marketing Manager - EMEA Region London, GBR
    DIRECTOR OF MARKETING STRATEGY, APPLICATION SERVERS San Jose, CA
    SENIOR SOFTWARE ENGINEER (PLATFORM) San Jose, CA
    E-COMMERCE INTEGRATION ARCHITECT San Jose, CA
    QUALITY ASSURANCE ENGINEER Redmond, WA
    Services Development Manager (Business Development Manager - Services) Paris, FRA; Munich, DEU
    SENIOR SOFTWARE ENGINEER (PLATFORM) Redmond, WA
    E-Marketing Programs Specialist EMEA London, GBR
    BUSINESS DEVELOPMENT DIRECTOR - E COMMERCE INTEGRATION San Jose, CA
    MANAGER, E-SALES Plano, TX

  • Time machine freezes with any drive

    I have tried everything - connecting several new drives, plugging it directly into the USB 3 port, taking it to the Apple store.

    Are the drives formatted properly?
    Drive Preparation
    1. Open Disk Utility in your Utilities folder.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled.) Click on the Security button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.

  • Macbook freezing with disc drive

    Hi
    My macbook is freezing when trying to copy a disc to the macbook, I can't even turn it off, the macbook is brand new, any ideas appreciated

    Direct you to the proper forum for MacBook :
    MacBook Series Forums
    https://discussions.apple.com/community/notebooks?view=discussions
    http://www.apple.com/support/macbookpro
    Mac OS X Forum
    https://discussions.apple.com/community/mac_os?view=discussions

  • JVM Crash With Oracle OCI Client

    Hi
    My app is running on Windows 7 64 bit, Jboss 4.2, launched from Eclipse, and runs fine when I use the Oracle thin client (10g, 32bit). However when I try to use the OCI client, I get this:
    # A fatal error has been detected by the Java Runtime Environment:
    # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d906f21, pid=4740, tid=5656
    # JRE version: 6.0_21-b07
    # Java VM: Java HotSpot(TM) Client VM (17.0-b17 interpreted mode windows-x86 )
    # Problematic frame:
    # V [jvm.dll+0x106f21]
    I'll post the contents of the log in another message because it's too long to fit here. Using the thin client is NOT an option unfortunately as the thin driver is missing some functionality that we need to use.
    I've installed the Oracle client in a folder that doesn't contain spaces, or parentheses (c:\oracle\.....) and the JDK is installed in a similar directory (c:\java\...)
    I've tried both 32bit and 64 bit versions of JDK1.6 and the Oracle 10g client. I have also tried mixed mode and interpreted mode JVM (Xint) with the same results.
    ojdbc14.jar is in my JBoss server's lib directory, and ocijdbc10.dll is in my path (c:\windows\system32).
    Anyone any ideas what's going wrong? Been trying to fix this for days now. Appreciate any help.
    Richard

    Sorted it (well, my colleague did anyway). We installed a fresh version (32 bit) JDK (6u21), the Oracle 10g (10.0.3) client (32 bit) and made sure that there were no other OCI DLLs anywhere. I had some in the JBoss bin directory which I had copied in earlier that morning and forgotten about. So, the only OCI DLLs I have now are in Oracle's installation directory. Once we removed those erroneous DLLs from the JBoss directory, the server made the connection successfully. I don't full understand why, because I was getting the error earlier without the erroneous DLLs being present too, so I think there was some additional interaction going on somewhere. One other thing that may have been important is the tnsnames.ora file I had. We found a post that said the tnsnames file generated by the installer, when it only has one entry in it, can include dodgy whitespace at the end which can cause problems. So, just to be on the safe side we added a second entry (to another DB) - maybe that was something to do with it.
    So, the Oracle 10g client and OCI driver DOES work on Windows 7 64 bit (at least for me anyway)

  • Problem to create data source with OCI type of driver

    Hi Experts
    We are creating an XA datasource with OCI type of driver using an enterprise application with data-sources.xml, the xml is like this:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE data-sources SYSTEM "data-sources.dtd" >
    <data-sources>
         <data-source>
              <data-source-name>OCI_DS_XA</data-source-name>
              <driver-name>ORACLE_DRIVER</driver-name>
              <init-connections>1</init-connections>
              <max-connections>25</max-connections>
              <max-time-to-wait-connection>120</max-time-to-wait-connection>
              <expiration-control>
                   <connection-lifetime>60</connection-lifetime>
                   <run-cleanup-thread>300</run-cleanup-thread>
              </expiration-control>
              <sql-engine>Vendor_SQL</sql-engine>
              <jdbc-2.0>
                   <xads-class-name>
                        oracle.jdbc.xa.client.OracleXADataSource
                   </xads-class-name>
                   <object-factory>
                        oracle.jdbc.pool.OracleDataSourceFactory
                   </object-factory>
                   <properties>
                        <property>
                             <property-name>serverName</property-name>
                             <property-value><SERVER_NAME></property-value>
                        </property>
                        <property>
                             <property-name>serverPort</property-name>
                             <property-value>1521</property-value>
                        </property>
                        <property>
                             <property-name>databaseName</property-name>
                             <property-value>ORCL</property-value>
                        </property>
                        <property>
                             <property-name>driverType</property-name>
                             <property-value>oci</property-value>
                        </property>
                        <property>
                             <property-name>user</property-name>
                             <property-value>username</property-value>
                        </property>
                        <property>
                             <property-name>password</property-name>
                             <property-value>password</property-value>
                        </property>
                   </properties>
              </jdbc-2.0>
              </data-source>
    </data-sources>
    We have installed oracle client in server M/C and configured all the environment variables. While we are deploying the application from CE developer studio IDE to the CE 7.1 AS, we are getting the  following error:
    Description:
              1. Exception has been returned while the 'sap.com/DS_TEST_EAR' was starting. Warning/Exception :
    [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 7653550:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "OCI_DS_XA".
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1467)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:468)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:419)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:495)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:554)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:248)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:389)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3387)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3373)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3276)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3249)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
    Caused by: com.sap.engine.frame.core.database.DatabaseException: Exception of type java.sql.SQLException occurred: Closed Connection.
         at com.sap.engine.core.database.impl.DataSourceAdministratorImpl.createDataSource(DataSourceAdministratorImpl.java:49)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1400)
         ... 33 more
    Caused by: java.sql.SQLException: Closed Connection
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227)
         at oracle.jdbc.driver.GetCharSetError.processError(T2CConnection.java:3082)
         at oracle.jdbc.driver.T2CConnection.getCharSetIds(T2CConnection.java:2811)
         at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:300)
         at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:344)
         at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:136)
         at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:79)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:545)
         at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:194)
         at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:121)
         at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:333)
         at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:84)
         at com.sap.sql.connect.factory.XADSPooledConnectionFactory.getPooledConnection(XADSPooledConnectionFactory.java:27)
         at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:677)
         at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.initConnections(DBDataSourcePoolImpl.java:1099)
         at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.<init>(DBDataSourcePoolImpl.java:49)
         at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:507)
         at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:136)
         at com.sap.sql.manager.OpenSQLManager.createDataSource(OpenSQLManager.java:141)
         at com.sap.engine.core.database.impl.DataSourceAdministratorImpl.createDataSource(DataSourceAdministratorImpl.java:42)
         ... 34 more
    But when we are creating the datasource with thin type of driver, it is working fine. We have already created a driver with name “ORACLE_DRIVER” in server using the ojdbc14.jar using Netweaver administrator consol.
    Same this is happening when we are creating the OCI type of datasource by using Netweaver administrator consol by specifying all the parameter as above and also the initial connection pool size is more than zero.
    Same thing is happening for normal (JDBC 1x) datasource creation with OCI type driver.

    Hello,
    I ran a search on SDN, related to your error code, i found the following:
    UnsupportedClassVersionError in NWDS CE
    DeploymentWarning-WebService-Collection
    Maybe its useful to you
    Regards,
    Siddhesh

  • Trying to install OS X MAvricks 10.9.3 on a new hard drive and it freezes with 3 minutes remaining

    I Am trying to install OS X MAvricks 10.9.3 on a erased hard drive and it freezes with 3 minutes remaining

    Where are you installing this from - the Recovery Volume.?

  • ORA-01401 error on char column with oracle oci driver

    Hello,
    We found a potential bug in the kodo.jdbc.sql.OracleDictionary class
    shipped as source with Kodo:
    In newer Kodo versions (at least in 3.3.4), the method
    public void setString (PreparedStatement stmnt, int idx, String
    val,          Column col)
    has the following code block:
    // call setFixedCHAR for fixed width character columns to get padding
    // semantics
    if (col != null && col.getType () == Types.CHAR
    && val != null && val.length () != col.getSize ())
    ((OraclePreparedStatement) inner).setFixedCHAR (idx, val);
    This block seems to be intended for select statements but is called on
    inserts/updates also. The latter causes a known problem with the Oracle
    oci driver when settings CHAR columns as FixedCHAR, which reports an
    ORA-01401 error (inserted value too large for column) when definitely no
    column is too long. This does not happen with the thin driver.
    We reproduced this with 8.1.7 and 9.2.0 drivers.
    For us we solved the problem by subclassing OracleDictionary and removing
    the new code block.
    Regards,
    Rainer Meyer
    ELAXY Financial Software & Solutions GmbH & Co. KG

    Rainer-
    I read at
    re:'ORA-01401 inserted value too large for column' - 9i that:
    "This is fixed in Oracle9i Release 2"
    Can you try that version of the driver? Also, does it fail in the Oracle
    10 OCI driver?
    Rainer Meyer wrote:
    Hello,
    We found a potential bug in the kodo.jdbc.sql.OracleDictionary class
    shipped as source with Kodo:
    In newer Kodo versions (at least in 3.3.4), the method
    public void setString (PreparedStatement stmnt, int idx, String
    val,          Column col)
    has the following code block:
    // call setFixedCHAR for fixed width character columns to get padding
    // semantics
    if (col != null && col.getType () == Types.CHAR
    && val != null && val.length () != col.getSize ())
    ((OraclePreparedStatement) inner).setFixedCHAR (idx, val);
    This block seems to be intended for select statements but is called on
    inserts/updates also. The latter causes a known problem with the Oracle
    oci driver when settings CHAR columns as FixedCHAR, which reports an
    ORA-01401 error (inserted value too large for column) when definitely no
    column is too long. This does not happen with the thin driver.
    We reproduced this with 8.1.7 and 9.2.0 drivers.
    For us we solved the problem by subclassing OracleDictionary and removing
    the new code block.
    Regards,
    Rainer Meyer
    ELAXY Financial Software & Solutions GmbH & Co. KG
    Marc Prud'hommeaux
    SolarMetric Inc.

  • Error on NT with 8.1.6 OCI driver and JDK 1.2

    I have the error:
    "The procedure entry point slzsetevar could not be located in the dynamic link library oracore8.dll"
    oracore8.dll is 8.1.5
    ocijdbc8.dll is 8.1.6
    Any help will be great.
    Thanks,
    8.1.6 OCI driver with JDK 1.2

    when using a jdbc oci driver you must have a matching oracle client installed.
    (fyi -- an oem install is not considered to be an oracle client install)
    use the jdbc oci 8.1.6 driver only from a platform with the oracle 8.1.6 client installed.
    what you've indicated is you're using an 8.1.6 jdbc driver with an 8.1.5 oracle client -- that will not work.
    move to an all 816 client and jdbc driver to "synch up" the dll's you mentioned.
    null

  • WL5.1 with Oracle OCI driver 8.1.6 and 8.1.7

    We have seen different behaviors when using WL5.1 with Oracle's OCI driver
    version 8.1.6 and 8.1.7
    Our application calls the same set of stored procedures, which creates in
    total of 10 reference cursors
    in the database (8.1.7). We close the reference cursor everytime the SP is
    called.
    After running the application for a while, we have the following situation:
    1) Using the 8.1.6. driver, we always have (at any given time) one
    reference cursor opened in the database
    for each connection in the connection pool.
    2) Using the 8.1.7 driver, we always have one reference cursor for each
    stored procedure for each connection in the connection pool(i.e. 10 open
    ref-cursor per connection).
    It seems that between 8.1.6 and 8.1.7, the driver caches ref-cursor
    differently. The 8.1.7 drive doesn't seem to be scalable. Has anyone
    notice the change?
    Is this behavior correct or configurable?
    Thanks.
    -Chuan

    We have seen different behaviors when using WL5.1 with Oracle's OCI driver
    version 8.1.6 and 8.1.7
    Our application calls the same set of stored procedures, which creates in
    total of 10 reference cursors
    in the database (8.1.7). We close the reference cursor everytime the SP is
    called.
    After running the application for a while, we have the following situation:
    1) Using the 8.1.6. driver, we always have (at any given time) one
    reference cursor opened in the database
    for each connection in the connection pool.
    2) Using the 8.1.7 driver, we always have one reference cursor for each
    stored procedure for each connection in the connection pool(i.e. 10 open
    ref-cursor per connection).
    It seems that between 8.1.6 and 8.1.7, the driver caches ref-cursor
    differently. The 8.1.7 drive doesn't seem to be scalable. Has anyone
    notice the change?
    Is this behavior correct or configurable?
    Thanks.
    -Chuan

  • Problem with default oci driver with database ORACLE 8.1.7

    Presently our application is using weblogic 5.1 with oracle 8.1.6 database. Our
    application uses OCI driver to connect OraclePool. We used weblogic/lib/solaris/oci815_8/libweblogicoci36.so
    libraary to connect to dataabse.
    We upgraded our Database from 8.1.6 to 8.1.7. After upgradation of database from
    8.1.6 to 8.1.7. By using above shared library we are getting following error.
    In the weblogic connoction pool, we specied minimum as 4 connections. When it
    is creating connections while startup first connection is successfully connecting
    and second onwards it is giving following error.
    url=jdbc:oracle:thin:@169.165.38.162:1570:PBGSUP, props=user=SUPPORT;password=
    SUPPORT;, allowShrinking=true, driver=oracle.jdbc.driver.OracleDriver, aclName=w
    eblogic.jdbc.connectionPool.oraclePool, # testTable=dual, capacityIncremen
    t=2, initialCapacity=5, url=jdbc:oracle:oci8:@PBGSUP, shrinkPeriodMins=5}
    Delaying 1 seconds before making a oraclePool pool connection.
    Thu Nov 22 09:38:58 CST 2001:<I> <JDBC Pool> Connection for pool "oraclePool"
    cr
    eated.
    Delaying 1 seconds before making a oraclePool pool connection.
    java.sql.SQLException: ORA-01017: invalid username/password; logon denied
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled Code)
    at java.sql.SQLException.<init>(SQLException.java:43)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
    at oracle.jdbc.oci8.OCIDBAccess.check_error(Compiled Code)
    at oracle.jdbc.oci8.OCIDBAccess.logon(OCIDBAccess.java:310)
    at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:200)
    at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.ja
    va:251)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:224)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
    nectionEnvFactory.java:149)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
    nectionEnvFactory.java:109)
    at weblogic.common.internal.ResourceAllocator.makeResources(Compiled Cod
    e)
    at weblogic.common.internal.ResourceAllocator.<init>(Compiled Code)
    at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
    ava:330)
    at weblogic.jdbc.common.internal.JdbcInfo.initPools(Compiled Code)
    at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
    at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
    at weblogic.t3.srvr.StartupThread.doWork(Compiled Code)
    at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java
    :62)
    Thu Nov 22 09:39:00 CST 2001:<I> <JDBC Pool> Sleeping in createResource()
    Thu Nov 22 09:39:01 CST 2001:<E> <JDBC Pool> Failed to create connection pool
    "oraclePool"
    For Oracle 8.1.7 do we need to any other library other than oci815_8. If so can
    you send those details

    Looks like you are using Oracle OCI driver and not WebLogic OCI driver so
    you really dont need the libweblogicoci36.so file in your
    LD_LIBRARY_PATH/PATH. Also your properties below show that you are using
    thin driver url and then also oci8 url, check you connection pool setting
    properly and may be try getting the latest oracle drivers.
    If you are trying to use weblogic jDrivers make sure your pool properties
    are set right.
    hth
    sree
    "Subba Rao.S..G" <[email protected]> wrote in message
    news:[email protected]...
    Presently our application is using weblogic 5.1 with oracle 8.1.6 database.
    Our
    application uses OCI driver to connect OraclePool. We used
    weblogic/lib/solaris/oci815_8/libweblogicoci36.so
    libraary to connect to dataabse.
    We upgraded our Database from 8.1.6 to 8.1.7. After upgradation of database
    from
    8.1.6 to 8.1.7. By using above shared library we are getting following
    error.
    In the weblogic connoction pool, we specied minimum as 4 connections. When
    it
    is creating connections while startup first connection is successfully
    connecting
    and second onwards it is giving following error.
    url=jdbc:oracle:thin:@169.165.38.162:1570:PBGSUP,
    props=user=SUPPORT;password=
    SUPPORT;, allowShrinking=true, driver=oracle.jdbc.driver.OracleDriver,
    aclName=w
    eblogic.jdbc.connectionPool.oraclePool, # testTable=dual,
    capacityIncremen
    t=2, initialCapacity=5, url=jdbc:oracle:oci8:@PBGSUP, shrinkPeriodMins=5}
    Delaying 1 seconds before making a oraclePool pool connection.
    Thu Nov 22 09:38:58 CST 2001:<I> <JDBC Pool> Connection for pool
    "oraclePool"
    cr
    eated.
    Delaying 1 seconds before making a oraclePool pool connection.
    java.sql.SQLException: ORA-01017: invalid username/password; logon denied
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled Code)
    at java.sql.SQLException.<init>(SQLException.java:43)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
    at oracle.jdbc.oci8.OCIDBAccess.check_error(Compiled Code)
    at oracle.jdbc.oci8.OCIDBAccess.logon(OCIDBAccess.java:310)
    at
    oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:200)
    at
    oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.ja
    va:251)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:224)
    at
    weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
    nectionEnvFactory.java:149)
    at
    weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
    nectionEnvFactory.java:109)
    at weblogic.common.internal.ResourceAllocator.makeResources(Compiled
    Cod
    e)
    at weblogic.common.internal.ResourceAllocator.<init>(Compiled Code)
    at
    weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
    ava:330)
    at weblogic.jdbc.common.internal.JdbcInfo.initPools(Compiled Code)
    at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
    at
    weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
    at weblogic.t3.srvr.StartupThread.doWork(Compiled Code)
    at
    weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java
    :62)
    Thu Nov 22 09:39:00 CST 2001:<I> <JDBC Pool> Sleeping in createResource()
    Thu Nov 22 09:39:01 CST 2001:<E> <JDBC Pool> Failed to create connection
    pool
    "oraclePool"
    For Oracle 8.1.7 do we need to any other library other than oci815_8. If so
    can
    you send those details

  • Mouse freezes with drive going into high pitch spin

    Hello to all .
    I have been experiencing a bit of a problem...  I currently own a Toshiba Satellite U205-S5034
    I test a lot of software on my machine... What I am encountering is mouse freeze as i rapidly zip
    through various applications with the drive going into a high pitch spin.  The only way that I rid this
    problem, I have to do a force shut down. Is there a remedy for such a problem?

    Thanks, I'll try that.
    I want to figure out also why I'm having this problem (sounds like speaker wires have been crossed!). When I used Compressor, I selected 'DVD Fatest Encode 90 mins", which ended up giving me two audio files: an AC3 Audio file and an AIFF audio file. I've been using the AC3 audio file, (and the M2V video file) in DVD Studio to burn a disc.
    I went backed and checked, it's the AC3 file that is screwed up; when I checked the AIFF file, the sound is fine (no buzzing).
    I wonder if it's possible there's something wrong with Compressor's AC3 audio routine?

  • Probem with databse connection using OCI driver

    hai folks,
    Iam using OCI driver to connect to the database.
    the program is compiling successfully but during runtime it is showing invalid url
    my code follows and my SID value is "mohan"
    import java.sql.*;
    import oracle.sql.*;
    import oracle.jdbc.oracore.Util;
    import oracle.jdbc.*;
    import java.math.BigDecimal;
    public class ArrayExample
         ResultSet rs;
    public static void main (String args[])
    throws Exception
         String driver="oracle.jdbc.driver.OracleDriver";
    DriverManager.registerDriver(new oracle.jdbc.OracleDriver());
    String url="jdbc:oracle://oci8:/@mohan";
    Class.forName(driver);
    Connection conn=DriverManager.getConnection(url,"SCOTT","TIGER");
    DriverManager.getConnection("jdbc:oracle://oci8:/@","scott","tiger") ;
    Statement stmt = conn.createStatement ();
    try
    stmt.execute ("DROP TABLE varray_table");
    stmt.execute ("DROP TYPE num_varray");
    System.out.println("mohan");
    catch (SQLException e)
    System.out.println(e);
    stmt.execute ("CREATE TYPE num_varray AS VARRAY(10) OF NUMBER(12, 2)");
    stmt.execute ("CREATE TABLE varray_table (col1 num_varray)");
    stmt.execute ("INSERT INTO varray_table VALUES (num_varray(100, 200))");
    ResultSet rs = stmt.executeQuery("SELECT * FROM varray_table");
    showResultSet (rs);
    int elements[] = { 300, 400, 500, 600 };
    ArrayDescriptor desc = ArrayDescriptor.createDescriptor("NUM_VARRAY", conn);
    ARRAY newArray = new ARRAY(desc, conn, elements);
    PreparedStatement ps =
    conn.prepareStatement ("insert into varray_table values (?)");
    ((OraclePreparedStatement)ps).setARRAY(1, newArray);
    ps.execute ();
    ResultSet rs = stmt.executeQuery("SELECT * FROM varray_table");
    showResultSet (rs);
    rs.close();
    ps.close();
    stmt.close();
    conn.close();
    public static void showResultSet (ResultSet rs)
    throws SQLException
    int line = 0;
    while (rs.next())
    line++;
    System.out.println("Row "+line+" : ");
    ARRAY array = ((OracleResultSet)rs).getARRAY (1);
    System.out.println ("Array is of type "+array.getSQLTypeName());
    System.out.println
    ("Array element is of typecode "+array.getBaseType());
    System.out.println ("Array is of length "+array.length());
    BigDecimal[] values = (BigDecimal[]) array.getArray();
    for (int i=0; i<values.length; i++)
    BigDecimal value = (BigDecimal) values;
    System.out.println(">> index "+i+" = "+value.intValue());
    please help me in sloving this problem
    my global database name and SID value in mohan
    Thanking u

    Bathina,
    Your problem is in your URL:
    String url="jdbc:oracle://oci8:/@mohan";As far as I know, you can't use the forward-slash character ("/"), by itself, as your database login name -- you must supply a "login/password". I don't know why, and if you don't like it, I suggest you create a TAR (Technical Assistance Request) via the MetaLink Web site.
    I recall similar questions being asked in this forum -- have you tried searching the forum archives?
    Good Luck,
    Avi.

Maybe you are looking for