OOW 2016 erster Tag

oow_2016

Der erste Tag auf der OpenWorld 2016. Es war ein Tag zum „Warmlaufen und orientieren“.

Das Dominate Thema war „Oracle Cloud“. Zur neuen Oracle 12c Rel. 2 durfte bis auf eine Folie in der Keynote von Larry Ellison nichts gesagt werden. Larry Ellison wird 12c Rel. 2 am Dienstag in seiner zweiten Keynote vorstellen.

Viele Sessions waren mit generellen Themen vertreten, teilweise mit absoluten Basics. Ein super Vortrag kam von Mauro Pagano zum Thema Performance mit seinem Tool SQLd360. Es ist eine Weiter bzw. Neuentwicklung von SqlT. Das Tool sollte sich jeder DBA der sich mit dem Thema Performance auseinandersetzt mal genauer ansehen.

Ein weiterer guter Vortrag kam von Simon Pane zum Thema Oracle Database Security. Viele Beispiele die man im täglichen DBA Umfeld direkt umsetzen und anwenden kann. Von Passworthandling, SQL-Net, Skripten etc..

Einer der ganz wenigen Vorträgen im Themenbereich Engineered Systems hatte den Titel „Explore Database Cloud in 45 Minutes“. Der praktische Teil der Session endete erstmal mit einem technischen Problem, da das Notebook & der Beamer nicht zueinander „fanden“. Insgesamt wurde im Vortrag allerdings nichts Neues berichtet.

 

Werbeanzeigen

ASM „corrupted metadata block“ check via amdu / kfed (Part 1)

corrupt

Last week we had a crash on our Exadata ASM Instance and we are not amused about this but we restart the instance and start working as usually.

About the environment: „GRID Software is Release 12.1 but the diskgroups are compatible 11.2.0.4“

To be save we start a check on the DATA diskgroup.


ALTER DISKGROUP DATA CHECK all NOREPAIR;

The check run online but nearly 25 hours
We saw in the meantime lots of errors in the ASM alert.log

Tue Jun 21 15:47:15 2016
NOTE: disk DATA_CD_10_srv1CD13, used AU total mismatch: DD={514269, 0} AT={514270, 0}
Tue Jun 21 15:47:15 2016
GMON querying group 1 at 567 for pid 52, osid 138892
GMON checking disk 143 for group 1 at 568 for pid 52, osid 138892

A MOS note said this should not be a problem but is this correct …?

The analyze is done via a  dump with amdu of the diskgroup when the „CHECK NO REPAIRS“ is ready.


amdu -diskstring 'o/*/*' -dump 'DATA'

Yes, we start the dump in a directory where we have enough space while the amdu tool creates a lot

of 2GB files dependent from the size of the diskgroup. One small file will also be created during this

dump and it is the  report.txt file.

The report.txt has information about the System, OS, Version, all scanned disks and also a list

about the scanned disks which have „corrupted metadata blocks“.

Here an example

---------------------------- SCANNING DISK N0002 -----------------------------

Disk N0002: '192.168.10.10/DATA_CD_01_srv1cd2">192.168.10.10/DATA_CD_01_srv1cd2'

AMDU-00209: Corrupt block found: Disk N0002 AU [454272] block [0] type [0]

AMDU-00201: Disk N0002: '192.168.10.10/DATA_CD_01_srv1cd2">192.168.10.10/DATA_CD_01_srv1cd2'

AMDU-00217: Message 217 not found;  product=RDBMS; facility=AMDU; arguments: [0] [1024] [blk_kfbl]

           Allocated AU's: <strong>507621</strong>

                Free AU's: 57627

       AU's read for dump: 194

       Block images saved: 12457

        Map lines written: 194

          Heartbeats seen: 0

  Corrupt metadata blocks: 1

        Corrupt AT blocks: 0

The next question was: „How can we check if this metadata block is corrupted?“

The answer is you need the kfed tool and theAllocated AU’s: 507621″ 

from the report.txt files.


