I can only echo what others have said. Changing any piece of the network in
RAC is a non-trivial problem requiring planning and rehearsal. I have
learned this from painful experience. Definitely open an SR on the
subject. In my experience, it would be easier to clone this to an entirely
new cluster with the new domain name rather than try to change the domain
names in the current cluster.
On Mon, Mar 29, 2021 at 11:31 AM Jared Still <jkstill@xxxxxxxxx> wrote:
I am with Mladen on this.
More than one of our clients has wanted to change some aspect of
networking in RAC, usually the IP range.
While the network team may think that changing the network is relatively
simple, it is not simple with RAC.
One client had to change the IP settings, no choice.
They casually mentioned this at a mtg.
Immediately we started raising red flags.
This was a non-trivial project that took significant planning and effort.
The domain change may be simpler, but it would be a good idea too look up
support notes, and open an SR with Oracle to inquire about it.
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Principal Consultant at Pythian
Oracle ACE Alumni
Pythian Blog http://www.pythian.com/blog/author/still/
Github: https://github.com/jkstill
On Fri, Mar 26, 2021 at 12:25 PM Mladen Gogala <gogala.mladen@xxxxxxxxx>
wrote:
Oh boy, that's a nightmare. Personally, I would try cheating: just add
new names to DNS and let both the new and the old names be resolved.
That way, your scan listener would remain functional and everything
would stay the same.
On 3/23/21 4:04 PM, Douglas Dunyan wrote:
Greets All !
So I have a 2-node RAC cluster running 11.2.0.3. The veep has
issued a directive to change the 'domain name' of the network domain,
to reflect the new company branding.
I understand the typical procedure is to remove node 2, deconfigure
node 1. Update system(s) with new domain name, reconfigure node 1,
then re-add node 2.
Just wondering if there is a way to do this with less impact, a
silver bullet as it were.
I am preferring something with a cleaner rollback in case of
issues, as I must implement it in production and there are no
non-production environments available to test.
I'm also wondering if it's even necessary. Couldn't my team just
add an alias for the new domain name (ie stand up a new dns server
with the same ip's ?)
I look forward to hearing thoughtful feedback.
TIA
DougD
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com
--
//www.freelists.org/webpage/oracle-l
