Just a quick post today as I wanted to highlight a video that has been made available by one of my colleagues, Valentin Tabacaru. Valentin is a sales consultant based out of one of our Spanish offices. The
I’m trying to branch out a bit and craft a few videos. This one is my first attempt and I discuss the new 12c IDENTITY column performance, specifically for Oracle RAC databases.
Link to video on YouTube: https://youtu.be/aW_K_rEFkrI
Note: I don’t focus my energies on the planning side much. So these videos are not rehearsed. I will prepare a few scripts so that I don’t have to type as much, but otherwise, these videos will just be me being me.
If you attempted to get to PeteWhoDidNotTweet over the past few days, you would have noticed it was down. The reason for that is I finally found the time to do something that I’ve wanted to do for some time – perform a major update of the entire website.
I am upgrading a 2-node Oracle RAC testbed from Oracle 18.104.22.168 to Oracle 22.214.171.124. This is a simple testbed and the database is virtually empty. I’m using the DBUA to perform the upgrade. Should be simple, right?
After the database is upgraded, the DBUA is trying to move the RAC configuration to the new home. Early on, I get a “file exists error”. I check the $ORACLE_BASE/cfgtoollogs/dbua/upgrade1 directory and in the PostUpgrade.log file, I get this curious error:
[oracle@nau-rac01 upgrade4]$ cat PostUpgrade.log
Just like everything else in Enterprise Manager, an Exadata is a target and all of its components are targets. All of these pieces can be removed through the 12c console.
Select Exadata from the bottom of the main Targets drop-down to display a list of Database Machines in your environment. Highlight the row containing the subject machine and press the Big Red X to take you into the detail page.