-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue][Patch]Patching script issue (patchDBBinaries.sh) #2822
Comments
@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 :
|
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"? 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";
The text was updated successfully, but these errors were encountered: