Connecting to and extracting metadata from DB2 z/OS requires certain database permissions. Metadata extraction itself is always read-only and does not modify data, but requires access to system tables to retrieve advanced metadata, such as the SQL definitions of views and stored procedures. Establishing the connection via the JDBC driver separately requires the BINDADD privilege to create the required DB2 packages.
- Required permissions via JDBC driver:
- Before you configure the connection, the database user must have the BINDADD privilege.
- This privilege allows the required DB2 packages to be created when the connection is established, and is separate from the read-only metadata extraction permissions described below.
- Consult your database administrator to ensure that you have the correct privileges.
- Required permissions for metadata extraction:
- The user must have read-only access to DB2 system tables.
- The exact minimal set of permissions varies by DB2 type and version; therefore, no universal grant list can be provided.
- In practice, a Database Administrator (DBA) must be involved to provision a user with sufficient access.
- Recommended approach:
-
Initial validation
- Test the metadata extraction using a full Sys Admin account (with all permissions).
-
This ensures the process works correctly against the target database.
-
Privilege reduction
-
Once validated, the DBA can create a dedicated user with reduced, read-only privileges that still allows successful metadata extraction.
-
-