DSXchange: DataStage and IBM Websphere Data Integration Forum
View next topic
View previous topic
Add To Favorites
Author Message
raji33



Group memberships:
Premium Members

Joined: 23 Sep 2010
Posts: 147
Location: NJ
Points: 1222

Post Posted: Fri Feb 02, 2018 11:43 am Reply with quote    Back to top    

DataStage® Release: 8x
Job Type: Parallel
OS: Unix
Team,

We are getting the below error while connecting to Big SQL through DB2 connector. We did catalog and configured isjdbc.config file as well. Any suggestions please?

DB2_Connector_0: DB2 function SQLFetch failed: SQLSTATE = 40504: Native Error Code = -1,229: Msg = [IBM][CLI Driver][DB2/LINUXX8664] SQL1229N The current transaction has been rolled back because of a system error. SQLSTATE=40504 (CC_DB2Connection::queryServerHostName, file CC_DB2Connection.cpp, line 3,246)

Thanks
asorrell
Site Admin

Group memberships:
Premium Members, DSXchange Team, Inner Circle, Server to Parallel Transition Group

Joined: 04 Apr 2003
Posts: 1656
Location: Colleyville, Texas
Points: 22565

Post Posted: Fri Feb 02, 2018 12:43 pm Reply with quote    Back to top    

SQLState 40504: A system error has caused the unit of work to be rolled back.
SQLCode -1229: The current transaction has been rolled back because of a system error.

https://www.ibm.com/support/knowledgecenter/en/SSEPGG_10.5.0/com.ibm.db2.luw.messages.sql.doc/doc/msql01229n.html

Doesn't say "why". You'll need to get your DB2 DBA to see what he sees on his side. Should be log with more info from their side.

_________________
Andy Sorrell
Certified DataStage Consultant
IBM Analytics Champion 2009 - 2017
Rate this response:  
Not yet rated
UCDI



Group memberships:
Premium Members

Joined: 21 Mar 2016
Posts: 289

Points: 2862

Post Posted: Mon Feb 05, 2018 10:54 am Reply with quote    Back to top    

It does say why Smile The error code can be tapped online to see what the root causes and resolutions might be. This almost always leads back to a DBA, though, but at least you can see what is happening.

I think this is what you seek:
https://www.ibm.com/support/knowledgecenter/SSEPGG_9.5.0/com.ibm.db2.luw.messages.sql.doc/doc/msql01229n.html


Another hit by google said "big sql can have this error due to connection problems caused by high activity"

I would re-run it once more, and if it dies again, get with the DBA.
Rate this response:  
Not yet rated
Display posts from previous:       

Add To Favorites
View next topic
View previous topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



Powered by phpBB © 2001, 2002 phpBB Group
Theme & Graphics by Daz :: Portal by Smartor
All times are GMT - 6 Hours