IBM AIX 7.1 – Common Problem 105 – 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

smit menus exit with ‘ODM database locked’ errors.

Environment & Reproduction

Concurrent smit/installp sessions or a crashed installer left a lock.

Root Cause Analysis

Stale lock files under /etc/objrepos/..lock remain on disk.

Quick Triage

Check for running installp, lppchk or smit with ps -ef | egrep ‘installp|smit’.

Step-by-Step Diagnosis

Inspect /etc/objrepos/*.lock and verify no PID still owns the file.

Solution – Primary Fix

Remove stale lock files only after confirming no installer runs: rm /etc/objrepos/lock.

Solution – Alternative Approaches

Reboot the LPAR if the lock cannot be cleared safely.

Verification & Acceptance Criteria

smit launches normally and lslpp -L completes without locking errors.

Rollback Plan

Restore from a mksysb-era /etc/objrepos backup if ODM is corrupted.

Prevention & Hardening

Avoid running multiple installp/SMIT sessions and use cfgmgr serially.

Related Errors & Cross-Refs

May appear after a failed installp run or aborted alt_disk_copy.

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

View all aix-7.1 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

IBM Docs: ODM, installp locking and smit troubleshooting.