Engineered Systems Arbeitsgruppe trifft Exadata Product Management

Nächste Woche startet die DOAG Konferenz 2021.

Auch in diesem Jahr wird die DOAG Engineered Systems Arbeitsgruppe sich über aktuelle Themen mit dem Exadata & ODA Product Management austauschen können.

Am Mittwoch, dem 17.11.2021 um 18:00 Uhr haben Kunden und Konferenzteilnehmer die Möglichkeit Fragen direkt ans Product Management zu stellen.

Vom Oracle Product Management sind dabei:

  • Gavin Parish
  • Carlos Ortiz
  • Paul Tsien

Wir freuen uns auf eine interessante und spannende Diskussion.

Wir sehen uns nächste Woche :-)

Exadata X9M angekündigt

Oracle Exadata Database Machine X9M

Die Exadata X9M Core Plattform basiert auf einer Scale-Out-Architektur, die die neuesten Intel CPUs, Intel® Optane™ Persistent Memory (PMem) und RDMA over Converged Ethernet (RoCE) kombiniert, um bis zu 27,6 Mio. IOPS und eine Latenz von unter 19 Mikrosekunden für OLTP Anwendungen liefert.

Zur Beschleunigung von Analytic Anwendungen liefert jedes X9M Rack einen Durchsatz beim Scannen von über 1 TB/s und bietet bis zu 576 CPUs in intelligenten Speicherservern zur Verarbeitung von Low-Level-SQL-Abfragen.

Ebenfalls neu ist die ZDLRA Appliance X9M

Die Recovery Appliance wurde speziell für den Schutz von Oracle-Datenbanken entwickelt und verfügt über einmalige Funktionen zur Wiederherstellung von Datenbanken ohne Datenverlust und zur automatischen Validierung von Backups.

Darüber hinaus stellt Oracle neue Cyber Vault Funktionen für die zuverlässige Wiederherstellung nach Ransomware Angriffen vor. Die neue Version der Recovery Appliance erhöht die Speicherkapazität um 30 Prozent. Der Einstiegspreis wurde um 50 Prozent gesenkt.

Zu den neuen Funktionen gehört auch die Synchronisation zwischen mehreren Recovery Appliances, um die Kontinuität von Backup und Recovery bei ungeplanten und geplanten Ausfällen zu gewährleisten. Darüber hinaus werden Optionen für die langfristige Backup-Aufbewahrung unterstützt.

Die Exadata X9M – Data Sheets – mit allen Details finden Sie hier

https://www.oracle.com/engineered-systems/exadata/database-machine/

Oracle Database World—Europe, Middle East, Africa

Hier stellt Oracle alle Neuigkeiten auch die X9M im Detail vor

https://www.oracle.com/de/database/database-world/event/

Agenda der DOAG 2021 Konferenz + Ausstellung 

Die Exadata X9M und viele Neuigkeiten werden natürlich auch auf der DOAG Konferenz 2021 vorgestellt

https://shop.doag.org/kua-agenda/

tfactl analyze error after AHF upgrade to 21.1.2

On a few Exadata Cluster I did an Upgrade of the AHF Software Stack to the actual

Version 21.1.2_20210513

Then I try to run „tfactl analyze“ and get the following error message:

ERROR! Unable to locate configuration file for tnt at /opt/oracle.ahf/tfa/ext/tnt/bin/tnt line 741.

ERROR! Unable to locate configuration file for tnt at /opt/oracle.ahf/tfa/ext/tnt/bin/tnt line 741.

To fix this error message do the following:

Run the below command on every node in the Cluster

tfactl createtntprop

tfactl analyze -last 2d works perfect again.

Exadata PMEMCache and PMEMLog – What’s to do?

Since 2019 the Exadata Machine X8M is out in the market with the new Persistent Memory (PMEM)

About PMEM you find a lot of articles which describe all the features and functions for example blogs.oracle.com

https://blogs.oracle.com/exadata/persistent-memory-in-exadata-x8m

 

But what does it mean for the daily DBA / DMA business?

While I am starting with the setup of a new X8M-2 Cluster I just take a closer look to the new component

 

Where do you find the PMEM?

PMEM ist part of the Storage Server and so you can take a look via ILOM WebGui / CLI

or via the „cellcli“ tool directly on the Storage Node

 


ssh celadm01
cellCLI list diskmap

