EM 13.5 : OMSPatcher Fails With EMLCMPackage not found in repository
(Doc ID 2964121.1)
Last updated on AUGUST 10, 2023
Applies to:
Enterprise Manager Base Platform - Version 13.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
In Enterprise Manager (EM) 13.5 Cloud Control while trying to apply Release Update (RU) system patch using the traditional method is failing with:
<OMS_HOME>\cfgtoollogs\omspatcher\<timestamp>_SystemPatch_<patch_number>\omspatcher_<timestamp>_apply.log:
[MM DD, YYYY HH:MM:SS PM] DB user name: SYSMAN is used for db connection
[MM DD, YYYY HH:MM:SS PM] DB user name: SYSMAN is used for db connection
[MM DD, YYYY HH:MM:SS PM] Checking if current RU version is valid to load LCM package :true
[MM DD, YYYY HH:MM:SS PM] DB user name: SYSMAN is used for db connection
[MM DD, YYYY HH:MM:SS PM] Checking if EMLCMPackageExist in repository.
[MM DD, YYYY HH:MM:SS PM] EMLCMPackage not found in repository.
[MM DD, YYYY HH:MM:SS PM] Checking isUpgradedLCMUserExist
query:select value from SYSMAN.LCM_ADMIN_PROPERTIES where name='LCM_ADMIN_USER_VERSION'
[MM DD, YYYY HH:MM:SS PM] DB user name: SYSMAN is used for db connection
[MM DD, YYYY HH:MM:SS PM] DB user name: SYSMAN is used for db connection
[MM DD, YYYY HH:MM:SS PM] DB user name: SYSMAN is used for db connection
[MM DD, YYYY HH:MM:SS PM] Checking if current RU version is valid to load LCM package :true
[MM DD, YYYY HH:MM:SS PM] DB user name: SYSMAN is used for db connection
[MM DD, YYYY HH:MM:SS PM] Checking if EMLCMPackageExist in repository.
[MM DD, YYYY HH:MM:SS PM] EMLCMPackage not found in repository.
[MM DD, YYYY HH:MM:SS PM] Checking isUpgradedLCMUserExist
query:select value from SYSMAN.LCM_ADMIN_PROPERTIES where name='LCM_ADMIN_USER_VERSION'
[MM DD, YYYY HH:MM:SS PM] DB user name: SYSMAN is used for db connection
Cause
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
Symptoms |
Cause |
Solution |
References |