---
esco_uri: http://data.europa.eu/esco/skill/744442ac-c157-4350-8be0-ce454df4f5c5
esco_label: "perform ICT troubleshooting"
relation: essential
onet_soc: 15-1242.00
source: model-knowledge
confidence: high
qa_count: 0
generator: gemma3:27b (prompt-designed and spot-checked by Claude)
generated: 2026-07-10
---

# perform ICT troubleshooting — Database Administrator

For a Database Administrator (DBA), 'perform ICT troubleshooting' isn’t about fixing user laptops – it’s about maintaining *database availability* and performance. Daily, this means quickly diagnosing issues impacting database servers, storage systems, network connectivity to those systems, or even the operating system itself. A typical task might be investigating slow query performance (is it the query, indexes, statistics, or underlying disk I/O?), a failed backup job (permissions issue? Storage full? Network glitch?), or an unexpected service outage. It's less 'rebooting things' and more 'methodically isolating the root cause'.

Tools DBAs use for troubleshooting are specialized: performance monitoring tools (like SolarWinds, Datadog, or database-specific tools like SQL Server Profiler/Extended Events), OS logging (Windows Event Viewer, Linux syslog), storage array health dashboards, and network diagnostic utilities (ping, traceroute, netstat).  Pitfalls include jumping to conclusions *before* gathering data – assuming a query is slow when the issue is actually disk contention. Another common mistake is ignoring seemingly unrelated logs; a database error might be triggered by an OS-level problem.

A 'good' DBA doesn’t just fix the immediate symptom, but identifies and addresses the underlying cause to prevent recurrence. This means documenting troubleshooting steps, updating runbooks with new solutions, and potentially collaborating with system administrators or network engineers. Proactive monitoring and alerting are key – catching issues *before* users report them is ideal.  It also involves understanding how database changes (schema updates, patching) can introduce unforeseen problems.

Finally, remote access troubleshooting is crucial. DBAs often support databases across multiple locations/cloud providers. Being able to securely diagnose and resolve issues remotely using tools like SSH, RDP, or cloud provider consoles is a core skill. This requires strong security awareness – ensuring access is audited and minimized.

## Weitere Anreicherung

Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).
