Excplicitly Including JDBC Operations in Tx

I have a situation where I have to create a new database connection each
time (the authentication/authorization happens at the database level). Is
there a way to include the database operations in an EJB's container-managed
transaction?
Thanks,
Bob

Bob Lee wrote:
In my situation, I have to create the connection each time. Do I have to
dynamically create a pool with a single connection? Or, can I just call
Driver.connect() and somehow explicitly add this connection to the current
Tx?I see, you don't know the user ID ahead of time... Yes, you could use the dynamic
pool API to make a one-connection pool. I suggest configuring the server to
have a one-connection pool and a TxDataSource for it at startup. Then when
you want to do a TX in an external client, you would destroy the initial pool and
recreate it with the DBMS user you want. This will allow you to use the TxDataSource
to get a connection, which if obtained in the context of a running UserTransaction,
will get automatically included in the tx.
Joe
>
>
Thanks,
Bob
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]..
Bob Lee wrote:
I have a situation where I have to create a new database connection each
time (the authentication/authorization happens at the database level).
Is
there a way to include the database operations in an EJB'scontainer-managed
transaction?Sure. The EJB should be tx-requires, which means it will start one whencalled
if one is not underway already, or will join the transaction in progressif there
is one. Your code will use the standard JTS/JTA API to obtain and start aUserTransaction.
Then you should obtain your JDBC connection fro a TxDataSource, and itwill be included
in the transaction. If your EJB(s) do any JDBC, it must be to the samepool.
Joe
Thanks,
Bob

