ODA: Seven Reasons for SSH Errors Using OAKCLI Commands Including: Patching, Upgrades, Deployment, or Creating Oracle Databases
(Doc ID 2003316.1)
Last updated on JANUARY 15, 2023
Applies to:Oracle Database Appliance Software - Version 188.8.131.52 to 184.108.40.206 [Release 2.1 to 12.1]
Information in this document applies to any platform.
This note describes various situations when ODA users might encounter SSH problems. Usually seen during maintenance, patching, upgrades or other administrative tasks using oakcli.
Often the problem is associated with root executing oakcli commands which in can trigger several scripts in the background which require SSH for root, grid and Oracle users.
The actual source can be misleading, however, as discussed in the following note:
from ODA: Oakcli Create Database Fails with Error in authorized_keys (Doc ID 1674279.1)
"...The following error encountered while creating database using oakcli..."
Do you want to set up the EM Dbconsole for this database: [ Y | N ]?N
INFO : Logging all actions in /opt/oracle/oak/onecmd/tmp/pt1-20140430150745.log and traces in /opt/oracle/oak/onecmd/tmp/pt1-20140430150745.trc
INFO : Loading configuration file /opt/oracle/oak/onecmd/create_database.params...
INFO : Creating nodelist files...
INFO : Setting up ssh for root...
INFO : Setting up ssh across the private network...
.....ERROR: Error in authorized_keys, file has more than one line on node <ip address> (see above text) at /opt/oracle/oak/onecmd/GridSteps.pm line 5750
If you see SSH errors during patching the steps executed during the oakcli command are in logfiles found in the /opt/oracle/oak/onecmd/tmp directory
Symptoms / error message text
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|SSH ODA Potential Problem Sources|
|Profile was edited for Oracle; root ; or Grid -- Review /etc/bashrc or /etc/issue|
|A mismatch in passwords for root, oracle or grid user between the two ODA Nodes|
|Removal or corruption of the SSH authorized_keys file on one or both nodes|
|Special characters embedded in the password used|
|A third party application controls SSH security and permissions|
|After ODA Infra Upgrade To 220.127.116.11.0 Cannot Establish SSH Connection when using LDAP|
|Special Way to debug the situation when above check still cannot fix the issue:|