The new Exclusive Mode default for password-based authentication in Oracle 12.2 conflicts with case-insensitive password configurations. All user login fails with ORA-1017 after upgrade to 12.2
(Doc ID 2075401.1)
Last updated on JULY 16, 2023
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database - Enterprise Edition - Version 12.1.0.1 and later
Information in this document applies to any platform.
Purpose
The new Exclusive Mode default for password-based authentication in Oracle 12.2 conflicts with case-insensitive password configurations.
After upgrade to 12.2, accounts may become inaccessible if a setting of FALSE for the sec_case_sensitive_logon instance initialization parameter is used,
because by default in 12.2 the instance is configured to run in Exclusive Mode.
For more details on Exclusive Mode, please see the section of Network Reference Manual which describes the SQLNET.ALLOWED_LOGON_VERSION_SERVER parameter. http://docs.oracle.com/database/121/NETRF/sqlnet.htm#NETRF2016
Scope
Details
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
| Purpose |
| Scope |
| Details |
| References |