IBM AIX 7.2 – Common Problem 229 – Diagnosis and Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

ODM is corrupt; lslpp, lsdev, installp queries fail with 0518-xxx errors.

Environment & Reproduction

Triggered after abrupt shutdowns, failed installp, or disk pressure on /etc/objrepos.

Root Cause Analysis

ODM stanzas in /etc/objrepos, /usr/lib/objrepos, /usr/share/lib/objrepos are missing or bad.

Quick Triage

Run lppchk -v and df -k / to confirm filesystem health and ODM integrity.

Step-by-Step Diagnosis

Inspect failing classes with odmget CuDv | head and review errpt for ODM events.

Solution – Primary Fix

Rebuild ODM from a recent mksysb or savevg copy, then verify with lppchk -v.

Solution – Alternative Approaches

Use installp -ac and inuclean to repair partial installs, or restore classes with odmadd.

Verification & Acceptance Criteria

lppchk -v is clean and installp -s reports no pending state.

Rollback Plan

Restore /etc/objrepos.bak if fileset state becomes inconsistent, then bosboot -a.

Prevention & Hardening

Take mksysb before installp and keep /etc/objrepos on a healthy rootvg disk.

Related Errors & Cross-Refs

Related to bosboot failures, lppchk warnings, and failed installp commits.

Related tutorial: View the step-by-step tutorial for aix-7.2.

View all aix-7.2 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

IBM AIX 7.2 documentation on ODM and installp troubleshooting.