When performing software patching in an Oracle environment, encountering errors can be frustrating and time-consuming. One such error, OPatchAuto Error Code 255, often halts the patching process, leaving administrators scrambling for solutions. In this blog post, we’ll delve into the causes of this error and provide a comprehensive troubleshooting guide to help you resolve it efficiently.
OPatchAuto Error Code 255 typically indicates a failure during the bootstrapping process, essential for initializing the patching operation. This error can arise for various reasons, including environment setup issues, missing prerequisites, or problems with the patch itself. To effectively troubleshoot this error, analyzing the potential causes and taking appropriate corrective actions methodically is essential.
Here are some steps you can take to troubleshoot and resolve this issue:
- Review log files
- Verify Environment setup
- Check patch readiness
- Check for known issues
- Manual patching
etc
The opatchauto analyze failed with the error 255. After reviewing the logs, the main issue was identified: “The bootstrap execution failed because it Failed to unzip files.”
[root@ORA-X2 OPatch]# ./opatchauto apply /u02/patch21/35642822/ -analyze OPatchauto session is initiated at Tue Jan 30 15:50:25 2024
OPATCHAUTO-72083: Performing bootstrap operations failed.
OPATCHAUTO-72083: The bootstrap execution failed because Failed to unzip files on path./u02/patch21/35642822/35643107/files/perl.zipError::.
OPATCHAUTO-72083: Fix the reported problem and re-run opatchauto.
com.oracle.glcm.patch.auto.OPatchAutoException: OPATCHAUTO-72083: Performing bootstrap operations failed.
OPATCHAUTO-72083: The bootstrap execution failed because Failed to unzip files on path./u02/patch21/35642822/35643107/files/perl.zipError::.
OPATCHAUTO-72083: Fix the reported problem and re-run opatchauto.
at com.oracle.glcm.patch.auto.db.util.BootstrapHandler.performBootstrapping(BootstrapHandler.java:531)
at com.oracle.glcm.patch.auto.db.util.BootstrapHandler.main(BootstrapHandler.java:95) OPatchauto session completed at Tue Jan 30 15:50:27 2024
Time taken to complete the session 0 minute, 2 seconds opatchauto bootstrapping failed with error code 255.The subdirectories do not have proper permissions, changed the permissions to 775 and started the analyze the patch.
[root@ORA-X2 OPatch]# [root@ORA-X2 35642822]# ls -ltr
total 232
drwxr-x--- 5 root root 62 Oct 4 11:47 35655527
drwxr-x--- 5 root root 62 Oct 4 11:47 35652062
drwxr-x--- 5 root root 81 Oct 4 11:48 35643107
drwxr-x--- 4 root root 48 Oct 4 11:48 35553096
drwxr-x--- 4 root root 48 Oct 4 11:48 33575402
-rw-r--r-- 1 root root 0 Oct 4 11:51 README.txt
drwxr-x--- 2 root root 4096 Oct 4 11:51 automation
-rw-rw-r-- 1 root root 5824 Oct 4 15:24 bundle.xml
-rw-r--r-- 1 root root 224866 Oct 18 15:50 README.html
[root@ORA-X2 35642822]# cd ..
[root@ORA-X2 patch21]# ls -ltr
total 3014268
drwxr-x--- 8 root root 4096 Oct 4 11:47 35642822
-rw-rw-r-- 1 root root 2164310 Oct 18 20:43 PatchSearch.xml
-rw-r--r-- 1 root root 3084439097 Jan 30 15:44 p35642822_190000_Linux-x86-64.zip
[root@ORA-X2 patch21]# chmod -R 775 *
[root@ORA-X2 patch21]# cd -
/u02/patch21/35642822
[root@ORA-X2 35642822]# [root@ORA-X2 35642822]# cd /u01/app/19.3.0/grid/OPatch
[root@ORA-X2 OPatch]# ./opatchauto apply /u02/patch21/35642822/ -analyze OPatchauto session is initiated at Tue Jan 30 15:56:08 2024 System initialization log file is /u01/app/19.3.0/grid/cfgtoollogs/opatchautodb/systemconfig2024-01-30_03-56-13PM.log. Session log file is /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/opatchauto2024-01-30_03-56-20PM.log
The id for this session is BMJZ Executing OPatch prereq operations to verify patch applicability on home /u01/app/19.3.0/grid
Patch applicability verified successfully on home /u01/app/19.3.0/grid Executing patch validation checks on home /u01/app/19.3.0/grid
Patch validation checks successfully completed on home /u01/app/19.3.0/grid OPatchAuto successful.
--------------------------------Summary--------------------------------
Analysis for applying patches has completed successfully: Host:ORA-X2
CRS Home:/u01/app/19.3.0/grid
Version:19.0.0.0.0 ==Following patches were SUCCESSFULLY analyzed to be applied: Patch: /u02/patch21/35642822/35655527
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-01-30_15-56-39PM_1.log Patch: /u02/patch21/35642822/35652062
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-01-30_15-56-39PM_1.log Patch: /u02/patch21/35642822/33575402
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-01-30_15-56-39PM_1.log Patch: /u02/patch21/35642822/35553096
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-01-30_15-56-39PM_1.log Patch: /u02/patch21/35642822/35643107
Log: /u01/app/19.3.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2024-01-30_15-56-39PM_1.log OPatchauto session completed at Tue Jan 30 15:57:25 2024
Time taken to complete the session 1 minute, 13 seconds
[root@ORA-X2 OPatch]#OPatchAuto Error Code 255 can be a challenging obstacle to overcome during software patching in an Oracle environment. However, by following the troubleshooting steps outlined in this guide and diligently investigating the underlying causes, you can effectively resolve the error and confidently resume the patching process. Remember to document your troubleshooting efforts and share your findings with the Oracle community to contribute to collective knowledge and support.
