Exadata GI Upgrade 11.2.0.4 to 12.1.0.2 + PSU Jul2016

giupg

Recently I did a upgrade to Grid Infrastructure 12.1.0.2 on a few Exadata Clusters

Here my summary of the installation

Before you start please read the following MOS note 1681467.1. This note is very helpful and describes the whole procedure in a Exadata environment

It’s not only the Upgrade to 12.1.0.2. In the same „session“ I also install the GI PSU Jul 2016 and the Oneoff Patch 23273686 because there is a known BUG in the SCAN Listener area (see below)

At the end of the article some „real news“ from GI 12.1.0.2 (see below „real“ news)

So let’s start

First of all keep in mind that the clusterware must be „up and running”

Step 1 Oracle environment

 

 export SRVM_USE_RACTRANS=true 

 unset ORACLE_HOME ORACLE_BASE ORACLE_SID 

./runInstaller 

Step 2 GI Software Installation

The next slides show the GI Installation Procedure

gi_upg_1

gi_upg_2

gi_upg_3

gi_upg_4

gi_upg_5

gi_upg_6

gi_upg_7

gi_upg_8

gi_upg_9

gi_upg_10

gi_upg_12

gi_upg_13

If the Setup is at that point you need to do the following but

please don’t close the Installer window

Step 3 Install latest opatch tool

Download opatch tool  Patch 6880880 (better you did it before)

On a Exadata the Installation can be done in one step via dcli


dcli -l oracle -g dbs_group unzip -oq -d /u01/app/12.1.0.2/grid p6880880_121010_LINUX.zip -d /u01/patchdepot

Step 3 Install GI PSU JUL 2016 23273686


Node 1 srvdb01

[root@srvdb01]# /u01/app/12.1.0.2/grid/OPatch/opatch napply -oh /u01/app/12.1.0.2/grid -local /u01/patchdepot/23273686

Node 2 srvdb02

[root@srvdb02]# /u01/app/12.1.0.2/grid/OPatch/opatch napply -oh /u01/app/12.1.0.2/grid -local /u01/patchdepot/23273686

While there is a known BUG you should directly install the following Oneoff Patch 20734332 here the Doc ID 2166451.1 with the details

(SCAN Listener or local listener fails to start after applying Patch 23273629 – Oracle Grid Infrastructure Patch Set Update 12.1.0.2.160719 (Jul2016))

Step 4 rootupgrade.sh 

After you finish the PSU Jul 2016 & Oneoff Patch installation the rootupgrade.sh must be started


Node 1 srvdb01

[root@srvdb01 grid]# /u01/app/12.1.0.2/grid/rootupgrade.sh

Node 2 srvdb02

[root@srvdb02 grid]# /u01/app/12.1.0.2/grid/rootupgrade.sh

The rootupgrade.sh script works around 15 minutes so stay calm

It finished with the following messages here as example from the last Node 2 srvdb02

….

Successfully accumulated necessary OCR keys.

Creating OCR keys for user ‚root‘, privgrp ‚root‘..

Operation successful. 14:53:13 CLSRSC-474: Initiating upgrade of resource types

14:54:33 CLSRSC-482: Running command: ‚upgrade model  -s 11.2.0.4.0 -d 12.1.0.2.0 -p first‘

14:54:33 CLSRSC-475: Upgrade of resource types successfully initiated.

14:54:35 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster … succeeded

gi_upg_14

Step 5 final tasks

finally some configuration tool runs and finished the GI Upgrade including PSU Jul 2016 and Oneoff Patch

And now the „real news“ in 12.1.0.2 

The most notable change belongs to the GIMR  (Grid Infrastructure Management Repository) 

Beginning with 12.1.0.1 it was an option installing the GIMR Database – MGMTDB

Starting with 12.1.0.2 it is mandatory and the MGMTDB database is automatically created as part of the upgrade installation process of 12.10.2 Grid Infrastructure. If you start a installation from scratch the GIMR Database is directly configured

Some interesting GI & MGMTDB commands

[oracle@srvdb01 ~]$ crsctl query crs activeversion

Oracle Clusterware active version on the cluster is [12.1.0.2.0]

[oracle@srvdb01 ~]$ crsctl query crs releaseversion

Oracle High Availability Services release version on the local node is [12.1.0.2.0]

[oracle@srvdb01 ~]$ crsctl query crs activeversion -f

Oracle Clusterware active version on the cluster is [12.1.0.2.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [3351897854].

MGMTDB Checks


[oracle@srvdb01 ~]$ srvctl status mgmtdb -verbose
Database is enabled
Instance -MGMTDB is running on node srvdb01. Instance status: Open.

[oracle@srvdb01 ~]$ srvctl config mgmtdb
Database unique name: _mgmtdb
Database name:
Oracle home: <CRS home>
Oracle user: oracle
Spfile: +DBFS_DG/_MGMTDB/PARAMETERFILE/spfile.268.926345767
Password file:
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Type: Management
PDB name: srv_cl12
PDB service: srv_cl12
Cluster name: srv-cl12
Database instance: -MGMTDB

Advertisements

Über spa

Oracle and Unix Professional, main focus on Oracle HA - Systems also an Exadata enthusiasts
Dieser Beitrag wurde unter Exadata, General, Grid Infrastructure, Oracle 12.1 abgelegt und mit , , verschlagwortet. Setze ein Lesezeichen auf den Permalink.

Kommentar verfassen

Trage deine Daten unten ein oder klicke ein Icon um dich einzuloggen:

WordPress.com-Logo

Du kommentierst mit Deinem WordPress.com-Konto. Abmelden / Ändern )

Twitter-Bild

Du kommentierst mit Deinem Twitter-Konto. Abmelden / Ändern )

Facebook-Foto

Du kommentierst mit Deinem Facebook-Konto. Abmelden / Ändern )

Google+ Foto

Du kommentierst mit Deinem Google+-Konto. Abmelden / Ändern )

Verbinde mit %s