DB2 type 2 driver blocking WLS 8.1 SP2 on startup

Hi,
I use DB2 type 2 driver with WLS 8.1 SP2 and did configure a jdbc connection pool as described in edocs. But when I start the server and the server tries to deploy the jdbc connection pool, the server hangs. I took some thread dumps and the thread to load the driver seems to be stuck, as it always shows the same stack trace.
Did anybody manage to use this driver? Any suggestions?
Thanks,
Nicole
"Thread-1" id: 0x0x00000380 prio: 5 ACTIVE, NONDAEMON, GCABLE thread: 0x0xaf028500 lastj: 0x0xbfff8e74 at COM.ibm.db2.jdbc.app.DB2Driver.SQLAllocEnv(Native Method)@0xa026894e at COM.ibm.db2.jdbc.app.DB2Driver.<init>(Unknown Source)@0xa0268456 at java.lang.Class.newInstanceCached(Unknown Source)@0xa6e3e533 at weblogic.jdbc.common.internal.ConnectionEnvFactory.loadDriver(ConnectionEnvFactory.java:46)@0xa0e5e9d2 at weblogic.jdbc.common.internal.ConnectionEnvFactory.<init>(ConnectionEnvFactory.java:79)@0xa0e5e819 at weblogic.jdbc.common.internal.ConnectionPool.initPooledResourceFactory(ConnectionPool.java:514)@0xa0e5e298 at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:165)@0xa0e5d2d3 at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:880)@0xa0e59bf2 at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:133)@0xa0e59994 at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:291)@0xa0e58aa2 at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:178)@0xa0e58709 at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)@0xa0e572a1 at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:590)@0xa0e56e36 at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:568)@0xa0e56649 at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:240)@0xa0e56424 at COM.jrockit.reflect.NativeMethodInvoker.invoke0(Native Method)@0xa6de9752 at COM.jrockit.reflect.NativeMethodInvoker.invoke(Unknown Source)@0xa6de987c at COM.jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)@0xa5d989f4 at java.lang.reflect.Method.invoke(Unknown Source)@0xa6de938d at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)@0xa4911d6c at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)@0xa491196d at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:476)@0xa4910de7 at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)@0xa49109d7 at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)@0xa49103f4 at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)@0xa4910399 at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)@0xa4910276 at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)@0xa3623f4f at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)@0xa4d5d048 at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7271)@0xa0e56285 at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1210)@0xa0e5608e at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:362)@0xa0e55cca at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)@0xa0e55baa at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)@0xa177839b at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)@0xa1777f3e at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)@0xa6520534 at weblogic.Server.main(Server.java:32)@0xa65200a3 --- End of stack trace

Sorry, it is running now. There was a misspelling in the environment variable DB2INSTANCE and therefore the requested instance was not reachable. Still interesting, that this can even prevent the server from booting. Now that I corrected the variable in the environment, everything is fine.
Thanks,
Nicole

Similar Messages

Problem with DB2 Type 4 driver

Hi
The problem has been narrowed down to a problem with the IBM DB2 Type 4
driver (COM.ibm.db2.jdbc.net.DB2Driver). In some situations, it introduces a
100ms delay when sending parameters for a prepared statement (846 bytes in
the truss trace below). With the IBM app driver (type 2) we get the
performance that we expect.
In other words, this has to do with TCP/IP communication and whether this is
a JVM, DB2 or Solaris issue we don't know. Probably a combination.
Regards
Steffen Jensen
Nordija
Below, the Solaris truss trace that shows how the JDBC driver (in the WLS
VM) sends data and how the DB2 listener process receives it.
WLS
24092: 5.6607 send(7, "\001\0\003 N", 6, 0) = 6
24092: 5.6611 send(7, "\0 O\001\004\001FFE7FFFB".., 846, 0) = 846
24092: 5.6682 poll(0xFEC07A50, 0, 10) = 0
24092: 5.6882 poll(0xFEC07A50, 0, 10) = 0
24092: 5.7082 poll(0xFEC07A50, 0, 10) = 0
24092: 5.7282 poll(0xFEC07A50, 0, 10) = 0
24092: 5.7482 poll(0xFEC07A50, 0, 10) = 0
24092: 5.7625 read(7, "\0", 1) = 1
DB2 listener
24109: 5,6607 recv(5, "\001", 2, 0) = 2
24109: 5,6617 recv(5, "\0\003 N", 4, 0) = 4
24109: 5,7583 recv(5, "\0 O\001\004\001FFE7FFFB".., 846, 0) = 846
24109: 5,7606 semop(2883608, 0xFFBED4C0, 1) = 0
24109: semnum=0 semop=1 semflg=0
24109: 5,7618 semop(2883608, 0xFFBED5C0, 1) = 0
24109: semnum=1 semop=-1 semflg=0

Hi
The problem has been narrowed down to a problem with the IBM DB2 Type 4
driver (COM.ibm.db2.jdbc.net.DB2Driver). In some situations, it introduces a
100ms delay when sending parameters for a prepared statement (846 bytes in
the truss trace below). With the IBM app driver (type 2) we get the
performance that we expect.
In other words, this has to do with TCP/IP communication and whether this is
a JVM, DB2 or Solaris issue we don't know. Probably a combination.
Regards
Steffen Jensen
Nordija
Below, the Solaris truss trace that shows how the JDBC driver (in the WLS
VM) sends data and how the DB2 listener process receives it.
WLS
24092: 5.6607 send(7, "\001\0\003 N", 6, 0) = 6
24092: 5.6611 send(7, "\0 O\001\004\001FFE7FFFB".., 846, 0) = 846
24092: 5.6682 poll(0xFEC07A50, 0, 10) = 0
24092: 5.6882 poll(0xFEC07A50, 0, 10) = 0
24092: 5.7082 poll(0xFEC07A50, 0, 10) = 0
24092: 5.7282 poll(0xFEC07A50, 0, 10) = 0
24092: 5.7482 poll(0xFEC07A50, 0, 10) = 0
24092: 5.7625 read(7, "\0", 1) = 1
DB2 listener
24109: 5,6607 recv(5, "\001", 2, 0) = 2
24109: 5,6617 recv(5, "\0\003 N", 4, 0) = 4
24109: 5,7583 recv(5, "\0 O\001\004\001FFE7FFFB".., 846, 0) = 846
24109: 5,7606 semop(2883608, 0xFFBED4C0, 1) = 0
24109: semnum=0 semop=1 semflg=0
24109: 5,7618 semop(2883608, 0xFFBED5C0, 1) = 0
24109: semnum=1 semop=-1 semflg=0

