DB2: Reducing feedback time when connection fails

building reports desktopintelligence
1

We are migrating our underlying database from Teradata to DB2 (on Linux). While converting some reports, I’ve had situations where data providers can be refreshed (on DB2) almost immediately, yet others in the same report fail to connect to the database (standard TCP/IP errors for those that use DB2). What I’m concerned about is that it takes a very long time (so long I couldn’t time it) for the error to come back. Does anyone know of a way to change settings such that either (1) the connectoin to DB2 persists until I close the report or (2) give faster feedback on connection errors.

P.S. I don’t even know why I get connection errors because the database is up and running.

Thanks for any help in advance

trudak (BOB member since 2003-05-02)

2

you can modify the BO connection parameters to hold the connection for x minutes but that may not be the problem. If you could send me some of the errors you get, I might be able to help. See my email address in profile

scott copeland (BOB member since 2002-08-15)