DataDeploy is Hung and Database is Locked

Girz

Hi,

DataDeploy was working fine after initial setup. There was a cleanup activity in the database.

IWDELTRACKER,IWIDMAPS, Along with the DataDeploy related tables got deleted.

Project uses Microsoft SQL DB

DATADEPLOY version is 7.3

After the clean-up we tried triggering DataDeploy which is getting hung with following error.

Also the Database is getting hung till do OpenDeploy restart. Kindly share the resolution for the same.

Also please let us know if there is any TimeOut on such issue so that the database won’t get hung forever due to datadeploy issue.

Following are the log error when the deployment is hung. The below statements gets repeatedly logged till OD is restarted

DBD: *******STACK TRACE*************

DBD: ERROR:

java.sql.SQLException: [TDS Driver]Read timed out

at com.inet.tds.e.a(Unknown Source)

at com.inet.tds.a.a(Unknown Source)

at com.inet.tds.a.if(Unknown Source)

at com.inet.tds.h.a(Unknown Source)

at com.inet.tds.h.getTables(Unknown Source)

at com.interwoven.dd100.dd.TableSchema.Exists(TableSchema.java:123)

at com.interwoven.dd100.dd.TableSchema.Exists(TableSchema.java:51)

at com.interwoven.dd100.dd.TDbSchemaRowSort.BuildTempTableName(TDbSchemaRowSort.java:197)

at com.interwoven.dd100.dd.TDbSchemaRowSort.BuildTempTable(TDbSchemaRowSort.java:174)

at com.interwoven.dd100.dd.TDbSchemaRowSort.PerformSort(TDbSchemaRowSort.java:82)

at com.interwoven.dd100.dd.TDbSchemaUpdateHelper.PerformSort(TDbSchemaUpdateHelper.java:137)

at com.interwoven.dd100.dd.TDbSchemaUpdateHelper.GetOperationRequired(TDbSchemaUpdateHelper.java:157)

at com.interwoven.dd100.dd.TDbSchemaGroupCfg.DoRealUpdate(TDbSchemaGroupCfg.java:837)

at com.interwoven.dd100.dd.TDbSchemaCfg.RealUpdateWithGroupTree(TDbSchemaCfg.java:955)

at com.interwoven.dd100.dd.TDbSchemaCfg.RealUpdate(TDbSchemaCfg.java:935)

at com.interwoven.dd100.dd.TDbSchemaAgent.BasicWriteTuple(TDbSchemaAgent.java:441)

at com.interwoven.dd100.dd.TDbSchemaAgent.WriteTuple(TDbSchemaAgent.java:336)

at com.interwoven.dd100.dd.TConsumerManager.WriteConsumerInternal(TConsumerManager.java:399)

at com.interwoven.dd100.dd.TConsumerManager.WriteConsumers(TConsumerManager.java:388)

at com.interwoven.dd100.dd.TAgentClient.DoOneTeamSiteSource(TAgentClient.java:1083)

at com.interwoven.dd100.dd.TAgentClient.ProcessOneFileList(TAgentClient.java:637)

at com.interwoven.dd100.dd.TAgentClient.ProcessFileList(TAgentClient.java:594)

at com.interwoven.dd100.dd.TAgentClient.DoTeamSiteSources(TAgentClient.java:539)

at com.interwoven.dd100.dd.TAgentClient.DoOneDeployment(TAgentClient.java:290)

at com.interwoven.dd100.dd.TAgentClient.Go(TAgentClient.java:181)

at com.interwoven.dd100.dd.IWDataDeploy.Go(IWDataDeploy.java:601)

at com.interwoven.dd100.dd.TDASThread.ProcessItem(TDASThread.java:203)

at com.interwoven.dd100.dd.TDASThread.run(TDASThread.java:128)

Thanks

Find more posts tagged with

Comments

Rick Poulin

That's the whole stack trace, nothing else? You should verify that you can ping your target db server and that the port is open and reachable. Aside from that, you'll probably have to get a DBA involved to check what's happening on the database end of things.

Girz

Hey rpoulin,

The log also had shared information that the DB connection was successful. After which DataDeploy Ideally creates a IW_TEMP Table and then it does an insert/update to the actual tables.

In this case it throws the STACK TRACE error(shown in my earlier thread) and database gets locked and only way to exit the datadeploy is by killing the datadeploy process else the DB is getting locked forever.

