![]() ![]() Additionally to the high availability benefit, Oracle apparently also performs load balancing across the configured interconnects. Oracle states that if one of the private interconnects fails, it will transparently use another one. If you decide to add a NIC to the cluster for use with the private interconnect later, use oifcfg as root to add the new interface (or watch this space for a later blog post on this). The documentation states that you don’t need to bond your NICs for the private interconnect, simply leave the ethx (or whatever name you NICs have on your OS) as they are, and indicate the ones you like to use for the private interconnect as private during the installation. But anyway, I’ll run a few tests in the lab when I have time with this new feature enabled, deliberately taking down NICs to see if the new feature works as labelled on the tin. Linux network bonding is actually quite simple to set up as well. Linux has always done this for you, even in the times of the 2.4 kernel. So – good news for anyone who is relying on third party software like for example HP ServiceGuard for network bonding. This functionality is available starting with Oracle Database 11g Release 2 (11.2.0.2).” “With Redundant Interconnect Usage, you can identify multiple interfaces to use for the cluster private network, without the need of using bonding or other technologies. The Grid Infrastructure installation guide for Linux states: The cluster_interconnect.haip is yet another step towards the self contained system. Have a look at these: $ crsctl stat res -t -init I couldn’t reproduce the test case, and my lab and real-life clusters run with 11.2.0.2 happily.Īfter the successful upgrade you’d be surprised to find new resources in Grid Infrastructure. As I said, you don’t have a choice for Grid Infrastructure which is always out-of-place.Īnd then there is the multicast issue Julian Dyke ( ) has written about. I’d say that the out-of-place upgrade for RDBMS binaries is wholeheartedly recommended as it makes backing out a change so much easier. The RDBMS binaries can be patched either in-place or out-of-place. I would not use anything less than 50-75G on my Grid Infrastructure mount point.This takes the new cluster health monitor facility (see below) into account, as well as the fact that Oracle performs log rotation for most logs in $GRID_HOME/log. Grid Infrastructure will be an out-of-place upgrade which means you have to manage your local disk space very carefully from now on. The casual observer may now ask: why do I have to apply a PSU when the bug fixes should be rolled up into the patchset anyway? I honestly don’t have an answer, other than that if you are not on Linux you should be fine. OUI hasn’t performed the test when it checked for prerequisistes which caught me off-guard. Before you can run rootupgrade.sh, the script tests if you applied the Grid Infrastructure PSU for 11.2.0.1.2. ![]() Interestingly upgrading from 11.2.0.1 to 11.2.0.2 is more painful than from Oracle 10g, at least on the Linux platform. Currently, MOS note 756671.1 doesn’t list any patch as recommended on top of 11.2.0.2. Optionally, apply PSUs or other patches when they become available. You no longer have to apply any of the interim releases-the patch contains everything you need, already on the correct version. In fact, for a fresh install it was usually easier to install and patch everything on only one node and then extend the patched software homes to the other nodes of the cluster.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |