Exception with WLS 6.1.3 & Oracle 9.2 thin driver

I'm testing out an upgrade from the Oracle thin driver that ships with WLS
6.1
to the Oracle 9.2 thin driver. My database server is running Oracle 8.1.7.
The only configuration change I made was to put the 9.2 classes12.zip at the
beginning of ths classpath. The line of my code where the exception is
being
throw is the first attempt at performing a resultSet.getLong() call. Has
anyone
gotten this combination to work yet? Any ideas on the error? I'd really
like to test out the native LOB support in the new drivers.
TIA - Gordon
<Oct 14, 2002 2:59:02 PM EDT> <Error> <Audit> <- Login failed because
loginName:
buyerOrgAdmin1034621942027 was not found.
com.eoriginal.engine.core.session.bas
icAccess.OrgUserDataAccessSessionBean_rngrwj_Impl::findUserAccountInfo,
java.lan
g.ArrayIndexOutOfBoundsException
at oracle.sql.NUMBER._fromLnxFmt(NUMBER.java:3181)
at oracle.sql.LnxLibThin.lnxsni(LnxLibThin.java:6571)
at oracle.sql.NUMBER.toLong(NUMBER.java:373)
at
oracle.jdbc.dbaccess.DBConversion.NumberBytesToLong(DBConversion.java
:2915)
at
oracle.jdbc.driver.OracleStatement.getLongValue(OracleStatement.java:
4373)
at
oracle.jdbc.driver.OracleResultSetImpl.getLong(OracleResultSetImpl.ja
va:529)
at
oracle.jdbc.driver.OracleResultSet.getLong(OracleResultSet.java:1540)
at weblogic.jdbc.jts.ResultSet.getLong(ResultSet.java:518)
at
weblogic.jdbc.rmi.internal.ResultSetImpl.getLong(ResultSetImpl.java:4
77)
at
weblogic.jdbc.rmi.internal.ResultSetStraightReader.getLong(ResultSetS
traightReader.java:142)
at
weblogic.jdbc.rmi.SerialResultSet.getLong(SerialResultSet.java:450)
at
com.eoriginal.engine.core.session.basicAccess.OrgUserDataAccessSessio
nBean.findUserAccountInfo(OrgUserDataAccessSessionBean.java:1272)
at
com.eoriginal.engine.core.session.basicAccess.OrgUserDataAccessSessio
nBean_rngrwj_EOImpl.findUserAccountInfo(OrgUserDataAccessSessionBean_rngrwj_
EOIm
pl.java:475)
at
com.eoriginal.engine.core.session.basicAccess.LoginSessionBean.valida
teLogin(LoginSessionBean.java:135)
at
com.eoriginal.engine.core.session.basicAccess.LoginSessionBean.valida
teLogin(LoginSessionBean.java:94)
at
com.eoriginal.engine.core.session.basicAccess.LoginSessionBean_moz7fh
EOImpl.validateLogin(LoginSessionBeanmoz7fh_EOImpl.java:37)
at
com.eoriginal.engine.core.session.basicAccess.LoginSessionBean_moz7fh
EOImplWLSkel.invoke(Unknown Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:274)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
(com.eoriginal.engine.core.session.basicAccess.LoginSessionBean_moz7fh_Impl:
:va
lidateLogin)>

Have you tried the thick (oci) driver?
We're looking to upgrade too.
"Richard" <[email protected]> wrote:
>
I try to connect to an Oracle 9.2.0 on Windows XP with the jdbc thin
driver. I
use weblogic server 7.0 SP1 (same problem with weblogic server 7.0.0).
I try direct connection (without pool) or with the weblogic pool, and
I get the
same error :
java.lang.ArrayIndexOutOfBoundsException
at oracle.security.o3logon.C0.r(C0)
at oracle.security.o3logon.C0.l(C0)
at oracle.security.o3logon.C1.c(C1)
at oracle.security.o3logon.O3LoginClientHelper.getEPasswd(O3LoginClientH
elper)
at oracle.jdbc.ttc7.O3log.<init>(O3log.java:289)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:251)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:246)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.ja
va:365)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:201)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:140)
at weblogic.jdbc.common.internal.ResourceAllocator.makeResources(Resourc
eAllocator.java:931)
at weblogic.jdbc.common.internal.ResourceAllocator.finishInit(ResourceAl
locator.java:457)
at weblogic.jdbc.common.internal.ResourceAllocator.<init>(ResourceAlloca
tor.java:316)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:292)
at weblogic.jdbc.common.internal.JDBCService.addDeploymentx(JDBCService.
java:282)
at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.j
ava:270)
The same test works well with an Oracle 9.0 !
I have already try with this differents drivers :
8.1.7, 9.0 and 9.2 and I always have the same problem.

