IBM AIX 7.2 – Common Problem 108 – 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

oslevel -s differs from oslevel -r after a Service Pack install.

Environment & Reproduction

Partial installp run on AIX 7.2 left some filesets at older level.

Root Cause Analysis

Missing or failed prerequisites prevented committing the SP fully.

Quick Triage

Run oslevel -s and oslevel -rq to compare current vs latest known levels.

Step-by-Step Diagnosis

Use instfix -i | grep ML and lppchk -v to find broken filesets.

Solution – Primary Fix

Re-run installp -agXYd /mnt/sp /software-bundle to finish the SP install.

Solution – Alternative Approaches

Use update_all on an alt_disk_copy clone instead of the active rootvg.

Verification & Acceptance Criteria

oslevel -s matches the target SP and lppchk -v reports no missing requisites.

Rollback Plan

Boot from the alt_disk_copy clone with bosboot if the update misbehaves.

Prevention & Hardening

Always alt_disk_copy before installp and verify with lppchk -v afterwards.

Related Errors & Cross-Refs

Often pairs with lppchk dependency warnings and broken commit states.

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 Docs: installp, oslevel, lppchk, alt_disk_install.