The operating system statistics are collected in the Exadata environment using the tool ExaWatcher automatically. You can generate statistics reports over a certain time as user root:
The following example generates the report for the period from 09/24/2018 till 09/26/2018:
./GetExaWatcherResults.sh –from 09/24/2018_00:00:00 –to 09/26/2018_23:59:59
Results will be generated as the BZIP2 Archive in the directory /opt/oracle.ExaWatcher/archive/ExtractedResults.
The results can be analyzed very simple via Browser. You can unpack the archive, go to the directory and see separate directories for the different statistics:
Weiterlesen „Exadata: OS performance analyzing via ExaWatcher“
About three months ago I found a script named host_access_control.
The script provides the API to managing several host access and security settings. The script is available on Compute Nodes and Storage Cells since the Exadata Software Version 18.104.22.168.0. The utility is located in /opt/oracle.cellos/host_access_control. The script is not documented in the Exadata Documentation, but in the Super Cluster documentation.
The script called with the Option „-h“ displays the help:
Weiterlesen „Change the security settings on Exadata with the script host_access_control“
Some time I have the problem with the vies of the Top Activity Page in the Cloud Control:
The Graf shrink to left and you can see only the part of the picture:
Weiterlesen „Cloud Control: the Graph in the Performance Top Activity view shrinks to left“
Do you know the problem: an Exadata does not have enough space in filesystem /u01? The Exadata has the locale storage and you can increase /u01.
1. Check filesystem and associated volume:
[root@myexadb01]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VGExaDb-LVDbSys1 30G 23G 5.7G 80% /
tmpfs 757G 4.0K 757G 1% /dev/shm
/dev/sda1 488M 48M 405M 11% /boot
/dev/mapper/VGExaDb-LVDbOra1 158G 107G 43G 72% /u01
Check the free space in the volume group:
PV VG Fmt Attr PSize PFree
/dev/sda2 VGExaDb lvm2 a—u 1.63t 1.38t
Weiterlesen „Extend Filesystem /u01 on an Exadata ComputeNode“
Steps to configure Oracle Data Guard version 12.2 for a pluggable database
This document describes the configuration of the Oracle Data Guard Version 12.2. We will configure a standby for a pluggable database.
My test environment consists of two Linux (OEL 7.3) servers: oradg1 and oradg2. I already created a pluggable database on the server oradg1. The database consists of the following components:
SQL> show con_name
SQL> set lines 200
SQL> col name forma a20
SQL> select con_id, name,open_mode, restricted from v$pdbs;
CON_ID NAME OPEN_MODE RES
---------- -------------------- ---------- ---
2 PDB$SEED READ ONLY NO
3 ORCLPDB1 READ WRITE NO
4 ORCLPDB2 READ WRITE NO
SQL> select PDB_ID,PDB_NAME,CON_ID,STATUS,LOGGING,FORCE_LOGGING from dba_pdbs;
PDB_ID PDB_NAME CON_ID STATUS LOGGING FOR
---------- -------------------- ---------- ---------- --------- ---
2 PDB$SEED 2 NORMAL LOGGING NO
3 ORCLPDB1 3 NORMAL LOGGING NO
4 ORCLPDB2 4 NORMAL LOGGING NO
Following tasks will be executed:
- Configuration the standby database on the server oradg2.
- Creation / drop a pdb on the primary database and verification what happens on the standby site.
- Executing the swithover tests.
In my previously post Steps to configure Oracle Data Guard 12.2 for non-multitenant database I created the physical standby for a non-multitenant database using a database creation assistant – dbca (new 12.2 feature). Unfortunately this feature is not available for a pluggable database and we will create a physical standby via RMAN utility.
Weiterlesen „Steps to configure Oracle Data Guard version 12.2 for a pluggable database“
This document describes the upgrade of the GI from 12.1 to 12.2 with installation of the RU August 2017.
The Exadata consists of:
- Two db nodes: exadb1/exadb2
- Three cell servers
The software release of Exadata components:
Infiniband Software version: 2.2.6-2 (Juli 2017)
Storage cells version: 22.214.171.124.2.170714
DB node versioin: 126.96.36.199.2.170714
GI Version: 188.8.131.52.170418
RDBMS Version: 184.108.40.206.170418
The order of the action:
- Out of the place installation of the Grid Infrastructure 12.2 on all database servers
- Installation RU Patch August 2017 on all database servers
- Upgrade Gird Infrastructure to 12.2
Weiterlesen „Upgrade Grid Infrastructure 12.1 to 12.2 + Install the 2017 August Release Update (RU) on Exadata“
This document describes the configuration of the Oracle Data Guard Version 12.2. We will configure a standby for a non-multitenant database.
Our test environment consists of two Linux (OEL 7.3) servers: oradg1 and oradg2. I already created the non-multitenant database on the server oradg1. We will configure the standby database on the server oradg2. We will use a new feature of 12.2 by creating a physical standby via dbca – oracle database creation assistant.
Primary server name/os: oradg1/Oracle Linux Server 7.3 (64 bit)
Standby server name/os: oradg2/Oracle Linux Server 7.3 (64 bit)
RDBMS Version (primary and standby): 220.127.116.11.0
ORACLE_HOME (primary and standby): /u01/app/oracle/product/12.2.0/dbhome_1
Primary ORACLE_SID/DB_UNIQUE_NAME: ORCL1/ORCL1PRM
Standby ORACLE_SID/DB_UNIQUE_NAME: ORCL1/ORCL1STB
Listener name/port (primary and standby): LISTENER/1521
Path to DB files (primary and standby): /u01/app/oracle/oradata/orcl1
Recovery area (primary and standby): /u01/app/oracle/fast_recovery_area/orcl1
Preparing the primary database
Weiterlesen „Steps to configure Oracle Data Guard 12.2 for non-multitenant database“