6b3b2abe4f
73 stackexchange-grounded, 516 model-knowledge (ESCO-seeded gemma3), 0 review_needed (calibration caveat documented). Adapters rebuilt with the full competence sets; final REPORT numbers; all verify checks pass. Known gap: engineering-manager lacks an ESCO package counterpart. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PDKeXvpT6tENSvyQGLV1Uq
2.4 KiB
esco_uri, esco_label, relation, onet_soc, source, confidence, qa_count, generator, generated
| esco_uri | esco_label | relation | onet_soc | source | confidence | qa_count | generator | generated |
|---|---|---|---|---|---|---|---|---|
| http://data.europa.eu/esco/skill/3cee858e-79e8-4a4b-b99f-93c7f735d58b | DB2 | optional | 15-1242.00 | model-knowledge | high | 0 | gemma3:27b (prompt-designed and spot-checked by Claude) | 2026-07-10 |
DB2 — Database Administrator
As a Database Administrator working with DB2, 'DB2 competence' isn’t just knowing it exists – it's being able to reliably deliver performance, availability, and data integrity within an IBM DB2 environment. Daily tasks revolve around monitoring database health (using tools like DB2 Command Line Processor, Data Studio, or third-party monitoring suites), applying maintenance (patching, reorgs, runstats), managing user access & security, and troubleshooting performance bottlenecks. You'll be constantly analyzing explain plans to optimize queries, tuning buffer pools, and ensuring adequate storage capacity.
Specifically, you’ll spend time configuring and maintaining high availability features like HADR (High Availability Disaster Recovery) or pureScale clusters – understanding how these work under the hood is crucial. Expect to deal with log management, backup/recovery strategies (using tools like db2backup and restore), and potentially working with DB2's catalog databases and node directory servers in distributed environments. A good DBA anticipates issues by proactively monitoring key metrics and automating routine tasks.
A common pitfall is treating DB2 as a 'black box'. Effective DBAs dig into the internals – understanding locking, transaction isolation levels, and how DB2 utilizes system resources. Another is neglecting regular health checks; deferred maintenance always leads to bigger problems down the line. Ignoring proper indexing or writing inefficient SQL are also frequent sources of performance issues you'll be tasked with resolving.
What 'good' looks like is a stable, performant database environment that meets business SLAs. It means being able to quickly diagnose and resolve incidents, proactively identify potential risks, and contribute to database design decisions that optimize for scalability and maintainability. It also involves staying current with new DB2 features and best practices – IBM frequently releases updates and enhancements.
Weitere Anreicherung
Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).