cancel
Showing results for 
Search instead for 
Did you mean: 

MOPATCH19P_2308-70004508 step clarification

former_member345358
Discoverer
0 Kudos
1,370

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


Accepted Solutions (0)

Answers (2)

Answers (2)

mamartins
Active Contributor
0 Kudos

According to official documentation:

Related to patch 35148476, added in SBP 19.19.0.0.230418 202305

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".

JamesZ
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Kishore,

Are you hitting the known issue mentioned in SAP note 3263756?

Best regards,
James