[oracle0@srv1db1]$ kfed read <strong>aun=507621</strong> aus=4194304 blkn=0 dev=o/<a href="http://192.168.10.10/DATA_CD_00_srv1cd2%7C" data-saferedirecturl="https://www.google.com/url?hl=de&q=http://192.168.10.10/DATA_CD_00_srv1cd2%257C&source=gmail&ust=1467906685880000&usg=AFQjCNHjeE0eAiO3K3BgawquJRg3dq2V0Q">192.168.10.10/DATA_CD_00_srv1cd2</a>

kfbh.endian:                         58 ; 0x000: 0x3a

kfbh.hard:                          162 ; 0x001: 0xa2

kfbh.type:                            0 ; 0x002: <strong>KFBTYP_INVALID</strong>

kfbh.datfmt:                          0 ; 0x003: 0x00

kfbh.block.blk:              1477423104 ; 0x004: blk=1477423104

kfbh.block.obj:              3200986444 ; 0x008: disk=732492

kfbh.check:                    67174540 ; 0x00c: 0x0401008c

kfbh.fcn.base:                    51826 ; 0x010: 0x0000ca72

kfbh.fcn.wrap:                        0 ; 0x014: 0x00000000

kfbh.spare1:                          0 ; 0x018: 0x00000000

kfbh.spare2:                          0 ; 0x01c: 0x00000000

1EFB9400000 0000A23A 580FB000 BECB2D4C 0401008C  [:......XL-......]

1EFB9400010 0000CA72 00000000 00000000 00000000  [r...............]

1EFB9400020 00000000 00000000 00000000 00000000  [................]

  Repeat 253 times

As you saw in the example the „kfbh.type = KFBTYP_INVALID“ which means the metadata block is corrupt.

So and how can I fix this?

In our situation we have an diskgroup which is compatible 11.2.0.4 so we have to start an


ALTER DISKGROUP DATA CHECK ALL REPAIR;

Yeah this could be very dangerous.

If the „CHECK ALL REPAIR“ find a corruption and try to repair this the diskgroup will be dismounted

This means all databases which are up and running will crash

But keep in mind that a „CHECK ALL REPAIR“ will also run 25 hours.

Is there another solution?
Yes but you need also a dismount of the diskgroup.

Then run the amdu tool „OFFLINE“ again and check the report.txt file again for corrupted metadata blocks

More details will be discussed in Part 2 about ASM kfed and amdu

So stay tuned.

 


 

Exdata Lifecycle / Patching

patching_icon

Operate an Exadata Database Machine means you have to manage the Lifecyle. One major task is the regular patching of the whole Exa Stack.

This blog article give you an overview about the Patching.

First remember which components are part of the lifecycle.

Following the component and the tool.

exadata

  • GRID & RDBMS
    • opatch (oplan)
  • DB Node
    • patchmgr (that’s new since Oct 2015)
  • Storage Grid
    • patchmgr
  • Network
    • patchmgr

Before starting the Patching you need to do a bullet proof planing otherwise you fail.

For a Quarter Rack with lets say 10 Production databases you need a planing phase of more or less 2-3 weeks.

How to setup a recommendation?

  • Analyze your ORACLE_HOMES
  • Check existing SR for every database
  • Meet with your Application Manager
  • Use Oracle Tools like exachk
  • Use the conflict analyzer in MOS

exachk will be your best friend

Check the My Oracle Support Note 1070954.1 and install the latest version

First take a look of the table of contents

exachk_0

and one very important table is the recommended version overview

exachk_1

What will be the best recommendation?

It doesn’t give an easy answer while Oracle has a lot of possibilities for the Patching:

  • the QFSDP the Quarterly Full Stack Download Patch
  • or Standalone Patchsets for every Component like Infinband, Cell Server, DB-Node and so on

So the decision has to be taken by the whole team of Application Manager and Oracle DBA’s and System Administrator

Weiterlesen „Exdata Lifecycle / Patching“

