It's nothing in this post. I just changed Oracle database name and did it something for Grid Infrastructure for standalone server also.
SQL> select name from v$database;
SQL> shutdown immediate
ORACLE instance shut down.
I had an error which i would call weird cause i couldn’t understand it . I was asked to start 2-Node 10.2.0.5 RAC db and its services.
Please follow the following steps in order to upgrade 184.108.40.206 Grid Infrastructure to 220.127.116.11
You need to apply GIPS2 ( Patch 9655006 – 18.104.22.168.2 – Grid Infrastructure PSU 2) before you could upgrade it to 22.214.171.124. You also must have latest 11.2 OPatch – 126.96.36.199.6.Latest OPatch for 11.2 – Patch 6880880. . . . → Read More: 11GR2 – Grid Infrastructure Upgrade – 188.8.131.52 to 184.108.40.206
Here’s a quote that says it all:
Dr Joseph Lykken of Fermilab – in response to some (negative) results from the Large Hadron Collider that suggest the simplest form of SuperSymmetry is wrong:
“It [supersymmetry] is a beautiful idea. It explains dark matter, it explains the Higgs boson, it explains some aspects of cosmology; but that doesn’t mean it’s right.”
Mind you, Feynmann got there years ago:
If you support Oracle RDBMS 220.127.116.11 and want to zero downtime applying
patches to databases then it is time to have a look at new possibility
of Online Patching delivered with 18.104.22.168 version and described here
RDBMS Online Patching Aka Hot Patching [ID 761111.1]
It seems really simple. We have an Oracle database (on all nodes of a full rack Exadata, to be exact), which a lot of end-users connect to through apps designed in a rather adhoc and haphazard manner - on Excel spreadsheets, Access forms, TOAD reports and other assorted tools. We want to control the access from these machines and streamline them.
“Oftentimes, a database administrator (DBA) simply looks at the symptoms and immediately starts changing the system to fix those symptoms”
Op. Cit. Oracle Database Performance Tuning Guide 11g Release 2 (11.2)
Ok, let’s do this
Here’s a deadlock graph the appeared on Oracle-L and OTN a couple of days ago.
A few days ago, we faced an interesting problem on one of our customer’s slave mysqld servers. An Alter for adding a new column was run on master server took 542 seconds where as it took few hours on the slave server to complete due to a SELECT blocking the Alter was not allowed to complete.
Here is the the select on the master server and it’s execution time from the binary logs.