ASM Using Databases Can't Disable OS Authentication or Use ASO: ORA-01031
Last updated on NOVEMBER 04, 2015
Applies to:Oracle Server - Enterprise Edition - Version 10.2.0.4 and later
Information in this document applies to any platform.
For a database that uses ASM as file system, if:
1. disabling OS authentication by setting:
SQLNET.AUTHENTICATION_SERVICES = (NONE)
2. enable any kind of ASO authentication
SQLNET.AUTHENTICATION_SERVICES = (kerberos, radius, ssl)
the database fails to authenticate to the ASM instance.
This would be the expected behavior, since the database uses bequeath to connect to the ASM and a bequeath session takes the environment from its client application, which in this situation is the database itself (oracle process).
Consequently, if setting as above the SQLNET.AUTHENTICATION_SERVICES parameter, the database would attempt to use that authentication method to log to the ASM service. Since ASM supports only the OS authentication, the database session fails with ORA-01031 (other errors might be experienced when enabling ASO, depending on the specific setting).
However, for the duty separation, this is a very desirable feature.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms