EM 13c: WebLogic Server12c Patch Procedure Takes a Long Time, OPatch Log Grows Continuously until Disk Partition is Full
(Doc ID 2358587.1)
Last updated on NOVEMBER 16, 2022
Applies to:
Enterprise Manager for Fusion Middleware - Version 13.2.1.0.0 to 13.2.3.0.0 [Release 13.1]Information in this document applies to any platform.
Symptoms
Using Enterprise Manager(EM) 13.2 Cloud Control to apply a patch to a WebLogic Server 12c target causes the patch procedure to take an indeterminately long time.
The procedure will hang on the step "Patch OracleHome with opatch" after the line "Checking for Patches : <number(s)>."
During this time, the OPatch log file (<oracle_home>/cfgtoollogs/opatch/opatch<timestamp>.log) grows continuously until the disk partition is full.
If the patch procedure is allowed to continue until the disk is full, the patch procedure will finally fail.
The procedure log entry in the same "Patch OracleHome with opatch" step will show:
Checking the Oracle Home manually with "opatch lsinventory" at any time during the above shows that the patch was actually successfully applied near the beginning of the patch procedure.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |