If you back up and restore DB2 multiple times a day to refresh data, Strategy may fail and the connection times out until the Warehouse Catalog is refreshed. The connections work correctly again after reading the tables for that instance via the Warehouse Catalog.
In the
DSSErrors.log, the following error message can be seen:
Current error...2020-03-30 16:02:00.866-04:00 [HOST:env-128055laio2use1][SERVER:CastorServer][PID:11595][THR:139783395591936][Database Classes][Error][UID:9743335811EA2D7185CB0080EFD5210A][SID:52DDD608AE3ECE840DDEEAB68AF3EE10][OID:0DF1DD9D4FEE84D87DF6CFA5CC8E4A5B] Connect failed. Unable to connect.
When the DB2 warehouse is restored, it takes much more time to connect to the data source the first time, as described in Binding for Db2 Driver.
You must have the appropriate privileges for the driver to create and bind packages. The privileges are:
The initial driver connection to a particular server may take a few minutes because of the number and size of the packages that must be created on the server. Subsequent connections do not incur this delay.
The default connect timeout is 60s for a report, and if it takes more than 60 seconds to connect to the source, a report will return a hang error. The default connect timeout is 300 seconds for the Warehouse Catalog, so reading the tables for that instance via the Warehouse Catalog can succeed. Once the first connection is successful, the following connection can succeed in a shorter time.
You can set the connection timeout on the Database Instance. Change the timeout from the default of 60 to 300.
