Patch 25755742: DATABASE PATCH SET UPDATE 12.1.0.2.170718
Patch 25755742: DATABASE PATCH SET UPDATE 12.1.0.2.170718
Today there was an interesting situation with Oracle PSU patching
Here you will discover that Oracle opatchauto perform patching on the running database without any issue and database remain running... not exactly :)
Prior that you can find very useful information in known issues for the patch:
1 Known Issues
1.1 In some environments the Database may fail to startup or take over 20 minutes longer to perform a clean startup
After installing the Jul2017 Database PSU 12.1.0.2.170718 patch, in some environments, the Database may fail to startup or take an additional 20 minutes to perform a clean startup. A clean startup means a startup that requires no recovery such as a startup after a shutdown normal.
This issue will be resolved by the Database PSU 12.1.0.2.170814 patch.
For customers who have not yet deployed the Jul2017 Database PSU, the recommendation is to deploy patch PSU 12.1.0.2.170814 or later.
If the Jul2017 Database PSU patch has already been deployed to production or if you are in the process of such a deployment and no Database startup issue is observed, then the new 170814 patch is not required since the issue is not impacting your configuration.
The example will be very short due to missing logs
Checking if database running
|
|
Starting with the pathing process ( Normally we should stop all running database from the Oracle Home but here we will show you that Oracle does not perform any checks on that :( )
|
[oracle@NODE1(Staging) 25755742]$ /u01/app/oracle/product/rdbms/12.1.0.2/OPatch/opatch apply -local
Verifying environment and performing prerequisite checks... Do you want to proceed? [y|n] Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
Patching component oracle.sqlplus.ic, 12.1.0.2.0... Patching component oracle.sqlplus, 12.1.0.2.0... Patching component oracle.tfa, 12.1.0.2.0... Patching component oracle.ordim.client, 12.1.0.2.0... Patching component oracle.ordim.client, 12.1.0.2.0... Patching component oracle.ordim.jai, 12.1.0.2.0... Patching component oracle.ordim.server, 12.1.0.2.0... Patching component oracle.rdbms, 12.1.0.2.0... Patching component oracle.rdbms.rsf, 12.1.0.2.0... Patching component oracle.rdbms.rman, 12.1.0.2.0... Patching component oracle.rdbms.install.plugins, 12.1.0.2.0... Patching component oracle.javavm.containers, 12.1.0.2.0... Patching component oracle.network.rsf, 12.1.0.2.0... OPatch succeeded. |
Checking if database running
|
[oracle@NODE1(Staging) 25755742]$ ps -ef | grep pmon
|
Lets check alert log:
| Wed Oct 11 14:16:43 2017 WARNING: Oracle executable binary mismatch detected. Binary of new process does not match binary which started instance issue alter system set "_disable_image_check" = true to disable these messages Wed Oct 11 14:16:43 2017 Errors in file /u01/app/oracle/diag/rdbms/TESTDB/TESTDB_2/trace/TESTDB_2_j000_11201.trc: ORA-27140: attach to post/wait facility failed ORA-27300: OS system dependent operation:invalid_egid failed with status: 1 ORA-27301: OS failure message: Operation not permitted ORA-27302: failure occurred at: skgpwinit6 ORA-27303: additional information: startup egid = 48114 (asmadmin), current egid = 48112 (oinstall) |
hmmm.. this message is expected...now we have to perfomr database restart but.. with abort option!