Xqe-jdb-0001 Problem Establishing Connection. Please Check The Database Server

Cloud (AWS/GCP/Azure):
Verify security group / firewall rules allow inbound traffic on DB port from your application’s IP.

Verify the DB process is running on the server:

Confirm the DB is accepting connections:

Check authentication and configuration:

Inspect resource usage:

Examine recent changes and incidents: deployments, network changes, cert rotations, firewall rules.

If you’ve gone through all the above and still see the error, gather:

Then engage your DBA or network team – the problem is likely outside Cognos (e.g., VPN tunnel down, DB in recovery mode, or corporate firewall change).

In Cognos Administration → Data Server Connections, double-check: Verify the DB process is running on the server:

Common mistake: Using localhost when the database is on a different machine.

Review the configuration in your reporting tool (e.g., Cognos Data Source Connection). Confirm the DB is accepting connections:

Cognos often gives a secondary error that’s much more useful. Check:

Look for lines containing XQE-JDB-0001 – immediately after, you’ll often see the actual JDBC exception (e.g., “Login failed for user”, “Connection refused”, “Driver not found”). “Login failed for user”

By default, many databases bind only to 127.0.0.1.

This is the silent killer. If you recently upgraded your application or your database version, your old JDBC drivers might be obsolete.