Lock file left by a different patch, Opatch would not try re-using the lock file.

Source: Internet
Author: User

Opatch was interrupted during the patching process and reported the following error after re-execution:

Utilsession Failed:lock file left by a different patch, Opatch would not try re-using the Lock file. Log File Location:/u11/app/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/14084247_apr_16_2016_13_21_29/ Apply2016-04-16_13-21-29pm_1.logopatch failed with error code 73

Viewing the log file also reported similar errors.
The reason is that the lock is still held on the local inventory after the previous Opatch session failed

Workaround:

1. Take a backup of  $ORACLE _home/.patch_storage2. Remove $ORACLE _home/.patch_storage/patch_locked% rm $ORACLE _home/.patch_storage/patch_locked3. Create $ORACLE _home/.patch_storage/patch_free% Touch $ORACLE _home/.patch_storage/patch_free4. Verify that "Opatch lsinventory" no longer reports the error% Opatch Lsinventory-detail

Lock file left by a different patch, Opatch would not try re-using the lock file.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.