X5-2 Jan2016 GI – Bug 22135419 – 12C GRID HOME PERMISSIONS NOT RESET

bug

 

 

The last days I did a Upgrade on a Exadata X5-2 Machine including the GRID Software.

During the GI Patching  (Patch 22243551) there was no error message.

But after a short while we get a lot of errors from the Database alert.logs.

ORA-27140: attach to post/wait facility failed
ORA-27300: OS system dependent operation:invalid_egid failed with status: 1
ORA-27301: OS failure message: Operation not permitted
ORA-27302: failure occurred at: skgpwinit6
ORA-27303: additional information: startup egid = 1002 (dba), current egid = 1001 (oinstall)

The error message means that the „group id“ (gid) was not correct set.

Using asmcmd was not possible.

$ asmcmd

/app/oragrid/product/<a href="http://12.1.0.2/grid/bin/kfod">12.1.0.2/grid/bin/kfod</a>: line 22: /export/home/oragrid/%ORACLE_HOME%/bin/kfod.bin: No such file or directory
/app/oragrid/product/<a href="http://12.1.0.2/grid/bin/kfod">12.1.0.2/grid/bin/kfod</a>: line 22: exec: /export/home/oragrid/%ORACLE_HOME%/bin/kfod.bin: cannot execute: No such file or directory
Use of uninitialized value $clus_mode in scalar chomp at /app/oragrid/product/<a href="http://12.1.0.2/grid/lib/asmcmdbase.pm">12.1.0.2/grid/lib/asmcmdbase.pm</a> line 5015.
Use of uninitialized value $clus_mode in string eq at /app/oragrid/product/<a href="http://12.1.0.2/grid/lib/asmcmdbase.pm">12.1.0.2/grid/lib/asmcmdbase.pm</a> line 5043.
Use of uninitialized value $clus_mode in string eq at /app/oragrid/product/<a href="http://12.1.0.2/grid/lib/asmcmdbase.pm">12.1.0.2/grid/lib/asmcmdbase.pm</a> line 5092.
Use of uninitialized value $clus_mode in string eq at /app/oragrid/product/<a href="http://12.1.0.2/grid/lib/asmcmdbase.pm">12.1.0.2/grid/lib/asmcmdbase.pm</a> line 5092.
Use of uninitialized value $clus_mode in string eq at /app/oragrid/product/<a href="http://12.1.0.2/grid/lib/asmcmdbase.pm">12.1.0.2/grid/lib/asmcmdbase.pm</a> line 5092.
Use of uninitialized value $clus_mode in string eq at /app/oragrid/product/<a href="http://12.1.0.2/grid/lib/asmcmdbase.pm">12.1.0.2/grid/lib/asmcmdbase.pm</a> line 5139.

This is a known Bug 22135419 – 12C GRID HOME PERMISSIONS NOT RESET.

It can be fixed by unlock & relock the GRID_HOME again.

# /u01/app/12.1.0.2/grid/crs/install/rootcrs.pl -unlock
# /u01/app//12.1.0.2/grid/crs/install/rootcrs.pl –patch

While updating every node here a X5-2 with 4 Nodes the Clusterware will be restarted.

No problem while you can do it node by node.

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 [942923749].

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 [942923749].

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 [942923749].

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 [942923749].

Afterwards the cluster upgrade state is [NORMAL]

The Bug is very tricky while during the patching you saw no error

 

 

 

 

 

Oracle Exadata Software 12.1.2.3.0

cropped-exadata.jpg

Since February 2016 Oracle released a new Version of the Exadata Software.

The Release is 12.1.2.3.0.

Here a short overview

  • very fast Software Updates
  • VLAN Support in the Exadata Deployment Assistant for networks
  • High Redundancy for Quarter and Eighth Racks
  • a new Quorum Disk Manager utility as command line tool
  • Create Diagpack for tracefiles and alerts
  • Firmware Update for hard disk controller on X2-2, X3-2, X4-2, X2-8, X3-8, X4-8
  • new InfiniBand Switch Firmware 2.1.8-1
  • ILOM / BIOS Firmware Update
  • Storage Index Preservation across Rebalance

