Upgrading db2 connect thin client from v9.1 to v9.5

I'm looking for instructions on how to upgrade the db2 connect thin client CLI and JDBC drivers from v9.1 to v9.5 (latest fixpack). I found note 867976 describing how to update the JDBC portion. I'm wondering if there is an official way of upgrading the CLI client, now that this is normally automatically installed as part of the SAPINST process. We want to upgrade our system from v9.1 thin client ot v9.5 thin client to use the new functionality.
(We have instructions for upgrading from v9 Fat client to v9.5 thin client.)

1.Copied new driver version into db2_clidriver and jdbc folders.
2. Ran db2radm to bind new collection
3. Used sappad to change connect.ini file back to Unix format.
4. Restarted Cluster.
New version working now.

Similar Messages

Problem using Weblogic 6 and Weblogic 8.1 thin clients from same applicatio

We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
Exceptions:
Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 6.1 SP7?.
 throws following exception while connecting to ?Weblogic 8.1?.
weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
 at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
 at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
 at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
 at weblogic.kernel.Kernel.initialize(Kernel.java:138)
 at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
 at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
 at java.lang.Class.newInstance0(Class.java:308)
 at java.lang.Class.newInstance(Class.java:261)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
 at javax.naming.InitialContext.init(InitialContext.java:219)
 at javax.naming.InitialContext.<init>(InitialContext.java:195)
 at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
 at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
 at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
java.lang.InternalError: error initializing kernel
 at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
 at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
 at java.lang.Class.newInstance0(Class.java:308)
 at java.lang.Class.newInstance(Class.java:261)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
 at javax.naming.InitialContext.init(InitialContext.java:219)
 at javax.naming.InitialContext.<init>(InitialContext.java:195)
 at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
 at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
 at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
Case 2: ?Weblogic 8.1? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 8.1?.
 throws following exception while connecting to ?Weblogic 6.1 SP7?.
avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more
Couldn't connect to any host
Cause: {1}
javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
Cause: {1}
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more

uday naik <> writes:
The thin-client isn't supported on 6.1, I'm not sure what you are doing.
andy
We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
Exceptions:
Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 6.1 SP7?.
 throws following exception while connecting to ?Weblogic 8.1?.
weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
 at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
 at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
 at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
 at weblogic.kernel.Kernel.initialize(Kernel.java:138)
 at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
 at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
 at java.lang.Class.newInstance0(Class.java:308)
 at java.lang.Class.newInstance(Class.java:261)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
 at javax.naming.InitialContext.init(InitialContext.java:219)
 at javax.naming.InitialContext.<init>(InitialContext.java:195)
 at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
 at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
 at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
java.lang.InternalError: error initializing kernel
 at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
 at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
 at java.lang.Class.newInstance0(Class.java:308)
 at java.lang.Class.newInstance(Class.java:261)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
 at javax.naming.InitialContext.init(InitialContext.java:219)
 at javax.naming.InitialContext.<init>(InitialContext.java:195)
 at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
 at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
 at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
Case 2: ?Weblogic 8.1? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 8.1?.
 throws following exception while connecting to ?Weblogic 6.1 SP7?.
avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more
Couldn't connect to any host
Cause: {1}
javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
Cause: {1}
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more

Monitoring an applet on a thin client from the server

Hello all,
I'm not even sure if this is possible or not, but here is what I would like to do.
I want to be able to monitor an applet running on a remote thin client device from the central server to determine if there have been any problems (exceptions, device failures, etc).
I'll be using java 1.5.0. If you require more info please let me know.
Thanks,

But would anyone know if there is a similar method for applets?
What makes you think you can't use that technique in an applet? Use that, and contact the server when there's an uncaught exception.
You'll probably want to report a number of caught exceptions too (unless you're really bad at handling exceptions).
Best bet is to use a utility class on your applet with a method like "logError(Throwable t, String message)" which will send the details up to the server, maybe output to the console, maybe even pop up a dialog. If you did this via an interface you could plug in different implementations and compound them if required.

Error while connecting to client from custom code 11g

