Users Could Not Login With Special Characters like #, ^ After Upgrade From 12.2.5.1 To 12.2.6.3
(Doc ID 2882314.1)
Last updated on JULY 10, 2022
Applies to:
Oracle Demantra Predictive Trade Planning - Version 12.2.6.3 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.6.3 version,CollabWB, Non-Production Environment
ACTUAL BEHAVIOR
---------------
After upgrade from 12.2.5.1 to 12.2.6.3, User with special character #, ^ could not login. User password follows the password policy that requires one special character.
EXPECTED BEHAVIOR
-----------------------
After upgrade from 12.2.5.1 to 12.2.6.3, User with special character #, ^ should be able to log in
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upgrade from 12.2.5.1 to 12.2.6.3 and DB upgrade to 19C
2. change password for User with special character #, ^
3. Not able to log in to collaborator workbench
Workaround is remove special character #, ^, able to log in
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |