Does anyone know how to get past this error.
The error has just started to occur once the query is run against the production database. Before this the query executed a lot quicker may be 20 second or so. Now the underlying query takes about 2.5 minutes to run.
We are trying to running our query against a DB2 database running on Solaris/NT.
It seems to me that the DB2 adapter is using the default command timeout for the DB2 .NET provider of 30 seconds.
I cannot find anyway to configure the DB2 adapter to run queries that run longer than 30 seconds.
Can anyone confirm that this a limitation for th Db2 adapter querying against a DB2 database running on Solaris/NT?