Closed eyaneylii closed 1 day ago
@yunus-qureshi @aditya059 any updates please
@eyaneylii 6880880 goes under the oneoffs directory and 36195566 under release update or both can go under one_offs
@yunus-qureshi Thank you for you're response but what I'm trying to say is : when I changed on the script the 6880880 with the new 36195566 it worked okay and the image was built so my questions are
Hi @eyaneylii ,
Q1. While applying p36195566_190000_Linux-x86-64 on oracle/database:19.3.0.0 I had an issue due to below lines on the patchDBBinaries.sh script
A. What was the issue?
Q2. You changed "if [[ $patch_zip =~ "6880880" ]]; then" to "if [[ $patch_zip =~ "36195566" ]]; then"? A. This is not correct. 6880880 is not applied but extracted to Oracle Home. 36195566 is applied using opatchauto tool
Oracle home comes with default opatch. We do recommend to extract latest opatch (6880880) in oracle home. With this new opatch (or old one if 6880880 is not extracted), we apply other release update and one-offs like 36195566.
Hi all,
While applying p36195566_190000_Linux-x86-64 on oracle/database:19.3.0.0 I had an issue due to below lines on the patchDBBinaries.sh script. I tried to change on the script instead of 6880880 I put 36195566 and that worked but is that okay or I should have the p6880880_190000_Linux-x86-64 under the one_offs directory ? if [[ $patch_zip =~ "6880880" ]]; then echo "Removing directory ${ORACLE_HOME}/OPatch"; rm -rf "${ORACLE_HOME}"/OPatch; echo "Unzipping OPatch archive ${patch_zip} to ${ORACLE_HOME}"; unzip -qo "$patch_zip" -d "$ORACLE_HOME";