Skip to content
January 16, 2016 / Shivananda Rao P

GI upgrade from 11.2.0.3 to 12.1.0.2 on a standalone machine using silent mode

This post demonstrates on how to perform a GI upgrade from 11.2.0.3 version to 12.1.0.2 on a standalone machine. Usually the upgrade is performed via a GUI, but here I’m demonstrating the upgrade through silent mode using the response file.

 

Environment:


Hostname                                  :   ora1-4
Current GI version                        :   11.2.0.3
GI response file location                 :   /u02/grid_install.rsp
Existing 11.2.0.3 GI Home                 :   /u01/app/oracle/product/11.2.0.3/grid
To be installed 12.1.0.2 GI Home location :   /u01/app/oracle/product/12.1.0.2/grid/

 

As you know, GI on a standalone machine makes use of High Availability Service (HAS) and not Cluster Ready Service (CRS). Let’s query the current HAS version.

 


[oracle@ora1-4 bin]$ ./crsctl query has releaseversion
Oracle High Availability Services release version on the local node is [11.2.0.3.0]
[oracle@ora1-4 bin]$
[oracle@ora1-4 bin]$
[oracle@ora1-4 bin]$ ./crsctl query has softwareversion
Oracle High Availability Services version on the local node is [11.2.0.3.0]
[oracle@ora1-4 bin]$

 

Unzip the 12.1.0.2 GI software pack and take a copy of the response file grid_install.rsp located at “<unzipped location>/grid/response”. Here I have copied it to “/u02”.

 

Make necessary changes to the copied response file. The changes for a standalone GI upgrade include:

 

1. ORACLE_HOSTNAME
     - Specify the hostname on which the GI upgrade is being performed.
2. INVENTORY_LOCATION
     - Specify the Inventory location.
3. oracle.install.option
     - Choose the option as UPGRADE as this is what we are performing
4. ORACLE_BASE
     - Specify the ORACLE_BASE location.
5. ORACLE_HOME
     - Specify the location where GI 12.1.0.2 needs to be installed.
6. Specify the OS groups for OSDBA, OSOPER and OSASM

7. Since this is a standalone, SCAN and Cluster has no role to play. So skipping these.

8. ASM part is also skipped because the GI on 11.2.0.3 is already having an ASM instance using DATA_NEW and FRA_NEW as diskgroups. Since I do not want a fresh ASM instance or a fresh diskgroup to be created, this has been skipped.

9. Under the UPGRADE section, if you would want the GI to be managed by OEM Grid Control, then select oracle.install.config.managementOption to CLOUD_CONTROL, else choose NONE. If CLOUD_CONTROL is chosen, then provide more details that has been asked for like OMS host name, OMS Port. In this demo, I do not want the GI to be managed by Grid Control and hence chosen as NONE.

 

Here is the response file with the updated values used to perform the upgrade to 12.1.0.2.

GI respone file.
Run the “runInstaller” with the silent option and providing the complete path of the response file. Make sure that ORACLE_HOME and ORA_CRS_HOME are unset else you may face the below error message.

 

 


[oracle@ora1-4 grid]$ ./runInstaller -silent -responseFile /u02/grid_install.rsp -showProgress
Starting Oracle Universal Installer...

Checking Temp space: must be greater than 415 MB. Actual 8756 MB Passed
Checking swap space: must be greater than 150 MB. Actual 10236 MB Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2016-01-10_06-29-38PM. Please wait ...[oracle@ora1-4 grid]$ [FATAL] [INS-30131] Initial setup required for the execution of installer validations failed.
CAUSE: Failed to access the temporary location.
ACTION: Ensure that the current user has required permissions to access the temporary location.
*ADDITIONAL INFORMATION:*
Exception details
 - PRVG-1561 : Setting ORA_CRS_HOME variable is not supported

Unset the ORACLE_HOME and ORA_CRS_HOME and run the runInstaller with silent option. If the pre-requisite checks fail, then the installation throws error.
If so, then take necessary actions accordingly.

 


[oracle@ora1-4 grid]$ unset ORACLE_HOME
[oracle@ora1-4 grid]$ unset ORA_CRS_HOME
[oracle@ora1-4 grid]$
[oracle@ora1-4 grid]$ ./runInstaller -silent -responseFile /u02/grid_install.rsp -showProgress
Starting Oracle Universal Installer...

Checking Temp space: must be greater than 415 MB. Actual 8756 MB Passed
Checking swap space: must be greater than 150 MB. Actual 10236 MB Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2016-01-10_06-30-53PM. Please wait ...
You can find the log of this install session at:
/u01/app/oraInventory/logs/installActions2016-01-10_06-30-53PM.log

Prepare in progress.
.................................................. 7% Done.

Prepare successful.

Copy files in progress.
.................................................. 12% Done.
.................................................. 22% Done.
.................................................. 27% Done.
.................................................. 32% Done.
.................................................. 40% Done.
.................................................. 48% Done.
.................................................. 53% Done.
.................................................. 58% Done.
.................................................. 63% Done.
....................
Copy files successful.

Link binaries in progress.
..........
Link binaries successful.

Setup files in progress.
.................................................. 68% Done.

Setup files successful.

Setup Inventory in progress.

Setup Inventory successful.
.................................................. 73% Done.

Finish Setup successful.
The installation of Oracle Grid Infrastructure 12c was successful.
Please check '/u01/app/oraInventory/logs/silentInstall2016-01-10_06-30-53PM.log' for more details.

