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.6 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/de9f85ba-e77f-48fd-8c66-f5ebaf32d655 | Oracle Relational Database | optional | 15-1242.00 | model-knowledge | high | 0 | gemma3:27b (prompt-designed and spot-checked by Claude) | 2026-07-10 |
Oracle Relational Database — Database Administrator
For a Database Administrator (DBA), 'Oracle Relational Database' competence isn’t just knowing Oracle exists; it's being fluent in its ecosystem for daily operational tasks. This means proficiently using SQL and PL/SQL to query, manipulate, and tune database performance – think writing complex queries to troubleshoot slow reports, creating stored procedures for automated data processing, or optimizing indexes based on AWR (Automatic Workload Repository) reports. You'll be constantly monitoring the database health via tools like Enterprise Manager (OEM), Data Pump for backups/restores, and RMAN (Recovery Manager) for disaster recovery planning & execution.
Daily work heavily involves capacity planning – predicting future storage needs, managing tablespaces, and ensuring sufficient resources are available. A significant portion is also dedicated to security: implementing user roles and permissions, auditing database activity, and applying patches/upgrades to address vulnerabilities. Troubleshooting often means deciphering alert logs, tracing execution plans, and identifying locking issues using tools like v$ views. Good DBAs proactively identify potential problems before they impact users.
The biggest pitfalls are ignoring performance trends (leading to outages), inadequate backup strategies (data loss!), and failing to stay current with Oracle releases/security updates. A 'good' DBA isn’t just reactive; they automate repetitive tasks using scripting (Shell, Python) and proactively monitor key metrics. They understand the interplay between database configuration parameters (init.ora/spfile) and application requirements. Knowing how to effectively use tools like SQL Developer or Toad for development & administration is also crucial.
Finally, this competence extends beyond just technical skill. It requires understanding Oracle’s architecture – memory structures (SGA, PGA), processes, and storage mechanisms – to diagnose complex issues and design scalable solutions. It's about being able to explain database concepts clearly to developers and other stakeholders, and translating business requirements into efficient database designs.
Weitere Anreicherung
Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).