DD 6.0.2 - Problem connecting to Sybase DB

Hoping someone here can help - or point me in the right direction....
We're finally getting around to trying out the deployment stuff I've been working on for the last couple of weeks - and, well, it ain't working ;-)

Environment

ProblemDAS: [Thu Aug 18 10:38:11 MDT 2005] Begin executing package_file_list
DAS: Area VPath:/default/main/bigticket/WORKAREA/bigticket_wa
DAS: Setting up TDbSchemaAgent.
DAS: Performing dbcheck for Sybase ASA
DAS: Connecting to a SQLAnyWhere 7.x server using jConnect....
DAS: url : jdbc:sybase:Tds:ip-addressort/dev1_bt
DAS: login : userid
DAS: login timeout=3
DAS: Connecting to the database...
DAS: Try connecting using jdbc:sybase:Tds:ip-addressort/dev1_bt...
DAS:
Connected to jdbc:sybase:Tds:ip-addressort/dev1_bt
DAS: Driver jConnect (TM) for JDBC (TM)
DAS: Version jConnect (TM) for JDBC(TM)/5.5(Build 25020)/P/JDK12/Tue Jun 19 3:13:19 2001
DAS:
DAS: *******************************************************
DAS: SQLException occured in TSybaseASADbCheckoDbCheck
DAS: Exception Message: SYSINFO not found. Specify owner.objectname or use sp_help to check whether the object exists
(sp_help may produce lots of output).

DAS: Vendor Error Code: 208
DAS: SQL state: 42000
DAS: *******************************************************Apparently we need to use a different version of jConnect and to that end, we've brought over a jconn3.jar file and put it into odhome/drivers/ but that doesn't seem to have made any difference.

Can someone tell me if/how we can put this version of the driver into place so it gets used instead of the one that thinks we're talking to a SqlAnywhere DB ?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Find more posts tagged with

Comments

Migrateduser

OD will pick up any .jar files you place under odhome/drivers (this is 602 right?). Are you sure you removed the old sybase jar... to ensure OD is using the right version?

Mariam

Adam Stoller

Here's the contents of my drivers/ directory (and yes, it's 6.0.2):

\Interwoven\OpenDeployNG\drivers>dir /OD
Volume in drive D is Apps
Volume Serial Number is C815-B2C2

Directory of

\Interwoven\OpenDeployNG\drivers

04/03/2005 02:48 AM 1,931,357 classes12.zip
04/03/2005 02:48 AM 498,433 ifxjdbc.jar
04/03/2005 02:48 AM 1,360,937 db2java_72_nt.zip
04/03/2005 02:48 AM 846,790 SybDriver55.jar
04/03/2005 02:48 AM 53,846 Una2000.jar
04/03/2005 02:48 AM 1,114,986 db2java_72_sol.zip
08/18/2005 10:36 AM 944,135 jconn3.jarAre you saying I have to remove SybDriver55.jar?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Adam Stoller

Besides having to take now the OD service (net stop iwod60) and waiting a bit
Removing the other driver didn't seem to help either:DAS: Setting up TDbSchemaAgent.
DAS: >>> Loading drivers <<<
DAS: ERROR Smiley Very Happy

D07001:JDBC jar/zip not found in the drivers directory
DAS: ERROR:ERROR: Loading drivers : com.sybase.jdbc2.jdbc.SybDriver
DAS: ERROR:ClassNotFoundException: com.sybase.jdbc2.jdbc.SybDriver
java.lang.ClassNotFoundException: com.sybase.jdbc2.jdbc.SybDriver
at com.interwoven.deploy.cdmain.IWCDClassLoader.loadClass(IWCDClassLoader.java:577)
at com.interwoven.deploy.cdmain.IWCDClassLoader.loadClass(IWCDClassLoader.java:448)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at com.interwoven.dd100.dd.JdbcCheckup.registerDriverWithDriverManager(JdbcCheckup.java:164)
at com.interwoven.dd100.dd.JdbcCheckup.LoadDrivers(JdbcCheckup.java:234)
at com.interwoven.dd100.dd.TDbAgent.(TDbAgent.java:263)
at com.interwoven.dd100.dd.TDbSchemaAgent.(TDbSchemaAgent.java:64)
at com.interwoven.dd100.dd.TConsumerManager.getDbAgentBasedOnGroupUpdate(TConsumerManager.java:513)
at com.interwoven.dd100.dd.TConsumerManager.SetupConsumer(TConsumerManager.java:586)
at com.interwoven.dd100.dd.TConsumerManager.SetupConsumersForOneDeployment(TConsumerManager.java:191)
at com.interwoven.dd100.dd.TConsumerManager.SetupConsumers(TConsumerManager.java:133)
at com.interwoven.dd100.dd.TAgentClient.Go(TAgentClient.java:105)
at com.interwoven.dd100.dd.IWDataDeploy.Go(IWDataDeploy.java:545)
at com.interwoven.dd100.dd.TDASThread.ProcessItem(TDASThread.java:203)
at com.interwoven.dd100.dd.TDASThread.run(TDASThread.java:128)
DAS: Performing dbcheck for Sybase ASA
DAS: Connecting to a SQLAnyWhere 7.x server using jConnect....
DAS: url : jdbc:sybase:Tds:ip-addressort/dev1_bt
DAS: login : userid
DAS: login timeout=0
DAS: Connecting to the database...
DAS: Try connecting using jdbc:sybase:Tds:ip-addressort/dev1_bt...
DAS: SQL failure
DAS: ERROR:ERROR: Could not connect to [jdbc:sybase:Tds:ip-addressort/dev1_bt]
DAS:
DAS: *******************************************************
DAS: SQLException occured in JdbcCheckup:MakeConnection()
DAS: Exception Message: No suitable driver
DAS: Vendor Error Code: 0
DAS: SQL state: 08001
DAS: *******************************************************