All details can be found in the Exadata Documenation:

http://docs.oracle.com/cd/E50790_01/doc/doc.121/e51953/app_whatsnew.htm#DBMSO21849

 

 

opatch lsinv doesn’t show Patching level of clusternodes

cluster_patch

 

 

 

We had a strange behaviour while running the „opatch lsinv“ in our Clusterware environment.

The opatch tool doesn’t show at the end the patchlevel and the name of the nodes itself.

It seems that during a lot of patch actions on this cluster that we lost the information inside the inventory.xml file that the CRS is equal true.

After researching of MOS we found a solution for this problem described in Doc-ID 1053393.1.

There ist a possibility to Update a flag CRS=true via the runinstaller in the GRID environment.

So the steps to fix this problem are the following

Our environment is a two node Oracle Enterprise Linux RAC Cluster with GI Software 12.1.0.2.


/u01/app/12.1.0.2/grid/oui/bin/runInstaller 
    -updateNodelist ORACLE_HOME="/u01/app/12.1.0.2/grid" CRS=true

Starting Oracle Universal Installer...

Checking swap space: must be greater than 500 MB. Actual 24575 MB Passed
The inventory pointer is located at /etc/oraInst.loc

'UpdateNodeList' was successful.

The "opatch lsinv" command show now the correct Patching Level and name of the Cluster nodes.

node1
Patch level status of Cluster nodes :

Patching Level Nodes
-------------- -----
1146027977 node2,node1

--------------------------------------------------------------------------------
node2
Patch level status of Cluster nodes :

Patching Level Nodes
-------------- -----
1146027977 node2,node1

--------------------------------------------------------------------------------
OPatch succeeded.

Additonal information

Check the software Patching level via the following command and compare the output with the „opatch lsinv“ as shown above.

[oracle@node1 ~]$crsctl query crs softwarepatch
Oracle Clusterware patch level on node node1 is [1146027977]

Yes, it is a good idea from time to time to check if both commands have the same output and also to update the opatch tool in your environment.

The latest opatch version can be downloaded via MOS link https://updates.oracle.com/download/6880880.html

 

 

 

Oracle Exadata and the glibc vulnerability (CVE-2015-7547)

Ora_Security_Patch

 

I think most of us heard about the „glibc“ vulnerability (CVE-2015-7547). We had a lot of Exadata Servers  and so we discuss how we could install the new rpm’s.

Yes, it seems to be no problem while My Oracle Support Doc-ID 2108582.1 describes what we had to do and by the way at the end of this procedure you had to reboot every DB Node and also every Cell Server. (While rebooting the Cell Server please read before the Doc-ID. 1188080.1.)

The note 2108582.1 said it is not necessary to do a relink but is this correct?

I was a little bit confused and I checked the Oracle Documentation and My Oracle Support again and I found  another Doc ID 1467060.1 „Relinking Oracle Home FAQ ( Frequently Asked Questions) “ which said that if you install an OS Patch than Oracle recommend to do a relink.

And in the Oracle Database Administrator Guide  was written that Oracle recommend to do an relink after Patching the OS.

We found for us a solution because we install the new rpm’s in conjunction with the Jan-2016 Patchbundle. During the Patchbundle Installation the relink was done automatically.

Keep in mind that Oracle Documentation recommend to do a relink no matter what an MOS Doc-ID said.

 

Clone ORACLE_HOME before installation of One-Off Patch

clone Kopie

We received a task from the quality department they need to test a new One-Off Patch in the test environment but we should not patch the actual installed version on this machine.

What could be a solution?

Often DBA’s install in this situation the whole Oracle Software stack from scratch and afterwards they patch this environment. But this could be very time consuming if you have to install a few bundle patches and some One-Off Patches.

We solve this problem by cloning the ORACLE_HOME and it works very good.

The environment is a two node RAC Cluster based on ASM with Grid & Oracle 11.2.0.4 software installed.