Hi,
I am trying to connect to the OIM client using a simple code as per documentation in:
http://docs.oracle.com/cd/E27559_01/dev.1112/e27150/apis.htm#CIHDFGAJ
The snipped is like:
System.out.println("Creating client....");
 String ctxFactory = "weblogic.jndi.WLInitialContextFactory";
 String serverURL = "t3://Hostname:port";
 String username = "username";
 String password = "password";
 Hashtable env = new Hashtable();
env.put(OIMClient.JAVA_NAMING_FACTORY_INITIAL,ctxFactory);
 env.put(OIMClient.JAVA_NAMING_PROVIDER_URL, serverURL);
 oimClient = new OIMClient(env);
 System.out.println(" Logging in");
 oimClient.login(username, password);
 System.out.println("Log in successful");
Envoked the method in main class but i am recieveing following error:
Creating client....
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/jrf/PortabilityLayerException
at cgc.com.customcode.OIMCustomCode.initiate(OIMCustomCode.java:30)
at cgc.com.customcode.OIMCustomCode.changeEmail(OIMCustomCode.java:50)
at cgc.com.customcode.OIMCustomCode.main(OIMCustomCode.java:81)
A bit of inspection shows error on code line :
--> oimClient = new OIMClient(env);
Is this a known issue, is there a way out ?
Thanks in advance

Thanks all,
Including jrf-api as per Sagar fixed the exception, then the error for APP_SERVER not found was coming:
I included the lines of code as suggested by NN:
 System.setProperty("java.security.auth.login.config",authConfigLoc);
 System.setProperty("APPSERVER_TYPE", "wls");
The code worked fine but giving some sort of exceptions:
Oct 9, 2012 1:32:25 PM oracle.iam.platform.context.ContextManager <clinit>
SEVERE: IAM-0030002
oracle.jrf.UnknownPlatformException: JRF is unable to determine the current application server platform.
 at oracle.jrf.ServerPlatformSupportFactory.getInstance(ServerPlatformSupportFactory.java:79)
 at oracle.iam.platform.context.ContextManager.<clinit>(ContextManager.java:77)
 at oracle.iam.platformservice.api.ClientLoginSessionServiceDelegate.loginSessionCreated(Unknown Source)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 at Thor.API.Base.SecurityInvocationHandler$1.run(SecurityInvocationHandler.java:68)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.security.Security.runAs(Security.java:41)
 at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(weblogicLoginSession.java:52)
 at Thor.API.Base.SecurityInvocationHandler.invoke(SecurityInvocationHandler.java:79)
 at $Proxy1.loginSessionCreated(Unknown Source)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 at oracle.iam.platform.OIMClient.loginSessionCreated(OIMClient.java:291)
 at oracle.iam.platform.OIMClient.login(OIMClient.java:215)
 at oracle.iam.platform.OIMClient.login(OIMClient.java:184)
 at cgc.com.customcode.OIMCustomCode.initiate(OIMCustomCode.java:38)
 at cgc.com.customcode.OIMCustomCode.changeEmail(OIMCustomCode.java:56)
 at cgc.com.customcode.OIMCustomCode.main(OIMCustomCode.java:87)

How connect one client from another client in SAP.

hi
In my company,HR module is in independent client.
So other Module FI want to get HR information.i want to write a function in HR system.
in FI module to call it and return data. (RFC).
how set it ? the two R/3 System can access one another.
how write abap code in report ? please give demo,thank you!

t_code sm59.
http://help.sap.com/saphelp_nw04/helpdata/en/22/0424ce488911d189490000e829fbbd/content.htm

Wyse Thin client not connecting to Windows 2008 R2 server

