WLST : Error connecting to a remote Weblogic server instance from OEPE 3.7

Question

Attempting a to run a weblogic script connecting to a remote weblogic server instance (10.3.5), which is generating the following exception in OEPE 3.7.2 -
username = 'weblogic'
password = 'weblogic6'
url='t3://xxx.xxx.com:7001'
connect(username,password,url)
Connecting to t3://xxx.xxx.com:7001 with userid weblogic ...
This Exception occurred at Fri Feb 01 13:20:54 MST 2013.
Error occured while performing connect : Error connecting to the server : Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStub
Use dumpStack() to view the full stacktrace :
java.lang.AssertionError: Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStubconnect
Problem invoking WLST - Traceback (innermost last):
File "C:\Users\hughese\workspace\12c_wlst\wlst\heapsize.py", line 13, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing connect : Error connecting to the server : Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStub
Use dumpStack() to view the full stacktrace
Connecting to the local weblogic server instance (t3://localhost:7001) works okay.
From the command prompt (wlst.cmd) I'm able to connect to the remote weblogic server instance -
wls:/offline> connect('weblogic','xxxxx','t3:xxx.xxx.com:7001') ;
Connecting to t3://xxx.xxx.com:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'IDMDomain'.
I've compared the CLASSPATHs between OEPE and the command prompt.
Any assistance would be greatly appreciated.
Edited by: 950635 on Feb 1, 2013 7:47 PM

Answer 1

Hi,
1)To get mysql JDBC driver to work on my Linux system, i had to add the classpath for the driver to the .bashrc:
CLASSPATH=./:home/<user>/java/mm.mysql-2.0.6/:home/<user>/java
Note that I execute the java program as the user <user> (and .bashrc is the config. file of this <user>...). Perhaps you must do this as well for the Oracle driver on your client machine. I don't know if your client machine is UNIX/LINUX or WINDOWS. It should only be clear that the CLASSPATH is set in the config. file of the user under which the java program runs and that this user has the permission to access the files.
There are no differences between accessing the database locally than accessing it by a network connection. The only thing that matters are that the connection parameters are right and that the network works properly.
2) are you sure that the table tname (case sensitivity?) exits?
Marc