Name PhysicalSerial SlotNumber Status PhysicalSize CellDisk DevicePartition GridDisks
PMEM_0_1 8089-a2-2022-000032d6 "CPU: 0; DIMM: 1" normal 126G PM_00_celadm01 /dev/dax5.0 "PMEMCACHE_PM_00_celadm01, PMEMLOG_PM_00_celadm01"
PMEM_0_3 8089-a2-2022-00003460 "CPU: 0; DIMM: 3" normal 126G PM_02_celadm01 /dev/dax4.0 "PMEMCACHE_PM_02_celadm01, PMEMLOG_PM_02_celadm01"
PMEM_0_5 8089-a2-2022-0000346a "CPU: 0; DIMM: 5" normal 126G PM_03_celadm01 /dev/dax3.0 "PMEMCACHE_PM_03_celadm01, PMEMLOG_PM_03_celadm01"
PMEM_0_6 8089-a2-2022-000034b3 "CPU: 0; DIMM: 6" normal 126G PM_04_celadm01 /dev/dax0.0 "PMEMCACHE_PM_04_celadm01, PMEMLOG_PM_04_celadm01"
PMEM_0_8 8089-a2-2022-00002f37 "CPU: 0; DIMM: 8" normal 126G PM_05_celadm01 /dev/dax1.0 "PMEMCACHE_PM_05_celadm01, PMEMLOG_PM_05_celadm01"
PMEM_0_10 8089-a2-2022-00002f56 "CPU: 0; DIMM: 10" normal 126G PM_01_celadm01 /dev/dax2.0 "PMEMCACHE_PM_01_celadm01, PMEMLOG_PM_01_celadm01"
PMEM_1_1 8089-a2-2022-0000317a "CPU: 1; DIMM: 1" normal 126G PM_06_celadm01 /dev/dax11.0 "PMEMCACHE_PM_06_celadm01, PMEMLOG_PM_06_celadm01"
PMEM_1_3 8089-a2-2022-00003041 "CPU: 1; DIMM: 3" normal 126G PM_08_celadm01 /dev/dax10.0 "PMEMCACHE_PM_08_celadm01, PMEMLOG_PM_08_celadm01"
PMEM_1_5 8089-a2-2024-00003922 "CPU: 1; DIMM: 5" normal 126G PM_09_celadm01 /dev/dax9.0 "PMEMCACHE_PM_09_celadm01, PMEMLOG_PM_09_celadm01"
PMEM_1_6 8089-a2-2024-00003ada "CPU: 1; DIMM: 6" normal 126G PM_10_celadm01 /dev/dax6.0 "PMEMCACHE_PM_10_celadm01, PMEMLOG_PM_10_celadm01"
PMEM_1_8 8089-a2-2024-00003948 "CPU: 1; DIMM: 8" normal 126G PM_11_celadm01 /dev/dax7.0 "PMEMCACHE_PM_11_celadm01, PMEMLOG_PM_11_celadm01"
PMEM_1_10 8089-a2-2024-00003be5 "CPU: 1; DIMM: 10" normal 126G PM_07_celadm01 /dev/dax8.0 "PMEMCACHE_PM_07_celadm01, PMEMLOG_PM_07_celadm01"

 


Next the Physical details and the Pmem Cache Details

CellCLI list physicaldisk detail
name: PMEM_1_10
diskType: PMEM
luns: P1_D10
makeModel: "Intel NMA1XXD128GPS"
physicalFirmware: 1.02.00.5435
physicalInsertTime: 2020-12-10T03:57:18+01:00
physicalSerial: 8089-a2-2024-00003be5
physicalSize: 126.375G
slotNumber: "CPU: 1; DIMM: 10"
status: normal


list pmemcache detail
name: celadm01_PMEMCACHE
cellDisk: PM_00_celadm01,PM_01_celadm01,PM_02_celadm01,PM_03_celadm01,PM_04_celadm01,PM_05_celadm01,PM_06_celadm01,PM_07_celadm01,PM_08_celadm01,PM_09_celadm01,PM_10_celadm01,PM_11_celadm01
creationTime: 2021-01-25T10:24:33+01:00
degradedCelldisks:
effectiveCacheSize: 1.465576171875T
id: 25e45edc-a027-463f-91a0-1185b03a7a8b
size: 1.465576171875T
status: normal

Weiterlesen

cluvfy „cheat sheet“ for RAC-Setup

While doing new RAC Cluster setup’s I was looking in parallel for an easy way to check an existing or new Oracle RAC Installation.

Yes, the tool to do most of the tasks is „cluvfy“, the Cluster Verification Utility. cluvfy can de downloaded and installed as standalone version.

cluvfy will be updated in a regular manner up to the actual Oracle Release Updates.

So please check My Oracle Support Patch 30839369. 

 

Download latest CVU Version and do the Setup 

Patch 30839369: Standalone CVU version 19.9 October 2020

 

check the Setup and Version

cluvfy –version

 

Here is my cluvfy „cheat sheet“

 

Post Hardware & OS Setup

    • cluvfy stage -post hwos -n all

 

Post Network Installation

    • cluvfy comp nodecon -n all -verbose

 

Post CRS Software Setup

    • cluvfy stage -post crsinst -n all

 