My Oracle Support: Doc ID 1221705.1 Cloning An Existing Oracle 11g Release 2

the steps are

as root user start a copy

cp -Rp /u01/app/oracle/product/11.2.0.4/dbhome_1 /u01/app/oracle/product/11.2.0.4/dbhome_2
as oracle user set the correct environment and start the Installer

cd $ORACLE_HOME/oui/bin

./runInstaller -detachHome ORACLE_HOME="/u01/app/oracle/product/11.2.0.4/dbhome_2"


cd $ORACLE_HOME/clone/bin

Start the perl script for cloning

perl clone.pl ORACLE_HOME="/u01/app/oracle/product/11.2.0.4/dbhome_2" ORACLE_HOME_NAME="OraDb11g_home3" ORACLE_BASE="/u01/app/oracle" OSDBA_GROUP=oinstall OSOPER_GROUP=oinstall

as root user start the root.sh script

/u01/app/oracle/product/11.2.0.4/dbhome_2/root.sh

final steps

check the log files

create the new diag directories

/u01/app/oracle/product/11.2.0.4/dbhome_2/bin/diagsetup basedir="/u01/app/oracle" oraclehome="/u01/app/oracle/product/11.2.0.4/dbhome_2"

Set the GRID environment and change the listener.ora for. ORACLE_HOME

lsnrctl reload listener

modify the “/etc/oratab”

While using RAC check the linked Oracle options Doc ID 948061.1

cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk rac_on ioracle
make -f ins_rdbms.mk ipc_rds ioracle

Now modify the database home

srvctl modify database -d tdb5o_s1 -o /u01/app/oracle/product/11.2.0.4/dbhome_2

srvctl start database -d tdb5o_s1

So the setup of the „new“ ORACLE_HOME is ready. Start with the installation of the One-Off Patch in rolling manner. (rolling while it is a RAC environment and the Patch is rolling installable.)

conclusion

As you see it is very easy to setup a second ORACLE_HOME for testing purposes.

If your One-Off Patch also updates the database via SQL Script use Flashback Database to set an guaranteed restore point before starting with the patching task.

After testing the One-Off Patch you do a flashback database and it is the same software level as before installing the patch.

 

Deinstallation von Oracle 11.2.0.X Software

Im normalen Betrieb kommt es selten vor, dass Oracle Software deinstalliert wird. Ich konnte mich auch nicht daran erinnern wann ich das letzte Mal RDBMS Software deinstalliert habe, aber jetzt liegt die Anfrage vor und zwar im Zusammenhang mit einer Teststellung.

Nach Abschluss der Teststellung für ein neues Produkt kam die Anfrage, dass die Software inklusive der dafür installierten Oracle Software gelöscht werden soll. Also dachte ich kein Problem starte doch einfach den runInstaller aus dem entsprechenden ORACLE_HOME und der „räumt“ dann auf.

Gesagt getan startet ich den Installer aus dem ORACLE_HOME  und dann kam direkt ein Pop-Up Window mit dem Hinweis man solle doch aus dem jeweiligen ORACLE_HOME das Programm „deinstall“ aufrufen.Gut also setzte ich die Umgebung und starte das deinstall Tool allerdings zuerst im „–precheck“ Modus.

Parallel schaute ich zur Sicherheit noch mal im Metalink nach und fand den Hinweis, dass Oracle ab der Release 11.2 empfiehlt die Software nicht mehr per Universal Installer zu deinstallieren. Vielmehr gibt es pro Oracle 11.2 Release ein separates deinstall Tool.

Dies ist in der der „Doc ID 1363753.1: Behaviour of the Oracle De-install/Deinstall/Uninstall Utility in 11gR2” ausführlich beschrieben.

So ging ich auf OTN und startete nun den Download the Software für die Release 11.2.0.4

http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

deinstall_tool

Nach dem Download wird zuerst das Tool in einem Verzeichnis außerhalb vom eigentlichen ORACLE_HOME ausgepackt.