Setup Oracle Base in progress.

Setup Oracle Base successful.
.................................................. 82% Done.

Prepare for configuration steps in progress.

Prepare for configuration steps successful.
..........
Update Inventory in progress.

Update Inventory successful.
.................................................. 95% Done.

As a root user, execute the following script(s):
1. /u01/app/oracle/product/12.1.0.2/grid/rootupgrade.sh
Run the script on the local node.

.................................................. 100% Done.
Successfully Setup Software.

 

Run the rootupgrade.sh script as ROOT user from the new 12.1.0.2 GI home. Here is outcome of the rootupgrade.sh script.

 

[root@ora1-4 ~]# /u01/app/oracle/product/12.1.0.2/grid/rootupgrade.sh
Check /u01/app/oracle/product/12.1.0.2/grid/install/root_ora1-4.mydomain_2016-01-10_18-50-05.log for the output of root script

[root@ora1-4 ~]#

 

Let’s check the output for the rootupgrade script.

 


[oracle@ora1-4 ~]$ cat /u01/app/oracle/product/12.1.0.2/grid/install/root_ora1-4.mydomain_2016-01-10_18-50-05.log
Performing root user operation.

The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/12.1.0.2/grid
Copying dbhome to /usr/local/bin ...
Copying oraenv to /usr/local/bin ...
Copying coraenv to /usr/local/bin ...

Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Using configuration parameter file: /u01/app/oracle/product/12.1.0.2/grid/crs/install/crsconfig_params

ASM Configuration upgraded successfully.

Creating OCR keys for user 'oracle', privgrp 'oinstall'..
Operation successful.
LOCAL ONLY MODE
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
CRS-4664: Node ora1-4 successfully pinned.
2016/01/10 18:51:37 CLSRSC-329: Replacing Clusterware entries in file 'oracle-ohasd.conf'

2016/01/10 18:52:40 CLSRSC-329: Replacing Clusterware entries in file 'oracle-ohasd.conf'

2016/01/10 18:54:10 CLSRSC-482: Running command: 'upgrade model -s 11.2.0.3.0 -d 12.1.0.2.0 -p first'

2016/01/10 18:54:18 CLSRSC-482: Running command: 'upgrade model -s 11.2.0.3.0 -d 12.1.0.2.0 -p last'

ora1-4 2016/01/10 18:54:19 /u01/app/oracle/product/12.1.0.2/grid/cdata/ora1-4/backup_20160110_185419.olr 0

ora1-4 2016/01/09 13:02:23 /u01/app/oracle/product/11.2.0.3/grid/cdata/ora1-4/backup_20160109_130223.olr -
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'ora1-4'
CRS-2673: Attempting to stop 'ora.evmd' on 'ora1-4'
CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'ora1-4'
CRS-2677: Stop of 'ora.LISTENER.lsnr' on 'ora1-4' succeeded
CRS-2677: Stop of 'ora.evmd' on 'ora1-4' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'ora1-4'
CRS-2677: Stop of 'ora.cssd' on 'ora1-4' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'ora1-4' has completed
CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
2016/01/10 18:56:03 CLSRSC-327: Successfully configured Oracle Restart for a standalone server

[oracle@ora1-4 ~]$

 

ASM too has been upgraded. Let’s check the HAS version from the 12.1.0.2 GI home.

 


[oracle@ora1-4 grid]$ cd /u01/app/oracle/product/12.1.0.2/grid/bin/
[oracle@ora1-4 bin]$
[oracle@ora1-4 bin]$
[oracle@ora1-4 bin]$ ./crsctl query has releaseversion
Oracle High Availability Services release version on the local node is [12.1.0.2.0]
[oracle@ora1-4 bin]$
[oracle@ora1-4 bin]$
[oracle@ora1-4 bin]$ ./crsctl query has softwareversion
Oracle High Availability Services version on the local node is [12.1.0.2.0]

 

The ASM home too would be updated in the ORATAB file automatically during the upgrade.

 


[oracle@ora1-4 bin]$ cat /etc/oratab | grep ASM
+ASM:/u01/app/oracle/product/12.1.0.2/grid:N # line added by Agent

 

Let’s connect to ASM instance and verify ther version and the state of it’s diskgroups.

 

[oracle@ora1-4 ~]$ sqlplus / as sysasm

SQL*Plus: Release 12.1.0.2.0 Production on Sun Jan 10 19:33:28 2016

Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Automatic Storage Management option

SQL> select name,state from v$asm_diskgroup;

NAME                           STATE
------------------------------ -----------
DATA_NEW                       MOUNTED
FRA_NEW                        MOUNTED

SQL> select banner from v$version;

BANNER
--------------------------------------------------------------------------------
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
PL/SQL Release 12.1.0.2.0 - Production
CORE 12.1.0.2.0 Production
TNS for Linux: Version 12.1.0.2.0 - Production
NLSRTL Version 12.1.0.2.0 - Production

As seen above, the GI has been upgraded successfully from 11.2.0.3 to 12.1.0.2.

 

 

COPYRIGHT

© Shivananda Rao P, 2012 to 2017. Unauthorized use and/or duplication of this material without express and written permission from this blog’s author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Shivananda Rao and http://www.shivanandarao-oracle.com with appropriate and specific direction to the original content.

 

 
DISCLAIMER

The views expressed here are my own and do not necessarily reflect the views of any other individual, business entity, or organization. The views expressed by visitors on this blog are theirs solely and may not reflect mine.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: