It was the seventh time that hour. Nora Chen stared at the terminal, her coffee long gone cold. The error wasn’t new—it had appeared three weeks ago, flickering like a bad omen across her monitor. But tonight, something felt different. The logs showed the connection dropping not at peak load, but during maintenance windows, when the database server reported zero external queries.
What the error string implies
When running reports via Dynamic Query Mode (DQM), Cognos bypasses older native client connections (Compatible Query Mode) and utilizes the Java-based Extensible Query Engine (XQE). The XQE relies exclusively on Type 4 JDBC drivers located within the Cognos directory structure ( \drivers ). When XQE issues a connection call and receives an unhandled socket exception, a connection timeout, or a fatal handshake failure from the underlying driver, it wraps that message into the generic wrapper: . 4 Most Common Root Causes and Fixes It was the seventh time that hour
. It indicates that the Cognos Query Engine (XQE) is unable to communicate with the underlying database server. Common Causes Incompatible JDBC Drivers
She never told Marcus. Some ghosts, she decided, are better left in the pipeline. But tonight, something felt different
Did this error start happening after a recent or driver update ?
sudo systemctl status postgresql (or mysql / mariadb / oracle ) The XQE relies exclusively on Type 4 JDBC
1. JDBC Driver Version Incompatibilities (e.g., IBM JCC Driver Bug)
Confirm the database server is listening on the expected port (e.g., 1433 for SQL Server) and that no firewall is blocking the traffic.