Similar Messages

  • ConnectionPool problems with WLS 7.0 and Oracle 9.2

    Hi,
    We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type 4. In our
    application on the productive system (and only there) we constantly encounter
    a whole set of SQLExceptions which have all in common that the Connection from
    the pool is not valid any more when the application tries to use it.
    Typical, recurring error messages are:
    - Exhausted ResultSet
    - Connection has already been closed
    - Closed Statement
    - Transaction is no longer active - status committing
    - NullPointerException at
    weblogic.jdbc.pool.Connection.prepareStatement()
    There are no special Statements which create these errors. They are spread at
    random across practically every query the application creates, and the same queries
    sometimes succeed and sometimes fail.
    I double and triple checked that all Connections, Statements and ResultSets are
    closed immediately after use. As an example, I attached a code snippet and a resulting
    StackTrace which.
    The problem also seems to occur only with an (unknown) minimum of concurrent usern,
    since in the approval tests on an almost identical test system these errors never
    occurred.
    I also followed the advice from Oracle and installed the latest Oracle JDBC driver
    (Oracle 10g) - to no avail.
    What else can I do?
    Another question: Is it correct that my Oracle JDBC driver is in the application
    classpath (via a reference in the Manifest file of the application jar), not in
    the system classpath? There has never been a problem with that, but in a Newsgroup
    answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"), Joe Weinstein
    suggested to "get it listed at the
    front of the -classpath argument that the startWebLogic script creates for the
    java line that starts the server".
    I hesitate to do so, since the driver is in a standard WebApp- directory, WEB-INF/lib.
    Is it possible and safe to add a jar located there to the system classpath? If
    it is possible, why is it necessary?
    Best regards,
    Andreas Zehrt
    [CodeSnippetsAndStackTraceForConnectionPoolProblem.txt]

    Andreas Zehrt wrote:
    Hi Joe,
    Your hint that there is a threading problem was right:
    On further investigation of the code I found out that the class that passes the
    Connection to the DAO not only stores it as a member at some point (which is not
    a good idea anyway) but is also a singleton - then, of course, it's no surprise
    that the Connection gets invalid in a incalculable way when concurrent threads
    share it.
    The singleton instantiation was not so obvious because the way of instantiation
    is controlled by a configuration parameter that can be overridden at different
    levels.
    I changed it and the productive logfiles indicate that the SQLExceptions related
    to that class have disappeared.I am happy to have helped.
    So, thanks a lot for the advice.
    But I am still wondering why this code has worked for so long a time with WLS
    5.1 and Oracle 8 (the system has been productive for over 2 years). Even in the
    approval tests with WLS 7.0 and Oracle 9, we did not run into problems, although
    it was multi-user environment.Mo idea.
    I still believe that there is a difference between WLS 5.1 and 7.0 in the way
    it treats pooled Oracle JDBC Connections. I wished both Oracle and Bea could be
    a little more explicit about those changes and possible version incompatabilities
    beyond the general advice "use the latest thin driver".Though I can think of no change to our pooling which would have had any material
    effect in this case, I will certainly do what I can to see that our documentation
    is explicit about changes.
    Joe
    Best regards, Andreas
    Joe Weinstein <[email protected]> wrote:
    Hi Andreas.
    Andreas Zehrt wrote:
    Hi,
    We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type4. In our
    application on the productive system (and only there) we constantlyencounter
    a whole set of SQLExceptions which have all in common that the Connectionfrom
    the pool is not valid any more when the application tries to use it.
    Typical, recurring error messages are:
    - Exhausted ResultSetThat is typically if the statement that created it is either re-executed
    or closed.
    - Connection has already been closedAs described. If you give a stacktrace, we could make a debug patch which
    would show
    where it was originally closed.
    - Closed Statementsame as above.
    - Transaction is no longer active - status committingThat implies your code is obtaining a connection from a transactional
    datasource,
    and then later trying to use it after the transaction which it was associated
    with,
    is finished.
    - NullPointerException at
    weblogic.jdbc.pool.Connection.prepareStatement()Maybe any of the above.
    There are no special Statements which create these errors. They arespread at
    random across practically every query the application creates, andthe same queries
    sometimes succeed and sometimes fail.
    I double and triple checked that all Connections, Statements and ResultSetsare
    closed immediately after use. As an example, I attached a code snippetand a resulting
    StackTrace which.
    The problem also seems to occur only with an (unknown) minimum of concurrentusern,
    since in the approval tests on an almost identical test system theseerrors never
    occurred.
    I also followed the advice from Oracle and installed the latest OracleJDBC driver
    (Oracle 10g) - to no avail.
    What else can I do?
    Another question: Is it correct that my Oracle JDBC driver is in theapplication
    classpath (via a reference in the Manifest file of the applicationjar), not in
    the system classpath? There has never been a problem with that, butin a Newsgroup
    answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"),Joe Weinstein
    suggested to "get it listed at the
    front of the -classpath argument that the startWebLogic script createsfor the
    java line that starts the server".
    I hesitate to do so, since the driver is in a standard WebApp- directory,WEB-INF/lib.
    Is it possible and safe to add a jar located there to the system classpath?If
    it is possible, why is it necessary?I was only concerned to ensure we know which driver we are working with.
    We also ship
    an oracle thin driver, which becomes obsolete soon...
    I am concerned that your code creates pool connections to be used later.
    The problems
    can arise if more than one thread ever gets the same connection, or if
    the connection
    is used in the same thread, spanning transactions. It does also seem
    that there may
    be a threading issue, because if two threads each call the code to create
    a connection,
    and two connections are made, but one over-writes the other, the two
    threads can
    end up using the same connection, and closing it. The over-written one
    never gets closed,
    resulting in that leak message you got...
    Joe
    The Connection parameter is opened by a business component class, ComaServiceProviderClassicImpl.It is propagated through
    several classes in the business layer, but not used, until the DAOtakes it to make the query.
    So, the Connection is closed where it was opened, not in the DAO class.
    public class ConcernDAOImpl extends BaseDAO {
         public Collection getConcernsForIncidents(Connection conn, Collectionincidents)
    throws DataAccessException, ConstraintException, ComaParseException{>
    sqlMessage.append(")");
    String sqlStmt = sqlMessage.toString();
    PreparedStatement pstmt = null;
    ResultSet rs = null;
    try {
    pstmt = conn.prepareStatement(sqlStmt);
    rs = pstmt.executeQuery();
    while (rs != null && rs.next()) {
    final Concern concern =
    new Concern(DAOUtil.getComaOID(rs, ComaDBNames.KDANR));
    concern.setIncidentOID(DAOUtil.getComaOID(rs, ComaDBNames.KDAVGENR));
    return concerns;
    } catch (SQLException sqle) {
    // Wrapps real SQL exception
    String[] message = new String[]{sqle.getMessage(), sqlStmt};
    throw new DataAccessException(ExpCode.S_ORACLE_SQL, message,
    sqle);
    } finally {
    closeAll(rs, pstmt);
    _logger.exitDebug(method);
    Here, the Connection is acquired and finally closed
    public class ComaServiceProviderClassicImpl {
         public void updateComplaint(
    final Request updateRequest,
    final ResponseSingleElement response,
    final Principal principal)
    throws SystemException {
    try {
    logger.info("updateComplaint", "store incident");
    // store the incident in the database
    incidentManager.storeIncident(getConnection(), updateIncident);
    // reload the incident from Cache and / or the databaseto get the ContactReferences.
    Incident returnIncident = incidentManager.loadIncident(//IncidentManager passes the Connection to the DAO
    getConnection(), updateIncident.getOID());
    } catch (RemoteException rex) {
    // remote exceptions
    rollbackIfNecessary();
    CoreUtils.unwrapRemoteException(rex, logger);
    } catch (SystemException e) {
    // all other exceptions --> rollback if necessary and rethrow
    rollbackIfNecessary();
    throw e;
    } finally {
    removeConnection();
    logger.exitDebug("updateComplaint");
    This is the resulting StackTrace:
    sql exception: [Closed Statement: next] - sql statement: [select *
         at de.deutschepost.ubbrief.coma.persistence.dao.ConcernDAOImpl.getConcernsForIncidents(ConcernDAOImpl.java:363)
         at de.deutschepost.ubbrief.coma.persistence.dao.CachingConcernDAOImpl.getConcernsForIncidents(CachingConcernDAOImpl.java:129)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadConcernStructuresIntoIncidents(IncidentManagerImpl.java:1067)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadStructureForIncident(IncidentManagerImpl.java:320)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadIncidents(IncidentManagerImpl.java:264)
         at de.deutschepost.ubbrief.coma.persistence.taskmanager.TaskManagerImpl.selectTasksForUser(TaskManagerImpl.java:299)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:113)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
         at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
         at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
         at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
         at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
         at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    ####<May 26, 2004 12:18:43 PM CEST> <Warning> <JDBC> <S0048016> <REMA20Z><Finalizer> <kernel identity> <> <001074> <A JDBC pool connection leak
    was detected. A Connection leak occurs when a connection obtained from
    the pool was not closed explicitly by calling close() and then was disposed
    by the garbage collector and returned to the connection pool. The following
    stack trace at create shows where the leaked connection was created.
    Stack trace at connection create:
         at weblogic.jdbc.pool.Connection.<init>(Connection.java:66)
         at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:294)
         at weblogic.jdbc.pool.Driver.connect(Driver.java:210)
         at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:373)
         at weblogic.jdbc.jts.Driver.connect(Driver.java:129)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:287)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionFromPool(ComaComponentImpl.java:163)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionInternal(ComaComponentImpl.java:135)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnection(ComaComponentImpl.java:99)
         at de.deutschepost.ubbrief.coma.persistence.customermanager.CurryCustomerManagerImpl.findCustomers(CurryCustomerManagerImpl.java:73)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2BaseImpl.resolveCustomerInstances(ComaServiceProviderZ2BaseImpl.java:808)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:213)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
         at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
         at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
         at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
         at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
         at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)

  • Oracle 7 - JDBC Thin driver - connect - compatibility

    When logging on to an Oracle server v.7.2.3.0.0 with JDBC-thin
    driver (classes111.zip), I get the message:
    ORA-01017 invalid username/ password; logon denied
    even if the password, username and connection string is correct.
    The connection worked OK until some work was performed on the
    database and some changes with SQL*Net was done.
    I thought the driver worked OK with all versions of SQL*Net
    listeners?
    The database can be connected to with SQL*Plus.
    null

    I have the same problem trying to connect to database cache on iAS with iAS.

  • Oracle 8 JDBC thin driver for tomcat

    Hi all,
    I have tomcat3.3 installed on HP UNIX with java version "HP-UX Java C.01.18.05"
    I need to connect to an oracle 8 database using a Oracle JDBC thin driver. Where can I obtain this driver? How to install and configure it for the tomcat application?
    Thanks for your help.
    Regards
    Shriram

    If you go to the link which the last person posted, http://technet.oracle.com/software/tech/java/sqlj_jdbc/content.html, there is no indication for HP-UX. The only OS it lists are NT and Solaris. Does anyone know if these versions will work on HP-UX?
    Please help.
    Thanks,
    Sam

  • Connect to oracle using jdba thin driver

    i want to use jdbc thin driver to connect to oracle 8i for linux intel.
    my code is:
    DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
    String dbURL = "jdbc:oracle:thin:@dbserver:1521:iasdb";
    Connection con = DriverManager.getConnection(dbURL,"scott","tiger");
    but an error is reported as "the network adapter can not establish connection".
    why?
    i can connect to oracle using JDBC-ODBC bridge successfully.

    i want to use jdbc thin driver to connect to oracle 8i for linux intel.
    my code is:
    DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
    String dbURL = "jdbc:oracle:thin:@dbserver:1521:iasdb";
    Connection con = DriverManager.getConnection(dbURL,"scott","tiger");
    but an error is reported as "the network adapter can not establish connection".
    why?
    i can connect to oracle using JDBC-ODBC bridge successfully.

  • How to connect to Oracle 11g using thin driver with service name & SID

    Hi Experts,
    Wish to know whether there is a common way to connect to Oracle 11g server using SID or service name.
    Earlier I used jdbc:oracle:thin:@<<server>:<<port>>:<<SID>> for connecting to individual Oracle server instances.
    Now I need to connect to Oracle RAC which provides service names. So I need to use jdbc:oracle:thin:@<<server>:<<port>>/<<service name>>.
    This connection string is internally constructed by a program and user inputs <<server>>, <<port>> and <<SID>> or <<Service Name>>. Now this requires two different connection strings based on the input whether its SID or service name.
    Is there a common connection string for these two? Based on some articles like this, I understood that we can generically use jdbc:oracle:thin:@<<server>:<<port>>/<<service>>, whether for SID and service.
    When I tried this format with SID, I am getting the below error. What I tried is jdbc:oracle:thin:@myoracleserver:1521/ORCL, where ORCL is the SID
    java.sql.SQLException: Listener refused the connection with the following error:
    ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
    Request your help in solving this. What I want is a single connection string whether its SID or service. Any help is of great value.
    Regards
    Sunil

    Wish to know whether there is a common way to connect to Oracle 11g server using SID or service name.
    Earlier I used jdbc:oracle:thin:@<<server>:<<port>>:<<SID>> for connecting to individual Oracle server instances.
    Now I need to connect to Oracle RAC which provides service names. So I need to use jdbc:oracle:thin:@<<server>:<<port>>/<<service name>>.
    This connection string is internally constructed by a program and user inputs <<server>>, <<port>> and <<SID>> or <<Service Name>>. Now this requires two different connection strings based on the input whether its SID or service name.
    Is there a common connection string for these two? Based on some articles like this, I understood that we can generically use jdbc:oracle:thin:@<<server>:<<port>>/<<service>>, whether for SID and service.
    When I tried this format with SID, I am getting the below error. What I tried is jdbc:oracle:thin:@myoracleserver:1521/ORCL, where ORCL is the SID
    java.sql.SQLException: Listener refused the connection with the following error:
    ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
    Request your help in solving this. What I want is a single connection string whether its SID or service. Any help is of great value.
    Oracle has an entire book for JDBC: The JDBC Developer Guide.
    There are chapters that provide ALL of the connection properties and the rules for creating connection urls.
    http://docs.oracle.com/cd/E11882_01/java.112/e16548/urls.htm#BEIDBFDF
    See table 8-3 in that doc

  • Hanging problem with Oracle JDBC thin driver

    Hi. We have an application running on top of WLS 6.1 accessing Oracle 8I with oracle's
    JDBC thin driver. Under stress testing, it appears to hang sometimes. Thread dump
    shows that many threads seem to be stuck at the same line of code in JDBC driver
    (at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)). Has anyone run into similar
    issue? Any help is much appreciated.
    "ExecuteThread: '1' for queue: 'default'" daemon prio=5 tid=0xe18960 nid=0xf wai
    ting on monitor [0xb3680000..0xb36819d8]
    at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)
    at oracle.sql.NUMBER._fromLnxFmt(NUMBER.java:2953)
    at oracle.sql.NUMBER.toBigDecimal(NUMBER.java:557)
    at oracle.sql.NUMBER.bigDecimalValue(NUMBER.java:1872)
    at oracle.jdbc.dbaccess.DBConversion.NumberBytesToBigDecimal(DBConversion.ja
    va:1771)
    at oracle.jdbc.driver.OracleStatement.getBigDecimalValue(OracleStatement.jav
    a:3357)
    at oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
    66)
    at oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
    23)
    at oracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java
    :401)
    at weblogic.jdbc.jts.ResultSet.getObject(ResultSet.java:268)
    at weblogic.jdbc.rmi.internal.ResultSetImpl.getObject(ResultSetImpl.java:592
    at weblogic.jdbc.rmi.internal.ResultSetStraightReader.getObject(ResultSetStr
    aightReader.java:198)
    at weblogic.jdbc.rmi.SerialResultSet.getObject(SerialResultSet.java:682)
    "ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x6d93a8 nid=0x14
    wa
    iting on monitor [0xb3180000..0xb31819d8]
    at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)
    at oracle.sql.NUMBER._fromLnxFmt(NUMBER.java:2953)
    at oracle.sql.NUMBER.toBigDecimal(NUMBER.java:557)
    at oracle.sql.NUMBER.bigDecimalValue(NUMBER.java:1872)
    at oracle.jdbc.dbaccess.DBConversion.NumberBytesToBigDecimal(DBConversion.ja
    va:1771)
    at oracle.jdbc.driver.OracleStatement.getBigDecimalValue(OracleStatement.jav
    a:3357)
    at oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
    66)
    at oracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
    23)
    at oracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java
    :401)
    at weblogic.jdbc.jts.ResultSet.getObject(ResultSet.java:268)
    at weblogic.jdbc.rmi.internal.ResultSetImpl.getObject(ResultSetImpl.java:592
    at weblogic.jdbc.rmi.internal.ResultSetStraightReader.getObject(ResultSetStr
    aightReader.java:198)
    at weblogic.jdbc.rmi.SerialResultSet.getObject(SerialResultSet.java:682)

    Try get the latest thin driver from oracle and place it in the beginning of
    the classpath in the server startup script to use it. This seems like a
    oracle thin driver bug, the newer driver might help.
    sree
    "Andrew Dong" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hi. We have an application running on top of WLS 6.1 accessing Oracle 8Iwith oracle's
    JDBC thin driver. Under stress testing, it appears to hang sometimes.Thread dump
    shows that many threads seem to be stuck at the same line of code in JDBCdriver
    (at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)). Has anyone run intosimilar
    issue? Any help is much appreciated.
    "ExecuteThread: '1' for queue: 'default'" daemon prio=5 tid=0xe18960nid=0xf wai
    ting on monitor [0xb3680000..0xb36819d8]
    at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)
    at oracle.sql.NUMBER._fromLnxFmt(NUMBER.java:2953)
    at oracle.sql.NUMBER.toBigDecimal(NUMBER.java:557)
    at oracle.sql.NUMBER.bigDecimalValue(NUMBER.java:1872)
    atoracle.jdbc.dbaccess.DBConversion.NumberBytesToBigDecimal(DBConversion.ja
    va:1771)
    atoracle.jdbc.driver.OracleStatement.getBigDecimalValue(OracleStatement.jav
    a:3357)
    atoracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
    66)
    atoracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
    23)
    atoracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java
    :401)
    at weblogic.jdbc.jts.ResultSet.getObject(ResultSet.java:268)
    atweblogic.jdbc.rmi.internal.ResultSetImpl.getObject(ResultSetImpl.java:592
    atweblogic.jdbc.rmi.internal.ResultSetStraightReader.getObject(ResultSetStr
    aightReader.java:198)
    atweblogic.jdbc.rmi.SerialResultSet.getObject(SerialResultSet.java:682)
    >
    "ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x6d93a8nid=0x14
    wa
    iting on monitor [0xb3180000..0xb31819d8]
    at oracle.sql.NUMBER._isPositive(NUMBER.java:2882)
    at oracle.sql.NUMBER._fromLnxFmt(NUMBER.java:2953)
    at oracle.sql.NUMBER.toBigDecimal(NUMBER.java:557)
    at oracle.sql.NUMBER.bigDecimalValue(NUMBER.java:1872)
    atoracle.jdbc.dbaccess.DBConversion.NumberBytesToBigDecimal(DBConversion.ja
    va:1771)
    atoracle.jdbc.driver.OracleStatement.getBigDecimalValue(OracleStatement.jav
    a:3357)
    atoracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
    66)
    atoracle.jdbc.driver.OracleStatement.getObjectValue(OracleStatement.java:41
    23)
    atoracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSetImpl.java
    :401)
    at weblogic.jdbc.jts.ResultSet.getObject(ResultSet.java:268)
    atweblogic.jdbc.rmi.internal.ResultSetImpl.getObject(ResultSetImpl.java:592
    atweblogic.jdbc.rmi.internal.ResultSetStraightReader.getObject(ResultSetStr
    aightReader.java:198)
    atweblogic.jdbc.rmi.SerialResultSet.getObject(SerialResultSet.java:682)
    >
    >

  • P-R-O-B-L-E-M with JDBC thin driver

    Thank you gmagana!
    I did not manage to make this code connect to Oracle at all:
    import java.sql.*;
    public class jdbcThin {
    public static void connect() {
              String     url = "jdbc:oracle:thin:uName/passW@myDatabase:1521:orcl";
              try {
                        Class.forName ("oracle.jdbc.driver.OracleDriver");
                   Connection conn = DriverManager.getConnection( url );
                   System.out.println ("The Oracle thin driver loaded!");
              catch (ClassNotFoundException e) {
                   System.out.println ("Did not load driver.");
                   e.printStackTrace ();
              catch (SQLException e) {
                   System.out.println ("Did not load driver.");
                   e.printStackTrace ();
    public static void main( String args[] ) {
              connect();
    // Do "statement" stuff after I successfully connect to Oracle.
    My setup:
    1. jdbcThin.class in located in: ~/runMe/jdbcThin.class
    2. Unextracted classes12.zip in: ~/runMe/classes12.zip
    3. Java Runtime: ~/runMe/bin or
    ~/runMe/jre/bin
    Command line:
    %~/runMe> java jdbcThin
    Message:
    Did not load driver.
    java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver
    at jdbcThin.connect(Compiled Code)
    at jdbcThin.main(Compiled Code)
    %~/runMe>
    Tried running it with classpath re-direction:
    %~/runMe> java -classpath /runMe classes12.zip.jdbcThin
    Message:
    zip.jdbcThin
    Can't find class classes12.zip.jdbcThin
    %~/runMe>
    I am not permitted to change anything in .cshrc or .profile where
    I could use/> setenv classpath path1:path2: ~etc.
    Oh, JAVA gods(!) I am stuck. <quite pissed> :(
    ...and what am I doing wrongly with JDBC thin?!
    H E L P !!!!!!!!!!!!!!!!!!!

    Thanks Shirish! (Symmetrical WRT sound!)
    Here is my adaptation of that snippet which compiles, except for one error:
    Class OracleDriver not found. How did you handled your classes12.zip and
    your class path? Exactly what should happen at the command line?!
    That is really my BIGGEST issue with these vendor drivers outside JDK.
    I am aware that many styles work, but given the EXACTLY correct environment
    setting. This is my main issue and why I specified my exact directories.
    1. If Oracle is in: ~ root/Oracle
    2. Thin driver in: ~ root/drivers/classes12.zip
    3. My connection code in: ~root/sources/connDB.class
    What EXACTLY should happen to compile and run:
    import java.sql.*;
    public class connDB {
    public static void connect() {
              Connection     conn;
              Statement     stmt;
              ResultSet          rtset;
              String          SQL;
              try {
    DriverManager.registerDriver(new OracleDriver());
    conn = DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:" + instance, username, password);
    stmt = conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_UPDATABLE);
    rtset = stmt.executeQuery(SQL);
    catch( SQLException sqle ) {
                   System.out.println ("Did not load driver.");
                   sqle.printStackTrace ();
    public static void main( String args[] ) {
              connect();
    I am sitting @~root/sources>
    So far I have no problem running any non-driver associated classes from there.
    But how do I make my code find this OracleDriver?! And should classes12.zip
    be extracted? I was told it should remain intact. Point is where should it be
    or what command line "command" gets this connDB.class + OracleDriver to run?

  • Using Oracle JDBC Thin Driver

    We are trying to use the Oracle supplied JDBC thin driver directly from within a jar file we add for our application.
    The classes in the jar file directly connect to an oracle database via the thin driver.
    The problem we've encountered is that if the JDBC Connection object is held in memory, after some time, the connection times out for no reason.
    Is there some restriction with weblogic in connecting directly to database from a class file and then caching the connection reference? It almost seems as if weblogic is severing the connections.
    thank you,
    BJ

    Stefan,
    You are right, although I would recommend just having the
    TestConnectionOnReserve= true and the testTableName set. Refresh Minutes
    becomes kind of redundent when you set these values.
    TestConnsOnReserve allows the server to verify if a connection that the
    client/application has requested is good , otherwise it recreates this
    connection and gives it to the client/application.
    hth
    sree
    "Stefan" <[email protected]> wrote in message
    news:[email protected]...
    Hi Sree,
    If instead a WL connection pool would be used this issue could be solved
    using
    "Refresh Period" and TestTableName right? In this case the connection would
    be
    alive as long as WL server is up. As a bonus we would have an automatic
    reconnection
    after an Oracle server reboot?
    thanks, stefan
    "Sree Bodapati" <[email protected]> wrote:
    Hi BJ,
    When you get connection directly using the Oracle thin driver, this is
    for
    sure your database timing out the connection when no activity is detected
    for sometime. You should consult with your DBA to ensure this timeout
    is set
    to a higher value at the server or ensure you dont hold on to theconnection
    for long durations or ensure you handle this situation by triggering
    a
    generic oracle process so that you periodically keep the connection busy
    to
    ensure that the database does not close it.
    This shouldnt be anything to do with WebLogic as you dont seem to be
    using
    WebLogic connection pool.
    hth
    sree
    "BJ Choi" <bongjin.choi@neoforma> wrote in message
    news:[email protected]...
    We are trying to use the Oracle supplied JDBC thin driver directly from
    within a jar file we add for our application.
    The classes in the jar file directly connect to an oracle database via
    the
    thin driver.
    The problem we've encountered is that if the JDBC Connection object is
    held
    in memory, after some time, the connection times out for no reason.
    Is there some restriction with weblogic in connecting directly to database
    from a class file and then caching the connection reference? It almost
    seems
    as if weblogic is severing the connections.
    thank you,
    BJ

  • Oracle thin driver

    Hi,
    Are there any problems while using Oracle's jdbc thin driver with Weblogic 6.1
    sp1?
    Is there a 9i version for Oracle thin driver?
    Regards
    Perumal

    Hi Vaidy,
    You should download the latest Oracle 9i thin driver from Oracles website
    and place it in the beginning of the classpath when you start the server. It
    is use it at your own risk, AFAIK make sure you dont use any 8.1.7 or 8.1.6
    driver specific calls in your application and it should work just fine. If
    you dont use Oracle extensions everything should be ok.
    hth
    sree
    "vaidy" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    Are there any problems while using Oracle's jdbc thin driver with Weblogic
    6.1
    sp1?
    Is there a 9i version for Oracle thin driver?
    Regards
    Perumal

  • Oracle XA driver problem with WLS 7.0.1.0, Oracle 9.0.1

    We are using simplified chinese, after swith to bea jdriver, it messed up
    all the encoding. So we cannot display Chinese character correctly.
    We are using WLS 7.0.1.0, Oracle 9.0.1 on both Windows and Solaris 8
    environment, BEA supplied JDK 1.3.1_03.
    We have many diffrent problems with oracle drivers:
    1. We want to use XA driver to support distributed transaction, However:
    * bea jdriver xa messes up with encoding
    * when using oracle 901 driver, everything works fince except webservices.
    Workshop application access the ejb, then the workshp application sets
    isolation level, but oracle driver does not support it and gives error. Is
    there a way to turn off isolation level in workshop? I tried manually edit
    weblogic-ejb-jar.xml, however,workshop cannot redeploy it after that.
    2. When not using XA, oracle thin driver works fine. But we lost XA
    capability.
    Any work around?

    I did try to change the value in this config file as well, but did not help.
    In fact, the installation default setting is with
    '<transaction-isolation-level>' commented out.
    And when I use bea oracle jdriver, it somehow messed up with database
    character set encoding, so our Chinese characters could not be retrieved
    correctly. And I try to set the encoding of jdriver to 'GBK', it did not
    work.
    "Anurag Pareek" <[email protected]> дÈëÏûÏ¢ÐÂÎÅ
    :[email protected]..
    Hello Ma,
    The transaction isolation level value for EJBs backing the JWS files is
    specified in the <transaction-isolation-level> tag in the
    WEB-INF/weblogic-jws-config.xml file of a Workshop project. You can
    manipulate this value to serve your purpose.
    Please do let me know how it goes.
    Regards,
    Anurag
    Workshop Support
    "Ma Jie" <[email protected]> wrote in message
    news:[email protected]..
    We are using simplified chinese, after swith to bea jdriver, it messed
    up
    all the encoding. So we cannot display Chinese character correctly.
    We are using WLS 7.0.1.0, Oracle 9.0.1 on both Windows and Solaris 8
    environment, BEA supplied JDK 1.3.1_03.
    We have many diffrent problems with oracle drivers:
    1. We want to use XA driver to support distributed transaction, However:
    * bea jdriver xa messes up with encoding
    * when using oracle 901 driver, everything works fince exceptwebservices.
    Workshop application access the ejb, then the workshp application sets
    isolation level, but oracle driver does not support it and gives error.Is
    there a way to turn off isolation level in workshop? I tried manuallyedit
    weblogic-ejb-jar.xml, however,workshop cannot redeploy it after that.
    2. When not using XA, oracle thin driver works fine. But we lost XA
    capability.
    Any work around?

  • Workaround for using Oracle JDBC extension with WLS pooling

    Reading the newsgroup I saw that many of us encountered the problems
    with ClassCastException when tried to use Oracle JDBC extension
    with WLS pooling. I also had.
    In this case BEA recommends to use dangerous
    method getVendorConnection() which exposes
    the physical connection object to your code.
    Yes it's really dangerous because of unsafe usage may breaks
    WLS pooled connection(s).
    Moreover, this practice will make your JDBC code
    unportable (your JDBC code in addition to Oracle dependence
    became Weblogic dependent):
    void doSmth() {
    Connection con = ...;
    Connection vCon = ((WLConnection)con).getVendorConnection();
    // + mess of usage con in one places and vCon in others
    // (where Oracle extensions are needed)
    // !Don't forget to don't close vCon!
    Sux.
    I found the workaround.
    Introduction
    ============
    Yes the real cause of ClassCastException is that
    in depth of Oracle driver the casting
    to class oracle.jdbc.driver.OracleConnection
    (not to interface oracle.jdbc.OracleConnection)
    is performed.
    Someone can say that this is bug or pure desing.
    Weblogic pooled connection provide dynamic
    implementation for all public interfaces
    which real physical (wrapped) connection object implements.
    Great feature!
    But I guess that all interface methods implemented
    by simple call-delegation to physical (wrapped) connection object.
    In case of oracle.jdbc.OracleConnection interface
    this approach doesn't work for at least one its method:
    public OracleConnection unwrap()
    WLS pooled connection shoudn't implement this method by
    delegation to physical connection object BUT should
    return physical connection object itself!
    // Wrong implementation of unwrap()
    // delegation is used
    public OracleConnection unwrap() {
    return physicalConnection.unwrap();
    // Right implementation of unwrap()
    // physical connection returned
    public OracleConnection unwrap() {
    return physicalConnection;
    Workaround
    ==========
    1. Develop your own OracleConnection wrapper class:
    import oracle.jdbc.OracleConnection;
    import weblogic.jdbc.extensions.WLConnection;
    public class MyOracleConnectionImpl implements OracleConnection {
    private OracleConnection con;
    public MyOracleConnectionImpl(OracleConnection connection)
    throws SQLException
    this.con = connection;
    public OracleConnection unwrap() {
    return (OracleConnection)
    ((WLConnection)con).getVendorConnection();
    /* Implement all other methods by delegation to con object */
    2. Don't get Connections directly from DataSource --
    develop your own simple (may be static) utility
    class which retrives Connections from dataSource
    and returns them wrapped into your MyOracleConnectionImpl
    to your code from some method:
    puclic abstract class MyConnectionSource {
    public static Connection getConnection() {
    Connection con = // get it from DataSource
    return new MyOracleConnectionImpl((OracleConnection)con);
    3. Add attribute RemoveInfectedConnectionsEnabled="false"
    to definition of your JDBCConnectionPool within config.xml
    You may do it because of you `safely` use vendorConnection --
    you don't expose it to application code.
    4. Enjoy the Oracle JDBC extensions in your code!
    Example:
    Connection con = MyConnectionSource.getConnection;
    ArrayDescriptor add =
    ArrayDescriptor.createDescriptor("your_type", con);
    Hope it helps to someone.
    Best regards,
    Eugene Voytitsky

    Hello Eugene Voytitsky,
    Thanks Eugene Voytitsky for your idea
    I have tried the solution suggested by You, but it did not work.
    It still throws ClassCastException.
    I am sorry for posting the whole code of two classes below.
    I did this to give you more clarity.
    I am also indicating the place where the exception was thrown..
    Please let me know if I am doing something wrong.
    OracleConnection Wrapper class
    package ejbTesting;
    // sql imports
    import java.sql.CallableStatement;
    import java.sql.Connection;
    import java.sql.DatabaseMetaData;
    import java.sql.PreparedStatement;
    import java.sql.SQLException;
    import java.sql.SQLWarning;
    import java.sql.Statement;
    // util imports
    import java.util.Map;
    import java.util.Properties;
    // imports from Oracle Driver Classes
    import oracle.jdbc.OracleConnection;
    import oracle.jdbc.OracleOCIFailover;
    import oracle.jdbc.OracleSavepoint;
    // import from Weblogic extensions
    import weblogic.jdbc.extensions.WLConnection;
    public class WeblogicConnectionWrapper implements OracleConnection
         // oracle connection object
         private OracleConnection connection;
         public WeblogicConnectionWrapper (OracleConnection orclConnection)
              try
                   this.connection = orclConnection;
              catch(Exception unexpected )
                   unexpected.printStackTrace();
         public OracleConnection unwrap()
              try
              // The datasource returns a weblogic.jdbc.pool.Connection
              // This needs to be type casted to weblogic.jdbc.extensions.WLConnection
              // Only this weblogic.jdbc.extensions.WLConnection CAN BE type casted
              // to OracleConnection
         return (OracleConnection) ((WLConnection) connection).getVendorConnection();
         catch(Exception sqlException )
              sqlException.printStackTrace ();
              return null;
         /* Implement all other methods by delegation to connection object */      
    public Connection _getPC()
    return connection._getPC();
    public void archive(int i, int j, String s)
    throws SQLException
    connection.archive(i, j, s);
    public void assertComplete()
    throws SQLException
    connection.assertComplete();
    public void clearWarnings()
    throws SQLException
    connection.clearWarnings();
    public void close()
    throws SQLException
    connection.close();
    public void commit()
    throws SQLException
    connection.commit();
    public Statement createStatement()
    throws SQLException
    return connection.createStatement();
    public Statement createStatement(int i, int j)
    throws SQLException
    return connection.createStatement(i, j);
    public boolean getAutoClose()
    throws SQLException
    return connection.getAutoClose();
    public boolean getAutoCommit()
    throws SQLException
    return connection.getAutoCommit();
    public CallableStatement getCallWithKey(String s)
    throws SQLException
    return connection.getCallWithKey(s);
    public String getCatalog()
    throws SQLException
    return connection.getCatalog();
    public boolean getCreateStatementAsRefCursor()
    return connection.getCreateStatementAsRefCursor();
    public int getDefaultExecuteBatch()
    return connection.getDefaultExecuteBatch();
    public int getDefaultRowPrefetch()
    return connection.getDefaultRowPrefetch();
    public Object getDescriptor(String s)
    return connection.getDescriptor(s);
    public boolean getExplicitCachingEnabled()
    throws SQLException
    return connection.getExplicitCachingEnabled();
    public boolean getImplicitCachingEnabled()
    throws SQLException
    return connection.getImplicitCachingEnabled();
    public boolean getIncludeSynonyms()
    return connection.getIncludeSynonyms();
    public Object getJavaObject(String s)
    throws SQLException
    return connection.getJavaObject(s);
    public DatabaseMetaData getMetaData()
    throws SQLException
    return connection.getMetaData();
    public Properties getProperties()
    return connection.getProperties();
    public boolean getRemarksReporting()
    return connection.getRemarksReporting();
    public boolean getRestrictGetTables()
    return connection.getRestrictGetTables();
    public String getSQLType(Object obj)
    throws SQLException
    return connection.getSQLType(obj);
    public String getSessionTimeZone()
    return connection.getSessionTimeZone();
    public int getStatementCacheSize()
    throws SQLException
    return connection.getStatementCacheSize();
    public PreparedStatement getStatementWithKey(String s)
    throws SQLException
    return connection.getStatementWithKey(s);
    public int getStmtCacheSize()
    return connection.getStmtCacheSize();
    public short getStructAttrCsId()
    throws SQLException
    return connection.getStructAttrCsId();
    public boolean getSynchronousMode()
    return connection.getSynchronousMode();
    public int getTransactionIsolation()
    throws SQLException
    return connection.getTransactionIsolation();
    public Map getTypeMap()
    throws SQLException
    return connection.getTypeMap();
    public String getUserName()
    throws SQLException
    return connection.getUserName();
    public boolean getUsingXAFlag()
    return connection.getUsingXAFlag();
    public SQLWarning getWarnings()
    throws SQLException
    return connection.getWarnings();
    public boolean getXAErrorFlag()
    return connection.getXAErrorFlag();
    public boolean isClosed()
    throws SQLException
    return connection.isClosed();
    public boolean isLogicalConnection()
    return connection.isLogicalConnection();
    public boolean isReadOnly()
    throws SQLException
    return connection.isReadOnly();
    public String nativeSQL(String s)
    throws SQLException
    return connection.nativeSQL(s);
    public Object openJoltConnection(String s, short word0, short word1)
    return connection.openJoltConnection(s, word0, word1);
    public void oracleReleaseSavepoint(OracleSavepoint oraclesavepoint)
    throws SQLException
    connection.oracleReleaseSavepoint(oraclesavepoint);
    public void oracleRollback(OracleSavepoint oraclesavepoint)
    throws SQLException
    connection.oracleRollback(oraclesavepoint);
    public OracleSavepoint oracleSetSavepoint()
    throws SQLException
    return connection.oracleSetSavepoint();
    public OracleSavepoint oracleSetSavepoint(String s)
    throws SQLException
    return connection.oracleSetSavepoint(s);
    public int pingDatabase(int i)
    throws SQLException
    return connection.pingDatabase(i);
    public CallableStatement prepareCall(String s)
    throws SQLException
    return connection.prepareCall(s);
    public CallableStatement prepareCall(String s, int i, int j)
    throws SQLException
    return connection.prepareCall(s, i, j);
    public CallableStatement prepareCallWithKey(String s)
    throws SQLException
    return connection.prepareCallWithKey(s);
    public PreparedStatement prepareStatement(String s)
    throws SQLException
    return connection.prepareStatement(s);
    public PreparedStatement prepareStatement(String s, int i, int j)
    throws SQLException
    return connection.prepareStatement(s, i, j);
    public PreparedStatement prepareStatementWithKey(String s)
    throws SQLException
    return connection.prepareStatementWithKey(s);
    public void purgeExplicitCache()
    throws SQLException
    connection.purgeExplicitCache();
    public void purgeImplicitCache()
    throws SQLException
    connection.purgeImplicitCache();
    public void putDescriptor(String s, Object obj)
    throws SQLException
    connection.putDescriptor(s, obj);
    public void registerApiDescription(String s, short word0, short word1, String
    s1)
    connection.registerApiDescription(s, word0, word1, s1);
    public void registerSQLType(String s, Class class1)
    throws SQLException
    connection.registerSQLType(s, class1);
    public void registerSQLType(String s, String s1)
    throws SQLException
    connection.registerSQLType(s, s1);
    public void registerTAFCallback(OracleOCIFailover oracleocifailover, Object
    obj)
    throws SQLException
    connection.registerTAFCallback(oracleocifailover, obj);
    public void rollback()
    throws SQLException
    connection.rollback();
    public void setAutoClose(boolean flag)
    throws SQLException
    connection.setAutoClose(flag);
    public void setAutoCommit(boolean flag)
    throws SQLException
    connection.setAutoCommit(flag);
    public void setCatalog(String s)
    throws SQLException
    connection.setCatalog(s);
    public void setCreateStatementAsRefCursor(boolean flag)
    connection.setCreateStatementAsRefCursor(flag);
    public void setDefaultExecuteBatch(int i)
    throws SQLException
    connection.setDefaultExecuteBatch(i);
    public void setDefaultRowPrefetch(int i)
    throws SQLException
    connection.setDefaultRowPrefetch(i);
    public void setExplicitCachingEnabled(boolean flag)
    throws SQLException
    connection.setExplicitCachingEnabled(flag);
    public void setImplicitCachingEnabled(boolean flag)
    throws SQLException
    connection.setImplicitCachingEnabled(flag);
    public void setIncludeSynonyms(boolean flag)
    connection.setIncludeSynonyms(flag);
    public void setReadOnly(boolean flag)
    throws SQLException
    connection.setReadOnly(flag);
    public void setRemarksReporting(boolean flag)
    connection.setRemarksReporting(flag);
    public void setRestrictGetTables(boolean flag)
    connection.setRestrictGetTables(flag);
    public void setSessionTimeZone(String s)
    throws SQLException
    connection.setSessionTimeZone(s);
    public void setStatementCacheSize(int i)
    throws SQLException
    connection.setStatementCacheSize(i);
    public void setStmtCacheSize(int i)
    throws SQLException
    connection.setStmtCacheSize(i);
    public void setStmtCacheSize(int i, boolean flag)
    throws SQLException
    connection.setStmtCacheSize(i, flag);
    public void setSynchronousMode(boolean flag)
    connection.setSynchronousMode(flag);
    public void setTransactionIsolation(int i)
    throws SQLException
    connection.setTransactionIsolation(i);
    public void setTypeMap(Map map)
    throws SQLException
    connection.setTypeMap(map);
    public void setUsingXAFlag(boolean flag)
    connection.setUsingXAFlag(flag);
    public void setWrapper(OracleConnection oracleconnection)
    connection.setWrapper(oracleconnection);
    public void setXAErrorFlag(boolean flag)
    connection.setXAErrorFlag(flag);
    public void shutdown(int i)
    throws SQLException
    connection.shutdown(i);
    public void startup(String s, int i)
    throws SQLException
    connection.startup(s, i);
    Util class to get Wrapped Connections from
    datasource
    package ejbTesting;
    // j2ee imports
    import javax.naming.InitialContext;
    import javax.sql.DataSource;
    // sql imports
    import java.sql.Connection;
    // imports from Oracle Driver Classes
    import oracle.jdbc.OracleConnection;
    * Wrapper class for the DataSource Connection from Weblogic pool
    public class DataSourceConnectionWrapper
         // datasource variable
         private static transient DataSource datasource = null;
         private static String dbName = "jdbc/workbench";
    * Method that returns the database connection
         public static Connection getConnection()
              try
                   // initialsing the datasource object
                   initialiseDataSource ();
                   // Getting a connection from the datasource
                   Connection con = datasource.getConnection( );
                   // wrapping it custom wrapper class and
                   // returning the connection object
                   return new WeblogicConnectionWrapper((OracleConnection)con);
              catch(Exception exception )
                   exception.printStackTrace();
                   return null;
         private static void initialiseDataSource( ) throws Exception
    if ( datasource == null )
    try
    InitialContext ic = new InitialContext( );
    datasource = (DataSource) ic.lookup( dbName );
    catch (Exception ne )
    throw new Exception( "NamingException while looking up DataSource with
    JNDI name" +
    dbName + ": \n" + ne.getMessage( ) );
    Exception Stack Trace
    The line 46 in DataSourceConnectionWrapper
    corresponds to
    return new WeblogicConnectionWrapper((OracleConnection)con);
    Which I feel is logical as the connection which we get from Weblogic
    datasource cannot be type casted to OracleConnection
    java.lang.ClassCastException: weblogic.jdbc.pool.Connection
    at ejbTesting.DataSourceConnectionWrapper.getConnection(DataSourceConnectionWrapper.java:46)

  • Startup problems with XA connection pools on Oracle and WLS 6.1

    I am having starup problems trying to set up a WLS 6.1 connection pool using
    XA. When I try to start the server, I get the following exception:
    <Nov 19, 2001 3:06:28 PM EST> <Error> <JDBC> <Cannot startup connection pool
    "dbdev1XAPool" weblogic.common.ResourceException: java.sql.SQLException:
    open failed for XAResource 'dbdev1' with error XAER_RMERR : A resource
    manager error has occured in the transaction branch. Check Oracle XA trace
    file(s) (if any) for database errors. The Oracle XA trace file(s) are
    located at the directory where yo
    u start the Weblogic Server, and have names like
    xa_<pool_name><MMDDYYYY>.trc.
    at weblogic.jdbc.oci.xa.XAConnection.<init>(XAConnection.java:58)
    at
    weblogic.jdbc.oci.xa.XADataSource.getXAConnection(XADataSource.java:600)
    at
    weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnec
    tionEnvFactory.java:194)
    at
    weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnec
    tionEnvFactory.java:54)
    at
    weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
    ava:698)
    at
    weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
    at
    weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:620
    at
    weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:329)
    The contents of the Oracle trace file:
    ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'.
    150627.1312:344.344.330727191:
    xaoopen:
    xa_info=Oracle_XA+Acc=P/cmauser/admin+SesTm=100+DB=dbdev1+Threads=true+LogDi
    r=.+DbgFl=0x15,rmid=330727191,flags=0x0
    150627.1312:344.344.330727191:
    ORA-12560: TNS:protocol adapter error
    150627.1312:344.344.330727191:
    xaolgn_help: XAER_RMERR; OCIServerAttach failed. ORA-12560.
    150627.1312:344.344.330727191:
    xaoopen: return -3
    I am running WLS 6.1 and Oracle 8.1.7 on windows (separate machines). The
    connection pool settings are:
    <JDBCConnectionPool CapacityIncrement="0"
    DriverName="weblogic.jdbc.oci.xa.XADataSource" InitialCapacity="40"
    MaxCapacity="40" Name="dbdev1XAPool"
    Properties="user=cmauser;password=admin;dataSourceName=dbdev1"
    RefreshMinutes="15" ShrinkingEnabled="false" SupportsLocalTransaction="true"
    Targets="cmatest" TestTableName="hppcontentsource" />
    I have not had any problems connecting to the same database through regular
    JDBC connection pools or through the utils.dbping utility.
    What am I doing wrong?

    This is a dup message. Add "DebugConfigInfo OFF" in httpd.conf.
    Jong
    [email protected] (Olaf Foellinger) wrote:
    >
    Hi,
    we're trying to setup apache on linux so that it's forwarding all jsp
    requests to Bea WLS 6.0 on Solaris. We've installed the mod_wl.so
    modules according to the documentation. When apache starts it shows the
    following warning:
    [Tue Jan  9 13:22:55 2001] [warn] Loaded DSO
    /usr/lib/apache/1.3/mod_wl.so uses plain Apache 1.3 +API, this module
    might crash under EAPI! (please recompile it with -DEAPI)
    and in fact, when we try to load a jsp page we get
    [Tue Jan  9 13:29:14 2001] [notice] child pid 5780 exit signal
    Segmentation fault (11)
    Does anyone have a working solution ? Can bea provide us with a plugin
    compiled with EAPI ?
    Greetings Olaf

  • Does Oracle 8.0.5 work with WLS 7.0

    We are having problems with WLS 7.0, Oracle 8.0.5 and CMP.
    Do anybody know a link or anything to help?
    Or do we have to upgrade the database to 8.1.7 (at least)?
    Regards
    Glenn Petersen

    Hi Glenn
    What is the problem you are seeing? any specific exceptions?
    sree
    "Glenn Petersen" <[email protected]> wrote in message
    news:[email protected]..
    >
    We are having problems with WLS 7.0, Oracle 8.0.5 and CMP.
    Do anybody know a link or anything to help?
    Or do we have to upgrade the database to 8.1.7 (at least)?
    Regards
    Glenn Petersen

  • Error configuring the Oracle 8.1.7 XA Thin driver with WLS 6.1 SP1

    I am trying to configure the Oracle 8.1.7.0 thin driver and am getting an SystemException
    when the pool tries to test the connection at server startup. It looks like the
    start() method is failing. I have put Oracle's Classes12.zip, jndi.zip, and the
    jta.zip on the classpath immediately after the weblogic.jar entry. Is this a
    classpath issue? Can someone that has this working please help me. Thanks in
    advance. Steve
    The following is the JDBC Pool entry in the config.xml file:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    InitialCapacity="0" LoginDelaySeconds="1" MaxCapacity="20"
    Name="oraclePoolSun3500XAThin" Properties="user=sschaber;url=jdbc:oracle:thin:@199.191.94.4:1521:ORCLT;password=sschaber;dataSourceName=oraclePoolSun3500XAThin"
    RefreshMinutes="5" ShrinkPeriodMinutes="30"
    Targets="memphisserver" TestConnectionsOnRelease="true"
    TestConnectionsOnReserve="true" TestTableName="Dual" URL="jdbc:oracle:thin:@199.191.94.4:1521:ORCLT"/>
    Also, here is the entire exception being thrown:
    <Apr 5, 2002 1:33:08 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <javax.transaction.SystemException:
    start() failed on resource 'oracle.jdbc.xa.client.Or
    acleXAResource' null
    at weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.java:998)
    at weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.java:234)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:374)
    at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:915)
    at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1114)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    <Apr 5, 2002 1:33:08 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <This
    connection will now be refreshed.>
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC> <Connection for XA pool "oraclePoolSun3500XAThin"
    refreshed.>
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <A connection
    from pool oraclePoolSun3500XAThin was tested during reserve with a select
    count(*) from Dual and failed:>
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <javax.transaction.SystemException:
    start() failed on resource 'oracle.jdbc.xa.client.Or
    acleXAResource' null at weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.java:998)
    at weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.java:234)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:374)
    at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:915)
    at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:465)
    at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:376)
    at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1103)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <This
    connection will now be refreshed.>

    This still does not work for me. I must be missing something here. Any help would
    be appreciated.
    Thanks,
    Steve
    "Sree Bodapati" <[email protected]> wrote:
    Hi Steve,
    I see the initial capacity is set to zero , can you push it up to atleast
    few connections and see if it helps, and Let me know.
    thanks
    sree
    "Steve Schaber" <[email protected]> wrote in message
    news:[email protected]...
    I made sure that we have the latest version of the classes12.zip file(8.1.7).
    Also, moved the classes12.zip, jndi.zip, and the jta.zip file beforethe
    weblogic.jar
    file in the classpath. I am still getting the same error.
    Steve
    "Sree Bodapati" <[email protected]> wrote:
    Put the classes12.zip and other zip files before the weblogic.jar
    file
    in
    the classpath. ensure that you have the latest classes12.zip filefrom
    oracle.
    sree
    "Steve Schaber" <[email protected]> wrote in message
    news:[email protected]...
    I am trying to configure the Oracle 8.1.7.0 thin driver and am gettingan
    SystemException
    when the pool tries to test the connection at server startup. It
    looks
    like the
    start() method is failing. I have put Oracle's Classes12.zip,
    jndi.zip,
    and the
    jta.zip on the classpath immediately after the weblogic.jar entry.Is
    this a
    classpath issue? Can someone that has this working please help
    me.
    Thanks in
    advance. Steve
    The following is the JDBC Pool entry in the config.xml file:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    InitialCapacity="0" LoginDelaySeconds="1" MaxCapacity="20"
    Name="oraclePoolSun3500XAThin"
    Properties="user=sschaber;url=jdbc:oracle:thin:@199.191.94.4:1521:ORCLT;pass
    word=sschaber;dataSourceName=oraclePoolSun3500XAThin"
    RefreshMinutes="5" ShrinkPeriodMinutes="30"
    Targets="memphisserver" TestConnectionsOnRelease="true"
    TestConnectionsOnReserve="true" TestTableName="Dual"URL="jdbc:oracle:thin:@199.191.94.4:1521:ORCLT"/>
    Also, here is the entire exception being thrown:
    <Apr 5, 2002 1:33:08 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><javax.transaction.SystemException:
    start() failed on resource 'oracle.jdbc.xa.client.Or
    acleXAResource' null
    at
    weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo..
    java:998)
    at
    weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.j
    ava:234)
    at
    weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
    nsactionImpl.java:374)
    atweblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:915)
    at
    weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:11
    14)
    at
    weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
    er.java:238)
    at
    weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
    :229)
    atweblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
    at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    <Apr 5, 2002 1:33:08 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><This
    connection will now be refreshed.>
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC> <Connection for XA pool"oraclePoolSun3500XAThin"
    refreshed.>
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><A
    connection
    from pool oraclePoolSun3500XAThin was tested during reserve with
    a
    select
    count(*) from Dual and failed:>
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><javax.transaction.SystemException:
    start() failed on resource 'oracle.jdbc.xa.client.Or
    acleXAResource' null at
    weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo..
    java:998)
    at
    weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.j
    ava:234)
    at
    weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
    nsactionImpl.java:374)
    atweblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:915)
    at
    weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:46
    5)
    at
    weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.j
    ava:376)
    at
    weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:11
    03)
    at
    weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
    er.java:238)
    at
    weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
    :229)
    atweblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
    at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><This
    connection will now be refreshed.>

Maybe you are looking for

  • Stored business object in BSP

    hi All, I am trying to imitate the store business document facility available in me23n against PO in our bSP application. I have put the file element and i can get the file and all but i am not able to store it as busines document, I need to store th

  • Help with showDocument() function

    Hello, I am trying to write a segment of code that will allow me to change the URL of a HTML frame, however, it is a different frame than that which contains the applet.... I have tried looking at the documentation for the showDocument function, but

  • Redeem serial number

    I had registered acrobat pro X and then due to problem with my laptop I reinstalled again. The acrobat does not recognise my serial number which was registered at that time. how to redeem?

  • Can anyone help me embed an rss feed

    I am trying to embed an rss feed.  Any help available?

  • Surname, first name in GAL

    Dear beekeepers, Outlook has an option to present all entries in the address book formatted like "surname, first name". Can the GAL (global address list) be configured accordingly? Regards, Thomas