Microsoft SQL Server JDBC driver and WLS JMS problem?

          Greetings,
          I'm using the Microsoft SQL Server JDBC driver with WLS with JMS
          persisted to SQL Server, during WLS startup the JMS attempts to
          read the JMSStore and JMSState tables in the db, if they are
          already present (say, from a previous run) the driver kicks out:
          java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
          not re-read row data for column 1.
          If the tables are not present, then WLS creates them and
          everything proceeds fine. Now, its not a good thing to attempt
          to reread row data for a ResultSet, especially for portability. Why is WLS JMS
          doing this? is there some config I can use to adjust JMS startup behavior for
          persisted JMS stores?
          Jay Houghton
          Centiv
          [email protected]
          long exception trace follows:
          <Oct 1, 2002 8:29:11 AM EDT> <Info> <JMS> <User connection factory "BroadcastTopicFactory"
          is started.>
          <Oct 1, 2002 8:29:18 AM EDT> <Info> <JMS> <JMSServer "EnergizerJMSServer", Opening
          JDBC store tables "JMSStore
          " and "JMSState" using connection pool "JMSConnectionPool".>
          <Oct 1, 2002 8:29:20 AM EDT> <Alert> <JMS> <JMSServer "EnergizerJMSServer", store
          failed to open, java.io.IOEx
          ception: JMS JDBC store, connection pool = <JMSConnectionPool>, prefix = <null>:
          recover
          java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
          not re-read row data for colum
          n 1.
          at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
          at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:618)
          at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:728)
          at weblogic.jms.store.JMSStore.recover(JMSStore.java:112)
          at weblogic.jms.backend.BEStore.open(BEStore.java:179)
          at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:330)
          at weblogic.jms.JMSService.createBackEnd(JMSService.java:923)
          at weblogic.jms.JMSService.addJMSServer(JMSService.java:1277)
          at weblogic.jms.JMSService.addDeployment(JMSService.java:1174)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:23
          3)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          at $Proxy40.updateDeployments(Unknown Source)
          at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub
          .java:2734)
          at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:362
          at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:154)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          at $Proxy57.start(Unknown Source)
          at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean
          _CachingStub.java:480)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
          at weblogic.management.Admin.finish(Admin.java:571)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:508)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
          at weblogic.Server.main(Server.java:35)


          Tom,
          thanks for the info, I'll bring this to support.
          I did try the weblogic jDriver for SQL Server and it works fine, so i think it
          must be the way JMS is interacting with the MS driver.
          here are my components:
          WLS 6.1sp1
          Microsoft® SQL Server™ 2000 Driver for JDBC™ is a (Type 4 JDBC) which provides
          partial JDBC 2 support (no blobs, clobs, etc)
          MS SQL Server 2000 (sp2?)
          thanks!
          Jay Houghton
          [email protected]
          Tom Barnes <[email protected]> wrote:
          >Hi Jay,
          >
          >This is not a known issue at BEA as far as I know, perhaps it is the
          >result
          >of a new driver/database combination. Try using a different driver,
          >or a different
          >version of the current driver. Meanwhile, use a file store (just as
          >reliable but faster) and log a case with customer support, including
          >information on your version, service-pack, and what driver you are using.
          >
          >Tom, BEA
          >
          >Jay Houghton wrote:
          >
          >> Greetings,
          >>
          >> I'm using the Microsoft SQL Server JDBC driver with WLS with JMS
          >> persisted to SQL Server, during WLS startup the JMS attempts to
          >> read the JMSStore and JMSState tables in the db, if they are
          >> already present (say, from a previous run) the driver kicks out:
          >>
          >> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet
          >can
          >> not re-read row data for column 1.
          >>
          >> If the tables are not present, then WLS creates them and
          >> everything proceeds fine. Now, its not a good thing to attempt
          >> to reread row data for a ResultSet, especially for portability. Why
          >is WLS JMS
          >> doing this? is there some config I can use to adjust JMS startup behavior
          >for
          >> persisted JMS stores?
          >>
          >> Jay Houghton
          >> Centiv
          >> [email protected]
          >>
          >> long exception trace follows:
          >>
          >> <Oct 1, 2002 8:29:11 AM EDT> <Info> <JMS> <User connection factory
          >"BroadcastTopicFactory"
          >> is started.>
          >> <Oct 1, 2002 8:29:18 AM EDT> <Info> <JMS> <JMSServer "EnergizerJMSServer",
          >Opening
          >> JDBC store tables "JMSStore
          >> " and "JMSState" using connection pool "JMSConnectionPool".>
          >> <Oct 1, 2002 8:29:20 AM EDT> <Alert> <JMS> <JMSServer "EnergizerJMSServer",
          >store
          >> failed to open, java.io.IOEx
          >> ception: JMS JDBC store, connection pool = <JMSConnectionPool>, prefix
          >= <null>:
          >> recover
          >> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet
          >can
          >> not re-read row data for colum
          >> n 1.
          >> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          >> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          >> at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
          >> at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:618)
          >> at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:728)
          >> at weblogic.jms.store.JMSStore.recover(JMSStore.java:112)
          >> at weblogic.jms.backend.BEStore.open(BEStore.java:179)
          >> at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:330)
          >> at weblogic.jms.JMSService.createBackEnd(JMSService.java:923)
          >> at weblogic.jms.JMSService.addJMSServer(JMSService.java:1277)
          >> at weblogic.jms.JMSService.addDeployment(JMSService.java:1174)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:23
          >> 3)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
          >> at java.lang.reflect.Method.invoke(Native Method)
          >> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          >> at $Proxy40.updateDeployments(Unknown Source)
          >> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub
          >> java:2734)
          >> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:362
          >> )
          >> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:154)
          >> at java.lang.reflect.Method.invoke(Native Method)
          >> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          >> at $Proxy57.start(Unknown Source)
          >> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean
          >> _CachingStub.java:480)
          >> at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
          >> at weblogic.management.Admin.finish(Admin.java:571)
          >> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:508)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
          >> at weblogic.Server.main(Server.java:35)
          >

Error in configuring Oracle OCI Driver in WLS

My application uses Oracle OCI driver for making JDBC connection from the server application.I have installed Oracle client in the machine.Added the Oracle Bin directory to System Path.But when i try to create the connection Pool Weblogic throws the error saying DLL file is not found in System.Library.Path.Can you help in solving this problem,Config detailsOS - Windows 2000 ProfessionalWeblogic 5.1 serverOracle 8.1.7 clientDriver used Oracle OCI driver...Expecting a reply

