Well, not really. If you read my co-worker Gurmeet's Blog, you’ll see the Exadata SL6 is one incredible machine. However, I want to talk about a very important aspect of the Exadata SL6 that I don’t think is getting enough play: its security features.
We’ve been fighting the security battle for years now and it has become a booming business estimated at $445 billion in 2016. You could even say that (more...)
We live in exciting times, Oracle Database 12.2 for Exadata was released earlier today.
The 12.2 database was already available on the Exadata Express Cloud Service and Database as a service for a few months now.
Today, it has been released for Exadata on-premises, five days earlier than the initial Oracle announcement of 15th Feb.
The documentation suggests that to run 12.2 database you need to run at least 12.1.2. (more...)
I was playing around with the Exadata X2-2 in the Enkitec lab this weekend, and hit an interesting issue when patching the storage servers. We were taking the system up to version 188.8.131.52.3 for testing purposes. I fired off the patchmgr script, and one of the storage servers failed when beginning the first phase of the patching cycle:
[root@enkdb03 patch_184.108.40.206.3.161208]# ./patchmgr -cells cell_group -patch -ignore_alerts
On a Data Guard Physical Standby, I noticed the following in the alert log:
Fri Jan 13 08:12:39 2017
Errors in file /u01/app/oracle/diag/rdbms/v1s/V1S1/trace/V1S1_arc1_399861.trc:
ORA-00322: log 41 of thread 2 is not current copy
ORA-00312: online log 41 thread 2: '+RECOC1/V1S/ONLINELOG/group_41.3099.912775569'
ORA-00322: log 41 of thread 2 is not current copy
ORA-00312: online log 41 thread 2: '+DATAC1/V1S/ONLINELOG/group_41.807.912775567'
If you read metalink note:
Physical standby – alert*log shows ORA-322, ORA-312 intermittently (more...)
This might not be relevant anymore, shame on me for keeping it draft for few months. However, there are still people running an older versions of Exadata storage software and it might still help someone out there.
With the release of Exadata storage software 220.127.116.11.0, Oracle announced that some 32bit (i686) packages will be removed from the OS as part of the upgrade.
This happened to me in the summer last (more...)
Interesting news about the coming Oracle 12 Release.
Release Schedule of Current Database Releases (Doc ID 742060.1)
Take a look :-)
It’s been a busy month – five Exadata deployments in the past three weeks and new personal best – 2x Exadata X6-2 Eighth Racks with CoD and storage upgrade deployed in only 6hrs!
An issue I encountered with the first deployment was that onecommand wouldn’t change the storage cells names. The default cell names (not hostnames!) are based on where they are mounted within the rack and they are assigned by the elastic configuration (more...)
Es geht los bis zum 13.2.2017 können Vorträge für den Exaday 2017 rund um das Thema Oracle Engineered Systems eingereicht werden
Ich freue mich auf viele spannende Vorträge …
Der Exaday 2017 findet dieses Jahr am 20. Juni 2017 in Frankfurt – Mörfelden statt
The Call for Paper is opened until 13.2.2017
Please submit for the Exaday 2017 all around the topic Oracle Engineered Systems
I had the pleasure to deploy another Exadata in the first week of 2017 and got my first issue this year.
As we know starting with Exadata X5, Oracle introduced the concept of Elastic Configuration. Apart from allowing you to mix and match the number of compute nodes and storage cells they have also changed how the IP addresses are assigned on the admin (eth0) interface. Prior X5, Exadata had default IP addresses set at (more...)
When I carried out my first Exadata patching, I came across ‘Linux Screen‘ in the documentation, which Oracle recommended to use when patching:
“It’s recommended to run the dbnodeupdate.sh session using the Linux ‘screen’ or ‘vnc’ utility such that when a network problem breaks the connection to the server the patching session continues.”
Basically ‘Linux Screen‘ allows you to:
- Have a shell that can be reconnected to if you (more...)
The upcoming SLOB 2.4 release will bring improved data loading error handling. While still using SLOB 2.3, users can suffer data loading failures that may appear–on the surface–to be difficult to diagnose.
Before I continue, I should point out that the most common data loading failure with SLOB in pre-2.4 releases is the concurrent data loading phase suffering lack of sort space in TEMP. To that end, here is an example of (more...)
There is a very interesting paper about the way of direction of the Exadata Database Machine.
Thanks a lot Günther Stürner.
While writing the previous two posts about GTTs and Smart Scan, I stumbled across an interesting observation. When I started putting my thoughts to (virtual) paper, I thought it was going to be a short post. Well, it wasn’t to be, again. Anyway, you might find this interesting.
If you read the previous posts this code example I used to populate the GTT might look familiar:
insert /*+ append */ into gtt select (more...)
Recently I did a upgrade to Grid Infrastructure 18.104.22.168 on a few Exadata Clusters
Here my summary of the installation
Before you start please read the following MOS note 1681467.1. This note is very helpful and describes the whole procedure in a Exadata environment
It’s not only the Upgrade to 22.214.171.124. In the same „session“ I also install the GI PSU Jul 2016 and the Oneoff Patch (more...)
Continuing the example of the previous blog post (is it possible to Smart Scan GTTs?), I am investigating if Smart Scans against GTTs can benefit from Flash Cache, or “optimised reads”. The easiest way to see this in your session is to calculate the change in session counters based on v$mystat or v$sesstat. Other tools might also provide information about the amount of data read from Flash Cache, but there are quite often extra (more...)
A question that has come up while preparing to deliver another Exadata Optimisation Class is whether you can offload queries against Global Temporary Tables (GTT) or not. There are subtle differences between heap tables and GTTs such as how statistics are handled and where they are stored that merit a little investigation.
I have used the lab environment on the X3-2 (Exadata 126.96.36.199.0, 188.8.131.52.160419 RDBMS) to test (more...)
In my previous post, I introduced Intel Pin. If you are new to pin, please follow this link to my previous post on how to set it up and how to run it.
One of the things you can do with Pin, is profile memory access. Profiling memory access using the pin tool ‘pinatrace’ is done in the following way:
$ cd ~/pin/pin-3.0-76991-gcc-linux
$ ./pin -pid 12284 -t source/tools/SimpleExamples/obj-intel64/pinatrace.so
The pid is (more...)
This blogpost is an introduction to Intel’s Pin dynamic instrumentation framework. Pin and the pintools were brought to my attention by Mahmoud Hatem in his blogpost Tracing Memory access of an oracle process: Intel PinTools. The Pin framework provides an API that abstracts instruction-set specifics (on the CPU layer). Because this is a dynamic binary instrumentation tool, it requires no recompiling of source code. This means we can use it with programs like the Oracle (more...)
This blogpost is about the Oracle redo log structures and redo efficiency in modern Oracle databases. Actually, a lot of subtle things changed surrounding redo (starting from Oracle 10 actually) which have gone fairly unnoticed. One thing the changes have gone unnoticed for is the Oracle documentation, the description of redo in it is an accurate description for Oracle 9, not how it is working in Oracle 10 or today in Oracle 12.1.0. (more...)
If you manage an Oracle Engineered System you may wonder how well your Smart Scans are performing. Are you taking full advantage of Exadata Optimizations? If so, how do you measure them?
Uwe Hesse explains well some important statistics on Exadata. For some time now, eDB360 includes a report on Smart Scan efficiency, which is nothing but a Google Chart on top of relevant statistics.
Sample chart below is from a data warehouse DW application. It (more...)