Configuration
SBS 2011 Server
Windows 2008 R2 server with Remote Desktop Services installed, License Manager installed.
WYSE WT3125SE thin clients with Windows CE 5
I setup the Windows 2008 with Remote Desktop Services and was able to successfully connect the Thin client. Then I installed the License Manger and applied my Open license using User Cals. Was able to login. Next day I get the following
error-"Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again" I still can connect fine from other machines even Windows Home Ed.
I remove license server and still was unable to connect. Built a second Windows 2008 R2 server with RDS on it. Was able to connect without issue. Pointed it to the first RDS server license manager and have still been able to connect with
the Thin Client. The thin client can rdp to the SBS server without issue in admin mode, can connect to RDS2 server but not RDS1 with the license manger. So my issue is with the license and so my question is what is it with the license server
running on that server that is keeping thin client from connecting. I even did a reload of RDS1 and tested connecting throughout the process and it worked up until I applied the license and then it stops. And then if I uninstall the license, rds, remove
from domain still not able to connect. Any help would be appreciated.

We had the same problem with older terminals after cloning a 2008R2 rds server and sysprep it.
The original rds server worked fine but when the old terminals connect to the new 1 they come up with the error : Because
of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again"
After reading all of the postings about this issue and tried the reactivate solution of the license server,
I was sure that it had something to do with the x509 certificates that are generated the first time you connect to a valid license server.
What I did, I installed a new license server activate it but did not install licenses on it.
I pointed the defective rds server to the newly installed license server and deleted the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
Certificate
X509 Certificate
X509 Certificate ID
X509 Certificate2
Then reboot.
After the reboot all old terminals can connect fine again. As final step I pointed the rds server to the same license server as the other ones,
reboot and all worked fine.
So conclusion is that when you pont a rds server to a license server that has the new type of licenses on it it will generate the wrong x509 certificates
that are not supported by the older clients, by pointing it first to 1 without any rds calls on it, it generates the older x509 certificates which are compatible with the older rdp clients then the switch to new license server will then not regenerate the
x509 certs so it keeps working.
I hope this helps someone
This issue was driving me crazy so very happy that it is resolved now
Cheers Frits

How to identify different connections/clients from RMIServer???

Anyone knows how one can do to identify different connections or clients from the implementation/server-object in RMI?? Do I have to send a hostname from the client via method parameter?? If so, any recommendations on which unique name to use??
Would really appreciate any answer to this!!! - thanx in advance!
ps; tried currentThread.getName(), but it would return different names from same client (changing at each call).
/Alejandro

Hi,
in order to identify clients I maintain a hash with references to
the clients. The clients register and unregister with special
remote methods of the server RMI object.
I didn't see an API in RMI to do this for me. And it was fairly easy to implement.
Have fun,
Klaus

Connect one JAVA ADS instance to multiple clients from the same ABAP system

Hi,
Does anyone know whether it is possible to connect multplie clients from the same ABAP system to a JAVA instance running ADS?
If so how do you setup the java destinations in Visual Admin and SM59 RFC connections?
Any help is appreciated,
Sander

Dear Sander,
this is always the case if you arrange the ADS connection.
You have to set up the RFC connection 'ADS' in ABAP side and this connection/destination is client independent. So you can use this from all clients of your abap system.
On Java side you have to arrange the already mentioned FP_ICF_DATA_<SID> destination. On the ABAP system and client (you specify in this destination) you have to maintain the user ADS_AGENT and your templates should also exist on this client. If there is no client defined, the default client will be used.
Regards
Istvan

Mac Pro with thin clients

Hello,
I am looking for a configuration of a Mac Pro server with thin clients so that software and data is centralized on one location.
Is that possible with Mac OS X ? And does Apple have thin clients ?
Hubert

I have the same question. I am about to buy a Mac Mini with Leopard server, if I can connect thin clients to it. I have good old PCs with Win and Linux, I want to use them as thin clients

Connection through jdbc thin client taking more time than from sqlplus!!!

Hello All
Machines A and B
Applicaion in A is connecting to B(9.2.0.6),db server.
The schema is so small with few tables and data in each table less than 500 rows
We are in the process of migrating the Application Schema in B to C[9.2.0.8].
But the response time is more when the application fetches from C.
Even while selecting the sysdate from dual.
The application is using the jdbc thin client for fetching the data.
When the same sql is executed by (from A to C)
sqlplus -s user/pass @execute.sql, its gets done in a fraction of a second.
But when the same is done through the application which uses jdbc thin client, it takes few seconds
to complete.
When tried with a small java program that uses classes12.jar (from A to C)
conn = DriverManager.getConnection(URL,UID,PASS);
               stop = System.currentTimeMillis();
               System.out.println("Connection time in milli sec: " + (stop - start));
               System.out.println();
