Applicable Delphix Versions
All Sub Releases
|5.2||220.127.116.11, 18.104.22.168, 22.214.171.124|
126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124
126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11 ,18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11
Upgrading the Oracle RDBMS software often involves the establishment of a new Oracle Home path in which the new release of the Oracle binaries is placed. Oracles supplied database upgrade assistant (dbua) can be used perform this task once the new Oracle Home and release are in place. DBUA performs the task of migrating the database(s) running from the old Oracle Home across to the new Oracle Home and then executing any post upgrade scripts that might be required. Once this has been completed the Delphix Virtualisation Engine dSources that were using the old Oracle Home needs be aligned with the new Oracle Home. This is not performed automatically and if Delphix believes the old home is still in use operations like snapsync performed against the dSources will fail.
This knowledge base article has been put together to shed light on some of the processes involved in upgrading Oracle Homes used by Delphix dSources and how to account for this within Delphix.
Warning : Upgrading Oracle Databases must be performed by an Oracle DBA in accordance with the version specific process supplied by Oracle themselves. The process detailed in this article is for educational purposes only and is no way meant to replace Oracles documented upgrade processes.
There are two Oracle Homes in play in this example of the upgrade process. The intention is to upgrade the dSource from Oracle 18.104.22.168 to 22.214.171.124.
o The original Oracle Home at release 126.96.36.199 that is currently in use by the dSource.
In the Delphix UI we see only the 188.8.131.52 prior to adding the new 184.108.40.206 Oracle Home.
o The new Oracle Home at release 220.127.116.11 that the dSource will be moved to in its upgraded version.
o The installation of this new Oracle Home will be performed by the DBA team or team responsible for maintaining the Oracle software. After the installation of the new ORACLE_HOME is performed, a refresh of the Delphix environment will need to be performed in order for the new Oracle software to be discovered and added to Delphix. Once the refresh has completed the new software should appear for the environment within the Delphix GUI.
o A dSource called "o112" that has been linked to the Delphix Virtualisation Engine. Note the 18.104.22.168 is in place.
o The installation of this new Oracle Home will be performed by the DBA team or team responsible for maintaining the Oracle software
o After the installation of the new ORACLE_HOME is performed, a refresh of the Delphix environment will need to be performed in order for the new Oracle software to be discovered and added to Delphix.
o Once the refresh has completed the new software should appear for the environment within Delphix.
o The upgrade of the dSource Oracle RDBMS will be performed by the DBA team or a team responsible for maintaining the Oracle RDBMS.
o In this example the upgrade was performed through dbua
o Currently we can see the current home being used by the Oracle instances processes through its environment and the ORACLE_HOME environment variable which is pointing to the 22.214.171.124 home (ORACLE_HOME=/u01/app/oracle/product/126.96.36.199/dbhome_1)
[oracle@oel6sin1 ~]$ ps -ef | grep pmon oracle 10402 1 0 17:28 ? 00:00:00 ora_pmon_o112 oracle 22146 9811 0 17:40 pts/2 00:00:00 grep pmon [oracle@oel6sin1 ~]$ ps e -ww -p 10402 PID TTY STAT TIME COMMAND 10402 ? Ss 0:00 ora_pmon_o112 HOSTNAME=oel6sin1.plb.internal TERM=xterm-256color SHELL=/bin/bash HISTSIZE=1000 SSH_CLIENT=192.168.0.15 61378 22 QTDIR=/usr/lib64/qt-3.3 OLDPWD=/u01/app/oracle/product/188.8.131.52/dbhome_1/network/admin QTINC=/usr/lib64/qt-3.3/include SSH_TTY=/dev/pts/2 USER=oracle LD_LIBRARY_PATH=/u01/app/oracle/product/184.108.40.206/dbhome_1/lib ORACLE_SID=o112 ORACLE_BASE=/u01/app/oracle MAIL=/var/spool/mail/oracle .. . ORACLE_HOME=/u01/app/oracle/product/220.127.116.11/dbhome_1 ORA_NET2_DESC=9,12 ORACLE_SPAWNED_PROCESS=1 SKGP_SPAWN_DIAG_PRE_FORK_TS=1534231738 SKGP_SPAWN_DIAG_POST_FORK_TS=1534231738 SKGP_SPAWN_DIAG_PRE_EXEC_TS=1534231738 [oracle@oel6sin1 ~]$
o To perform the upgrade the environment needs to be set to the new ORACLE_HOME before invoking dbua. The file /etc/oratab (linux) can be used to locate the home if the DBA's have placed an entry in here.
[oracle@oel6sin1 admin]$ egrep '18.104.22.168' /etc/oratab home11204:/u01/app/oracle/product/22.214.171.124/dbhome_1:N [oracle@oel6sin1 admin]$ . oraenv ORACLE_SID = [orc112] ? home11204 The Oracle base remains unchanged with value /u01/app/oracle [oracle@oel6sin1 admin]$ export ORACLE_SID=o112 [oracle@oel6sin1 admin]$ dbua
o DBUA will appear and the upgrade is performed through following the wizard through to its completion.
o Ensure the correct database is selected to perform the upgrade against.
o Set the upgrade options like the recompilation of any invalid PL/SQL code held with the database. Please note not all screens presented by dbua are shown in this example to manage the size of the knowledge base article.
o A summary screen is presented after all steps in the wizard have been completed.
o Clicking on finish will kick the upgrade off and dbua will stop the database, relocate it to its new Oracle Home, restart it and perform the upgrade of the RDBMS internals.
Please note: this example demonstrates a successful upgrade. Should any problems be encountered during the upgrade process the database will potentially need to be restored from a backup captured prior to starting the upgrade process, the problem encountered rectified and the upgrade performed once more.
o Once the dbua wizard has completed the upgrade the dSource has been upgraded from Oracles perspective. Please note the amount of time taken to perform the upgrade can take tens of minutes through to several hours.
o The /etc/oratab entry for the dSoure will have been adjusted by dbua and reflect the new home post upgrade.
o To confirm the state of the dSource database post upgrade a few basic checks should be performed.
o Set the environment using the new oratab entry.
[oracle@oel6sin1 ~]$ . oraenv ORACLE_SID = [o112] ? o112 The Oracle base remains unchanged with value /u01/app/oracle [oracle@oel6sin1 ~]$ set | grep ORA OLD_ORACLE_BASE=/u01/app/oracle ORABASE_EXEC=/u01/app/oracle/product/126.96.36.199/dbhome_1/bin/orabase ORACLE_BASE=/u01/app/oracle ORACLE_HOME=/u01/app/oracle/product/188.8.131.52/dbhome_1 ORACLE_SID=o112 ORAHOME=/u01/app/oracle/product/184.108.40.206/dbhome_1 ORASID=o112
o The processes environment has been aligned to the new Oracle Home
[oracle@oel6sin1 ~]$ ps -ef | grep pmon oracle 26023 1 0 18:39 ? 00:00:00 ora_pmon_o112 oracle 26166 9811 0 18:43 pts/2 00:00:00 grep pmon
[oracle@oel6sin1 ~]$ ps e -ww -p 26023 PID TTY STAT TIME COMMAND 26023 ? Ss 0:00 ora_pmon_o112 XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt GDM_LANG=en_US.UTF-8 LANG=en_US.UTF-8 ORACLE_BASE=/u01/app/oracle ORACLE_SID=o112 ORBIT_SOCKETDIR=/tmp/orbit-oracle XMODIFIERS=@im=none G_BROKEN_FILENAMES=1 HOME=/home/oracle GDM_KEYBOARD_LAYOUT=gb LD_LIBRARY_PATH=/u01/app/oracle/product/220.127.116.11/dbhome_1/lib:/u01/app/oracle/product/18.104.22.168/dbhome_1/jdk/jre/lib/amd64/server: /u01/app/oracle/product/22.214.171.124/dbhome_1/jdk/jre/lib/amd64:/u01/app/oracle/product/126.96.36.199/dbhome_1/jdk/jre/../lib/amd64: /etc/ORCLcluster/oracm/lib:/u01/app/oracle/product/188.8.131.52/dbhome_1/lib:/u01/app/oracle/product/184.108.40.206/dbhome_1/network/lib: /u01/app/oracle/product/220.127.116.11/dbhome_1/lib USER=oracle QTINC=/usr/lib64/qt-3.3/include NLS_LANG=AMERICAN_AMERICA.AL32UTF8 ORACLE_HOME=/u01/app/oracle/product/18.104.22.168/dbhome_1 SHELL=/bin/bash LOGNAME=oracle
o The database instance is now showing the new release.
SQL> select instance_name,version,status from v$instance; INSTANCE_NAME VERSION STATUS ---------------- ----------------- ------------ o112 22.214.171.124.0 OPEN
o The database software components are also showing 126.96.36.199 where appropriate.
SQL> SET PAGESIZE 60 SET LINESIZE 300 SET VERIFY OFF COL comp_name FOR a44 HEA 'Component' COL version FOR a17 HEA 'Version' COL status FOR a17 HEA 'Status' SELECT comp_name, version, status FROM dba_registry; Component Version Status -------------------------------------------- ----------------- ----------------- OWB 188.8.131.52.0 VALID Oracle Application Express 3.2.1.00.12 VALID Oracle Enterprise Manager 184.108.40.206.0 VALID OLAP Catalog 220.127.116.11.0 VALID Spatial 18.104.22.168.0 VALID Oracle Multimedia 22.214.171.124.0 VALID Oracle XML Database 126.96.36.199.0 VALID Oracle Text 188.8.131.52.0 VALID Oracle Expression Filter 184.108.40.206.0 VALID Oracle Rules Manager 220.127.116.11.0 VALID Oracle Workspace Manager 18.104.22.168.0 VALID Oracle Database Catalog Views 22.214.171.124.0 VALID Oracle Database Packages and Types 126.96.36.199.0 VALID JServer JAVA Virtual Machine 188.8.131.52.0 VALID Oracle XDK 184.108.40.206.0 VALID Oracle Database Java Packages 220.127.116.11.0 VALID OLAP Analytic Workspace 18.104.22.168.0 VALID Oracle OLAP API 22.214.171.124.0 VALID 18 rows selected.
Changes required in Delphix after Upgrading the Oracle Release
o An environment refresh should be performed post upgrade. This will allow Delphix to gather information about the current state of the Oracle Homes, listeners in place, databases running and any other Oracle alterations appearing in the environment.
o Immediately following the upgrade Delphix still believes the dSource is running from the 126.96.36.199 Oracle Home.
o To align Delphix and the details held in regards to the dSource o112 the UI can be used to upgrade the dSource. All this is really doing is moving the dSources configuration from the old home to the new home and only adjusts meta data held within Delphix itself.
o While the old version remains in place on the Delphix side dSource snapsync operations will fail.
o To align the database with the new Oracle Home and the 188.8.131.52 release that the dSource is actually using now use the "Upgrade" menu item.
o Select the new Oracle Home from which the dSource o112 is now running post upgrade or patching.
o The Delphix GUI and CLI should now reflect the location of the new home and the version of the new release for the dSource.