---
esco_uri: http://data.europa.eu/esco/skill/84251cb1-babf-4d17-a3cd-baa642c24c8d
esco_label: "IBM Informix"
relation: optional
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
---

# IBM Informix — Database Administrator

As an Informix DBA, 'competence' in IBM Informix isn’t just *knowing* it exists; it's being able to keep critical business systems running on it. Daily tasks revolve around performance monitoring (using tools like `onstat`, `sysmaster`), backup/recovery (`onbar`), and ensuring data integrity. You'll spend time troubleshooting slow queries – often involving analyzing execution plans with `explain` and tuning indexes. A big part is also user management, security configuration, and applying maintenance releases/patches without disrupting service. It’s a hands-on role; expect to be in the shell frequently.

Typical work isn't glamorous 'designing' databases (though you might do some schema changes), but *maintaining* existing ones. You'll deal with log file analysis, space management (tablespaces!), and potentially replication setup/monitoring if high availability is required.  Pitfalls include misconfigured caching parameters leading to performance bottlenecks, failing to properly test backups before a disaster, or overlooking security vulnerabilities in user permissions. Knowing the difference between `dbaccess` vs. `isql` for different tasks is crucial.

What 'good' looks like isn’t just fixing problems *when* they happen, but proactively preventing them. This means automating routine maintenance with scripts (shell/perl are common), setting up alerts for critical thresholds in `onstat`, and having a solid disaster recovery plan that's regularly tested.  Understanding the nuances of Informix’s storage engine – its clustered architecture and how it impacts performance – is key to being truly effective.

While newer database technologies dominate headlines, many organizations *still* rely heavily on Informix for legacy applications. Therefore, a good DBA needs not only technical skill but also an understanding of the business impact of database downtime and the ability to communicate effectively with application developers and system administrators.

## Weitere Anreicherung

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