..It was found that creating the connection was taking time.
But the same is not happening when tired through the sqlplus
Could someone throw some light into this?
What could be the reason for jdbc to get slower while establishing connections?
TIA,
JJ

are you using latest drivers - http://www.oracle.com/technology/tech/java/sqlj_jdbc/index.html
you may want to check some options reducing jdbc connection cost from the otn samples - http://www.oracle.com/technology/sample_code/tech/java/sqlj_jdbc/index.html

Problem connecting from WL 8.1 Thin client to WL 8.1 App Server in AIX OS

Hi,
I'm trying to use WL 8.1 thin client to connect to BEA Weblogic server 8.1 in AIX OS. However, when I execute my thin client, I get the following error:
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/corba/se/connection/ORBSocketFactory
My thin client is running in AIX OS, using IBM JRE 1.4.2 similar to BEA Weblogic Server 8.1.
The following is my thin client code to connect to weblogic server:
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, url);
Context ctx = new InitialContext(h);
Object home = ctx.lookup(jndiName);
When I ran my thin client, i included wlclient.jar and weblogic.jar in the classpath.
Thanks in advance for your help :)

Brian Yap <> writes:
The thin-client is not supported on AIX.
andy
Hi,
I'm trying to use WL 8.1 thin client to connect to BEA Weblogic server 8.1 in AIX OS. However, when I execute my thin client, I get the following error:
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/corba/se/connection/ORBSocketFactory
My thin client is running in AIX OS, using IBM JRE 1.4.2 similar to BEA Weblogic Server 8.1.
The following is my thin client code to connect to weblogic server:
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, url);
Context ctx = new InitialContext(h);
Object home = ctx.lookup(jndiName);
When I ran my thin client, i included wlclient.jar and weblogic.jar in the classpath.
Thanks in advance for your help :)

Remoted DB2 connection from SAP

Hello Experts,
We have a requirement to connect the remote DB DB2 (No SAP) which is on I series from our SAP ECC EHP 5 system so I made a below entry in table DBCON -
Database connection - PRMS_TEST
DBS - DB4
Username - SAP
*Password ***********
Connection Information - AS4_HOST=S1031993;AS4_DB_LIBRARY=RMTLIB
but while doing the test connection, it gives the below error-
B Loading DB library '/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so' ...
M *** ERROR => DlLoadLib()==DLENOACCESS - dlopen("/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so") FAILED
"/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so: cannot open shared object file: No such file or directory" [dlux.c 445]
M {root-id=000C298267DF1EE0BBC9171365715368}_{conn-id=00000000000000000000000000000000}_0
B *** ERROR => Couldn't load library '/usr/sap/ECD/DVEBMGS00/exe/dbdb4slib.so'
[dbcon.c 5263]
B {root-id=000C298267DF1EE0BBC9171365715368}_{conn-id=00000000000000000000000000000000}_0
B ***LOG BYG=> could not load library for database connection PRMS_TEST [dbds 886]
B ***LOG BZY=> unexpected return code 8192 calling DBDS [dbacds 1536]
My SAP environment is -
SAP - ECC EHP 5
Kernel Release 720 patch 90
OS - Red Hat Linux 5.5 - 64 bit
Database - DB2 (DB6)
Kindlly let us know if I have to put the file dbdb4slib.so in kernel directory and from where I can get this file and if my DBCON entry is correct ?
Regards
Saurabh Mishra

