Re: Further Adventures in RAC - Cannot Add Instance

From: David Barbour <david.barbour1_at_gmail.com>
Date: Tue, 9 Jun 2020 22:23:56 -0500
Message-ID: <CAFH+iffcHcBoFA684gsCPoEepGVGec34hq+p5SSQMGebdd91Tw_at_mail.gmail.com>



Okay - got it figured out. Hope this helps someone who might be encountering a similar issue.

We're adding two new servers (nodes) to our RAC and will delete the old ones. The add/delete is to avoid a loss of service as we are an educational SAS with a ton of kids online at any given time.

Anyway, the new servers are on RHEL 7.6 and the old ones are on RHEL 6.8. Seems the OS was installed and configured (by default) to use a ecdsa-sha2-nistp256 encoded key. So even though the correct ssh-rsa key was in id_rsa.pub on all the servers, the known_hosts file on the new server(s) defaulted to a ecdsa-sha2-nistp256 encoded key. The sshUserSetup.sh completed successfully on all nodes, but the dbca trace file showed the grid user did not have rights. Ended up doing the equivalency the 'old-fashioned' manual way and manually editing known_hosts.

Fun with Oracle.

On Sun, Jun 7, 2020 at 10:30 PM David Barbour <david.barbour1_at_gmail.com> wrote:

> Thanks Mladen. This was a software only clone, so I'm not sure it applies
> but I am probably going to have to open a support ticket.
>
> On Sun, Jun 7, 2020 at 8:27 PM Mladen Gogala <gogala.mladen_at_gmail.com>
> wrote:
>
>> I had a similar issue and it was a bug. Oracle support has provided me
>> with a patch:
>>
>> R12 TNS-01189: The listener could not authenticate the user Error When
>> Cloning RAC (Doc ID 1468042.1)
>> I am not sure whether your issue is the same, you'll have to check with
>> Oracle Support.
>> Regards
>>
>> On 6/7/20 8:51 PM, David Barbour wrote:
>>
>> I figured after I was able to identify the disk on the new node, the rest
>> would be easy. Ran add.node.sh, cloned the ORACLE_HOME and went to add
>> an instance. Nope. dbca isn't listing the new node. There are a couple
>> of Oracle notes on this but I've tried those suggestions and had no
>> success.
>>
>> This is RHEL 7.6 running oracle 12.2.0.1 - patched through Jan 2020.
>>
>> +ASM3_at_1103477-db7:/u01/app/12.2.0/grid/network/admin $ olsnodes
>> 685921-db5
>> 685925-db6
>> 1103477-db7
>>
>> [root_at_1103477-db7 bin]# ./crsctl query crs softwareversion
>> Oracle Clusterware version on node [1103477-db7] is [12.2.0.1.0]
>>
>> +ASM3_at_1103477-db7:/home/grid $ srvctl status scan_listener
>> SCAN Listener LISTENER_SCAN1 is enabled
>> SCAN listener LISTENER_SCAN1 is running on node 1103477-db7
>> SCAN Listener LISTENER_SCAN2 is enabled
>> SCAN listener LISTENER_SCAN2 is running on node 685925-db6
>> SCAN Listener LISTENER_SCAN3 is enabled
>> SCAN listener LISTENER_SCAN3 is running on node 685921-db5
>>
>> [root_at_1103477-db7 bin]# ./crsctl status res -t
>>
>> ora.LISTENER.lsnr ONLINE OFFLINE 1103477-db7 STABLE
>> ONLINE ONLINE 685921-db5 STABLE
>> ONLINE ONLINE 685925-db6 STABLE
>>
>> I cannot get this listener online. Here's what happens:
>>
>> +ASM3_at_1103477-db7:/u01/app/12.2.0/grid/network/admin $ lsnrctl start listener
>>
>> LSNRCTL for Linux: Version 12.2.0.1.0 - Production on 07-JUN-2020 19:49:54
>>
>> Copyright (c) 1991, 2016, Oracle. All rights reserved.
>>
>> TNS-01106: Listener using listener name LISTENER_SCAN1 has already been started
>> +ASM3_at_1103477-db7:/u01/app/12.2.0/grid/network/admin $ lsnrctl stop listener
>>
>> LSNRCTL for Linux: Version 12.2.0.1.0 - Production on 07-JUN-2020 19:50:24
>>
>> Copyright (c) 1991, 2016, Oracle. All rights reserved.
>>
>> Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=scan01-dfw.istation.com)(PORT=1521)))
>> TNS-01189: The listener could not authenticate the user
>>
>> Any ideas here?
>>
>> --
>> Mladen Gogala
>> Database Consultant
>> Tel: (347) 321-1217
>>
>>

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Jun 10 2020 - 05:23:56 CEST

Original text of this message