SQL30108N A connection failed but has been re-established

ray.wurlod · Post by **ray.wurlod** » Thu Feb 26, 2015 4:00 pm

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.

joycerecacho · Post by **joycerecacho** » Thu Feb 26, 2015 4:11 pm

But COMMIT in a Select Statement?

SURA · Post by **SURA** » Thu Feb 26, 2015 4:28 pm

Can you able to view the data from Datastage?

joycerecacho · Post by **joycerecacho** » Thu Feb 26, 2015 5:13 pm

It is a Lookup Sparse which uses parameter at the where condition so I cant view the data, unless I cut it off.

ray.wurlod · Post by **ray.wurlod** » Thu Feb 26, 2015 7:08 pm

Is the right square bracket in the FROM clause a typo, or the cause of the problem?

joycerecacho · Post by **joycerecacho** » Thu Feb 26, 2015 7:28 pm

At the FROM clause there is the table owner as a parameter.
We usually do it at the jobs and it perfectly works.

qt_ky · Post by **qt_ky** » Thu Feb 26, 2015 8:36 pm

The production environment is different in some way.

Try toggling the DB2 Connector stage's "Keep conductor connection alive" setting.

qt_ky · Post by **qt_ky** » Mon Mar 16, 2015 8:51 am

Great! Thank you for sharing the magic setting combination.

DSXchange

SQL30108N A connection failed but has been re-established

Re: SQL30108N A connection failed but has been re-establishe

Re: SQL30108N A connection failed but has been re-establishe