As per note 663756, I can use the DB2 CLI driver as I am on Kernel release 720 (see below) -
If you use a DB2 CLI driver client, the following changes are required in
the procedure described above because the CLI driver does not support DB2
CLP and BIND commands:
o The CATALOG commands are omitted.
o The target host and port must be entered in the table DBCON.
For example, the CON ENV row looks as follows:
DB6_DB_NAME=HOSTDB;DB6_DB_TYPE=DB2/390;DB6_DB_HOST=<hostname>;
DB6_DB_SVCENAME=<portnum>;
o The BIND commands must be executed by a runtime client.
Alternatively, you can use the DB2Binder utility from Note 784264
to bind the CLI packages.
Is that mean that I need to only maintain the DBCON entry as all other commands are omitted for CLI driver and license file is mandatory or temp license will work ?
As per note 784264, I checked my CLASSPATH directory and it contain the JDBC driver file -
sapecdci1:db2ecd 58> pwd
/db2/db2ecd/db2_software/java
sapecdci1:db2ecd 59> ls db2*.jar
db2dbgm.jar db2jcc4.jar db2jcc.jar db2jcc_license_cu.jar db2policy.jar db2umplugin.jar
sapecdci1:db2ecd 60> db2set -all
[e] DB2DBDFT=ECD
 DB2_RESTORE_GRANT_ADMIN_AUTHORITIES=YES [DB2_WORKLOAD]
 DB2_BLOCKING_WITHHOLD_LOBLOCATOR=NO [DB2_WORKLOAD]
 DB2_AGENT_CACHING_FMP=OFF [DB2_WORKLOAD]
 DB2_TRUST_MDC_BLOCK_FULL_HINT=YES [DB2_WORKLOAD]
 DB2_CREATE_INDEX_COLLECT_STATS=YES [DB2_WORKLOAD]
 DB2_ATS_ENABLE=YES [DB2_WORKLOAD]
 DB2_RESTRICT_DDF=YES [DB2_WORKLOAD]
 DB2_DUMP_SECTION_ENV=YES [DB2_WORKLOAD]
 DB2_OPT_MAX_TEMP_SIZE=10240 [DB2_WORKLOAD]
 DB2_WORKLOAD=SAP
 DB2_TRUNCATE_REUSESTORAGE=IMPORT [DB2_WORKLOAD]
 DB2_MDC_ROLLOUT=DEFER [DB2_WORKLOAD]
 DB2_ATM_CMD_LINE_ARGS=-include-manual-tables [DB2_WORKLOAD]
 DB2_SKIPINSERTED=YES [DB2_WORKLOAD]
 DB2_VIEW_REOPT_VALUES=YES [DB2_WORKLOAD]
 DB2_OBJECT_TABLE_ENTRIES=65532 [DB2_WORKLOAD]
 DB2_OPTPROFILE=YES [DB2_WORKLOAD]
 DB2_IMPLICIT_UNICODE=YES [DB2_WORKLOAD]
 DB2_RUNTIME_DEBUG_FLAGS=TOLERANT_FLOAT [DB2_WORKLOAD]
 DB2STMM=APPLY_HEURISTICS:YES [DB2_WORKLOAD]
 DB2_INLIST_TO_NLJN=YES [DB2_WORKLOAD]
 DB2_MINIMIZE_LISTPREFETCH=YES [DB2_WORKLOAD]
 DB2_REDUCED_OPTIMIZATION=4,INDEX,JOIN,NO_TQ_FACT,NO_HSJN_BUILD_FACT,STARJN_CARD_SKEW,NO_SORT_MGJOIN,CART OFF,CAP OFF [DB2_WORKLOAD]
 DB2NOTIFYVERBOSE=YES [DB2_WORKLOAD]
 DB2TERRITORY=1
 DB2_INTERESTING_KEYS=YES [DB2_WORKLOAD]
 DB2_EVALUNCOMMITTED=YES [DB2_WORKLOAD]
 DB2_EXTENDED_OPTIMIZATION=NLJOIN_KEYCARD,IXOR [DB2_WORKLOAD]
 DB2_ANTIJOIN=EXTEND [DB2_WORKLOAD]
 DB2COMPOPT=327685,131776 [DB2_WORKLOAD]
 DB2ATLD_PORTS=60000:65000
 DB2ENVLIST=INSTHOME SAPSYSTEMNAME dbs_db6_schema DIR_LIBRARY LD_LIBRARY_PATH
 DB2COMM=TCPIP [DB2_WORKLOAD]
[g] DB2FCMCOMM=TCPIP4
[g] DB2SYSTEM=sapecdci1
[g] DB2INSTDEF=db2ecd
sapecdci1:db2ecd 61> java com.ibm.db2.jcc.DB3Binder
Exception in thread "main" java.lang.NoClassDefFoundError: com.ibm.db2.jcc.DB3Binder
 at gnu.java.lang.MainThread.run(libgcj.so.7rh)
Caused by: java.lang.ClassNotFoundException: com.ibm.db2.jcc.DB3Binder not found in gnu.gcj.runtime.SystemClassLoader{urls=[file:/db2/db2ecd/sqllib/java/db2jcc_license_cu.jar,file:/db2/db2ecd/sqllib/java/db2jcc.jar,file:/db2/db2ecd/sqllib/function/,file:./,file:/db2/db2ecd/sqllib/java/db2java.zip,file:./,file:/db2/db2ecd/sqllib/java/db2java.zip,file:./], parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}
 at java.net.URLClassLoader.findClass(libgcj.so.7rh)
 at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
 at java.lang.ClassLoader.loadClass(libgcj.so.7rh)
 at gnu.java.lang.MainThread.run(libgcj.so.7rh)
sapecdci1:db2ecd 62> db2 get dbm cfg | grep -i svcename
TCP/IP Service name (SVCENAME) = sapdb2ECD
SSL service name (SSL_SVCENAME) =

Establish SSL connection to Oracle Instance w/JDBC Thin Client

