EM 13C:Agent Patch Plan Fails At Analyze With Error "The lock file .lock is still present in the patch stage location"
(Doc ID 3038811.1)
Last updated on AUGUST 02, 2024
Applies to:
Enterprise Manager Base Platform - Version 13.5.0.0.0 to 13.5.0.0.0 [Release 13c]Information in this document applies to any platform.
Symptoms
In Enterprise Manager Cloud Control Analyze of Agent Patch Plan fails:
From console on step CheckIfPatchAlreadyStaged
Wed Jul 31 14:34:24 2024 - [INFO] The lock file .lock is already present in the patch stage location /<dir>/p<patch_num>_XXX, so wait 2 s...
Wed Jul 31 14:34:26 2024 - [INFO] The lock file .lock is already present in the patch stage location /<dir>/p<patch_num>_XXX, so wait 2 s...
Wed Jul 31 14:34:28 2024 - [ERROR] The lock file .lock is still present in the patch stage location /<dir>/p<patch_num>_XXX even after waiting for 319 sec, the specified timeout. The cause may be that the lock file ".lock" was not successfully deleted from the directory "/<dir>/p<patch_num>_XXX" in the last patch file staging activity. Delete the lock file ".lock" from the directory "/<dir>/p<patch_num>_XXX" manually and retry.
Wed Jul 31 14:34:26 2024 - [INFO] The lock file .lock is already present in the patch stage location /<dir>/p<patch_num>_XXX, so wait 2 s...
Wed Jul 31 14:34:28 2024 - [ERROR] The lock file .lock is still present in the patch stage location /<dir>/p<patch_num>_XXX even after waiting for 319 sec, the specified timeout. The cause may be that the lock file ".lock" was not successfully deleted from the directory "/<dir>/p<patch_num>_XXX" in the last patch file staging activity. Delete the lock file ".lock" from the directory "/<dir>/p<patch_num>_XXX" manually and retry.
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 |