Long story short, faced this issue while running OneCommand for one Exadata system. The root.sh step (Initialize Cluster Software) was failing with the following error on the screen
Checking file root_dm01dbadm02.in.oracle.com_2017-04-27_18-13-27.log on node dm01dbadm02.somedomain.com
Error: Error running root scripts, please investigate…
Errors occurred. Send /u01/onecommand/linux-x64/WorkDir/Diag-170427_181710.zip to Oracle to receive assistance.
Doesn’t make much sense. So let us check the log file of this step
I am quite excited to have been accepted to speak at the upcoming DOAG Exaday taking place June 20 in Frankfurt. It is the third time I have been lucky enough to present at the event, having spoken both in Frankfurt in Hamburg in previous years.
As you can probably imagine by looking at this weblog, I am a great supporter of the Oracle Engineered Systems community. My interest is not limited to Germany: I still remember (more...)
Hit this silly issue while doing an Exadata deployment for a customer. Step 1 was giving the following error:
ERROR: 192.168.99.102 configured on dm01celadm01.example.com as dm01dbadm02 does not match expected value dm01dbadm02.example.com
I wasn’t able to make sense of it for quite some time until a colleague pointed out that the reverse lookup entries should be done for FQDN only. As it is clear in the above message (more...)
Thanks to the prep-work done by Andy Colvin, who continuously and boldly goes where no man has gone before, one of our Exadata systems in the lab is now fully upgraded to 22.214.171.124. It comes fully equipped with the matching cellos to support all the cool new features. Exciting times!
The reason for this post is simple: I have started working on our talk for @Enkitec’s E4 conference in June but (more...)
I decided this week to be a little brave and upgrade one of the Enkitec Exadata racks to 126.96.36.199. I installed the 188.8.131.52.0 Exadata image a few weeks ago, and have been waiting for a chance to upgrade clusterware to 12.2. Thankfully, Oracle provides a very good note for this, but I did hit one large snag that should be documented.
The process for upgrading GI to 12.2 (more...)
Oracle Linux is engineered for Oracle Cloud. This operating system:
- Is designed for business-critical workloads in the cloud
- Uses latest technologies such as Docker
- Is a major contributor to mainline Linux cloud features
- Powers Oracle Engineered Systems and Oracle Cloud
To get the most out of Oracle Linux, take the Oracle Linux advanced administration training. If using Oracle Linux 7, take the Oracle Linux 7: Advanced Administration course in one of the following formats:
Recently I was applying the data dictionary part from an (exadata bundle) patch and ran into the following errors:
ORA-24324: service handle not initialized
ORA-24323: value not allowed
ORA-27140: attach to post/wait facility failed
ORA-27300: OS system dependent operation:invalid_egid failed with status: 1
ORA-27301: OS failure message: Operation not permitted
ORA-27302: failure occurred at: skgpwinit6
ORA-27303: additional information: startup egid = 1001 (oinstall), current egid = 1002 (dba)
This was very weird, I had just (more...)
Recently, I was trying to setup TDE. Doing that I found out the Oracle provided documentation isn’t overly clear, and there is a way to do it in pre-Oracle 12, which is done using ‘alter system’ commands, and a new-ish way to do it in Oracle 12, using ‘administer key management’ commands. I am using version 184.108.40.206.170117, so decided to use the ‘administer key management’ commands. This blogpost is about an (more...)
When sifting through a sql_trace file from Oracle version 12.2, I noticed a new wait event: ‘PGA memory operation’:
WAIT #0x7ff225353470: nam='PGA memory operation' ela= 16 p1=131072 p2=0 p3=0 obj#=484 tim=15648003957
The current documentation has no description for it. Let’s see what V$EVENT_NAME says:
SQL> select event#, name, parameter1, parameter2, parameter3, wait_class
2 from v$event_name where name = 'PGA memory operation';
EVENT# NAME PARAMETER1 PARAMETER2 PARAMETER3 WAIT_CLASS
------ ------------------------------------- ---------- ---------- ---------- ---------------
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 220.127.116.11.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_18.104.22.168.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 22.214.171.124.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...)