My Oracle Support Banner

How to Interpret, Understand and Resolve Common pkg(1) Errors on Solaris 11 (Doc ID 1574718.1)

Last updated on JUNE 12, 2024

Applies to:

Solaris Operating System - Version 11.0 and later
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)

Purpose



At this time, in the event pkg(1M) encounters a problem whilst attempting to install a pkg, install a zone or update a system, it reports a complex message which doesn't always provide a clear explanation as to why the pkg(1M) command failed.  This document aims to clarify the meaning of the most common pkg(1M) failures and provide an explanation, cause and solution for each message. 

 

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Troubleshooting Steps
 Scenario 1: IPS repository image is older than the client
 Scenario 2: The IPS repository is incomplete
 Scenario 3: A pkg fails to install because of a version dependency lock
 Scenario 4: Framework error: code: 35 reason: error: Missing support repository certificate
 Scenario 5: Framework error: code: 28 reason: Operation too slow
 Scenario 6: The requested operation cannot be completed due to invalid package metadata
 Scenario 7: pkg uninstall: The proposed operation cannot be performed on a live image.
 Scenario 8: pkg update fails with message: "User cannot be installed without user database files present." 
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.