You need to set your path to point to the <wls-install-home>/bin/oci8xx_x/
folder as well. I dont think 5.1 supports 817 type 2 driver, you may have to
use the thin driver from oracle instead.
sree
"Varadharajan" <[email protected]> wrote in message
news:3b8f070f$[email protected]..
My application uses Oracle OCI driver for making JDBC connection from theserver application.I have installed Oracle client in the machine.Added the
Oracle Bin directory to System Path.But when i try to create the connection
Pool Weblogic throws the error saying DLL file is not found in
System.Library.Path.Can you help in solving this problem,Config detailsOS -
Windows 2000 ProfessionalWeblogic 5.1 serverOracle 8.1.7 clientDriver used
Oracle OCI driver...Expecting a reply

Z/os db2 (type 2) transaction isolation from rr to cs, general questions

Let me preface this by saying I'm pretty uninformed when it comes to database transaction isolation and what it really means to my application. I've done some homework on the differences between the read committed (cs) and repeatable read (rs) but still a little fuzzy.
App stats: Mainframe z/os db2 v8 (type 2 driver), WAS 6.0.x.x The app runs with about 80000 concurrent users (using about 150-200 JDBC connections in the pool).
I found this which held some good information: http://forum.java.sun.com/thread.jspa?forumID=48&threadID=586570 but it leaves me with some questions still.
Our Mainframe dba is saying he sees a lot of locking (not dead locks, just locks) and it is eating up the MIPS. He told us to set our transaction isolation level to cs to reduce the locking db2 does. But I don't know enough about this to make a good decision. The general consenus I've gotten from various forums (spring, hibernate) is that using CS will cause more problems than it will fix.
The only sql error I see in our logs is due to an insert or update to a FK being invalid. I suppose this could cause some locking problems but would this cause deadlocks?
If anyone can provide some links to explain this, I'd be really appreciative. Or if you have any first hand knowledge -- even better.
Thanks for your time.

I am also not an expert and haven't used DB/2 on z/OS but am using it on OS/400. I think your DBA is confused.
From what I have experienced setting commit control to CS causes more locking than RS. From what I can determine (which has been through trial and error so it may not be totally accurate) CS causes the database to exclusive lock all records in the cursor while RS will use shared locks. I do know from painful experience that if you set all your transactions to CS you will experience frequent update problems due to record locks. We had to go through and set everything to RS and, once we did, our concurrency problems were nearly eliminated. There are some instances that you have to use *CS, however, such as when a stored procedure returns a cursor, but the compiler will tell you about this.
Another thing that doesn't make sense is locks are typically implemented as data structures in memory and do not require much if any processor time. I don't know the specifics of DB/2 implementation but Oracle uses simple semaphores, so I would assume IBM does, too.
Also, from my experience, there appears to be no way around DB/2 locking. Having come from an Oracle background I find the amount of locking DB/2 does totally frustrating. It's not as bad as SQL Server but can become problematic at times. That is just my $.02 anyway.

BLOBs in DB2 using DataDirect Driver

I am using DataDirect JDBC Type-4 driver to connect to DB2. I have requirement to store large serialized java
objects. For that initially I used BLOB type but when I call
PreparedStatement.setBinarystream(colNo, inputStream, SerObjLength)
I get an error saying: VALUE OF INPUT HOST VARIABLE NUM {0} NOT USED; WRONG DATA TYPE.
As per DataDirect, they don't support BLOBs because DRDA restrictions(??). So I tried with CLOB. Now inserting
is fine but when I retirve data using ObjectInputStream.readObject() I get error: java.io.InvalidClassException:
java.util.Properties; Local class not compatible: stream classdesc serialVersionUID=4112578634029874751
local class serialVersionUID=4112578634029874840.
Now my question is, can we use CLOB for storing serialized
objects? If not, what data type I can use for this to work or what are the other solutions.
Any help on this is highly appreciated!!
thanks in advance,
dw

i have the same problem. when i try to insert a binary on a blob colum says:
"LOB col cannnot be selected by DRDA "
(?????? help!). what does it means ?
when i used other drivers (hit db2) tell the same message. what is the problem with db2?? anyone ?
anyone has a example that insert a blob in a blob colum with sucess in db2 ??
thanks

"uses a file type that is blocked from opening in this version" error message when opening a *.doc file with Word already running

