The following is from a former colleague, worth mentioning. The ASM targets in OEM-GC give the next active warnings: Metric: Disk Group Percent Imbalance Message: Disk Group SYSTEMDG requires rebalance because the space usage imbalance between disks is high. Metric: Disk Size Imbalance (%) Message: Disk Group SYSTEMDG has failure groups with disks of different
A short post after a tweet of Johannes Ahrends (@carajandb on twitter). He brought to our attention that he was worried: SE2 doesn’t include RAC anymore in 19c. Is it a documentation bug? Unfortunately not… his worries appeared to be ligitimate. He made a blogpost about it – in the German language. Tried to summarize
This post has already been published in the past on the AMIS-blog. To build an Oracle 12C RAC database – on Virtual Boxes – there’s at least shared storage needed for ASM, and a DNS-server for the SCAN-addresses. Several methods can be used for this, but for the storage in my private project I
Oracle will not provide ASMLib packages for kernels distributed by Red Hat as part of RHEL 6.
The second and final post about an issue with a RAC-configuration with two SAN's. Problem was a i/o-freeze of minutes when crashing one of the two SAN's. The first post I ended with a 'cliffhanger' because we had a solution, but not tested it yet.
Remember the old days. You had just a few processes to watch. Something has changed along the way. A lot of processes should be running on your database system (with infrastructure), but how are they connected to eachother and what is the startup sequence ? Or.. what processes I can kill without any other proces starting it up... :-)
Since 11.2.0.2 there's a new parameter, "_datafile_write_errors_crash_instance" to prevent the intance to crash when a write error on a datafile occurs. But.. should I use this or not.
With this setup we are facing the issue that if we loose a complete SAN, the IO’s to the ASM diskgroups will be blocked for approx 3 till 4 minutes. Oracle does not like this. After 70 seconds after a freeze, rdbms is starting to reboot (expected behaviour).
As the documentation about restoring an OCR did not work as it should be, hereby a method to do this.
This is the second post of my little project of building my own RAC on my Windows7-desktop (64-bits, 8GB RAM), using 3 VM’s (VM-workstation , 7.1.3 build-324285) : * 2 VM’s for two RAC-nodes, based on OEL 5.5, 11.2.0.2 for infra, and database. * 1 VM as my own SAN, based on Openfiler 2.3 (free), for ASM.
© Copyright 2012 - 2023 | Jobacle by Job | All Rights Reserved | Powered by WordPress
