APPLIES TO: Oracle Database - Standard Edition - Version 12.2.0.1 and later Information in this document applies to any platform. SYMPTOMS When Operating System (OS) Authentication (also called External Authentication) for SYSDBA is disabled, using SRVCTL to start the Database fails with ORA-1017. That would be done by setting the following line and value in the sqlnet.ora file: SQLNET.AUTHENTICATION_SERVICES = (NONE)
Using SQL*Plus to connect using the Oracle Password works and the Database starts. CHANGES OS Authentication was disabled by setting the following in the sqlnet.ora file on the Database Server: SQLNET.AUTHENTICATION_SERVICES = (NONE) CAUSE GRID and Clusterware programs that connect with RAC privileges, require OS Authentication for connectivity to the various resources such as the Database, so that a username and password are not required when managing resources automatically. So when you disable OS Authentication for all Database functions, it works for SQL*Plus (which can use the password file) but not for GRID which does not use the password authentication. SOLUTION When using GRID for managing resources like Databases, OS (External) Authentication is a requirement. Disabling OS Authentication will result in RAC operations being impacted. Therefore, OS Authentication is mandatory for GRID actions.
References: About Authentication Methods for Database Administrators |