IBM Db2 13 z/OS DBA Professional study materials
IBM Db2 13 z/OS DBA Professional study resources

IBM Db2 13 z/OS DBA Professional study plan

IBM Db2 13 z/OS DBA Professional · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Db2 13 for z/OS Database Administration

  • Map the Db2 13 for z/OS object hierarchy (storage group, database, table space, table, index) and draw it from memory without notes

  • Configure a scratch Db2 13 subsystem or sandbox and create partitioned table spaces with different page sizes, then verify allocations through catalog queries

  • Write and run catalog queries against SYSIBM.SYSTABLESPACE, SYSIBM.SYSTABLES, and SYSIBM.SYSINDEXES to confirm physical attributes of what you created

  • Explain the differences between segmented, partitioned-by-growth, and range-partitioned universal table spaces and pick the right one for three sample workloads

Your checkpoint

A one-page table space decision matrix plus a saved set of catalog queries that reproduce the structure of a test database

Week 2

Db2 13 for z/OS Database Administration & Db2 13 for z/OS Performance and Tuning

  • Design and implement referential integrity constraints and check constraints on a test schema, then test insert and delete behavior

  • Create and alter indexes (including index on expression and include-column indexes) and measure the effect on access path selection

  • Analyze RUNSTATS output and explain how COLGROUP statistics and histogram statistics influence the optimizer for skewed data

  • Draft a schema change procedure covering DDL versioning, pending alterations, and REORG requirements

Your checkpoint

A schema change runbook with before-and-after EXPLAIN output showing at least one access path improvement

Week 3

Db2 13 for z/OS Performance and Tuning

  • Read EXPLAIN and PLAN_TABLE output for at least five queries and identify the chosen access path, join method, and sort behavior

  • Force alternative access paths with optimization hints or catalog statistics and compare predicted costs

  • Set up a monitoring baseline using Db2 statistics and accounting traces, and interpret key performance fields for CPU, getpage, and lock wait

  • Tune a deliberately slow query by adding an index or rewriting predicates, and document the measured before/after difference

Your checkpoint

A query tuning case study with EXPLAIN snapshots and trace-derived metrics for three queries

Week 4

Db2 13 for z/OS Performance and Tuning & Db2 13 for z/OS Availability and Recovery

  • Explain the Db2 log architecture (active logs, archive logs, BSDS) and describe what happens to each during a failure

  • Configure and test copy and recovery utilities in a sandbox, including inline image copies taken during REORG

  • Perform a point-in-time recovery of a table space and verify data consistency afterward

  • Interpret checkpoint and log-related statistics to spot recovery risk before an outage occurs

Your checkpoint

A recovery test report documenting a successful point-in-time table space recovery with the commands used and verification steps

Week 5

Db2 13 for z/OS Availability and Recovery

  • Compare conditional restart options and describe when each is appropriate after an abnormal termination

  • Design a backup strategy that balances full image copies, incremental copies, and log-based recovery against recovery time objectives

  • Describe data sharing considerations for recovery, including group attach and coupling facility structure failure scenarios

  • Practice recovering an index and a table space independently and confirm how Db2 handles index rebuild versus index recovery

Your checkpoint

A written backup and recovery strategy for a two-member data sharing group with stated RTO and RPO assumptions

Week 6

Db2 13 for z/OS Security and Utilities

  • Implement role-based authorization using roles, trusted contexts, and secondary authorization IDs, and test privilege inheritance

  • Explain and apply row and column access control with column masks and row permissions on a test table

  • Run LOAD, REORG, RUNSTATS, and UNLOAD utilities with appropriate parameters and verify output and catalog updates

  • Describe utility restart and termination behavior and the role of the Db2 utilities panel in managing concurrent utility jobs

Your checkpoint

A security configuration worksheet plus a utility job library with working JCL for LOAD, REORG, RUNSTATS, and UNLOAD

Week 7

Db2 13 for z/OS Security and Utilities & Db2 13 for z/OS Availability and Recovery

  • Audit authorization failures and privilege escalation paths using catalog authorization tables and audit trace output

  • Configure audit trace classes for a specific compliance scenario and explain the performance tradeoff

  • Describe utility impact on availability, including when REORG with inline copy allows concurrent access and when it does not

  • Review Db2 13 changes relevant to security and utilities and note which affect existing procedures

Your checkpoint

An audit and compliance checklist mapping required trace classes to specific authorization events, with a short note on availability impact

Week 8

Db2 13 for z/OS Database Administration & Db2 13 for z/OS Performance and Tuning & Db2 13 for z/OS Availability and Recovery & Db2 13 for z/OS Security and Utilities

  • Complete a full-length timed practice assessment across all four domains and score it by domain

  • Re-study the two weakest subareas identified by the practice assessment and re-test those areas

  • Write out from memory the catalog queries, recovery commands, and utility parameters you most often got wrong

  • Build a final one-page reference sheet covering access path rules, recovery decision points, and authorization model terms

Your checkpoint

A timed practice assessment score report with a per-domain breakdown and a one-page personal reference sheet

Milestones

Week 2: Can explain universal table space types and create each from memory, and can read EXPLAIN output for a simple query without reference material

Week 4: Successfully completed a point-in-time table space recovery in a sandbox and can describe log and BSDS behavior during failure

Week 6: Demonstrates working row and column access control and can run the four core utilities with correct parameters

Week 8: Scores at or above target on a timed full-domain practice assessment, with no domain below a self-set floor