Last year, Tim Hall, the one and only Mr @oraclebase , had the great idea to say thank you to the community with OTN appreciation day. This was a fantastic moment on which lots of people posted about their favorite Oracle product. Last year I wrote a short heads up for Dataguard. You can read it here. For this edition of the appreciation event, I chose a 12c feature: Application Continuity. This feature is introduced in 12c R1 and does basically what…
A few months ago (about october) ago we were contacted with the simple question: Can you run an oracle database in the cloud, the Azure cloud. Well … it depends. The little detail was, that the database is about 34TB and there are a few other multi TB databases AND there are a lot of copies of them. And … the final decision for go live is … end of 2016. Well, we accepted the challenge. The deadline was strict, so that’s also…
A while ago a customer gave me a heads up about the “bug” concerning the default passwords for root and celladmin. I was thinking a bit further and I wondered if the “documentation bug” I found while adding a new OVM in the virtualised exadata is solved. The official documentation can be found here . Then “Managing Oracle VM Domains on Oracle Exadata Database Machine” and then “Creating Oracle RAC VM Clusters” brings you to the point I want to warn you…
Thanks Tim Hall for the idea about OTN Appreciation day. The feature I like the most in oracle is a rather “old” one, but it can be extremely useful: Dataguard. Why dataguard? I find it extremely easy to set it up, maintain it and it can save you a lot of “troubles”. Especially on big(ger) databases it takes down the time to recover in case of a failure down to seconds instead of hours. The concept is simple: (image borrowed from the…
I could create a very short blogpost summarising this first POUG conference: AMAZING! But as this marvellous event deserves what it deservers, I’m going to write a little post about it, as a way of saying thank you! Poug: it’s a word with double meaning. Intentionally it would stand for Poland Oracle User Group but thanks to Kamil (@ora600pl ) and his team it was turned into Pint with the Oracle User Group. I met Kamil only at UKOUG Ireland this…
It all started a couple of months ago. I submitted a presentation and my friend Philippe Fierens submitted a panel session together with Adam Bolinski (Ora600.pl) , but unfortunately, I’m joining #teamRejected Lots of cool and nice people had to join as well, so it’s not too bad. Then great news came and my boss asked if I was interested of visiting Oracle Openworld. I didn’t have to think twice, so my answer was yes very quickly. The trip starts…
It’s patching time again. So on one of our test systems we gave the july 2016 bundle a go. It’s a simple system, just a plain database 126.96.36.199 with the april bundle applied. No grid infrastructure, no asm, just a plain simple database system. The sequence is the same as always. Unzipping, conflict check, nothing new. In our case, no conflicts were found so the next step is opatch apply. All went good until a certain point the make command failed…
It all starts with creation of a database on a Database appliance which failed with the error
Validation of server pool succeeded.
Registering database with Oracle Restart
PRCR-1006 : Failed to add resource ora.demodb.db for demodb
PRCR-1071 : Failed to register or update resource ora.demodb.db
CRS-2566: User 'oracle' does not have sufficient permissions to operate on resource 'ora.redo.datastore.acfs', which is part of the dependency specification.
DBCA_PROGRESS : DBCA Operation failed.
One of the things … is it due to running on the ODA or is it a general cluster issue? It was easy to verify as this customer had another ODA on which everything just works smoothly. So we started to compare the environments. One tiny little thing appeared to be different: the ACL. On a working ODA:
[grid@ODA_A-1 ~]$ crsctl status resource ora.redo.datastore.acfs -p |grep ACL
Well that’s it guys. I moved from tumblr ( http://vanpupi.tumblr.com ) to wordpress to have some more flexibility, mostly for the code-tags actually. We’ll see where it will bring us.