Step by Step Guide To Troubleshooting Enterprise User Security (EUS) - Password Authentication
(Doc ID 453853.1)
Last updated on DECEMBER 31, 2024
Applies to:
Advanced Networking Option - Version 10.1.0.2 to 12.1.0.2 [Release 10.1 to 12.1]Information in this document applies to any platform.
Purpose
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
This guide provide detailed steps on verifying/troubleshooting password authenticated Enterprise User Security (EUS).
Troubleshooting Steps
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 |
| Troubleshooting Steps |
Section I: Verify the Enterprise User Security (EUS) configuration |
| Step 1: Verify OID instance configuration |
Step 2: Verify Enterprise User Security (EUS) configuration on the OID |
Step 3: Verify the password policy for the realm |
Step 4: Verify Enterprise User Security (EUS) configuration on the DB |
Section II: Common Errors and Known issues |
| 1. ORA-1017: Invalid username/password; login denied |
| 2. Invalid Credentials with EUS login through OEM |
3. ORA-28043: Invalid bind credentials for DB/OID connection |
4. ORA-28030: Server encountered problems accessing LDAP directory service |
| 5. ORA-28273: No mapping for user nickname to LDAP distinguished name exists |
| 6. ORA-28274: No ORACLE password attribute corresponding to user nickname exists |
| 7. "ORA-01012: not logged on" when executing a query after successful EUS connection AS SYSDBA |
| 8. EUS authentication does not work when using TNS connect string |
| 9. ldap_search: Insufficient access |
| 10. EUS authentication fails when TDE and EUS wallet points to the same location |
| 11. ORA-1017 when connecting through proxy user |
Section III: Collect Event tracing for further analysis |
| References |