Page 1 of 1
Posted: Thu Feb 26, 2015 4:00 pm
by ray.wurlod
It's a network dropout ultimately, which makes it interesting that you're able to reproduce it. I think that you need to go to official support on this one - perhaps the call to SQLEndTran to send the COMMIT is also sending something that causes a network interrupt.
Posted: Thu Feb 26, 2015 4:11 pm
by joycerecacho
But COMMIT in a Select Statement?
Re: SQL30108N A connection failed but has been re-establishe
Posted: Thu Feb 26, 2015 4:28 pm
by SURA
Can you able to view the data from Datastage?
Re: SQL30108N A connection failed but has been re-establishe
Posted: Thu Feb 26, 2015 5:13 pm
by joycerecacho
It is a Lookup Sparse which uses parameter at the where condition so I cant view the data, unless I cut it off.
Posted: Thu Feb 26, 2015 7:08 pm
by ray.wurlod
Is the right square bracket in the FROM clause a typo, or the cause of the problem?
Posted: Thu Feb 26, 2015 7:28 pm
by joycerecacho
At the FROM clause there is the table owner as a parameter.
We usually do it at the jobs and it perfectly works.
Posted: Thu Feb 26, 2015 8:36 pm
by qt_ky
The production environment is different in some way.
Try toggling the DB2 Connector stage's "Keep conductor connection alive" setting.
Posted: Mon Mar 16, 2015 8:51 am
by qt_ky
Great! Thank you for sharing the magic setting combination.