Advertisement

Wednesday, January 16, 2019

Oracle Database - 18c - RAC (DB) 18c Patching (Apply OJVM 18.4.0.0.0)

This blog is now in continuation with my previous blog of Patching DB to 18.4.0.0.0

The requirements for this patch are that RU 18.4.0.0.0 should be present on DB
and OPatch must be 12.2.0.1.7


Patch 28502229 - Oracle JavaVM Component Release Update 18.4.0.0.0

Step 1  - Patch Pre-req and Installation[As oracle - On All Nodes Rolling Mode]
(All sub-steps are to be executed on all nodes in the given order)


# cd /tmp
# mv p28502229_180000_Linux-x86-64.zip /tmp/install/
# cd /tmp/install/
# unzip -qq p28502229_180000_Linux-x86-64.zip

# cd /tmp/install/28502229


Pre-req check
# export ORACLE_HOME=/u01/app/oracle/product/180/db/
# export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH

# opatch prereq CheckConflictAgainstOHWithDetail -ph ./


Stop Home on the Node
(Fill the Oracle Home and Node Name Information)
# srvctl stop home -oraclehome /u01/app/oracle/product/180/db -statefile /tmp/state.out -node rac18c01 -stopoption IMMEDIATE


Patch the DB
# opatch apply 


Start Home on the Node
(Fill the Oracle Home and Node Name Information and the name of statefile previously used )

# srvctl start home -oraclehome /u01/app/oracle/product/180/db -statefile /tmp/state.out -node rac18c01 



Step 2 - Patch Post Installation (Steps can be done on any Node - and should be done only one node)
On Step 2 - the Downtime starts for the DB 
Below Steps are only for Standalone DB (i.e. non CDB) 
# sqlplus /nolog
    connect / as sysdba
    alter system set cluster_database=false scope=spfile;

$ORACLE_HOME/bin/srvctl stop database -database orpl -stopoption IMMEDIATE
sqlplus /nolog
    connect / as sysdba
    startup upgrade 

# cd $ORACLE_HOME/OPatch
# ./datapatch -verbose
SQL Patching tool version 18.0.0.0.0 Production on Wed Jan 16 03:01:35 2019
Copyright (c) 2012, 2018, Oracle.  All rights reserved.

Log file for this invocation: /u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_75734_2019_01_16_03_01_35/sqlpatch_invocation.log

Connecting to database...OK
Gathering database info...done
Bootstrapping registry and package to current versions...done
Determining current state...done

Current state of interim SQL patches:
Interim patch 27923415 (OJVM RELEASE UPDATE: 18.3.0.0.180717 (27923415)):
  Binary registry: Not installed
  SQL registry: Applied successfully on 03-SEP-18 11.53.04.325168 PM
Interim patch 28502229 (OJVM RELEASE UPDATE: 18.4.0.0.181016 (28502229)):
  Binary registry: Installed
  SQL registry: Not installed

Current state of release update SQL patches:
  Binary registry:
    18.4.0.0.0 Release_Update 1809251743: Installed
  SQL registry:
    Applied 18.4.0.0.0 Release_Update 1809251743 successfully on 16-JAN-19 01.46.15.700202 AM

Adding patches to installation queue and performing prereq checks...done
Installation queue:
  The following interim patches will be rolled back:
    27923415 (OJVM RELEASE UPDATE: 18.3.0.0.180717 (27923415))
  No release update patches need to be installed
  The following interim patches will be applied:
    28502229 (OJVM RELEASE UPDATE: 18.4.0.0.181016 (28502229))

Installing patches...
Patch installation complete.  Total patches installed: 2

Validating logfiles...done
Patch 27923415 rollback: SUCCESS
  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/27923415/22239273/27923415_rollback_ORPL_2019Jan16_03_01_49.log (no errors)
Patch 28502229 apply: SUCCESS
  logfile: /u01/app/oracle/cfgtoollogs/sqlpatch/28502229/22435400/28502229_apply_ORPL_2019Jan16_03_01_52.log (no errors)

SQL Patching tool complete on Wed Jan 16 03:01:52 2019





Start DB Again
# sqlplus /nolog
    connect / as sysdba
    alter system set cluster_database=true scope=spfile;
    shutdown ;
# $ORACLE_HOME/bin/srvctl start database -d orpl



Recompile DB Objects
sqlplus /nolog
    connect / as sysdba
    @?/rdbms/admin/utlrp.sql



Patch Validation

# opatch lspatches

28502229;OJVM RELEASE UPDATE: 18.4.0.0.181016 (28502229)



2 comments:
Write comments
  1. there's no way to hot-patch yet? We have to schedule an stop-window per month if we want to keep updated with each release?

    ReplyDelete
    Replies
    1. You can always have a RAC Database for your support, though OJVM patches are not rolling installable.

      Delete