Preflight checks for IBM Db2 for LUW
Before running the IBM Db2 for LUW crawler, run preflight checks to perform necessary technical validations.
Before running the IBM Db2 for LUW crawler, you can run preflight checks to perform the necessary technical validations. The following preflight checks are completed:
Connectivity check
Verifies that Atlan can reach your server and confirms it's a Db2 for LUW system by reading the reported service level.
✅ IBM Db2 for LUW version: $version
❌ Version string '$version' does not start with 'DB2 v' — the endpoint may not be a IBM Db2 for LUW system; verify the connection URL
❌ Version check failed: $error
A version string that doesn't begin with DB2 v means the connection reached a Db2 server that isn't a LUW server. Use the IBM Db2 for z/OS connector for a z/OS subsystem.
Common connection failures include SQL30081N when the host or port is wrong, and SQL30082N when the credentials are rejected. If the version probe fails with -551, grant the Atlan user access to the administrative view.
Permissions check
Verifies that the Atlan user can read the database system catalog.
✅ All required catalog permissions verified
❌ SELECT permission denied (vendor error -551): $error
⚠️ Skipped — connectivity failed
A -551 failure means the user can't read one of the catalog views Atlan queries - check the catalog access.
Object count check
Counts the non-system schemas that match the include and exclude filters.
✅ Found $schemaCount non-system schemas
❌ No non-system schemas are visible — nothing would be crawled. Verify the login's catalog visibility and the include/exclude filter.
⚠️ Skipped — permissions check failed
⚠️ Skipped — connectivity failed
See also
- Crawl IBM Db2 for LUW: Run the crawler after preflight checks pass
- Set up IBM Db2 for LUW: Configure connection and authentication