i know this note very well, but I am searching something from DBA experience.
Generally because Exadata is such a standardised platform the risk to be close to the release qfsdp is not high so in most case an n or n-1 strategy for the qfsdp is the best way to go..Are you facing specific issues ?
If you have an option it is always best not to virtualize your database machine as you avoid any potential overheads of the virtualization though since the virtual Io on Exadata uses infiniband virtual functions it has much less effect than scsi but you will face some overheads due to vnic virtualization.
the first is to take alook into the Note 888828.1.
Then it depends a little bit how often you plan to do the Patching. May be most of the customers did a Patching two times a year Spring and Winter for example.
The DBA Part of the Patching is more or less the same as for Patching an Oracle Database so opatch.
For virtualization there is no special document. Exadata 18.104.22.168.0 release and patch (28000787) (Doc ID 2397397.1)
here an example the Doc-ID has itself information if you use virtualization.
But what is your real problem?
every week we face some new issue, so it is hard to say what is the real problem. However on ACS support calls we got response "yeah I saw that exact problem on other customer environment." Then we got a nonworking patch, multiple times. Now I am trying to find people with similar environment/issues/experience.
1 person found this helpful
okay I know these problems and it is of course not easy to communicate with the Oracle Support.
Hardware issue should be solved by the so called ASR System which you hopefully have configured.
Otherwise you as customer need to create an Hardware Service Request and do the whole organization for this.
If it is the first Exadata in your environment you will have in the beginning a curve to learn all these daily tasks.
May be you should check your IT Organization and separate the daily tasks
- Network and Operating System by some System Admins
- Storage, Grid, RDBMS by Oracle DBA's
Check Publications: "Oracle Exadata Life Cycle & Services" it is from 2014 but really state of the art.
Take a look to my Blog there is a paper about the Lifecycle and how you can do it.
thanks for publication & link. Currently we are separated to more teams, that is not the case.
but then I don't understand why you are so struggling?
Where is your real problem?
As mentioned the first step is to check the "Exadata bible" 888828.1 Note and if you don't find something open an SR.
If the answer is not okay for you then escalate the SR and ask for more details.
May be open the SR when the Support came from the US timezone.
Sometimes it helps but take into account that the different local time could be a problem.