Several customers running different versions of Office 2011 (14.4.1-14.4.5) on OSX varying from 10.7.5 to 10.9.5, running on various kinds of hardware (iMac/MacBook Pro/MacBook Air) of various ages are having issues opening *.doc files if the Word is already open. The error message that gets displayed is, "XXXX.doc uses a file type that is blocked from opening in this version"
When the customer tries to open the same file via File-Open, she gets "The file is locked for editing. you can open the file as read-only".
When trying to do so, she gets "Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters".
If Word gets Force-quit, the same document opens without any problems.
1. Repairing Disk permissions was ran several times. and the volume was found to be OK.
2. I have noticed that in this scenario either deleting the normal.dotm or com.microsoft.word.plist (~/Library/Preferences) sometimes resolves the issue, sometimes it doesn’t. There is no pattern to follow. All versions of Office are affected, the fully updated and the non-updated ones.
3. I have tried completely removing the suite using Office 2011 Uninstall.app and/or Remove Office 2011 Uninstaller.pkg, then going through customer's library and manually removing all the Office references.
4. None of these systems had Office 2008 in the past.
Any help will be greatly appreciated.

Reboot both the Mac and the server. Word opens .DOC files and Excel opens .XLS files. As you have found out by copying the files to the computer. It is the connection between the 2 computer that is causing the error.

Problem to create data source with OCI type of driver

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

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

Jdbc connectivity using type 4 driver using oracle10g

Hi while running a jdbc program using type 4 driver using oracle 10 g I am Getting following exception
java.lang.NullPointerException
java.lang.NullPointerException
at Type4ConnectTest.main(Type4ConnectTest.java:31)
Exception in thread "main" java.lang.ClassNotFoundException: oracle.jdbc.driver.
OracleDriver
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at Type4ConnectTest.main(Type4ConnectTest.java:15)
My Program Code is..
import java.sql.*;
class Type4ConnectTest
public static void main(String args[])throws Exception
Connection con=null;
Statement st=null;
ResultSet rs=null;
try
// DriverManager.registerDriver(new Oracle:jdbc:OracleDriver());
Class.forName("oracle.jdbc.OracleDriver");
String url="jdbcracle:thin:@localhost:1521";
con=DriverManager.getConnection(url,"sarika","sarika");
catch(NullPointerException e)
System.out.println("e");
e.printStackTrace();
finally
try
con.close();
st.close();
rs.close();
catch(Exception e)
System.out.println(e);
e.printStackTrace();
I also set path of ojdbc14.jar and orai18n.jar in environment variable.
pls help to solve the problem

Class.forName("SOME_DRIVER_CLASS");Is tricky to use because it will compile not needing to reference the vendors jar file.
You have to remember to deploy it though where ever you plan to run this program.
If you are running from command line
java -cp PATH_TO_JAR Type4ConnectTest

What type of drive is in my MBP?

Hi Forum,
Can anyone tell me what type of drive i have in my Spetember 2007 MBP? I have a new drive and need to get an encasement for the old one ot use as external drive.
A quick read tells me a SATA drive. Do i need a SATA case? can this case have both USB and FW if i find such an encasement?
or have i got it wrong?

Hi,
your MacBook Pro has a SATA-connection for the harddisk.
But since you already have the new drive I just hope you got the correct one !
MacSales has some real nice enclosures for the 2.5" harddisk of your MBP with USB and Firewire if you want.
http://eshop.macsales.com/shop/firewire/
Regards
Stefan

Transfer of stock from Returns stock type to Unrestricted/Blocked

Hi,Friends
How to transfer of stock from Returns stock type to Unrestricted/Blocked
what movement type will trigger by transfering this stock,
Thanks & Regards
Krishna

Hi,
use MB1B Mvt Type 453 returns to unrestricted
Unrestriced to Blocked stock use - 344
Thanks & Regards,
kiran

Touch driver blocked due to failed logo requirements