Ich führte die Installation da es sich um einen RAC – Cluster auf dem ersten Clusterknoten durch.


<strong>/u01/app/oracle/deinstall</strong>

rw-r--r-- 1 root root 119521122 Nov  5 13:42 linux.x64_11204_deinstall.zip

unzip linux.x64_11204_deinstall.zip

Achtung! Das „deinstall“ Tool löscht nicht nur die Oracle Software mit sämtlichen Komponenten, sondern auch alle dazugehörigen Datenbanken, Konfig-Dateien auf dem Betriebssystem. Daher empfiehlt es sich vorher ein Backup durchzuführen.

Im Folgenden der Start des deinstall Tools und Output der Verarbeitung


$./deinstall -home /u01/app/oracle/product/11.2.0/dbhome_4



location of logs /u01/app/oraInventory/logs/

############ ORACLE DEINSTALL & DECONFIG TOOL START ############

######################### CHECK OPERATION START #########################

## [START] Install check configuration ##

Checking for existence of the Oracle home location /u01/app/oracle/product/11.2.0.4/dbhome_4

Oracle Home type selected for deinstall is: Oracle Real Application Cluster Database

Oracle Base selected for deinstall is: /u01/app/oracle

Checking for existence of central inventory location /u01/app/oraInventory

Checking for existence of the Oracle Grid Infrastructure home /u01/app/12.1.0.2/grid

The following nodes are part of this cluster: s96db1,s96db2

Checking for sufficient temp space availability on node(s) : 's96db1,s96db2'

&nbsp;

## [END] Install check configuration ##

Network Configuration check config START

Network de-configuration trace file location: /u01/app/oraInventory/logs/netdc_check2015-11-05_02-31-29-PM.log

Network Configuration check config END

Database Check Configuration START

Database de-configuration trace file location: /u01/app/oraInventory/logs/databasedc_check2015-11-05_02-31-34-PM.log

Use comma as separator when specifying list of values as input

Specify the list of database names that are configured in this Oracle home []:

Database Check Configuration END

Enterprise Manager Configuration Assistant START

EMCA de-configuration trace file location: /u01/app/oraInventory/logs/emcadc_check2015-11-05_02-35-33-PM.log

Enterprise Manager Configuration Assistant END

Oracle Configuration Manager check START

OCM check log file location : /u01/app/oraInventory/logs//ocm_check_2015-11-05_02-35-33-PM.log

Oracle Configuration Manager check END

######################### CHECK OPERATION END #########################

####################### CHECK OPERATION SUMMARY #######################

Oracle Grid Infrastructure Home is: /u01/app/12.1.0.2/grid

The cluster node(s) on which the Oracle home deinstallation will be performed are:s96db1,s96db2

Oracle Home selected for deinstall is: /u01/app/oracle/product/11.2.0.4/dbhome_4

Inventory Location where the Oracle home registered is: /u01/app/oraInventory

No Enterprise Manager configuration to be updated for any database(s)

No Enterprise Manager ASM targets to update

No Enterprise Manager listener targets to migrate

Checking the config status for CCR

s96db1 : Oracle Home exists with CCR directory, but CCR is not configured

s96db2 : Oracle Home exists with CCR directory, but CCR is not configured

CCR check is finished

Do you want to continue (y - yes, n - no)? [n]: y

A log of this session will be written to: '/u01/app/oraInventory/logs/deinstall_deconfig2015-11-05_02-31-23-PM.out'

Any error messages from this session will be written to: '/u01/app/oraInventory/logs/deinstall_deconfig2015-11-05_02-31-23-PM.err'

######################## CLEAN OPERATION START ########################

Enterprise Manager Configuration Assistant START

EMCA de-configuration trace file location: /u01/app/oraInventory/logs/emcadc_clean2015-11-05_02-35-33-PM.log

Updating Enterprise Manager ASM targets (if any)

Updating Enterprise Manager listener targets (if any)

Enterprise Manager Configuration Assistant END