Hello all,
I am writing a monitoring utility that will allow me to establish connections to both Oracle instances and LDAP repositories and query them to determine that they are up and running. My utility consists of a number of objects that handle connections to the LDAP and Oracle instances. I need to be able to do SSL and non-SSL connections to said instances.
My issue is this: I am able to do SSL and non-SSL to LDAP, and non-SSL to an Oracle instance. I am having problems, though, establishing an SSL connection to an Oracle instance (I am using the thin client). Whenever I try, a SQLException is thrown that states: "Encountered a problem with the secret store. Check the wallet location for the presense of an open wallet (cwallet.sso) and ensure that the wallet contains the correct credentials..."
Ok, a little background for those who may need it. Oracle uses a wallet to hold certs that allow SSL connections. I have a wallet on my box, and, from the command line, I am able to sqlplus into and tnsping the appropriate Oracle instances, so I know it is setup properly. The inability to connect only occurs in my code. My code looks like this:
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Security.addProvider(new oracle.security.pki.OraclePKIProvider());
/*Setup connection properties*/
String connectionString = "testbox01:1000:ssl_instances_name";
String userName = "userName";
String pwd = "password";
Properties props = new Properties();
props.put("oracle.net.ssl_version", 3.0");
props.put("oracle.net.wallet_location", "SOURCE=(METHOD=file)(METHOD_DATA=(DIRECTORY=c:\\wallet)))");
props.put("oracle.net.ssl_cipher_suites", "ssl cipher suites");
props.put("oracle.net.ssl_server_dn_match", "FALSE");
props.put("oracle.net.ssl_client_authentication", "true");
/*Do connection and return connection object
OracleDataSource ods = new OracleDataSource();
ods.setUser(userName);
ods.setPassword(pwd);
ods.setUrl("jdbc:oracle:thin:@" + connectionString);
ods.setConnectionProperties(props);
Connection conn = ods.getConnection(); <---This is where code errors out with SQLException described above.
return conn;
And that's pretty much it. Anyone have any ideas?

Ok, that looked horrible. Let's try this again: 
 
I am writing a monitoring utility that will allow me to establish connections to both Oracle instances and LDAP repositories and query them to determine that they are up and running. My utility consists of a number of objects that handle connections to the LDAP and Oracle instances. I need to be able to do SSL and non-SSL connections to said instances. 
 
My issue is this: I am able to do SSL and non-SSL to LDAP, and non-SSL to an Oracle instance. I am having problems, though, establishing an SSL connection to an Oracle instance. Whenever I try, a SQLException is thrown that states: "Encountered a problem with the secret store. Check the wallet location for the presense of an open wallet (cwallet.sso) and ensure that the wallet contains the correct credentials..." 
 
Ok, a little background for those who may need it. Oracle uses a wallet to hold certs that allow SSL connections. I have a wallet on my box, and, from the command line, I am able to sqlplus into and tnsping the appropriate Oracle instances, so I know it is setup properly. The inability to connect only occurs in my code. My code looks like this: 
 
***** 
 
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver()); 
Security.addProvider(new oracle.security.pki.OraclePKIProvider()); 
 
/*Setup connection properties*/ 
 
String connectionString = "testbox01:1000:ssl_instances_name"; 
String userName = "userName"; 
String pwd = "password"; 
 
Properties props = new Properties(); 
props.put("oracle.net.ssl_version", 3.0"); 
props.put("oracle.net.wallet_location", "SOURCE=(METHOD=file)(METHOD_DATA=(DIRECTORY=c:\\wallet)))"); 
props.put("oracle.net.ssl_cipher_suites", "ssl cipher suites"); 
props.put("oracle.net.ssl_server_dn_match", "FALSE"); 
props.put("oracle.net.ssl_client_authentication", "true"); 
 
/*Do connection and return connection object*/ 
OracleDataSource ods = new OracleDataSource(); 
ods.setUser(userName); 
ods.setPassword(pwd); 
ods.setUrl("jdbc:oracle:thin:@" + connectionString); 
ods.setConnectionProperties(props); 
 
Connection conn = ods.getConnection(); <---This is where code errors out with SQLException described above. 
 
return conn; 
 
***** 
 
And that's pretty much it. Anyone have any ideas?

T5325 Thin Clients losing remote desktop connection

My company just bought about 50 of these thin clients and they are setup to run an automatic remote desktop connection. I have the connection setup to auto start when the thin client is powered on and it just brings the user to a windows login screen. After they have logged in and leave their thin client to go on break sometimes it just brings them to a blank screen with an HP logo and the thin client has to be restarted to get back into the remote desktop, or I have to go into admin and restart the RDP connection. Any idea why this is happening? Is there a setting somewhere I need to change?
Any help would be great!

We are having this same issue and it is maddening. I have contacted HP on several occasions and I don't know if it is the language barrier or simple ignorance, but so far the issue is ongoing. I have looked high and low on the net and no one seems to be able to tell me why this is happening despite a number of plausible theories. We have a couple hundred terminals throughout the company which are spread across three servers none of which are close to congested yet.. However, the 10 or so t5325's we have are used specifically for digital signage. They run automated sessions that launch animated JAVA windows. They run great for the most part, but seemingly at random they will freeze in their tracks. The sessions drop from our terminal server and cannot be restarted remotely. After the units are power cycled they come back up directly and begin their sessions again. You can shadow these units (VNC) and the moment the display come on the unit closes the RDP session and reopens the same and start running again, odd behavior. I have tried changing session logout timers, disabling / enabling TCP settings, creating client-side refresh scripts, restarting the sessions at regular intervals via admin script, flashing BIOS and ThinPro OS to the current level, voodoo rituals, and pagan sacrifice. Yet, they still behave in exactly the same manner with no actions on my part having any apparent affect.. Currently, I am of the mind to purchase small all-in-one pc's to do the job. If anyone knows of any way to fix this PLEASE respond to this post.

OS_USER not correct when connecting using JDBC Thin Client on 10G

Hi Folks,
We are migrating an application from a 9i database to 10g and have a problem that someone might have come across before.
The application is a Java applet based application that connects to the database using JDBC Thin client. on 9i the OS_USER comes up as the user running the applet but in 10G it is coming up as the user account that installed 10G on the DB server.
We tried using a 9i client to identify if it was a client or DB issue but its the same problem with the 9i client connecting to the 10G DB.
If anyone can help it would be much appreciated.
Thanks,
John.

What is the return of this command?
SELECT sys_context ('USERENV', 'OS_USER') FROM dual;
Is it the DB user or the OS user?

Upgrading db2 connect thin client from v9.1 to v9.5

Similar Messages

Maybe you are looking for