on 2023 Sep 01 8:04 PM
While applying OPATCH19P_2308-70004508
ls -al $IHRDBMS/bin/oradism
# temporarily change to super user
su root -c "chown `id -u` $IHRDBMS/bin/oradism && chmod u+rw $IHRDBMS/bin/oradism"
is not changing the ownership of the file $IHRDBMS/bin/oradism" to oracle while permission changes to below, should it run the mopatch and not cause any issue with patching activity. Kindly confirm
-rwxr-x---. 1 root oinstall 145920 Apr 18 13:28 /oracle/SI1/19.0.0/bin/oradism
Request clarification before answering.
According to official documentation:
For Linux x86-64 only:
Execute the following command after shutting down the database instance but before starting MOPatch:
In this script, 'oracle' is the software owner. Otherwise adapt accordingly.
# temporarily change to super user
su root -c "chown oracle:oinstall $IHRDBMS/bin/oradism && chmod 0750 $IHRDBMS/bin/oradism"
Immediately after executing MOPatch and before starting up the database instance execute the following command:
# temporarily change to super user
su root -c "chown root:oinstall $IHRDBMS/bin/oradism && chmod 4750 $IHRDBMS/bin/oradism"
Then ensure that the permissions and ownership of $IHRDBMS/bin/oradism
look exactly like in the example below:
-rwsr-x--- 1 root oinstall <timestamp> $IHRDBMS/bin/oradism
For details see SAP Note 3263756 (Linux) Oracle Database 19c SBP fails during mopatch with "Cannot add write permissions for patch copy target oradism".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kishore,
Are you hitting the known issue mentioned in SAP note 3263756?
Best regards,
James
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
11 | |
9 | |
8 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.