It may be that even though you successfully ran the Insight Setup tool to configure Insight, and the Setup tool had no problems connecting to the remote DB2 databases, neither Insight nor Cognos can connect to these databases.
If you have this problem, running an Insight report from Cognos Connection results in the error:
The logon failed
You may also see this error in cogserver.log:
Failure QE-DEF-0285 The logon failed.QE-DEF-0325 The logon failed for the following reason:RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in: RIDW UDA-SQL-0031 Unable to access the "RIDW" database. Check that the connection parameters to the database are configured correctly. For example, ensure that the data source connection contains the signon information, such as a password, to connect to the database.UDA-SQL-0107 A general exception has occurred during the operation "attach".
There are configuration problems that can prevent Insight from connecting to a remote DB2 database that won't impact Insight Setup because Setup tests the connection to the remote DB2 database via the JDBC thin driver, which is not impacted by configuration problems with operating system environment variables.
Things to check
If Insight is installed on a different server than DB2, find out whether the DB2 databases you cannot connect to from the Insight system were cataloged locally with the DB2 client (on the Insight system).
In addition, if you are using a 64-bit DB2 client on UNIX, please check your LD_LIBRARY_PATH environment variable to see if the 32-bit DB2 libraries are present.
To fix the problem
If using UNIX, and your system does not have the 32-bit IBM DB2 libraries in LD_LIBRARY_PATH, you should resolve this configuration issue as described in the DB2 considerations documentation.
If Insight is installed on a different server than DB2, the DB2 databases need to be cataloged locally with the DB2 client (on the Insight system). You can find instructions on how to do this in the How to setup a DB2 V9 remote CLM Data Warehouse on a reporting server location Jazz article.
You should also verify that the WAS JVM Process owner has the db2profile sourced into the JVM session (see Step 5 in the How to setup a DB2 V9 remote CLM Data Warehouse on a reporting server location Jazz article).