DBD: Connecting to the database...
DBD: Try connecting using jdbc:inetdae:XXXXXXX:1433?database=XXXXXXXXXX&sql7=true...
DBD:
Connected to jdbc:inetdae:XXXXXX:1433?database=XXXXXXXX&sql7=true
DBD: Driver i-net UNA 2000
DBD: Version 4.18
DBD: Connected to [XXXXXXXX:1433?database=XXXXXX]
DBD: Creating identifier mapping table: IWOV_IDMAPS
DBD: CREATE TABLE IWOV_IDMAPS (TYPE INT NOT NULL, SHORTID VARCHAR(30) NOT NULL, LONGID VARCHAR(1024) NOT NULL)
DBD: Created identifier mapping table: IWOV_IDMAPS Successfully
DBD: Creating index on IWOV_IDMAPS
DBD: CREATE TABLE IWDELTRACKER ( PATH VARCHAR(255) NOT NULL , AREA VARCHAR(255) NOT NULL , KEYCOLNAME VARCHAR(255) NOT NULL , KEYCOLVALUE VARCHAR(255) NOT NULL )
DBD: CREATE INDEX iwdelt_idx ON IWDELTRACKER( PATH , AREA )
DBD: IWDELTRACKER created successfully.
DBD: Table [XXXX] exists.
DBD: Table [XXXX] exists.
DBD: Running deployment [XXXXX]
DBD: extraction type=default
DBD: tuple mode=wide

DBD: TTableSchemaHelper object for [XXXX] found in cache.
DBD: Loading com.inet.tds.TdsDriver
DBD: url      : jdbc:inetdae:XXXXXXXXXX:1433?database=XXXXXX&sql7=true
DBD: login    : XXXXXXXX
DBD: login timeout=3
DBD: Connecting to the database...
DBD: Try connecting using jdbc:inetdae:XXXXXXXX:1433?database=XXXXXXXX&sql7=true...
DBD:
Connected to jdbc:inetdae:XXXXXXX:1433?database=XXXXXX&sql7=true
DBD:   Driver         i-net UNA 2000
DBD:   Version        4.18
DBD:
DBD: *******************************************************
DBD: SQLException occured in TableSchema:Exists()
DBD: Exception Message: [TDS Driver]Read timed out
DBD: Vendor Error Code: 0
DBD: SQL state: S1T00
DBD: *******************************************************

Rick Poulin

What is this TDS driver and why aren't you using the one provided by Microsoft?

Girz

TeamSite OpenDeploy supports

"microsoft-microsoft"
Specifies Microsoft SQL Server. Sets a defaultmax-id-length of 128.
"microsoft-inetuna"
Specifies Microsoft SQL Server using an i-net UNA driver. Sets
a default max-id-length of 128.

Not sure about the details of microsoft-inetuna package.

Can anyone tell me the importance of the jar files present in <od-home>/userlib/ folder. Suspecting it to be some environment issue.

In my setup I have only one jar file which is odadapter.jar.

Thanks

Adam Stoller

I believe the jar files in ODHOME/userlib are for custom tuple preprocessors and/or custom OD adaptors - should not be involved with straight-forward DB connectivity.

Girz

Wanted to know what are the standard drivers(jar files) to be available incase of deploying content to MSSQL DB.

<od-home>/drivers/

Using microsoft-microsoft" and "microsoft-inetuna" as the database vendor in the DD deployment descriptor.

Atttached the jar existing in my system for OD

I am using MS SQL DB 2008 R2

Thanks

Rick Poulin

HP is somewhat limited in what drivers it's allowed to ship with the product because of licensing. Just google "microsoft jdbc driver" and you'll get a jar file that you can drop into this folder.

Girz

I did install the sqljdbc4.jar but since I am using a custom dB which is being updated by datadeploy, datadeploy fails to update asking to use inet una driver ...

I don't understand why the database gets hanged while updating . issue still exists

Rick Poulin

Girz wrote:
I am using a custom dB which is being updated by datadeploy

This is nothing special to you. That's what DataDeploy does.

Assuming you have no real reason to be using a special driver, I'd suspect you have an issue in your config files somewhere. Post your odbase.xml, database.xml and ddcfg file.

Tim_P

Hi,

I hope the following information helps.

From https://www.inetsoftware.de/products/jdbc-driver/ms-sql/faq#javasqlsqlexceptiontds-driver-read-timed-out:

"java.sql.SQLException: [TDS Driver]Read timed out

Generally, this error message means that the driver is waiting for an
answer from the SQL Server of its own request. If you like to execute a
command (SELECT, UPDATE, INSERT…) that need more time to finish then
you can increment the query timeout of your statement to resolve the
problem.

The default query timeout is that value of the driver login timeout that
was valid at this time at the connection was created. You can read or
change the login timeout of the Driver Manager with set/getLoginTimeout."

So the error message "Exception Message: [TDS Driver]Read timed out" means that the driver timed out waiting for an answer from the SQL Server.

Your login timeout is currently set to 3 seconds. It could be that it needs more time to create the tables.

In the DataDeploy configuration file edit the "database" line to include a timeout. For example, change:

<database name="microsoft-db" db="<host>:1433?database=<database>" user="<user>" password="<password>" vendor = "microsoft-microsoft" cache-db-connection="no" update-type="standalone" state-field="state" real-update="yes" delete-tracker="yes" enforce-ri="no" max-id-length = "128">

To the following, to add a timeout of 180 seconds to the end (timeout="180"):

Please save the file and then retry the deployment.

Thanks.

--Tim_P
(HP Support)