Re: Not to use SCAN in 11gR2 RAC
Date: Sat, 17 Oct 2009 06:39:58 -0700 (PDT)
Thanks for everybody's response. I tried to find official statement on Metalink and database documentation. Didn't find any. The closest is "Oracle recommends that you configure clients to use SCANs, but it is not required that you use SCANs." If anybody can find reference, please post.
I tried to use "srvctl stop listener -l LISTENER_SCAN1" to stop the SCAN listener and got an error that explicitly says SCAN listener can't be stopped. "kill <SCAN tnslsnr IP>" worked. After that, I can continue to use the connection string that resolves to the VIP's. I can't tell if there's any harm done. But I'll keep SCAN when I install for production, for reasons of future updates or patching, and because I didn't find an official statement I can remove it. I opened an SR on this.
On Oct 16, 2009, at 11:59 AM, Yong Huang <yong321_at_yahoo.com> wrote:
> We installed 220.127.116.11 RAC on a RHEL 5.3 two-node cluster
> successfully. It looks like SCAN (Single Client Access Name) must
> be assigned during installation.