Exadata in den OCI Exadata Cloud Service - Von On-Premises - DOAG
←
→
Transkription von Seiteninhalten
Wenn Ihr Browser die Seite nicht korrekt rendert, bitte, lesen Sie den Inhalt der Seite unten
Von On-Premises
Exadata in den OCI
Exadata Cloud Service
Präsentiert von Jessica Steger und Stefan Seck
1
Agenda / Inhaltsverzeichnis
► Allgemeines zum Exadata Cloud Service
► Design-Phase
► verwendete Cloud Services
► Netzwerk und Security
► Migrations-Phase
► Migrations-Szenarien
► Budget
► ExaCS im Einsatz
► Best Practices
► Maintenance
► Patching
► Additional Steps
Die nachfolgenden Slides enthalten Textausschnitte
und Grafiken aus Oracle Hersteller-Präsentationen
Logicalis Von On-Premises in Exadata Cloud Service 2Exadata Cloud Service Logicalis Von On-Premises in Exadata Cloud Service 3
Exadata Lösungen
Level of automation
On-Premises Cloud at Customer Public Cloud
Cloud at Customer Cloud Service Cloud
Customer Data Center Oracle Data Center
Customer Managed Co-Managed Fully Oracle Managed
Purchased Subscription with Universal Credit-based Consumption
Logicalis
4
Von On-Premises in Exadata Cloud Service 4Exadata Database Cloud Service Management model
Data/Schema ► Kunde verantwortet alles innerhalb der Datenbank – Daten, Schemata, etc.
Customer
► Kein Oracle Zugriff
Databases
► Kunde kontrolliert Automation für DBs und VMs
DomU
► Nutzt Oracle Tooling für Anlage, Patching, Backup, Skalierung von DBs
► Betreibt die supporteten Oracle Datenbank Versionen 11.2.0.4 bis 19c
Hypervisor
► Kein Oracle Zugriff auf DomU und die Datenbanken
► Customer betreibt Software und Operationen in DomU und verantwortet zugehörige
Exadata
DB Servers Themen
► Patchen der domU mit Grid, OH über patchmgr ; imageinfo als root / sudo
Oracle
NW fabric
► Oracle besitzt, managed, und kontrolliert Hypervisor mit dom0, DB Server, Storage
Server, Infrastruktur Network, etc.
Exadata Storage
Servers ► Kein Kunden-Zugriff oder Kontrolle, Oracle verantwortet alle Themen
► Rolling Patching der dom0, Cells und Switche von Oracle
Logicalis
5
Von On-Premises in Exadata Cloud Service 5ExaCS System Shapes
Exadata Database Cloud
Base System X8 Quarter Rack X8 Half Rack X8 Full Rack
Service Shapes
Anzahl Datenbank Server 2 2 4 8
Maximale OCPUs 48 100 200 400
Summe RAM der Database Server 720 GB 1,440 GB 2,880 GB 5,760 GB
Anzahl Storage Servers 3 3 6 12
Gesammte Flash Kapazität 38.4 TB 76.8 TB 153.6 TB 307.2 TB
Max DB Größe – kein ASM Backup 59.8 TB 119.8 TB 239.5 TB 479.0 TB
SQL 8K Read IOPS 562,500 1,194,000 2,388,000 4,776,000
SQL 8K Write IOPS 518,000 1,088,000 2,176,000 4,352,000
Logicalis
6
Von On-Premises in Exadata Cloud Service 6Software Lizenz Modelle
Oracle Database Enterprise Edition Oracle Database Enterprise Edition Bring
Extreme Performance Your Own License
▪ Für maximale Innovation ▪ Zur Bewahrung der On-Premises Investitionen
▪ Enthält alle Oracle Datenbank Optionen und ▪ Enthält nur zu nutzende Optionen
Management Packs ▪ 1 On-Premises Lizenz = 2 OCPUs
▪ inklusive Software Support ▪ Software Support notwendig
▪ Reduziert TCO starker als andere Clouds
Security und Performance Optionen enthalten in BYOL
RAC Active Data Partitioning Multi-tenant
Guard
Plus alle anderen Optionen
und Management Packs.
Advanced Transparent Data Masking Real Application Diagnostics &
Compression in-Memory DB Data Encryption & Subsetting Testing Tuning Pack
Logicalis
7
Von On-Premises in Exadata Cloud Service 7Scaling und Bursting
Konfigurierte OCPUs
► OCPU nutzungsbasierte Kosten
► Stündliche Anpassung, keine Mindest-Abnahme
► mindestens 2 OCPUs pro DB-Server
Einsparung
CPU Nutzung
► OCPUS lassen sich ohne Downtime ändern
► Zahlung über Universal Credits
► Reservierte Exadata Infrastruktur Stündliches
► 48-hour minimale Laufzeit mit Pay-as-You-Go, ansonsten Scaling aktivierte
monatlicher Festpreis OCPUs
► Hardware Kosten zusammen mit Storage Server SW und Workload
Support
► Base System und QR:
Skalierung der OCPU als Vielfaches von 2 für beide DB Nodes
► Half Rack: Skalierung der OCPU als Vielfache von 4
► Full Rack: Skalierung der OCPU als Vielfache von 8 Nutzungs-Zeit
Logicalis
8
Von On-Premises in Exadata Cloud Service 8Design Phase Logicalis Von On-Premises in Exadata Cloud Service 9
Oracle Cloud Infrastructure (OCI)
► Standort Frankfurt in drei Rechenzentren (ADs) mit mind. 8 km Entfernung
► Provider Equinix und Interxion
► End-to-End SLA auf Verfügbarkeit, Performance, und Verwaltbarkeit (APIs)
► IaaS SLAs unter https://cloud.oracle.com/iaas/sla
► Neue Services flexibel einbindbar (Docker & Kubernetes, Mongo DB, Analytics, Autonomous DB etc.)
► Sicher, da nur Kunde oder der MSP Zugriff auf Netzwerk und deren VMs hat (ssh-Keys hat nur der Kunde / MSP)
► Flexibel skalierbar, Mehrbedarf kann schnell abgefangen werden
► Global verteilte OCI Regionen
► Anbindung an Azure über private Peering (Frankfurt geplant)
► Dokumentation für IaaS und PaaS Services unter
https://docs.cloud.oracle.com/en-us/iaas/pdf/ug/OCI_User_Guide.pdf
10Von On-Premises in Exadata Cloud ServiceOCI Universal Credits
http://www.oracle.com/us/corporate/contracts/paas-iaas-universal-credits-3940775.pdf
► Universal Credits können für IaaS und PaaS Service genutzt werden
► Monatlicher oder Jährlicher Sockelbetrag (Monthly Flex und Annual Flex) wird je nach Laufzeit und Abnahmevolumen
rabattiert
► IaaS & PaaS Leistungen werden entsprechend der Rate Card Preise vom Sockelbetrag abgezogen
► Mehrbedarf für Lastpeaks und Wachstum wird direkt von Oracle über in Rate Card genannten „Overage“ Preis abgerechnet
► Neue Cloud Services werden entsprechend der in der Rate Card genannten Rabatte für die jeweilige Produkt-Kategorie
bepreist
11Von On-Premises in Exadata Cloud ServiceExadata Cloud Service
► 99.95% Availability SLA mit Real Application Clusters und Active Data Guard
► ExaCS Wechsel auf andere Shape über Data Guard
► X8M Generation bietet Flex Shape nach Bereitstellung eines QR Systems
=> Anpassung der Anzahl von DB- und Storage Servern
1. Exadata Infrastructure => Scale Infrastructure
2. Exadata VM Clusters => Scale Exadata VM Cluster
► Exadata Cloud Service Service Limit erhöhen (1 Monat vorher)
► Anforderung Anbindung an Co-Location Equinix
► Cross-Connects vom Fastconnect in das Colo-Rack
► AD1 etc für jeden Kunden anders, damit eine Gleichverteilung der genutzten Ressourcen erreicht wird
Logicalis Von On-Premises in Exadata Cloud Service 12Service Limit nur für notwendige ADs erhöhen Logicalis Von On-Premises in Exadata Cloud Service 13
ExaCS Diskgruppen Sizing Logicalis Von On-Premises in Exadata Cloud Service 14
Weitere verwendete Cloud Services
► Netzwerk-Anbindung
► Private Anbindung an On Premises mit Oracle FastConnect mit 1 Gbps oder 10 Gbps
► Ausgehender Datenverkehr ab 10 TB / Monat kostenpflichtig
► Object Storage für Backup, direkte Integration des Exadata Cloud Services für RMAN Backups
► SLA 99,9 %, mehrere Kopien über ADs hinweg
► Korrupte Datenblöcke werden automatisiert erkannt und bereinigt
► Compute Ressourcen (VMs und Block Storage), keine Downtime bei Skalierung, flexible RAM und Core Zuweisung
► nur innerhalb einer AD in mehreren Fault Domains: SLA 99,95 % (Downtime/a < 21,56 min)
► Verteilt über mindestens zwei Ads: SLA 99,99 % (Downtime/a < 4,38 min)
► File Storage, NFSv3-kompatibles File System
► NAS Service wird aus einer AD bedient
► Storage Snapshots täglich zeitgleich mit RMAN Backup
Logicalis Von On-Premises in Exadata Cloud Service 15OCI File Service Architektur
OCI REGION
AVAILABILITY DOMAIN-1 AVAILABILITY DOMAIN-2
File System
► Primary resources for storing files in FSS
10.0.2.0/24
► To access your file systems, you create a new (or
use an existing) mount target
► 100 File Systems per Mount Target
► AD-specific
► Accessible from OCI VM/BM instances
NFS client ► Accessible from on-premises through
NFS client
FastConnect/VPN
10.0.0.0/24 10.0.1.0/24
VCN, 10.0.0.0/16
Logicalis Von On-Premises in Exadata Cloud Service 16Netzwerk-Layout
► Netzwerk-Layout
► Frontend in Public LAN (Load Balancer VIP)
► App-Server und DBs in private LAN
► ExaCS Client LAN
► ExaCS Backup LAN
► VPN keine doppelten Subnetze, VPN Konfig schwer zu troubleshooten, da VPN keine Logfiles im OCI, genau an die OCI
Anleitung halten!
► Security-Listen
Logicalis Von On-Premises in Exadata Cloud Service 17ORACLE CLOUD INFRASTRUCTURE (Frankfurt)
Availability Domain 1 Availability Domain 2 AD 3
Internet
Prod-LB Test-LB
Gateway
VIP VIP
Subnet A PROD Subnet F Test PROD- Test
10.0.60.0/24 LB 02 Subnet E
10.0.10.0/24 LB02
Mgmt
PROD- Test 10.0.50.0/2
NAT LB 01 LB 01 4
Gateway
Subnet B PROD
10.0.20.0/24 ID & Access
Prod Prod Monitoring Management
App-Server App-Server Server
Subnet C Test
Kunde 10.0.30.0/24
Test Test
App-Server App-Server File Storage
Dynamic
Routing
Subnet D Primary Prod DBs Standby Prod DBs
Health-Check Monitoring 10.0.40.0/24Standby Test DBs Primary Test DBs
Gateway
VPN OEM
Service Desk Server
Service Management
Managed Service via ssh
Exadata Exadata Object
System System Storage
zusätzliche HW
FastConnect (1 Gbit) zusätzliche HW
DBs- und Appserver Colocation (Equinix) Colocation (Equinix)
in andere Clouds
Von On-Premises in Exadata Cloud Service
18Migrations-Phase Logicalis Von On-Premises in Exadata Cloud Service 19
Migrations-Phase
► ZDM
► über Backup & Restore geht, und DB-Files sind anschließend verschlüsselt
► Data Guard einrichten geht nicht, da SCAN Listener Zugriff aus der Cloud auf das On Premises System nicht auf das
Client-Netz zugegriffen werden konnte
► Data Guard Handling in GUI => Switchover von Standby Seite aus
► Data Guard per Tooling nur als async / Maximum Performance möglich => Maximum Availability von Hand aufsetzen
► Migration über RMAN-Backup & Data Guard
► DB ist nicht verschlüsselt
► Data Guard für minimal Downtime Migration
► nach Go-Live erst Verschlüsselung einschalten
► Backup in Object Storage
Logicalis Von On-Premises in Exadata Cloud Service 20Probleme
► nach Patchen war DB nicht gepatched
► Clustername max 11 Buchstaben, kein Unterstrich
► exacli mit Cluster-Namen exacsclu plus Clustername-ID exacsclu-069 !
► enable Data Guard über Cloud Tooling
=> Wallets werden gezippt übertragen, Backup-Library wird auch übertragen
=> wenn mehr als 80 MB übertragen werden, bricht der Job ab
► Bug 31669774 : EXACS :- THE DATAGUARD OPERATION FAILED BECAUSE THE PRIMARY DATABASE WALLET SIZE
EXCEEDED THE LIMIT OF 1MB
► Bug 31477766 : EXACS :- THE DATAGUARD OPERATION FAILED BECAUSE THE PRIMARY DATABASE WALLET SIZE
EXCEEDED THE LIMIT OF 1MB.
=> Both are closed as Duplicate of
Bug 31266378 : SEND_WALLET CREATING TAR FILE TOO LARGE
Logicalis Von On-Premises in Exadata Cloud Service 21Kostenkontrolle, daher Budget einrichten Logicalis Von On-Premises in Exadata Cloud Service 22
ExaCS im Einsatz Logicalis Von On-Premises in Exadata Cloud Service 23
Best Practices for ExaCS DB Systems
• Use Oracle-supplied cloud interfaces
• Oracle Cloud Infrastructure Console
• Oracle Cloud My Services REST APIs
• CLI or cloud-specific tools like dbaascli and dbaasapi
• to perform lifecycle management
• for administrative operations on your Exadata DB system.
• If an operation can be performed by using the Console as well as a command line utility, Oracle recommends that you
use the Console.
• e.g.: use the Console instead of using dbaasapi to create databases.
• Compute Node OS
• Do not change users
• Do not manually manipulate SSH key settings associated with your Exadata DB system
Logicalis Von On-Premises in Exadata Cloud Service 24Best Practices for ExaCS DB Systems
• Database Patches
• use the exadbcpatchmulti to apply Oracle Database patches instead of manually running opatch.
• apply only patches that are available through the Database service.
• Do not apply patches from any other source unless you are directed to do so by Oracle Support.
• Apply the quarterly patches regularly, every quarter if possible.
• Do not change the ports for Oracle Net Listener.
Logicalis Von On-Premises in Exadata Cloud Service 25Exadata Cloud Service typical Deployment Flow
Creating
Creating Creating Modifying Launching
Creating a Gateways- Creating
Routing Security Security Exadata
VCN NAT/IGW Subnets
Tables Lists Rules DB System
and SG
• Note: Service Gateway can handle all internal communication including backups, patching within OCI region
• The two subnets you create for the Exadata DB system must not overlap with 192.168.128.0/20.
• Note: For deploying Exadata Cloud Service in OCI you must have IAM policy allowing the operation.
E.g: Allow group DBAdmins to manage database-family in tenancy
Logicalis Von On-Premises in Exadata Cloud Service 26Security Rules for the Exadata System (EXA_SL & EXABCK_SL) Logicalis Von On-Premises in Exadata Cloud Service 27
Security Rules for the Exadata System (EXA_SL) Logicalis Von On-Premises in Exadata Cloud Service 28
Node Access to Object Storage: Static Route To be able to back up databases, and patch and update cloud tools on an Exadata DB system, you must configure access to Oracle Cloud Infrastructure Object Storage. Regardless of how you configure the VCN with that access (for example, with a service gateway), you may also need to configure a static route to Object Storage on each of the compute nodes in the cluster. This is only required if you are not using automatic backups. If you are using customized backups using the backup APIs, then you must route traffic destined for Object Storage through the backup interface (BONDETH1). This is not necessary if you are using the automatic backups created with the Console, APIs, or CLIs. Logicalis Von On-Premises in Exadata Cloud Service 29
Security Rules for Exadata DB Backup Logicalis Von On-Premises in Exadata Cloud Service 30
Object Storage IP allocations Oracle Cloud Infrastructure Object Storage uses the CIDR block IP range 134.70.0.0/17 for all regions. This range was introduced in April and May of 2018. As of June 1, 2018, Object Storage no longer supports the following discontinued IP ranges. Oracle recommends that you remove these older IP addresses from your access-control lists, firewall rules, and other rules after you have adopted the new IP ranges. The discontinued IP ranges are: • Germany Central (Frankfurt): 130.61.0.0/16 • UK South (London): 132.145.0.0/16 • US East (Ashburn): 129.213.0.0/16 • US West (Phoenix): 129.146.0.0/16 Logicalis Von On-Premises in Exadata Cloud Service 31
Configure a static route for Object Storage access
1. SSH to a compute node in the Exadata DB system.
2. Log in as opc and then sudo to root user. Use sudo su - with a hyphen to invoke the root user's profile.
3. Identify the gateway configured for the BONDETH1 interface.
[root@dbsys ~]# grep GATEWAY /etc/sysconfig/network-scripts/ifcfg-bondeth1 | awk -F"=" '{print$2} ' 172.0.0.1
4. Add the following static rule for BONDETH1 to the /etc/sysconfig/networkscripts/route-bondeth1 file:
10.0.X.0/XX dev bondeth1 table 211
default via dev bondeth1 table 211
134.70.0.0/17 via dev bondeth1
5. Restart the interface.
[root@dbsys ~]# ifdown bondeth1; ifup bondeth1;
The file changes from the previous step take effect immediately after the ifdown and ifup commands run.
6. Repeat the preceding steps on each compute node in the Exadata DB system.
Logicalis Von On-Premises in Exadata Cloud Service 32A rchitects of C hange ExadataCS - Maintenance Logicalis Von On-Premises in Exadata Cloud Service 33
Change Exadata Automatic Infrastructure Maintenance Logicalis Von On-Premises in Exadata Cloud Service 34
Change next Exadata DB System Maintenance Logicalis Von On-Premises in Exadata Cloud Service 35
Maintenance / Maintenance History Logicalis Von On-Premises in Exadata Cloud Service 36
A rchitects of C hange ExadataCS - Patching Logicalis Von On-Premises in Exadata Cloud Service 37
Patching Exadata DB Systems, Databases, and Database Homes
Patching an Exadata DB system updates the components on all the compute nodes on that system.
DB system patch updates the grid infrastructure (GI)
Database Home patch updates the Oracle Database software shared by the databases in that home.
patch by moving it to a patched Database Home
patch the current Database Home
Best Practices:
• Back up your databases before you apply any patches
• Patch a DB system before you patch the Databases Homes and databases on that system.
• run the precheck operation
• To patch a database to a version other than the database version of the current home, move the database to a Database
Home running the target version. This technique requires less downtime and allows you to easily roll back the database to
the previous version by moving it back to the old Database Home.
Logicalis Von On-Premises in Exadata Cloud Service 38Exadata DB System Patch How to update Exadata System Software on database servers in the Exadata Cloud Service (Doc ID 2417624.1) How to update the Exadata System Software (DomU) to 19c on the Exadata Cloud Service in OCI (Doc ID 2521053.1) Logicalis Von On-Premises in Exadata Cloud Service 39
Patch DB System Logicalis Von On-Premises in Exadata Cloud Service 40
Patch Database Home Logicalis Von On-Premises in Exadata Cloud Service 41
Patch History Logicalis Von On-Premises in Exadata Cloud Service 42
Check Patch with opatch [oracle@EXACS6-8bi441 ~]$ opatch lspatches 30432118;MERGE REQUEST ON TOP OF 19.0.0.0.0 FOR BUGS 28852325 29997937 29997959;DSTV34 UPDATE - TZDATA2019B - NEED OJVM FIX 30413137;ORA-00600 INTERNAL ERROR CODE, ARGUMENTS [2006] 30484981;OJVM RELEASE UPDATE: 19.6.0.0.200114 (30484981) 30557433;Database Release Update : 19.6.0.0.200114 (30557433) 30489227;OCW RELEASE UPDATE 19.6.0.0.0 (30489227) [opc@EXACS6-8bi441 ~]$ sudo su - grid Last login: Mon May 11 12:11:21 CEST 2020 [grid@EXACS6-8bi441 ~]$ opatch lspatches 30898856;TOMCAT RELEASE UPDATE 19.0.0.0.0 (30898856) 30894985;OCW RELEASE UPDATE 19.7.0.0.0 (30894985) 30869304;ACFS RELEASE UPDATE 19.7.0.0.0 (30869304) 30869156;Database Release Update : 19.7.0.0.200414 (30869156) Logicalis Von On-Premises in Exadata Cloud Service 43
Check Patch with opatch lsinv
Local Machine Information::
Hostname: EXACS6-8bi441.exasn.dat.oraclevcn.com
ARU platform id: 226 Patch 30413137 : applied on Wed Jan 08 16:04:10 CET 2020
ARU platform description:: Linux x86-64 Unique Patch ID: 23192721
Patch description: "ORA-00600 INTERNAL ERROR CODE, ARGUMENTS
Installed Top-level Products (1): [2006]"
Created on 6 Nov 2019, 03:58:55 hrs PST8PDT
Oracle Database 19c 19.0.0.0.0
There are 1 products installed in this Oracle Home. Patch 30484981 : applied on Wed Jan 08 16:03:22 CET 2020
Unique Patch ID: 23248235
Patch description: "OJVM RELEASE UPDATE: 19.6.0.0.200114
Interim patches (6) : (30484981)"
Created on 5 Dec 2019, 05:10:10 hrs PST8PDT
Patch 30432118 : applied on Wed Jan 08 16:05:30 CET 2020
Unique Patch ID: 23166117 Patch 30557433 : applied on Wed Jan 08 15:58:40 CET 2020
Unique Patch ID: 23305305
Patch description: "MERGE REQUEST ON TOP OF 19.0.0.0.0 FOR BUGS 28852325 29997937"
Created on 3 Dec 2019, 18:28:56 hrs PST8PDT Patch description: "Database Release Update : 19.6.0.0.200114
(30557433)"
Patch 29997959 : applied on Wed Jan 08 16:05:00 CET 2020 Created on 6 Jan 2020, 19:07:34 hrs PST8PDT
Unique Patch ID: 23176319
Patch description: "DSTV34 UPDATE - TZDATA2019B - NEED OJVM FIX" Patch 30489227 : applied on Wed Jan 08 15:55:42 CET 2020
Created on 23 Oct 2019, 00:10:00 hrs PST8PDT Unique Patch ID: 23305624
Patch description: "OCW RELEASE UPDATE 19.6.0.0.0 (30489227)"
Created on 7 Jan 2020, 03:37:45 hrs PST8PDT
-----------------------------------------------------------------
---------------
OPatch succeeded.
Logicalis Von On-Premises in Exadata Cloud Service 44Checking available cloud tooling updates [root@EXACS6-8bi441 ~]# dbaascli patch tools list DBAAS CLI version 19.4.4.0.0DBGI Executing command patch tools list Checking tools on all nodes Current Patchid on EXACS6-8bi441: 19.4.4.0.0DBGI_200331.1141 No applicable tools patches are available All Nodes have the same tools version [root@EXACS6-8bi441 ~]# dbaascli patch tools auto status DBAAS CLI version 19.4.4.0.0DBGI Executing command patch tools auto status /var/opt/oracle/misc/rpmupd -status INFO : auto rpm update is enabled dbaascli Execution completed Logicalis Von On-Premises in Exadata Cloud Service 45
Viewing Information about Available Software Images [root@EXACS6-8bi441 ~]# dbaascli cswlib list DBAAS CLI version 19.4.4.0.0DBGI Executing command cswlib list INFO : Log file => /var/opt/oracle/log/list/list_2020-05-11_16:31:46.67162241956.log INFO : dbimage fixup executed. ############ List of Available BP ############# -OCT2019 (For DB Versions 18000 12201 12102 11204 19000) -JAN2020 (For DB Versions 18000 12201 12102 11204 19000) -APR2020 (For DB Versions 18000 12201 12102 11204 19000) ############ List of Available NONCDB BP ####### -OCT2019 (For DB Versions 12102 19000) -JAN2020 (For DB Versions 12102 19000) -APR2020 (For DB Versions 12102 19000) Logicalis Von On-Premises in Exadata Cloud Service 46
List Patches Oracle Grid Infrastructure [root@EXACS6-8bi441 ~]# dbaascli patch db list --oh EXACS6-8bi441:/u01/app/19.0.0.0/grid DBAAS CLI version 19.4.4.0.0DBGI Executing command patch db list --oh EXACS6-8bi441:/u01/app/19.0.0.0/grid INFO : EXACS patching Reference found where even-sized list expected at /var/opt/oracle/exapatch/precheck.pm line 64. No applicable patches are available Oracle Database [root@EXACS6-8bi441 ~]# dbaascli patch db list --oh EXACS6-8bi441:/u02/app/oracle/product/19.0.0.0/dbhome_2 DBAAS CLI version 19.4.4.0.0DBGI Executing command patch db list --oh EXACS6-8bi441:/u02/app/oracle/product/19.0.0.0/dbhome_2 INFO : EXACS patching Reference found where even-sized list expected at /var/opt/oracle/exapatch/precheck.pm line 64. Available Patches patchid :30899722 (Database Release Update : 19.7.0.0.200414 (Apr 2020)) Install database patch using dbaascli patch db apply --patchid 30899722 --dbnames Logicalis Von On-Premises in Exadata Cloud Service 47
To check prerequisites before applying a patch Oracle Database: [root@EXACS6-8bi441 ~]# dbaascli patch db prereq --patchid 30899722 --dbnames exacs19c DBAAS CLI version 19.4.4.0.0DBGI Executing command patch db prereq --patchid 30899722 --dbnames exacs19c INFO: EXACS patching This might take some time, please take a look at file /var/opt/oracle/log/exadbcpatch/exadbcpatch.log for progress Prereq check completed successfully, ready to apply patch Logicalis Von On-Premises in Exadata Cloud Service 48
Apply a Patch Oracle Database: [root@EXACS6-8bi441 ~]# dbaascli patch db apply --patchid 30899722 --dbnames exacs19c INFO : EXACS patching This might take some time, please take a look at file /var/opt/oracle/log/exadbcpatch/exadbcpatch.log for progress Patch installation successful Logicalis Von On-Premises in Exadata Cloud Service 49
ExaCS - Additional Steps Logicalis Von On-Premises in Exadata Cloud Service 50
Connecting to a Storage Server with ExaCLI [opc@EXACS6-8bi441 .ssh]$ cat /etc/oracle/cell/network-config/cellip.ora cell="192.168.xxx.14;192.168.xxx.15" cell="192.168.xxx.16;192.168.xxx.17" cell="192.168.xxx.18;192.168.xxx.19„ [grid@EXACS6-8bi441 ~]$ crsctl get cluster name CRS-6724: Current cluster name is 'EXACS6CLU-069' [opc@EXACS6-8bi441 .ssh]$ exacli -l cloud_user_EXACS6CLU-069 -c 192.168.xxx.18 --cookie-jar No cookies found for cloud_user@192.168.xxx.18. Password: *********** EXA-30016: This connection is not secure. You have asked ExaCLI to connect to cell 192.168.xxx.18 securely. The identity of 192.168.xxx.18 cannot be verified. Got certificate from server: C=US,ST=California,L=Redwood City,O=Oracle Corporation,OU=Oracle Exadata,CN=localhost Do you want to accept and store this certificate? (Press y/n) Logicalis Von On-Premises in Exadata Cloud Service 51
Monitoring and Managing with exacli
LIST
LIST ALERTHISTORY
LIST CELL
LIST METRICCURRENT attributes name, metricObjectName ORDER BY metricObjectName asc, name desc LIMIT 5
LIST METRICHISTORY WHERE name like 'CT_.*‘
CREATE, ALTER, DROP; LIST
DIAGPACK
List diagnostic packages
Create diagnostic packages to gather logs and trace files into a single compressed file
IORMPLAN
Alter IORM plans, and to apply plans to storage servers.
Logicalis Von On-Premises in Exadata Cloud Service 52Create SR from OCI Console Logicalis Von On-Premises in Exadata Cloud Service 53
Verifying Database and system information
[root@EXACS6-8bi441 opc]# dbaascli dbhome info
DBAAS CLI version 19.4.4.0.0DBGI
[root@EXACS6-8bi441 opc]# dbaascli database status --dbname
Executing command dbhome info
exacs319c
Enter a homename or just press enter if you want details of all homes
DBAAS CLI version 19.4.4.0.0DBGI
1.HOME_NAME=OraDB19Home1
Executing command database status
HOME_LOC=/u02/app/oracle/product/19.0.0.0/dbhome_3
Database Status:
VERSION=19.7.0.0
Instance exacs19c1 is running on node EXACS6-8bi441. Instance
PATCH_LEVEL=19.7.0.0
status: Open.
DBs installed=
Instance exacs19c2 is running on node EXACS6-8bi442. Instance
OH Backup=NOT Configured
status: Open.
2.HOME_NAME=OraHome1
Database name: exacs19c
HOME_LOC=/u02/app/oracle/product/12.2.0/dbhome_2
Oracle Database 19c EE Extreme Perf Release 19.0.0.0.0 -
VERSION=12.2.0.1
Production
PATCH_LEVEL=12.2.0.1.200414
DBs installed=
OH Backup=NOT Configured
3.HOME_NAME=OraHome100_19600_dbru200114_0
HOME_LOC=/u02/app/oracle/product/19.0.0.0/dbhome_2
VERSION=19.6.0.0
PATCH_LEVEL=19.6.0.0
DBs installed=exacs19c
Agent DB IDs=a6c83fd4-04c0-4b23-9ce1-4cdf61cf3f97
OH Backup=NOT Configured
Logicalis Von On-Premises in Exadata Cloud Service 54Verifying ASM information
[opc@EXACS6-8bi441 ~]$ sudo su - grid
[grid@EXACS6-8bi441 ~]$ sqlplus / as sysdba [grid@EXACS6-8bi441 ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 177G 0 177G 0% /dev
SQL> select failgroup, count(*) tmpfs 354G 1.1G 353G 1% /dev/shm
from v$asm_disk group by failgroup; tmpfs 177G 3.1M 177G 1% /run
tmpfs 177G 0 177G 0% /sys/fs/cgroup
FAILGROUP COUNT(*) /dev/mapper/VGExaDb-LVDbSys1 24G 9.1G 14G 41% /
------------------------------ ---------- /dev/xvda1 488M 52M 411M 12% /boot
EXACS6_8BI441 1 /dev/xvdi 1.1T 43G 985G 5% /u02
EXACS6_8BI442 1 /dev/mapper/VGExaDb-LVDbOra1 148G 5.4G 135G 4% /u01
FRA102307EXDCL07 24 /dev/xvdb 50G 13G 34G 28% /u01/app/19.0.0.0/grid
FRA102307EXDCL08 24 tmpfs 36G 0 36G 0% /run/user/0
FRA102307EXDCL09 24 /dev/asm/acfsvol01-476 560G 112G 449G 20% /acfs01
/dev/asm/acfsgold_01-476 5.9T 13G 5.9T 1% /acfs/acfs_gold
tmpfs 36G 0 36G 0% /run/user/2000
lcfss.mgmtsn.dat.oraclevcn.com:/FSS-ORACLE 8.0E 4.2T 8.0E 1% /u04
tmpfs 36G 0 36G 0% /run/user/1001
ASMCMD> lsdg
State Type Rebal Sector Logical_Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name
MOUNTED HIGH N 512 512 4096 4194304 188301312 152114280 10461184 47217698 0 Y DATAC1/
MOUNTED HIGH N 512 512 4096 4194304 47075328 46653348 2615296 14679350 0 N RECOC1/
Logicalis Von On-Premises in Exadata Cloud Service 55Vielen Dank! Kontakt Jessica Steger +49 152 22 51 64 03 jessica.steger@logicalis.de Stefan Seck +49 151 52 64 35 76 stefan.seck@logicalis.de www.logicalis.de
Sie können auch lesen
