: Databases use dedicated ports (e.g., IBM Db2 uses 50000 , Microsoft SQL Server uses 1433 , and Oracle uses 1521 ). If a firewall blocks these ports between the servers, the connection drops.
catch (SQLException e) System.err.println("Error Code: " + e.getErrorCode()); System.err.println("SQL State: " + e.getSQLState()); e.printStackTrace();
Navigate to your local installation path: \drivers . : Databases use dedicated ports (e
: IBM Cognos will not recognize newly added JDBC drivers until the IBM Cognos service is completely restarted via the Cognos Configuration tool. 3. Review the Connection String in Cognos Analytics
Any or stack traces found immediately below the error code inside your xqe.log file. Share public link : IBM Cognos will not recognize newly added
– update it and then refresh the application’s connection pool.
Set up monitoring tools (Prometheus, Datadog, Zabbix) to alert you when the database becomes unreachable or connection counts approach the limit. Proactive alerts can catch issues before users notice. Share public link – update it and then
The user interface only displays the generic XQE-JDB-0001 message, hiding the actual Java stack trace. To view the underlying exception:
For scheduled jobs that may encounter transient network glitches, add a retry mechanism (e.g., 3 attempts with exponential backoff). This turns a hard failure into a temporary hiccup.
Thus, the error translates to: The query execution engine, using JDBC, failed to open a network socket or handshake with the target database server.
A: Check <cognos_install>/logs/cogserver.log . Increase logging level for the XQE component via Cognos Configuration → Logging → set “XQE” to “Debug”. Restart the service and reproduce the error.