I am attempting to migrate from 6.0.1 to 6.1 on a W2K system with an Oracle 8.1.7 DB.
I’ve set my tnpool as follows:
<?xml>

<idataxmlcoder>
<record>
<value>tnpool</value>
<number>2</number>
<number>20</number>
<number>60000</number>
<value>jdbc:wm:oracle://localhost:1521;SID=orcl</value>
<value></value>
<byte></byte>
<value>DataDirect SequeLink JDBC Driver (TN Only)</value>
<value>Trading Networks DB Pool</value>
</record>
</idataxmlcoder>

I can successfully test the connection from the JDBC settings in IS Admin, and when I finally gave up trying to migrate, I am able to open the DB and view profiles, etc. from the TN Console.

However, whenever I try to run the migrate utility or tnquery, I get:
java.sql.SQLException: No suitable driver
java.sql.SQLException: No suitable driver
java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:532)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at com.wm.app.tn.db.Datastore.getOfflineConnection(Datastore.java:603)
at com.wm.app.tn.db.Datastore.getConnection(Datastore.java:263)
at com.wm.app.tn.db.Datastore.getDBMetaData(Datastore.java:505)
at com.wm.app.tn.db.Datastore.init(Datastore.java:175)
at com.wm.app.tn.db.Embedded.init(Embedded.java:104)
at com.wm.app.tn.util.migrate.migratedata_to_tn_61.main (migratedata_to_tn_61.java:32)

wM Tech Services solved this for me. (Thanks Amit.)
It turns out that you should use the Oracle drivers, not SequeLink to access Oracle databases. Boy do I feel dumb!

Hi Randle,

My question is not related to this thread but I saw that you mentioned here that you have migrated 6.0.1 to 6.1 on W2K and I was once posting a question about that. My problem was that the installer wanted me to install 6.1 into a directory without spaces in name and my 6.0.1 is in c:\Program Files\webMethods6. Therefore if I install 6.1 in a different directory than I am not sure how this upgrade works. To me it sounds like another installation in a different location rather than installation on top of an existing 6.0.1. Please let me know how you did with your upgrade to 6.1 on W2K.
Many thanks.

I experienced intermittent problems with the installer and spaces in file names a while back, so I’ve been using c:\webmethodsnn since 4.6.
However, I don’t think 6.1 has a problem. I just tried doing an install to c:\Program Files\webMethods6 and received no complaints up the point where I quit to avoid doing the actual install.
I think the last problem I had was with spaces in the target path name when I was creating an install image. Might that be your problem?
Good luck.

This is the problem I have with the installer 6.1 while upgrading to 6.1 and installing it to a directory c:\Program Files\webMethods6, where currently I have 6.0.1 installed and running without problems. Have you seen this?

Sorry, Fenek. I’ve never seen that screen before. It’s particularly strange since when I run the installer “C:\Program Files\webMethods6” is the default installation directory. I have to change it to “C:\webMethods6” at installation time.
Since no one’s volunteered any info here, maybe you should try webMethods tech support.

In middle of upgrade process, we got to the migrate step. When running
migratedata_to_tn_6-1.bat we get the following error:

java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:563)
at java.sql.DriverManager.getConnection(DriverManager.java:163)
at com.wm.app.tn.db.Datastore.getNewConnection(Datastore.java:455)
at com.wm.app.tn.db.WallyPool$PoolEntry.<init>(WallyPool.java:426)
at
com.wm.app.tn.db.WallyPool.getAvailConnection(WallyPool.java:309)
at com.wm.app.tn.db.WallyPool.getConnection(WallyPool.java:172)
at com.wm.app.tn.db.Datastore.getConnection(Datastore.java:441)
at com.wm.app.tn.db.Datastore.init(Datastore.java:276)
at com.wm.app.tn.db.Embedded.init(Embedded.java:117)
at
com.wm.app.tn.util.migrate.migratedata_to_tn_61.main(migratedata_to_t
n_61.java:32)
java.lang.NoClassDefFoundError: javax/mail/internet/AddressException
at com.wm.app.b2b.server.ServerAPI.logError(ServerAPI.java:107)
at com.wm.app.tn.err.SystemLog2.log(SystemLog2.java:635)
at com.wm.app.tn.db.Datastore.init(Datastore.java:336)
at com.wm.app.tn.db.Embedded.init(Embedded.java:117)
at
com.wm.app.tn.util.migrate.migratedata_to_tn_61.main(migratedata_to_t
n_61.java:32)

This is despite the TN JDBC pool being correctly defined in the
Administrator. We are able to connect to TN from the pool, restarted the
function… I removed the echo off at the beginning of the bat files that
run and this is the full command that it tries to run when getting this
error:

D:\Program
Files\webMethods6\IntegrationServer\packages\WmTN\config\migrate>“d:\
Program Files\webMethods6\IntegrationServer\jvm\bin\java” -ms128M -mx384M
-class
path “d:\Program Files\webMethods6\IntegrationServer\lib\classes”;“d:
\Program Fi
les\webMethods6\IntegrationServer\lib\server.jar”;“d:\Program
Files\webMethods6\
IntegrationServer\lib\client.jar”;“d:\Program
Files\webMethods6\IntegrationServe
r\lib\server.zip”;.;“d:\Program
Files\webMethods6\IntegrationServer\lib\entrust\
entbase.jar”;“d:\Program
Files\webMethods6\IntegrationServer\lib\jdk11x_update.j
ar”;“d:\Program Files\webMethods6\IntegrationServer\jvm\LIB\RT.JAR”;“d:
\Program
Files\webMethods6\IntegrationServer\jvm\lib\i18n.jar”;“d:\Program
Files\webMetho
ds6\IntegrationServer\lib\classes”;“d:\Program
Files\webMethods6\IntegrationServ
er\lib\jars\cryptix32-pgp.jar”;“d:\Program
Files\webMethods6\IntegrationServer\l
ib\jars\cryptix32.jar”;“d:\Program
Files\webMethods6\IntegrationServer\lib\jars\
cs_cloudscape.jar”;“d:\Program
Files\webMethods6\IntegrationServer\lib\jars\cs_t
ools.jar”;“d:\Program
Files\webMethods6\IntegrationServer\lib\jars\ediint.jar”;"
d:\Program Files\webMethods6\IntegrationServer\lib\jars\editn.jar";“d:
\Program F
iles\webMethods6\IntegrationServer\lib\jars\sl53_cj33.jar”;“d:\Program
Files\web
Methods6\IntegrationServer\lib\jars\Sprinta2000.jar”;“d:\Program
Files\webMethod
s6\IntegrationServer\lib\jars\tncore.jar”;“d:\Program
Files\webMethods6\Integrat
ionServer\packages\WmTN\code\jars\ediintdoc.jar”;“d:\Program
Files\webMethods6\I
ntegrationServer\packages\WmTN\code\jars\editn.jar”;“d:\Program
Files\webMethods
6\IntegrationServer\packages\WmTN\code\jars\tnclient.jar”;"d:\Program
Files\webM
ethods6\Integra

I ran into the same problem in upgrading from 6.0.1 to 6.1. webMethods apparently changed the format of the JDBC URL for the Oracle driver - the new format is in the installation guide, but no mention is made in the upgrade guide. Our database was Oracle, but it might affect other drivers too. Check your 6.1 installation guide and make sure the new URL format is being followed.

The new format is jdbc:wm:oracle://srv:1521;SID=db

Notice there is a wm in the middle for 6.1 connection pool settings.