Also, the following error is continuously seen in the DSSErrors logs.
Error type: System call error. Error communicating with connection process. Child Process hung: Command ConnectionSetConnectionParameters.
2011-01-27 03:41:20.979+08:00 Cannot execute command because there was an error on a previous command
A separate DSN is being used for the Statistics DB connection. Also, it is seen that the Statistics database can be connected to from DB Query Tool.
CAUSE
This behavior can be seen in cases where the time to create a connection to the Statistics database takes more than 20 seconds. When creating a Statistics database connection, the default connection attempt timeout is 10 seconds. The DB Classes layer adds 10 seconds to provide leeway for restrictive connection attempt timeouts such as this case and this is the reason why this issue is seen only in cases where the connection to the Statistics database takes more than 20 seconds.
The Statistics database connection has this 10 seconds timeout value hard coded and does not use the parameters that are set through Strategy Developer on the DB connection editor.
ACTION
Users should investigate why the connection time is greater than 20 seconds. Typically, it should not take more than 20 seconds to establish a connection. A connection time of 20 or more seconds are indicative of some network issue and this can cause other performance issues.
In some cases, the connectivity time drastically improves when the IP address of the database server name is used instead of the host name, when defining the DSN.
If the connection time is greater with the use of a hostname as compared to IP address, it is indicative of issues with the DSN configuration and users should look into fixing that.