If I use jconn2.jar instead of jconn3.jar - it looks like the same error as before - where it seems to think it's dealing with SqlAnyWhere 7 - which we aren't - and it complains about not finding SYSINFO

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Adam Stoller

At this point - we believe that jconn2.jar is the "correct" one to have present (jconn3.jar seems to be ignored)

The part of the message that concerns the local Sybase DB guy here is:

DAS: Performing dbcheck for Sybase ASA

He says it should be using ASE not ASA -- is there some place where this is configured that I could change it? or are we SOL here?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Sorry.. I thought the jconn jar was a replacement for the SybDriver55... if the classes don't clobber one another that's fine to keep both.

For your database connection specification, did you set vendor="sybasease"?

What's the version of Sybase?

Mariam

Migrateduser

Just another note: if you set vendor to just 'sybase' that will indicate ASA... so be sure it is set to 'sybasease'

Mariam

Adam Stoller

For your database connection specification, did you set vendor="sybasease"?

LOL --- I saw that and thought someone had misspelled "sybase" - sigh - okay - having fixed that back again, I'm still having some problems, but there's a lot less detail about the problem in the log file:...
DAS: [Thu Aug 18 13:51:49 MDT 2005] Begin executing package_file_list
DAS: Area VPath:/default/main/bigticket/WORKAREA/bigticket_wa
DAS: Setting up TDbSchemaAgent.
DAS: url : jdbc:sybase:Tds:ip-addressort/master?USE_METADATA=true
DAS: login : userid
DAS: login timeout=0
DAS: Connecting to the database...
DAS: Try connecting using jdbc:sybase:Tds:ip-addressort/master?USE_METADATA=true...
DAS:
Connected to jdbc:sybase:Tds:ip-addressort/master?USE_METADATA=true
DAS: Driver jConnect (TM) for JDBC (TM)
DAS: Version jConnect (TM) for JDBC(TM)/5.5(Build 25329)/P/EBF11937/JDK13/Fri Apr 30 2:16:56 2004
DAS: url : jdbc:sybase:Tds:ip-addressort/dev1_bt?USE_METADATA=true
DAS: login : userid
DAS: login timeout=3
DAS: Connecting to the database...
DAS: Try connecting using jdbc:sybase:Tds:ip-addressort/dev1_bt?USE_METADATA=true...
DAS:
Connected to jdbc:sybase:Tds:ip-addressort/dev1_bt?USE_METADATA=true
DAS: Driver jConnect (TM) for JDBC (TM)
DAS: Version jConnect (TM) for JDBC(TM)/5.5(Build 25329)/P/EBF11937/JDK13/Fri Apr 30 2:16:56 2004
DAS: Connected to [ip-addressort/dev1_bt]
DAS: Creating identifier mapping table: IWOV_IDMAPS
DAS: CREATE TABLE IWOV_IDMAPS (TYPE INT NOT NULL, SHORTID VARCHAR(30) NOT NULL, LONGID TEXT NOT NULL)
DAS: Created identifier mapping table: IWOV_IDMAPS Successfully
DAS: Creating index on IWOV_IDMAPS
DAS: CREATE TABLE IWDELTRACKER ( PATH VARCHAR(255) NOT NULL , AREA VARCHAR(255) NOT NULL , KEYCOLNAME VARCHAR(255) NOT NULL , KEYCOLVALUE
VARCHAR(255) NOT NULL )
DAS: CREATE INDEX iwdelt_idx ON IWDELTRACKER( PATH , AREA )
DAS: IWDELTRACKER created successfully.
DAS: ERROR:Unable to initialize TDbSchemaGroupInfo object.
DAS: Error occured in TDbSchemaAgentI can find no reference to any such error message in the DD manuals. Anyone know what this error message means? What I should be looking to fix?

(I'm sooooo close to actually having something that "works" ;-)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Can you give some details on the user tables that DD is creating...perhaps post the dbschema. It looks like there could be a problem with the dbschema.

Mariam

Adam Stoller

I'll send files under separate cover - don't want to waste time trying to sanitize them for public forum viewing)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

msrinivas

Similar problems.......did you figure this thing out? My understand is that it has to do something with the case sensitivty of Sybase.

Thank you,

Srinivas

Adam Stoller

Sigh - sorry - I must have figured it out or it just went away - but I'm no longer working on that project and no longer remember the details of that particular problem or its solution - sorry.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

msrinivas

Thank you for the reply!

The problem is that the entire Sybase DB (not just the instance that you are working with) including system tables etc., HAVE to be case-insensitive. I am not sure why this "feature" is there but unfortunately DD looks for table names in CAPS and you will run into this problem is the tables are lower case or are case-sensitive.

Can some one from IWOV engineering shed some light on why this is so?

Srinivas