If the Cognos server cannot reach the database server's port (e.g., 1433 for SQL Server, 1521 for Oracle), the connection will fail.
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. If the Cognos server cannot reach the database
Search for the string XQE-JDB-0001 to find the exact underlying exception, such as java.net.ConnectException: Connection refused or com.ibm.db2.jcc.am.DisconnectException . Step 3: Validate Driver Environment Configuration If you share with third parties, their policies apply
Confirm that the database server is online and accepting connections on the correct port from the application server's IP address. Search for the string XQE-JDB-0001 to find the
that indicates the Extensible Query Engine (XQE) cannot establish a handshake with the backend database. While the surface-level message suggests checking the "database server," the root cause often lies in the configuration of the JDBC driver, locale settings, or security protocols. Primary Causes and Solutions Driver Incompatibilities
The most straightforward reason for a connection failure is a blocked or misconfigured network pathway between the IBM Cognos server and the database server.