Browsed byCategory: Exadata

Ok I cannot name the customer (Approval pending) but a very exciting project just came to an end. You might be aware that I currently have a focus on exadata and high availability and sometimes nice projects come across your way. The title is an invented one, as it was a combination of looooots of exadata stuff and dataguard. And admit, it just sounds cool, isn’t it? 😉 The beginning The initial question was: “Can we expand our X3-2 non-prod…

Like this:

Today I had the honour to join my colleague Freek D’Hooge (find him here: @dhoogfr )in the datacenter. Task for today, reimage an 1/8th X7 Exadata using PXE. Andy (Colvin) warned me already that, when trying to reimage them, they are now using UEFI – boot. Knowing this in advance, this would be an #exatastic day. As usual, Andy was right. Trying to boot one of the cells on the pxe “the old method” resulted in: “Secure boot violation: Invalid signature…

Some days start as an exatastic day and end up grasping your hair. This post is about such a day. A brand new shiny X7 Quarter Rack exadata was being installed for a customer. This setup was a fairly straightforward one. Quarter rack, full ovm and 2 virtual clusters. Not too fancy. LACP is being used for the public network on the fibers and vlan tagging is done on the switch. Given that, my customer created a OEDA configuration using…

Share this:

Like this:

Gotcha! This post is not about memory settings at all, but a quick heads up. If you are dealing with several generations of exadata’s and you like ironhugging them as much as I do, sometimes things can get confusing. The X7 exadata has changed a bit so when you use them, it’s nice to do things right. Only way to do it right is check it, double check it and verify. One of the things which is always in my…

Share this:

Like this:

Some customers ask for help to fill in the Exadata Deployment assistant (OEDA for short). This is the case in my current project. They bought a shiny brand new X7 and requested assistance for the OEDA as they faced an issue with the admin network. It reproduces very easily so I will show this using a demo example. A small introduction is maybe needed for this. Most of us know the 10.x.x.x/8 or the 172.16.x.x and 192.168.1.x/24 ranges that are…

Share this:

Like this:

Recently I was granted access to the finest and latest exadata. Unfortunately it’s not mine, but I was asked if I managed to log in remotely as a test. Of course I wanted to test that. As it turned out, it was the very latest build of 18c which is available for exadata. You can find the release schedules for Oracle versions here: the single-source-of-truth MOS Note: 742060.1 – Release Schedule of Current Database Releases. I realised this was a cool opportunity…

Like this:

Today I was at one of my Exadata customers for a (PL/)SQL performance tuning assignment. In the meantime there is a parallel project running for a new Exadata. So as you might know, the configuration for an Exadata starts with running the OEDA-tool. The latest version can always be found on My Oracle Support note 888828.1. At the moment of writing this blog, the latest one was January 2018 with patch number 27370068. One of the things which caught our attention,…

Before Christmas 2017 I had the honour to expand the compute node storage for a virtualised exadata. Better said, OVM on exadata. This can be done for several reasons. The most logic one, also the reason why this customer bought the disk expansion, is that you want to create more virtual machines and you have ran out of space on /EXAVMIMAGES. The preparation is actually pretty simple. It is documented completely in the Exadata Database Machine Maintenance Guide. And look,…

Like this:

UPDATE: This blogpost is not longer maintained for up-to-date info according the engineered systems. It is best to check MOS for the current EOL dates. Remember your brand new X2-2 exadata or even a V2, they were (or should have been) blazingly fast when purchased. But all things come to an end, so also the end of life (EOL) for systems strikes your systems sooner or later. From time to time I get the question “how long is my exadata…

Share this:

Like this:

The title summaries this complete blogpost, the OEDA (oracle exadata deployment assistant) does a lot more than you would expect. Therefor it is pretty important that you should use a recent version every time when fiddling around with virtual machines on the exadata. A simple example I just discovered and did not know about. In my previous blogpost about the bond_eth issue (find it here: http://vanpupi.stepi.net/index.php/2017/06/09/exadata-ovm-creation-second-argument-is-not-defined-bondeth_mode/ ) you could read that there was a problem while I invoked domU maker manually…