Clustermanager integrity

    • cluvfy comp clumgr –allnodes

 

Check OCR integrity

    • cluvfy comp ocr -allnodes

 

Check ASM integrity (if used)

    • cluvfy comp asm -allnodes

 

Post check Oracle Home Setup and all your other Oracle Homes

    • cluvfy comp software -allnodes -d /u01/app/oracle/product/19.0.0/dbhome_1 -allfiles

 

I do not post the output from all these commands because this depends on your RAC Setup. 

What I can say is the checks and the output is very detailed and helpful.

If you get error messages during the runtime fix these errors because then you can be sure that your RAC setup is healthy and functioning. 

 

 

 

 

Oracle Exadata Deployment Assistant (OEDA) new Update Dec 2020

The configuration of an Exadata Systems without the OEDA tool is not possible. Oracle is continuously improving this tool. In the meantime there are monthly updates available. This ensures that every hardware or software change can be implemented on customer site via OEDA.

What has to be done to get the OEDA up and running?

Download the patch from My Oracle Support  Patch 30640393

The tool is available for many platforms including Windows, Mac OS, Linux, etc.

The actual monthly build is

Update 32241522 for Release 19.9 and Earlier

from December 2020

After the download unzip the file. In my environment a directory „macosx-x64″ was created.

The Setup is very easy start on the command line

./installOedaServer.sh -p 7072

At the end of the installation the Webserver starts on the localhost

the OEDA tool automatically in your browser.

http://localhost:7072/oeda

 

 

Now you are ready to start the configuration for the new Exadata Project.

 

 

 

 

 

 

 

How to check the Oracle Patch history

(new Update see below)

Patching is a task which is really often done and if you sit in front of a Oracle System which

you know while doing regularly maintenance the Patch status is more or less known to you

 

But what if your college ask:

„Please check an Oracle System from a new customer and let me know if they had patched

the System in the last six month.“

 

Now most of us do a Login set the environment for example Oracle_Home or Grid_Home

and start an „opatch“ or checked via the database and registry.

 

To get a complete overview what happen on the System is more easy from my point of view

while taking a look in the opatch_history.txt file.

This textfile exist for every Oracle Home on the server and shows the complete history

 

ssh host1

su - oracle

cat /etc/oratab

db1:/u01/app/oracle/product/12.2.0.1/dbhome_1:Y

. oraenv

cd /u01/app/oracle/product/12.2.0.1/dbhome_1/cfgtoollogs/opatch

vi opatch_history.txt


You saw exactly at which time which command was entered against the Oracle Home.

So you can very easy check when and which Patches where applied in the last time.

 

Date & Time : Mon Aug 03 02:05:45 CEST 2020

Oracle Home : /u01/app/oracle/product/12.2.0.1/dbhome_1

OPatch Ver. : 12.2.0.1.19

Current Dir : /u01/app/oracle/product/12.2.0.1/dbhome_1

Command     : lsinventory -oh /u01/app/oracle/product/12.2.0.1/dbhome_1 -local -invPtrLoc /u01/app/oracle/product/12.2.0.1/dbhome_1/oraInst.loc

Log File    : /u01/app/oracle/product/12.2.0.1/dbhome_1/cfgtoollogs/opatch/opatch2020-08-03_02-05-45AM_1.log


Another example for an Oracle Grid Home here Release 19c.

 

Grid Home is „/u01/app/19.0.0/grid“

/u01/app/19.0.0/grid/cfgtoollogs/opatch/opatch_history.txt

 

Date & Time : Mon Aug 03 02:26:04 CEST 2020

Oracle Home : /u01/app/19.0.0/grid

OPatch Ver. : 12.2.0.1.17

Current Dir : /u01/app/19.0.0/grid

Command     : lsinventory -oh /u01/app/19.0.0/grid -local -invPtrLoc /u01/app/19.0.0/grid/oraInst.loc

Log File    : /u01/app/19.0.0/grid/cfgtoollogs/opatch/opatch2020-08-03_02-26-04AM_1.log
Try it and check your opatch_history.txt file. It is really helpful.

 

Update on this Post after Roy (Swonger) VP from Oracle ask me if I can add an additional information I do of course.

Roy says:

One of the most common issues I see is when customers run OPatch but forget to run Datapatch to apply the SQL changes to the database. Mike had a good blog post about the dba_registry_history and dba_registry_sqlpatch views that explains which to use depending on the version you are running: https://mikedietrichde.com/2016/11/30/dba_registry_history-vs-dba_registry_sqlpatch/ 

Yes, please take a look to Mike’s Blog which is very helpful (as all his posts 👍)

In my special case the main topic of my college was the question „Can you check if the customer has tried to install Patches in the Grid Home during the last month?“. This question could be easy answered via the opatch_history.txt file. 

So have fun during the next patching action and not forget the datapatch