Similar Messages

  • EJB and JDBC operation

              Hi,
              We r using both JDBC and EJB's to perform DB operations.
              We have encountered a problem where operations on the EJB's
              dont apply on JDBC operations done later on in the same txn.
              The same goes the other way (If we perform an insert using JDBC and then try to
              lookup the bean with that ID, it fails).
              We understand the reason for this behaviour, I'm looking for a way to make them
              "see" each other, is that possible somehow ?
              thanks,
              Asher.
              

    You need to run both operations in a JTA transaction and ensure that you
              get your JDBC connections from a TxDataSource.
              -- Rob
              Chuk wrote:
              > Hi,
              > We r using both JDBC and EJB's to perform DB operations.
              > We have encountered a problem where operations on the EJB's
              > dont apply on JDBC operations done later on in the same txn.
              > The same goes the other way (If we perform an insert using JDBC and then try to
              > lookup the bean with that ID, it fails).
              > We understand the reason for this behaviour, I'm looking for a way to make them
              > "see" each other, is that possible somehow ?
              >
              > thanks,
              > Asher.
              >
              

  • Jdbc operating system authentication

    Is it only possible to use operating system authentication for jdbc connections (thin/oci) with an oracle11g database ?
    Is it possible to use operating system authentication for jdbc connections with earlier versions of oracle ?
    Thanks, Seb

    Seb,
    As far as I am aware, you cannot use operating system authentication for JDBC connections in all versions up to and including 10g.
    I have not used Oracle 11g, so I don't know about that version.
    Good Luck,
    Avi.

  • .jar includes jdbc driver but doesn't work

    Hi
    I'm quite new with Java. I've just created my first app in java, it's some kind of CMS. I have to give to my friend who can only install JVM and I can't set up his computer, because he lives in other city. What's the problem then:
    I tried to compile (build) complete file with jdbc driver. And actually I've done it (when I open jar with winrar I see that mysql-connector.jar is there) but it's not working. I still have error:
    SQLException: com.mysql.jdbc.Driver
    No suitable driver
    08001
    It works fine when I'm running it with NetBeans, but built jar doesn't work at all.
    Please help me with this problem. I was searching in many forums for the same problem, but no one had it (I mean EXACTLY the same). I have had many problems already with adding connector to NetBeans project at the beginning, but finally I've done it after 2 days - reinstallation of NB solved the problem. Is it possible that's NB fault again?
    Thx for any clues
    Michael

    Hello,
    Try to include a Class-Path option in the Manifest of your jar and see if that works.
    Hope this helps

  • Deadlock while perform JDBC operations?

    Hello,
    We are running Weblogic 7.0SP2 with Oracle 9.2.x as the db.
    We use Oracle for TOPLink as our orm tool for all db access.
    We are encountering strange deadlocks while doing db reads and updates from a
    message-driven EJB (MDB) whose onMessage() method has a "Required" transaction
    attribute.
    I have attached a partial thread-dump below. It seems that multiple threads (3+)
    are waiting to lock the same monitor:
    - waiting to lock <39f68f0> (a oracle.jdbc.driver.OracleConnection)
    This is strange as each thread is running in its own transaction, and so it should
    be using a unique jdbc connection. btw, we use a Weblogic Connection Pool. The
    TOPLink orm tool obtains a connection from the pool by using the DataSource.getConnection()
    method.
    My confusion arises from the fact that some threads are locked while performing
    read operations and for some reason are waiting to lock the same monitor.
    Any help will be greatly appreciated.
    p.s. i also verified that there are more connections available from the pool,
    and idle ExecuteThreads while the deadlock occurs.
    Eventually, the transaction times out and gets rolled-back.
    Partial Thread Dump:
    ================
    "ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0x13502c00 nid=0xde8
    waiting for monitor entry [0x145ff000..0x145ffdbc]
         at oracle.jdbc.driver.OracleConnection.prepareStatement(OracleConnection.java:818)
         - waiting to lock <39f68f0> (a oracle.jdbc.driver.OracleConnection)
         at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:191)
         at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:139)
         at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:92)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.prepareStatement(Unknown
    Source)
    <clipped>
    "ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x13549930 nid=0x874
    waiting for monitor entry [0x1447f000..0x1447fdbc]
         at oracle.jdbc.driver.OracleConnection.prepareStatement(OracleConnection.java:818)
         - waiting to lock <39f68f0> (a oracle.jdbc.driver.OracleConnection)
         at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:191)
         at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:139)
         at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:92)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.prepareStatement(Unknown
    Source)
    <clipped>
    "ExecuteThread: '5' for queue: 'default'" daemon prio=5 tid=0x1324e688 nid=0xa58
    waiting for monitor entry [0x1443f000..0x1443fdbc]
         at oracle.jdbc.driver.OracleConnection.prepareStatement(OracleConnection.java:818)
         - waiting to lock <39f68f0> (a oracle.jdbc.driver.OracleConnection)
         at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:191)
         at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:139)
         at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:92)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.prepareStatement(Unknown
    Source)
    <clipped>
    "ExecuteThread: '3' for queue: 'default'" daemon prio=5 tid=0x1353aa38 nid=0xda8
    waiting for monitor entry [0x143bf000..0x143bfdbc]
         at oracle.jdbc.driver.OracleConnection.prepareStatement(OracleConnection.java:818)
         at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:191)
         at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:139)
         at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:92)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.prepareStatement(Unknown
    Source)
         at oracle.toplink.queryframework.SQLCall.prepareStatement(Unknown Source)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(Unknown
    Source)
    <clipped>
    "ExecuteThread: '1' for queue: 'default'" daemon prio=5 tid=0x13520e10 nid=0xb3c
    waiting on monitor [0x1433f000..0x1433fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3147cb0> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3147cb0> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '0' for queue: 'default'" daemon prio=5 tid=0x1350bc10 nid=0x98c
    waiting on monitor [0x142ff000..0x142ffdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3147c30> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3147c30> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)

    I've attached the full thread dump.
    Thanks.
    Full thread dump:
    "ListenThread.Default" prio=5 tid=0x13921e80 nid=0x1198 runnable [0x1533f000..0x1533fdbc]
         at java.net.PlainSocketImpl.socketAccept(Native Method)
         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
         - locked <4d19ed8> (a java.net.PlainSocketImpl)
         at java.net.ServerSocket.implAccept(ServerSocket.java:238)
         at java.net.ServerSocket.accept(ServerSocket.java:217)
         at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
         at weblogic.t3.srvr.ListenThread.run(ListenThread.java:263)
    "Thread-8" prio=5 tid=0x13865788 nid=0xfc4 waiting on monitor [0x152ff000..0x152ffdbc]
         at java.lang.Thread.sleep(Native Method)
         at weblogic.management.deploy.GenericAppPoller.run(GenericAppPoller.java:139)
    "Thread-7" prio=5 tid=0x136747e0 nid=0x1088 waiting on monitor [0x152bf000..0x152bfdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <48d0178> (a java.util.TaskQueue)
         at java.lang.Object.wait(Object.java:415)
         at java.util.TimerThread.mainLoop(Timer.java:401)
         - locked <48d0178> (a java.util.TaskQueue)
         at java.util.TimerThread.run(Timer.java:380)
    "ExecuteThread: '1' for queue: 'JMSStore<null>.ioThreadPool'" daemon prio=5 tid=0x135ddd60
    nid=0x1080 waiting on monitor [0x1527f000..0x1527fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3a1ecd8> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3a1ecd8> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '0' for queue: 'JMSStore<null>.ioThreadPool'" daemon prio=5 tid=0x136e0c20
    nid=0xdc4 waiting on monitor [0x1523f000..0x1523fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3a1ec58> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3a1ec58> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon prio=5 tid=0x135d5c20
    nid=0x1038 waiting on monitor [0x151ff000..0x151ffdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3a0c830> (a weblogic.jms.backend.BETimerTree)
         at weblogic.jms.backend.BETimerTree.execute(BETimerTree.java:140)
         - locked <3a0c830> (a weblogic.jms.backend.BETimerTree)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
    "ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon prio=5 tid=0x13524de0
    nid=0xd14 waiting on monitor [0x151bf000..0x151bfdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3995660> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3995660> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon prio=5 tid=0x13524ca8
    nid=0x11b0 waiting on monitor [0x1517f000..0x1517fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <39955e0> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <39955e0> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon prio=5 tid=0x13525230
    nid=0xd5c waiting on monitor [0x1513f000..0x1513fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3995560> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3995560> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon prio=5 tid=0x13525a60
    nid=0xc00 waiting on monitor [0x150ff000..0x150ffdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <39954e0> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <39954e0> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "CoreHealthMonitor" daemon prio=5 tid=0x13558ed0 nid=0xbe0 waiting on monitor
    [0x150bf000..0x150bfdbc]
         at java.lang.Thread.sleep(Native Method)
         at weblogic.t3.srvr.CoreHealthMonitorThread.run(CoreHealthMonitorThread.java:114)
    "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x1351f3b8
    nid=0xe0c waiting on monitor [0x1507f000..0x1507fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3536ca8> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3536ca8> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x1351e7f0
    nid=0xb10 waiting on monitor [0x1503f000..0x1503fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3536c28> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3536c28> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x1351dc28
    nid=0xc08 waiting on monitor [0x14fff000..0x14fffdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3536ba8> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3536ba8> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x1351d060
    nid=0x1110 waiting on monitor [0x14fbf000..0x14fbfdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3536b28> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3536b28> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x1351c528
    nid=0x1168 waiting on monitor [0x14f7f000..0x14f7fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3536aa8> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3536aa8> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x1351ba90 nid=0x101c
    waiting on monitor [0x14f3f000..0x14f3fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3536a28> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3536a28> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x1351aff8 nid=0xca8
    waiting on monitor [0x14eff000..0x14effdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <35369a8> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <35369a8> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x1347e1e8 nid=0xd6c
    waiting on monitor [0x14ebf000..0x14ebfdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3536928> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3536928> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x1347d6c8 nid=0x107c
    waiting on monitor [0x14e7f000..0x14e7fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <35368a8> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <35368a8> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x1347cc30 nid=0x1120
    waiting on monitor [0x14e3f000..0x14e3fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3536828> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3536828> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x1346c680 nid=0xdb8
    waiting on monitor [0x14dff000..0x14dffdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <35367a8> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <35367a8> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x13516ca8 nid=0x78
    waiting on monitor [0x14dbf000..0x14dbfdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3536728> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3536728> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x13516ae8 nid=0xc58
    waiting on monitor [0x14d7f000..0x14d7fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <35366a8> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <35366a8> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x13475c88 nid=0xe04
    waiting on monitor [0x14d3f000..0x14d3fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3536628> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3536628> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x13475e38 nid=0xa3c
    waiting on monitor [0x14cff000..0x14cffdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <35365a8> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <35365a8> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'" daemon prio=5
    tid=0x1355acc0 nid=0x12a8 waiting on monitor [0x14cbf000..0x14cbfdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <350df40> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <350df40> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'" daemon prio=5
    tid=0x13468a68 nid=0x1150 waiting on monitor [0x14c7f000..0x14c7fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <350dec0> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <350dec0> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'" daemon prio=5
    tid=0x13468930 nid=0xd20 waiting on monitor [0x14c3f000..0x14c3fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <350de40> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <350de40> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "Thread-5" prio=5 tid=0x135c4d90 nid=0x11cc waiting on monitor [0x14bff000..0x14bffdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3508dc0> (a java.util.TaskQueue)
         at java.util.TimerThread.mainLoop(Timer.java:427)
         - locked <3508dc0> (a java.util.TaskQueue)
         at java.util.TimerThread.run(Timer.java:380)
    "ExecuteThread: '1' for queue: 'DRS'" daemon prio=5 tid=0x1345a408 nid=0x218 waiting
    on monitor [0x14bbf000..0x14bbfdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <350dd08> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <350dd08> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '0' for queue: 'DRS'" daemon prio=5 tid=0x13468c18 nid=0xc88 waiting
    on monitor [0x14b7f000..0x14b7fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <350dc88> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <350dc88> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "Thread-4" prio=5 tid=0x1363da58 nid=0x968 waiting on monitor [0x14b3f000..0x14b3fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3504838> (a weblogic.xml.util.cache.entitycache.StatisticsMonitor)
         at weblogic.xml.util.cache.entitycache.StatisticsMonitor.run(EntityCache.java:1579)
         - locked <3504838> (a weblogic.xml.util.cache.entitycache.StatisticsMonitor)
    "VDE Transaction Processor Thread" prio=2 tid=0x135b29b0 nid=0xd90 waiting on
    monitor [0x14aff000..0x14affdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3375f90> (a com.octetstring.vde.backend.standard.TransactionProcessor)
         at java.lang.Object.wait(Object.java:415)
         at com.octetstring.vde.backend.standard.TransactionProcessor.waitChange(TransactionProcessor.java:306)
         - locked <3375f90> (a com.octetstring.vde.backend.standard.TransactionProcessor)
         at com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionProcessor.java:192)
    "ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x1358aa70
    nid=0x1194 waiting on monitor [0x14abf000..0x14abfdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <314b120> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <314b120> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x134ece18
    nid=0x11c0 waiting on monitor [0x14a7f000..0x14a7fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <314b0a0> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <314b0a0> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x134ec700
    nid=0x8a8 waiting on monitor [0x14a3f000..0x14a3fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <314b020> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <314b020> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x1328ae18
    nid=0x1e0 waiting on monitor [0x149ff000..0x149ffdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <314afa0> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <314afa0> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x1328a2f8
    nid=0x10dc waiting on monitor [0x149bf000..0x149bfdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <314af20> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <314af20> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x13742ab0
    nid=0xd68 waiting on monitor [0x1497f000..0x1497fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <314aea0> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <314aea0> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x13296cc8
    nid=0x7dc waiting on monitor [0x1493f000..0x1493fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <314ae20> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <314ae20> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x135a98c0
    nid=0x1084 waiting on monitor [0x148ff000..0x148ffdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <314ada0> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <314ada0> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x1328c548
    nid=0xc48 waiting on monitor [0x148bf000..0x148bfdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <314ad20> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <314ad20> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x136bf818
    nid=0x12a0 waiting on monitor [0x1487f000..0x1487fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <314aca0> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <314aca0> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon prio=5 tid=0x134ee818
    nid=0x108c waiting on monitor [0x1483f000..0x1483fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <31486a0> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <31486a0> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon prio=5 tid=0x1328c410
    nid=0x1070 waiting on monitor [0x147ff000..0x147ffdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3148620> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3148620> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "TimeEventGenerator" daemon prio=5 tid=0x136bfaa0 nid=0xe7c waiting on monitor
    [0x147bf000..0x147bfdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3145058> (a weblogic.time.common.internal.TimeTable)
         at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
         - locked <3145058> (a weblogic.time.common.internal.TimeTable)
         at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:139)
         at java.lang.Thread.run(Thread.java:479)
    "ExecuteThread: '1' for queue: '_weblogic_dgc_queue'" daemon prio=5 tid=0x135f5498
    nid=0x1134 waiting on monitor [0x1477f000..0x1477fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <31484e8> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <31484e8> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '0' for queue: '_weblogic_dgc_queue'" daemon prio=5 tid=0x135f2a90
    nid=0x1158 waiting on monitor [0x1473f000..0x1473fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3148468> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3148468> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "HighPriority TimeEventGenerator" daemon prio=9 tid=0x136c2d10 nid=0xfcc waiting
    on monitor [0x146ff000..0x146ffdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3147378> (a weblogic.time.common.internal.TimeTable)
         at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
         - locked <3147378> (a weblogic.time.common.internal.TimeTable)
         at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:139)
         at java.lang.Thread.run(Thread.java:479)
    "SpinnerRandomSource" daemon prio=5 tid=0x13518d78 nid=0x1074 waiting on monitor
    [0x146bf000..0x146bfdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3147a68> (a java.lang.Object)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:60)
         at java.lang.Thread.run(Thread.java:479)
    "ExecuteThread: '14' for queue: 'default'" daemon prio=5 tid=0x13245968 nid=0x1210
    waiting on monitor [0x1467f000..0x1467fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3148330> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3148330> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '13' for queue: 'default'" daemon prio=5 tid=0x135037c8 nid=0x1128
    waiting on monitor [0x1463f000..0x1463fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <31482b0> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <31482b0> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0x13502c00 nid=0xde8
    waiting for monitor entry [0x145ff000..0x145ffdbc]
         at oracle.jdbc.driver.OracleConnection.prepareStatement(OracleConnection.java:818)
         - waiting to lock <39f68f0> (a oracle.jdbc.driver.OracleConnection)
         at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:191)
         at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:139)
         at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:92)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.prepareStatement(Unknown
    Source)
         at oracle.toplink.queryframework.SQLCall.prepareStatement(Unknown Source)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(Unknown
    Source)
         at oracle.toplink.threetier.ServerSession.executeCall(Unknown Source)
         at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(Unknown
    Source)
         at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(Unknown
    Source)
         at oracle.toplink.internal.queryframework.CallQueryMechanism.selectOneRow(Unknown
    Source)
         at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectOneRowFromTable(Unknown
    Source)
         at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectOneRow(Unknown
    Source)
         at oracle.toplink.queryframework.ReadObjectQuery.execute(Unknown Source)
         at oracle.toplink.queryframework.DatabaseQuery.execute(Unknown Source)
         at oracle.toplink.queryframework.ReadQuery.execute(Unknown Source)
         at oracle.toplink.publicinterface.Session.internalExecuteQuery(Unknown Source)
         at oracle.toplink.threetier.ServerSession.internalExecuteQuery(Unknown Source)
         at oracle.toplink.threetier.ClientSession.internalExecuteQuery(Unknown Source)
         at oracle.toplink.publicinterface.Session.executeQuery(Unknown Source)
         at oracle.toplink.publicinterface.UnitOfWork.internalExecuteQuery(Unknown Source)
         at oracle.toplink.publicinterface.Session.executeQuery(Unknown Source)
         at oracle.toplink.publicinterface.Session.executeQuery(Unknown Source)
         at cygent.service.da.impl.DataAccessImpl.read(DataAccessImpl.java:1674)
         at cygent.service.da.impl.DataAccessImpl.read(DataAccessImpl.java:1635)
         at cygent.service.frame.TaskActivationEventDispatcher.registerListenerTask(TaskActivationEventDispatcher.java:255)
         at cygent.domain.taskManager.state.TaskNewState.schedule(TaskNewState.java:303)
         at cygent.domain.taskManager.state.TaskNewState.activate(TaskNewState.java:243)
         at cygent.domain.taskManager.TaskInstance.activate(TaskInstance.java:331)
         at cygent.service.frame.TaskManagementMessageBeanHelper.activateTask(TaskManagementMessageBeanHelper.java:317)
         at cygent.service.frame.TaskManagementMessageBeanImpl.onMessage(TaskManagementMessageBeanImpl.java:299)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:364)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:298)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:273)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2310)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2233)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
    "ExecuteThread: '11' for queue: 'default'" daemon prio=5 tid=0x1358d630 nid=0x114c
    waiting on monitor [0x145bf000..0x145bfdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <31481b0> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <31481b0> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '10' for queue: 'default'" daemon prio=5 tid=0x1358cab8 nid=0xd30
    waiting on monitor [0x1457f000..0x1457fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3148130> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3148130> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '9' for queue: 'default'" daemon prio=5 tid=0x1324efa8 nid=0xcb4
    waiting on monitor [0x1453f000..0x1453fdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <31480b0> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <31480b0> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '8' for queue: 'default'" daemon prio=5 tid=0x1324ed20 nid=0x10ec
    waiting on monitor [0x144ff000..0x144ffdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3148030> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3148030> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '7' for queue: 'default'" daemon prio=5 tid=0x13549bb8 nid=0x11e4
    waiting on monitor [0x144bf000..0x144bfdbc]
         at java.lang.Object.wait(Native Method)
         - waiting on <3147fb0> (a weblogic.kernel.ExecuteThread)
         at java.lang.Object.wait(Object.java:415)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:146)
         - locked <3147fb0> (a weblogic.kernel.ExecuteThread)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:172)
    "ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x13549930 nid=0x874
    waiting for monitor entry [0x1447f000..0x1447fdbc]
         at oracle.jdbc.driver.OracleConnection.prepareStatement(OracleConnection.java:818)
         - waiting to lock <39f68f0> (a oracle.jdbc

  • Sqldeveloper and multiple homes - how to force it to use included jdbc

    Hello,
    I'm having a hard time to get Sqldev 1.5 working with a WE8MSWIN1252 database on windows system that has also a 10.2.0.3 home installed.
    It looks like it's then not using the own jdbc but the 10.2.0.3 thin jdbc found in the Oracle home - running into bug 4659157 - euro symbol and other 1252 characters have problems .
    Can I enforce Sqldeveloper 1.5 to use the included 11.1.0.6 jdbc drivers?
    Regards,
    Gunther

    Hi -K-,
    I have 2 homes in my machine:
    9i - "C:\oracle\ora92\"
    10 - "C:\oracle\product\10.2.0\client_1\"
    In each tnsnames.ora file in "\network\admin\" dir in each home, set up their services to point to the correct server: where 9i or 10g.
    Now, when I set up, as you said:
    91 echo home
    set ORACLE_HOME = C:\ oracle\ora92\
    start sqldeveloper.exe
    Failed, because when I create a connection of TNS type, it is only see the service tnsnames.ora file located in the home 10.
    Any other suggestions?
    Thank you in advance.

  • JDBC operation throws a NullPointerException

    Hi all...
    It seems that any attempt to perform a jdbc access from a deployed LCA (my process at this point only contains the JDBC 'query multiple to xml' operation) results in the following exception on the LC server (see below). The query and xml generation all seem to work ok from the Workbench. I can mail the lca upon request. Thanks.
    [4/28/08 17:10:15:557 EDT] 00000059 SystemOut O [Flex] [ERROR] Root cause: java.lang.NullPointerException
    at com.adobe.idp.dsc.jdbc.helper.SqlHelper.executeQuery(SqlHelper.java:85)
    at com.adobe.idp.dsc.jdbc.JDBCService.queryMultipleToXml(JDBCService.java:391)
    at sun.reflect.GeneratedMethodAccessor1517.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:181)
    at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:134)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
    at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTr ansactionCMTAdapterBean.java:336)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doSupports(Ej bTransactionCMTAdapterBean.java:212)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EJSLocalStatelessEjbTransactionCMTAdapter_ caf58c4f.doSupports(Unknown Source)
    at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:104)
    at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
    at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
    at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:88)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
    at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:113)
    at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:102)
    at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:88)
    at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:21 0)
    at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:57)
    at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
    at com.adobe.idp.taskmanager.dsc.service.TaskManagerServiceImpl.renderForm(TaskManagerServic eImpl.java:3404)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:181)
    at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:134)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:44)
    at com.adobe.idp.dsc.trans

    I don't see any blank values anywhere. I have a single 'Assign Task' operation with the following config. I can send an lca if you like.
    Initial User = 'Assign to Process Creator'
    Form Data Mappings => input form variable = /process_data/myXFAForm
    output form var = /process_data/myXFAForm
    myXFAForm has as its Render Service/Operation = JdbService/queryMultipleToXml with the following settings:
    datasourceName(literal)= IDP_DS
    sql_info(literal)= select FIRST_NAME, LAST_NAME, CONTACT_INFO, ORACLE_USERID from TVS_TVAS_USER where STATUS='ACTIVE'
    xml_info (literal) = root: tvasUsers; element: User; mapping: [{element_name=firstname, column_index=1, column_name=FIRST_NAME}, {element_name=lastname, column_index=2, column_name=LAST_NAME}, {element_name=emailAddress, column_index=3, column_name=CONTACT_INFO}, {element_name=tvasUserID, column_index=4, column_name=ORACLE_USERID}]
    service output settings:
    document=task/Document

  • Map including spliting operation dosen't work in MDM Import Server

    Hi All,
    I met a problem with MDM Import Server when using a map file with spliting operation in it, although I can use it in MDM import manager to load data successfully. The error in log file is like this:
    Record Matching...
    Importing Lookup...
    One or more attribute values are invalid.
    One or more attribute values are invalid.
    One or more attribute values are invalid.
    One or more attribute values are invalid.
    Import Failed!
    The spliting in my map is: I split field "Category" into category1 and category2 with space " ". e.g. value "Trousers M" is splitted into "Trousers" and "M"  . Then I map category1 to category and category2 to size.
    I tried to delete this spliting and just map "Category" to "Category" then it works well for Import Server.
    Is it the bug of MDM import server? can anyone give me a explaination?
    Thanks! Bin

    Under Configuration Options of the Import Manager,
    check the values for
    <b>Default Batch Handling</b>
    AutoMap Unmapped Values = Yes
    Unmapped value Handling = Add/Ignore/Fail.
    Set the values according to your needs.
    Make sure that the data source is updatable as well.

  • Deleted all content on my xperia. Including the operating system. Now its 'dead'

    I unlocked my bootloader and install Cyanogenmod. I realized that i wanted to go back to the normal xperia experience. When i wanted to delete cyanogenmod and install the original software but i deleted some wrong files and now my phone is dead. I cant turn it on the screen stays black but my led at the top still light when i but in the charger.
    - Frederik
    Xperia Z1

    Just follow all the steps given in the link:
    Copy the Customization.ini file. You find it in the Flash_tool_for_Xperia_X.zip.
    Paste the Customization.ini file into the installation folder. The installation folder is the folder named Emma in the installation path examples on point 3.1 and 3.2 above
    All we have to decide is what to do with the time that is given to us - J.R.R. Tolkien

  • JDBC and Hung Update Operations

    Hi,
    I am learning JDBC interface in Java with Oracle database and have noticed a strange problem when I perform simple update (i.e. insert) operation (using bind variable of PreparedStatement).
    I am currently running Oracle database version 9.2.0.1.0 on Solaris 10 with my client program running on JVM Sun 1.5 with JDBC ojdbc5_g.jar. The database instance runs on Solaris OS and the JDBC thin driver is run on either Windows or Linux in an internal LAN network (using TCP). I can connect and perform queries from my JDBC code just fine; I can also perform the usual operation from SQL*Plus on my database hosting machine as well as remotely on the machines that I run the JDBC code using SQL*Plus client.
    Now, if the JDBC code attempts to perform a modification operation AND any a user connected to the database through SQL*Plus also performs some sort of update operation on the "same" table that the JDBC code is trying to modify, then the JDBC code hangs. The two operations are being performed at various times. Just to give you a scenario in which the code does or does not become responsive:
    If I login via SQL*Plus and connect to the database but perform solely "select" statements on my designated table, and run the JDBC updating code, everything works fine. The insert is done accordingly even in the subsequent updates via JDBC as long as the SQL*Plus user performs only "select" queries.
    As soon as I perform a modification operation (i.e. delete the inserted row by the JDBC code) in SQL*Plus, any subsequent attempts to, let's say insert a row, by the JDBC code would result in an operation to hang (just to note, I can acquire the connection in this scenario but the actual execution of operation from JDBC hangs, no response) -- even if I wait half an hour and run my JDBC program, the operation hangs.
    The strange thing is, to remedy this, a user that has performed some sort of modification operation on the table via SQL*Plus has to "disconnect" from the database. As soon as the SQL*Plus user disconnects, the JDBC operation goes through and program successfully performs the update
    By the way, I am also utilizing DataSource in my code (without JNDI) to establish connections but I've tried the DriverManager in my code with the same result. One last remark is that the isolation level has been set to READ COMMITTED if that has anything to do with it (but the thing is neither of updating operations from JDBC or SQL*Plus are being done at the same time -- as I've mentioned, I even waited a few minutes between each run). Perhaps, the SQL*Plus holds a luck on the rows of the table for some reason and once the user disconnects, the JDBC program goes through shrug
    Any hint would be appreciated.

    The issue is that by default, a SQL-PLUS session operates in
    'autocommit false' mode, so when you do any sort of update,
    your SQL-PLUS session has a transaction and will hold an
    exclusive lock on anything you've updated, until you commit,
    or disconnect. The JDBC session, or any second separate
    concurrent SQL-PLUS session will also be blocked.
    Joe Weinstein at BEA Systems

  • Need help understanding service, repair, operating system reinstall

    I bought a Thinkpad X1 Carbon 3443 laptop on the black friday sale in November 2013. Due to demand, the unit didn't ship until after Christmas. I didn't complain, but Lenovo offered a 5% rebate for my troubles. Still waiting on that to be processed.I've had all the documented problems with the Intel 6205 wireless card that are all over the forums. I finally upgraded my router just to resolve the issue.In March of 2015, after the warranty expired, one of the hinges broke. I took it to an authorized repair facility and was told (after 4 weeks) the part was no longer available. I called the service center listed on the website. They offered to ship me a box so I could send them the laptop for evaluation. Since it was out of warranty I would have to pay for any repairs.After two weeks, they sent the laptop back. They never contacted me during the process. I didn't get any quotes on the cost, nor did I authorize any work. They say they fixed the laptop. I can see the hinge is physically fixed. However, I cannot start the laptop. They wiped all my data, including the operating system. I have all my files backed up,  but since this laptop does not have a CD or DVD drive, I don't have a way to reinstall the OS, which is Windows 8.1.Also, today, I received an invoice, saying they charged my credit card for what is almost the cost of a new machine. Lesson learned, never give the Chinese your credit card. So, my question, is there any way I can reinstall Windows 8.1? I don't have it on a disk or any hardware. It was shipped with the laptop at purchase. Service deleted it, so I don't have a copy at all. Also, don't be like me. Buy something else.

    After looking at the Telus specific software download page (in North American menu) I noticed that there is a link for the 4.5 version and the 4.3 that I have.  I guess 4.5 is available there then.  I might give Telus a quick call and see if they know anything about it.  More then likely not.  The tech support people tend to be ill informed on anything detailed such as this.
    thanks again

  • AdHoc Set Query - set operations - practical use

    Hi
    I am writing a user manual about AdHoc Query - including Set operations. I am looking for good examples when to use the different operations.  A-B is easy.  Example - 'give me all employees that are not on maternity leave'.  But I am struggling with good practical examples on when to use Union and Intersection.  It needs to be examples that cannot be covered by selection criteria in one single query.
    Does anyone have any good practical examples?  Any help appreciated.
    Kirsten

    Hi Kirsten,
    I use Set Operations many times to find individuals who do not have a certain infotype or plan.  Example:  Find all retirees who are not enrolled in a medical plan.  Group A = All retirees;
    Group B = All retirees in a medical plan.  A - B = Retirees with no medical plan coverage. 
    Ad Hoc Query does not allow you to use "Or" logic in selection with different criteria.  A Union could be used for this.  An example would be employees who are in pay Grade 1 - 5 (Group A) or earn less than $50,000 per year (Group B).  Intersection would be those in Grades 1 - 5 and earn less than $50,000 per year. 
    Paul

  • Upgraded to R12 and Operating Unit Error is coming

    We have upgraded to R12. As per the metalink note 259546.1 we have applied a patch to create a non usable operating system as we are not using any of the financial modules.
    But now when I am trying to open "Create Timesheet Screen" it gives the following error.
    "java.sql.SQLException: ORA-20001: SQL_PLSQL_ERROR: N, ROUTINE, MO_GLOBAL.INIT, N, ERRNO, -20001, N, REASON, ORA-20001: APP-FND-02901: You do not have access privilege to any operating unit. Please check if your profile option MO: Security Profile includes any operating unit or the profile option MO: Operating Unit is set.
    I checked the profile option MO:Operating Unit, which is assigned by the the patch that I applied for creation of non-usable operating system.
    Any one faced some similar issues

    Additional Info
    I have set only MO: Operating Unit profile and not MO: Security Profile

  • Delete COPA characteristics which not used in any operating concern

    Hello SAP experts,
    Please advise me on how to delete PA characteristic "WW001" created by mistake that we are hoping to delete if possible. However, when attempting to delete in KEA5, the error log appear as
    Data element RKEG_WW001 is used in these table/view
    CACS_S_COND_MA
    JVKOMP
    KOMG
    KOMGF
    KOMGFNEW
    KOMGFOLD
    KOMP
    KOMPAKE
    STR_KOMG
    TRCON_IT_KOMP
    WB2_EKOMP
    And does not allow the deletion
    WW001 have already been delete from the operating concerns.
    Please shed some light on how to do this?
    Thanks in advance for your help
    Yang

    Hi,
    In order to delete a characteristic you should perform                    
    the following activities:                                                                               
    1. Delete the corresponding characteristics and value fields from         
    Customizing in all clients (this includes forms, reports, planning        
    layouts, and so forth). To locate characteristics and value fields, use   
    the appropriate where-used list in the Customizing Monitor. You can       
    access it by choosing Tools -> Analysis -> Check Customizing Settings     
    (TA KECM).                                                                
    You can jump directly from the where-used list to the relevant            
    Customizing transaction and then delete the appropriate field there.      
    2. Switch to the screen for maintaining the data structure of an          
    operating concern (Maintain operating concern).                           
    3. If you need to effect other changes to the datastucture for the        
    operating concern before making any deletions, effect those changes and   
    save the data structure.                                                  
    4. In order to be able to select the fields of the data structure,        
    choose Extras -> Characteristics (or Value fields) -> Unlock.             
    5. Select the characteristics and value fields to be deleted and remove   
    them from the data structure with the "Reset fields" function.            
    6. Reactivate the operating concern. The system starts by checking        
    whether the operating concern contains any data and whether the fields    
    to be deleted are still being used in any Customizing settings.           
    7. If none of the fields are still in use, the system then starts the     
    re-activation. If the operating concern does not contain any data or      
    does not require the database system to be converted, the tables are      
    activated. You are then able to activate the environment for the          
    operating concern. In this case, the following activities no longer       
    apply.                                                                    
    If the operating concern already contains data, a system message tells    
    you that the database needs to be converted. If you proceed, an           
    activation log appears (at the top of the list).                          
    8. Analyze the activation log. If it only contains error messages         
    telling you to convert the tables, proceed with the next activity.        
    You must otherwise remove the cause of the errors before the tables can   
    be converted. In this case, you should answer "No" to the next prompt,    
    which asks whether the conversion transaction should start.               
    9. If you still only receive error messages telling you to convert the    
    tables, choose "Back" and start the conversion.                                      
    10. Plan a job for the conversion. A list of the tables to be converted              
    is shown for this. If the tables only contain a small amount of data                 
    (less than 10 000 records), then all the tables can be converted in one              
    job. In that case, you can select all the tables.                                    
    For larger tables, conversion should take place in several jobs.                     
    However, you should ensure that table CE4xxxx (where xxxx = operating                
    concern) is the last table to be converted.                                          
    Warning. No other changes can be made to the operating concern during                
    the conversion.                                                                      
    A copy of the table is generated during the conversion. The database                 
    system should have sufficient memory available for this copy.                        
    To schedule conversion as a job, use the "Schedule selections" function.             
    You can display the current status of the conversion by selecting the                
    "Refresh" icon. Tables disappear from the list once they have been                   
    converted sucessfully. If a conversion is taking a while, it is also                 
    possible to leave the transaction. You can then continue the conversion              
    using DB requests -> Mass processing in one of the following ways:                   
    With the job overview. You access this by choosing System -> Services ->  Jobs.                                                                               
    Using the database utility transaction. You access this by choosing                  
    Utilities -> Database Utility in the ABAP Dictionary menu.                           
    You can use the status function to call up the status of the operating               
    concern during operating concern maintenance. You need to activate all  tables after conversion.                                                             
    11. To analyze errors that have occurred during the conversion, you can  use the database utility transaction by choosing Extras -> Logs. The log             
    has the same name as the conversion job: TBATG-date. You can also  restart the conversion with this transaction.                                        
    For more information on the database utility, choose Help -> Application           
    help while still in the above transaction.                                           
    12. Once you have activated all the tables in the operating concern,                 
    generate the operating concern environment from within operating concern maintenance.                                                                         
    You can then use the operating concern again.                                        
    Please, refer to the IMG documentation under Controlling ->                          
    Profitability Analysis -> Structures -> Define operating concern                     
    -> Maintain operating concern, for further details.                                                                               
    It is not possible to transport information about 'deleting of             
    characteristics (value fields)' with transaction KE3I. Only                          
    characteristics and value fields included in operating concern (to be                
    transported) are transported with KE3I. Deleted characteristics and                  
    value fields are ignored. You have to delete these characteristics and               
    value fields manually in each system.    
    Best regards,
    Maria Luisa

  • JDBC thin and thick clients

    What is the difference between JDBC thin and JDBC thick clients and their usage ?

    hi,
    in sort tearms,
    Oracle has a thin client driver which mean you can connect to a oracle database without the Oracle client installed on your machine.
    Thick client would need the Oracle Client database drivers etc.. Drivers include JDBC-ODBC bridge drivers JDBC drivers depending on tns resolution.
    thanks

Maybe you are looking for