I have the HP Envy m6 Win8 laptop which is not a touch screen laptop. My laptop, sinc January, has been repeatedly freezing requiring hard restarts. I have taken it into GeekSquad 4 times now and had the motherboard replaced, my hard drive replaced, and
my drivers updated. However, it's still having issues. I looked at the failed event log and this is what it says:
Source: win32k
event ID: 266
General: Touch driver blocked due to failed logo requirements
There's also another one that says:
Source: PrintService
event ID: 215
General: Installing printer driver- failed, error code 0xBC8, HRESULT 0x80070BC8. See the event user data for context information.
At the same exact time as event 215, this one occurs as well:
Source: PrintService
event ID: 370
General: The print spooler failed to regenerate the printer driver information for driver Microsoft enhanced Point and Print compatibility driver for environment Windows x64. Win32 system error code 3016 (0xbc8). This can occur after an operating system
upgrade or because of data loss on the hard drive.
I can't find anything on the web to fix this issue. My husband is a comm guy who works on computers all the time and can't figure it out. GeekSquad has had my laptop for (total) a month and can't figure it out. Any insight would be much appreciated! I just
want my computer (which is only 8 months old) to stop freezing! :(

I've the same problem also. I'm using acer ravo. problem is the pc just lost connection to display/monitor without any reason after being left for some hours and wont wake up..the only thing to reestablish the display/monitor is by hard restart.
Pls help

IBM DB2 JDBC Universal Driver

Hello,
On page 36 of the DF XI3.0 Installation Guide, there is a link for the IBM DB2 JDBC Universal Driver. When I click on this link I get the following error:
Downloads Message
2005-01-13 12:10:16.882164R download was not found in the database
Thanks for the help!
Jason

Hello
Thanks Scott for your reply. We have resolved this issue in house as follows:
- our Systems Support team installed the DB2 Connect client software on the DF server
- copied the jar file to the leselect/drivers directory
Also, because we are using the z series we needed an additional driver db2jcc_license_cisuz.jar which was copied into the same drivers dir.
Thanks!
Jason

When I retrieve returnpack from customer, stock type should be blocked

Hello,
When I retrieve returnpack from customer, I want stock type should be blocked. When I use standart movement type 622, stock type is unrestricted use. Are there any way for this? I couldn't find any movement type which retrieve returnpack stock from customer stock (for example 622v) to storage location stock (for example 622).
Best regards,
Yasar Unalp

BADI ME_PROCESS_PO_CUST .
here you can add the Logic .

Unsatisfied Link Error when using Oracle OCI (Type II) driver

Using Oracle OCI (Type II) driver on HPUX with Oracle 9.2.0.4.
If when creating a connection pool via the console, using the Oracle OCI (Type
II) driver, you get the error "Unsatisfied link error with library libocijdbc9.sl
or format error" then check that the library included in the SHLIB_PATH is pointing
at the $ORACLE_HOME/lib32 directory and not just the $ORACL_HOME/lib

We do not offer a JDBC driver for Linux in version 5.1. In version 6.0,we
do offer a type 4 driver for Linux.
In version 5.1, I suggest trying the platform independent type 4 JDBC driver
available for free from Oracle. It is supported (as is any JDBC driver)
with WebLogic Server. To download it:
Go to http://www.oracle.com and select the "Download" option.
From the resulting page, use the "Select Utility or Driver" dropdown to
select Oracle JDBC drivers
From the resulting page, scroll down a little (since SQLJ stuff appears at
the top).
Or, to go directly there:
http://technet.oracle.com/software/tech/java/sqlj_jdbc/software_index.htm
Thanks,
Michael
Michael Girdley, BEA Systems Inc
Learning WebLogic? Buy the book.
http://www.learnweblogic.com/
"Michael W. Warren, Sr." <[email protected]> wrote in message
news:[email protected]..
I have installed WebLogic 6.0 on Solaris platform and verified that the
server comes up
and that I can connect to it via Netscape. Next step was to verify
installation of WebLogic
jDriver for Oracle. When I run the following:
java utils.dbping ORACLE scott tiger
I get the following error:
Starting Loading jDriver/Oracle .....
Error encountered:
java.sql.SQLException: System.loadLibrary threw
java.lang.UnsatisfiedLinkError
with the message
'/ldatae/bea/wlserver6.0/lib/solaris/oci816_8/libweblogicoci37.so:
ld.so.1: /ldatae/bea/jdk130/jre/bin/../bin/sparc/native_threads/java:
fatal: libgen.so.1: open failed: No such file or directory'.
at
weblogic.jdbcbase.oci.Driver.loadLibraryIfNeeded(Driver.java:202)
at weblogic.jdbcbase.oci.Driver.connect(Driver.java:57)
at java.sql.DriverManager.getConnection(DriverManager.java:517)
at java.sql.DriverManager.getConnection(DriverManager.java:146)
at utils.dbping.main(dbping.java:182)
Anyone seen this? Help!!!
Thanks in advance
Mike Warren, Sr.
[email protected]

DB2 type 2 driver blocking WLS 8.1 SP2 on startup

Similar Messages

Maybe you are looking for