OPatch failure when individually applying Oracle patch 19509982 in RSA Identity Governance & Lifecycle

3 years ago

Originally Published: 2018-10-29

Article Number

000041699

Applies To

RSA Product Set: RSA Identity Governance & Lifecycle
RSA Product/Service Type: Appliance
RSA Version/Condition: All

Issue

When applying Oracle patch 19509982 individually on an appliance as per article 000031110 - All RSA Identity Governance and Lifecycle reviews fail with error ORA-01792 when using Oracle 12.1.0.2.0, the application of the Oracle patch fails with the following error in the opatch<timestamp>.log file:

[Oct 25, 2018 10:25:34 AM] [INFO]   [OPSR-TIME] Finished modifying the system for patch 19509982
[Oct 25, 2018 10:25:34 AM] [INFO]   ApplySession adding interim patch '19509982' to inventory
[Oct 25, 2018 10:25:34 AM] [INFO]   [OPSR-TIME] Saving patch 19509982 to inventory
[Oct 25, 2018 10:25:34 AM] [WARNING]OUI-67124:ApplySession failed in system modification phase... 'ApplySession::apply failed (no detail available).'
[Oct 25, 2018 10:25:34 AM] [INFO]   Restoring "/u01/app/oracle/product/12.1.0/db_1" to the state prior to running NApply...

The 'ApplySession::apply failed' message is normally followed by an error message that explains the failure. In this case however, it is followed by 'no detail available' so further troubleshooting is necessary. To troubleshoot, enable OPatch debug and apply the patch again:

Run the following commands as the oracle user.

Navigate to /home/oracle/CPU/19509982:

cd /home/oracle/CPU/19509982

Stop the RSA Identity Governance & Lifecycle server:

acm stop

Stop the Oracle Listener service:

acm stoporacle

Export the OPATCH_DEBUG value:

export OPATCH_DEBUG=true

Apply the patch:

opatch apply

Cause

In this case, the problem was due to incorrect file permissions. The debug output showed that as part of the patch process, the file /home/oracle/CPU/19509982/etc/config/inventory.xml was copied to /u01/app/oracle/product/12.1.0/db_1/inventory/oneoffs/19509982/etc/config/inventory.xml and it was failing because the subdirectory /u01/app/oracle/product/12.1.0/db_1/inventory/oneoffs/19509982/etc/config was owned by root instead of by the oracle user.

Resolution

In this case, the solution is to modify the ownership of /u01/app/oracle/product/12.1.0/db_1/inventory/oneoffs/19509982/etc/config from root to oracle. Follow one of the options below:

1. Change owner and group of one directory

As root, change ownership as follows:

# cd /u01/app/oracle/product/12.1.0/db_1/inventory/oneoffs/19509982/etc
# chown oracle:oinstall config

2. Change owner and group recursively

Since all the subdirectories should be owned by the oracle user, you could change the ownership recursively from the top down to ensure the ownership is correct for all subdirectories:

As root, change ownership as follows:

# cd /u01
# chown -R oracle:oinstall app

Don't see what you're looking for?

1. Change owner and group of one directory

2. Change owner and group recursively

Related Articles

Trending Articles