SQL30081N

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
kanasai167
Participant
Posts: 63
Joined: Mon Sep 12, 2011 2:11 am

SQL30081N

Post by kanasai167 »

Hi All
does any one know how to solve this bug on datastage.

DB2_Connector_0: SQLEndTran(SQL_COMMIT) reported: SQLSTATE = 08007: Native Error Code = -30,081: Msg = [IBM][CLI Driver]
SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP".
Communication API being used: "SOCKETS". Location where the error was detected: "10.10.50.58".
Communication function detecting the error: "send". Protocol specific error code(s): "10054", "*", "0".
SQLSTATE=08001 (CC_DB2Connection::commit, file CC_DB2Connection.cpp, line 1,491)

Thanks
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

I think that a bit more information is required.

- Does it always occur
- Does it only occur for one table or for all tables?
- Has this ever worked before and now no longer works?
- Since "commit" is mentioned, what are your commit settings in the stage?
- Can you read from this table?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Why does a communication error on your system constitute a bug? :?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
kanasai167
Participant
Posts: 63
Joined: Mon Sep 12, 2011 2:11 am

Post by kanasai167 »

Hi
this problem is just occur recently, previous running prefectly, i was able read from that table. there is no any commit setting in the stage.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

- Is this a sporadic error or does it always occur? If it always occurs, does it always occur on the same record / after the same amount of data?
- What has changed between the time it worked and now? Both in the job, the table, the database and the system
- Are you writing large amounts of data? If you specify a commit interval (e.g. 10,000 rows) does the error no occur?
kanasai167
Participant
Posts: 63
Joined: Mon Sep 12, 2011 2:11 am

Post by kanasai167 »

It occurs everytime on the same job and same record count (which is equal to the total record count within the job , 11+ million rows of records.)
No changes on the job, but there is some database configuration changes on the logging part.

Where i can set the commit interval ? Is it the array size in DB2 connector stage ?

Thanks
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

The commit frequency is set under "Transaction -> Record Count" in the connector stage.
kanasai167
Participant
Posts: 63
Joined: Mon Sep 12, 2011 2:11 am

Post by kanasai167 »

what is the recommendation record count if my job is around 11+ million rows of records?

Thanks
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

There are far too many variables at play for us to make anything other than a poor guess... IMHO it would be best to take that question to your DBA.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply