In NOARCHIVELOG mode the database can only be backed up when the database is closed/mounted and in a consistent mode. We can simply do that by putting the database is MOUNT mode and initiating backup as shown below.
Oracle Clusterware version on node[ol7-12c-rac1]is[18.104.22.168.0]
Oracle Clusterware version on node[ol7-12c-rac2]is[22.214.171.124.0]
Red Hat Enterprise Linux Server release7.1(Maipo)
Before we download the required patch, we need to verify if we have java user objects in use in the database. This helps us determine if we need the OJVM patch or not. If Multimedia, Spatial, and/or OLAP features/components are installed and used in the database then the OJVM patch will be required.
I did not require an OJVM patch, you can further check MOS: 397701.1 for object count in 12c.
Moving on to the actual patching, this is the link to the PSU I will be using for this activity (Patch 22646084: GRID INFRASTRUCTURE PATCH SET UPDATE 126.96.36.199.160419 (APR2016)). This PSU includes the DB PSU.
Before you proceed any further, look at the README. It gives all the information required. Notice that it requires OPatch version 188.8.131.52.7 or later. Using a lower version might give unfavorable results or fail the patching.
Download the latest OPatch and select 184.108.40.206.0 release from the release selection drop down.
During patch installation, OPatch saves copied of all the files that will be replace by the new patch before new/patched versions of these files are loaded in $ORACLE_HOME/.patch_storage. Known as rollback files, these are important in making a patch rollback. Optionally, take a backup of $GRID_HOME/.patch_storage and $DB_HOME/.patch_storage.
Run opatch lsinventory on all the homes that will be patched.
Patchdescription:"OCW Patch Set Update : 220.127.116.11.160419 (22502555)"
Created on14Apr2016,02:42:10hrs PST8PDT
Patch22291127:applied on Sun Sep1117:44:30CDT2016
Patchdescription:"Database Patch Set Update : 18.104.22.168.160419 (22291127)"
Created on6Apr2016,03:46:21hrs PST8PDT
Like catbundle in 11g, 12c has datapatch. Refer for MOS 1585822.1
Datapatch determines the requisite apply/rollback actions by matching an internal repository with the patch inventory.
Datapatch should be invoked when the database is restarted after a patching session.
Enterprise Manager and OPatchAuto call datapatch automatically during every patching session.
If OPatch is used to install RDBMS patches then datapatch has to be explictly called to complete any patching actions after database restart.
Datapatch will automatically determine the set of patches that need to be installed and a set of patches that need to be rolled back.
Datapatch ensures that a patch has been installed/rolled back in all RAC instances before to initiate any post-patch SQL actions on the database.
In Oracle Multitenant environment datapatch will patch the root and any pluggable databases that are opened.
In order to patch all pluggable databases, it should be ensured that before to invoke datapatch all pluggable databases are opened.
If an unpatched pluggable database is opened in Oracle Multitenant then calling datapatch will complete the pending patch actions.
To update DBA_REGISTRY_SQLPATCH with the PSU information run the following.
12c Grid Control (OEM) comes with many improvements, visual and otherwise. Its responsive compared to 11g. I put some load on my targets (using the strategy in my last post). I will put some screenshots here.
Oracle Enterprise Manager Cloud Control 12c – Home Page
Oracle Enterprise Manager Cloud Control 12c – High Availability Console Home Page
Oracle Enterprise Manager Cloud Control 12c – Dataguard Administration Home Page
Oracle Enterprise Manager Cloud Control 12c – Cluster Page
Oracle Enterprise Manager Cloud Control 12c – Cluster Performance Home Page
Oracle Enterprise Manager Cloud Control 12c – Database Instance Home Page
Oracle Enterprise Manager Cloud Control 12c – Database Instance Performance Home Page
Oracle Enterprise Manager Cloud Control 12c – Database Instance Top Activity Home Page
Oracle Enterprise Manager Cloud Control 12c – Database Instance Activity
Data being inserted, shows the size of the segment