Day 1? Really, is that all? There are so many things going on it feels like day 3.
And I'm not even participating in everything since I'm also coming back to do some family time each day.
I gave this a go this morning after not being able to find Kent on the first day. It was interesting and there were some good exercises that everyone should consider doing in the morning, though with respect to Kent, for me the woo outweighed a lot of good that can come out of meditation and moving your body.
I’ve done several Exadata deployments in the past two months and had to upgrade the Exadata storage software on half of them. Reason for that was because units shipped before May had their Exadata storage software version of 188.8.131.52.0.
The upgrade process of the database nodes ran fine but when I ran dbnodeupdate.sh -c for completing post upgrade steps I got an error that the system wasn’t on the expected Exadata release or kernel:
For example :
[oracle@localhost ~]$ rman target /
Recovery Manager: Release 184.108.40.206.0 - Production on Tue Jun 23 16:57:19 2015
The following technical detail was put together by a colleague John Evans and have taken it , with his permission, and wrapped some more detail around it as it seemed to be of real value to anybody who might have upgraded an agent to 220.127.116.11
Following an upgrade of the EM agent from 18.104.22.168 (or 22.214.171.124) to 126.96.36.199 after about 90 days of usage we saw a number of agents failing with out of memory errors.
There’s been an interesting recent discussion on the OTN Database forum regarding “Index blank blocks after large update that was rolled back“. Setting aside the odd scenario of updating a column that previously had 20 million distinct values to the same value on a 2 billion row table, the key questions raised are why the blank index leaf blocks […]
Data Pump is one of the most basic things, but it has so many parameters that can transform in a complex thing.
Anyway, this utility is probably the most used tool for any DBA. So, try to focus during you training in the things that are not very common.
Be good exporting at tablespace / schema / database levels. Also, be ready to include or exclude something from backups (there are good DBA views to help you in those parameters as DATABASE_EXPORT_OBJECTS).
So, I would recommend you to study:
Creating an external is not a easy task. Why? Because, at least for me, this is one of the most complexes Oracle syntaxes.
So, the best approach for me in this topic is to go quickly in the documentation place of external tables and use a template.
Practice a bit to be prepared for the exam:
Path do Documentation:
When creating the GoldenGate Integrated Extract I get the OGG-02060 error. How do I resolve it?
The post OGG-02060 The Oracle Mining Database is not Configured Properly to Support Integrated Capture. appeared first on VitalSoftTech.
When certain SQL features get used in pre-12c versions that force non-parallel evaluation, like using ROWNUM or certain Analytic Functions like LAG/LEAD, then - depending on the overall plan shape - Oracle can start to decompose the parallel execution plan into several so called DFO trees (If you want learn more about DFO trees and DFOs I recommend watching my online tutorial on my Youtube channel).Now having multiple DFO trees in a single parallel execution plan comes with seve