Database de-configuration trace file location: /u01/app/oraInventory/logs/databasedc_clean2015-11-05_02-36-13-PM.log

&nbsp;

Network Configuration clean config START

Network de-configuration trace file location: /u01/app/oraInventory/logs/netdc_clean2015-11-05_02-36-13-PM.log

De-configuring Listener configuration file on all nodes...

Listener configuration file de-configured successfully.

De-configuring Naming Methods configuration file on all nodes...

Naming Methods configuration file de-configured successfully.

&nbsp;

De-configuring Local Net Service Names configuration file on all nodes...

Local Net Service Names configuration file de-configured successfully.

&nbsp;

De-configuring Directory Usage configuration file on all nodes...

Directory Usage configuration file de-configured successfully.

De-configuring backup files on all nodes...

Backup files de-configured successfully.

The network configuration has been cleaned up successfully.

Network Configuration clean config END

Oracle Configuration Manager clean START

OCM clean log file location : /u01/app/oraInventory/logs//ocm_clean_2015-11-05_02-35-33-PM.log

Oracle Configuration Manager clean END

Setting the force flag to false

Setting the force flag to cleanup the Oracle Base

Oracle Universal Installer clean START

Oracle Universal Installer clean START

&nbsp;

Detach Oracle home '/u01/app/oracle/product/11.2.0.4/dbhome_4' from the central inventory on the local node : Done

Delete directory '/u01/app/oracle/product/11.2.0.4/dbhome_4 on the local node : Done

The Oracle Base directory '/u01/app/oracle' will not be removed on local node. The directory is in use by Oracle Home '/u01/app/oracle/product/11.2.0.4/dbhome_1'.

Detach Oracle home '/u01/app/oracle/product/11.2.0.4/dbhome_4 from the central inventory on the remote nodes 's96db2' : Done

Delete directory '/u01/app/oracle/product/11.2.0.4/dbhome_4' on the remote nodes 's96db2' : Done

&nbsp;

Oracle Universal Installer cleanup was successful.

Oracle Universal Installer clean END

### [START] Oracle install clean ##

Clean install operation removing temporary directory '/tmp/deinstall2015-11-05_02-31-23PM' on node 's96db1'

Clean install operation removing temporary directory '/tmp/deinstall2015-11-05_02-31-23PM' on node 's96db2'

## [END] Oracle install clean ##

######################### CLEAN OPERATION END #########################

&nbsp;

&nbsp;

####################### CLEAN OPERATION SUMMARY #######################

Cleaning the config for CCR

As CCR is not configured, so skipping the cleaning of CCR configuration

CCR clean is finished

Successfully detached Oracle home '/u01/app/oracle/product/11.2.0.4/dbhome_4' from the central inventory on the local node.

Successfully deleted directory '/u01/app/oracle/product/11.2.0.4/dbhome_4 on the local node.

Successfully detached Oracle home '/u01/app/oracle/product/11.2.0.4/dbhome_4' from the central inventory on the remote nodes 's96db2'.

Successfully deleted directory '/u01/app/oracle/product/11.2.0.4/dbhome_4' on the remote nodes 's96db2'.

Oracle Universal Installer cleanup was successful.

Oracle deinstall tool successfully cleaned up temporary directories.

#######################################################################

############# ORACLE DEINSTALL & DECONFIG TOOL END #############

[oracle@s96db1 deinstall]$

Die Deinstallation lief ohne Probleme und löschte auf beiden Clusterknoten die Software und die dazugehörige Dateien, Datenbanken und Konfigurationsdateien.

Abschließend prüfte nochmal das  zentrale Inventory. Dort wird das gelöschte ORACLE_HOME als „REMOVED“ gekennzeichnet.


<strong>Check of central inventory File</strong>

cd /u01/app/oraInventory/ContentsXML

<HOME NAME="OraDb11g_home6" LOC="/u01/app/oracle/product/11.2.0.4/dbhome_4" 
TYPE="O" IDX="10" <strong><strong>REMOVED</strong></strong>="T"/>