DataDeploy 5.6 SP2 -> DB2 8.1 connection hang

Hi,

I'm trying to do a standalone deployment as a proof of concept from DataDeploy (5.6 SP2, Solaris) to DB2 8.1. I have tested the drivers (db2java.zip and db2cc.jar) with a tool running on my desktop (dbVisualizer) and can connect OK using that. I have amended iwdd.ipl to point to these drivers, as they are not installed by default.

However, when I kick off a connection using DD, I'm getting a hang.

Executing iwdd.ipl cfg=../conf/loz.cfg deployment=xml-to-db, I get the response:

DataDeploy Version 5.6.0 Build 43585 Interwoven 20041201
Database Vendor set to ibm
Setting up consumer TDbAgent
>>> Loading drivers <<<
url : jdbc:db2://ukhldbs005.hld.uk.fid-intl.com:60000/wpsdb
login : db2prtd1
login timeout=3
Connecting to the database...
Try connecting using jdbc:db2://ukhldbs005.hld.uk.fid-intl.com:60000/wpsdb...

and there it hangs forever. Any idea what could be wrong, or what line of inquiry I could pursue next?

I've included a paste of /conf/loz.cfg below:

------------
loz.cfg
------------
<data-deploy-configuration>
<client>
<deployment name="xml-to-db">
<source>

<xml-formatted-data file="/export/home/a367477/portal_data.xml" >
<fields>
<field name="id" element="id" />
<field name="title" element="title" />
<field name="text" element="text" />
</fields>
</xml-formatted-data>
</source>
<destinations>
<database
name = "portal_poc_db"
db = "//ukhldbs005.hld.uk.fid-intl.com:60000/wpsdb"
user = "db2prtd1"
password = "wardsback"
vendor = "ibm"
table = "fragments"/>
</destinations>
</deployment>
</client>
</data-deploy-configuration>

Find more posts tagged with

Comments

iwovGraduate

From the server where you are running DD, what happens you run
"telnet ukhldbs005.hld.uk.fid-intl.com 60000" ?
Just making sure if you are able to establish a connection.

Lozza

Yep, a connection can be made:

# telnet ukhldbs005.hld.uk.fid-intl.com 60000
Trying 10.160.142.8...
Connected to ukhldbs005.uk.fid-intl.com.
Escape character is '^]'.

Lozza

I think I've found the solution to this, and am posting it in case any other losers out there make the same mistake.

Where most ordinary database tools seem quite happy to use (and fall back) to the JCC driver when connecing to DB2, DataDeploy explicitly requires the use of the JDBC Net driver, and absolutely requires db2jstrt to be executed on the DB2 server to start the JDBC listener daemon. This is on port 6789 by default.

Yes, this is all in the release notes for OD/DD. However the only indication you get when db2jstrt hasn't been run correctly is a connection hang with no error message or timeout. Helpful don't you think?

IWguy

Thanks for the info Lozza, I was going home tonight to peruse the notes to find the cause of this exact problem I found this morning but you've just saved me some time. I'll drink a beer for you tonight!