Common Error Messages

Inventory is locked during Apply Update

Issue: During Release Update, OPatch inventory may get locked in the following scenarios:

When running ApplyUpdate one or more services were running.
ApplyUpdate process is hung due to some OPatch issue .
Files or folders which needs to be patched are open by some other processes.

[Error during Oracle Home discovery Phase]. 
Detail: OPatchSession cannot load inventory for the given Oracle Home C:\Oracle\Middleware\EPMSystem11R1. 
Possible causes are:
No read or write permission to ORACLE_HOME/.patch_storage
Central Inventory is locked by another OUI instance
No read permission to Central Inventory
The lock file exists in ORACLE_HOME/.patch_storage
The Oracle Home does not exist in Central Inventory

Solution: Find and delete the locks under:

<MIDDLEWARE_HOME>\.patch_storage
<MIDDLEWARE_HOME>\EPMSystem11R1\.patch_storage
<ORACLE_INVENTORY DIR>\Inventory\ (locks folder should be deleted)

Note:

If a file or folder is being used by some other process, close the application or kill the process and re-run the ApplyUpdate script again.

Release Update is run when product is not installed in the environment

Issue: During Release Update if a specific product is not installed in the environment and if ApplyUpdate.ps1 | or ApplyUpdate.sh is run, you will see a warning in the summary and the detail log:

Summary log 
2022/04/05 08:56:36 WARN Failed to apply EssbaseServer OPatch. Check OPatch log for more details

Detail log
The details are:
Patch 33485383: Required component(s) missing : [ oracle.epmsystem.essbase.server, 11.1.2.4.0 ] 
[ Error during Prerequisite for apply Phase]. Detail: OPatch failed during prerequisite checks: 
Prerequisite check "CheckApplicable" failed.
System is intact, OPatch will not restore the system
Recommended actions : This patch requires some components to be installed in the home. Either the Oracle Home doesn't have the components or this patch is not suitable for this Oracle Home.
OPatch failed with error code = 39

Solution: In this case, OPatch (which is internally used by ApplyUpdate script) automatically detects that the product is not installed and skips applying this patch. You will see the following message in the ApplyUpdateDetail-<date>.log

Patch 33485383: Required component(s) missing : [ oracle.epmsystem.essbase.server, 11.1.2.4.0 ] 
[Error during Prerequisite for apply Phase]. Detail: OPatch failed during prerequisite checks: 
Prerequisite check "CheckApplicable" failed.
System is intact, OPatch will not restore the system
Recommended actions : This patch requires some components to be installed in the home. Either the Oracle Home doesn't have the components or this patch is not suitable for this Oracle Home.
OPatch failed with error code = 39

Release Update is run when product is already updated

Issue: During Release Update if a specific product OPatch is already applied in the environment and if ApplyUpdate.ps1 | or ApplyUpdate.sh is run, you will see a warning in the summary and the detail log:

Summary log 
2022/04/05 23:17:47 WARN Failed to apply EssbaseServer OPatch. Check OPatch log for more details

Detail log
The following patch(es) are already installed in the Oracle Home.
[33485386]
Please roll back the existing identical patch(es) first.

Solution: In this case, OPatch (which is internally used by ApplyUpdate script) automatically detects that the product or FMW OPatch is already installed/applied and skips applying this patch. You will see the following message in the ApplyUpdateDetail-<date>.log

The following patch(es) are already installed in the Oracle Home.
[33485386]
Please roll back the existing identical patch(es) first.

Issue:

Unable to run FR (Financial Reporting) reports after applying WebLogic CPU OCT 2022 Patches.
HTML reports are not accessible after rollback of 11.2.12 patches.

Solution:

Create a new directory, for example : Oracle/Middleware/EPMSystem11R1/products/financialreporting/lib/owasp-esapi/resources.
Copy all the properties files (*.properties) from Oracle/Middleware/EPMSystem11R1/products/financialreporting/lib/resources/esapi to the newly created directory.
Edit the ESAPI.properties and update ESAPI.Logger entry as follows:
```
ESAPI.Logger=org.owasp.esapi.logging.slf4j.Slf4JLogFactory
```
Restart all the services.