Last updated on JANUARY 05, 2017
Applies to:Oracle Demantra Demand Management - Version 12.2.5 and later
Information in this document applies to any platform.
Customer mentions that they have upgraded Demantra to 220.127.116.11 in Dec 2015. After that whenever they make any changes to a user ( password change, email change or any other change) they get the following error
“Update of the user_id table has failed.”
This happens to all users, as a test they created a new user, left the email blank and then tried to add the email and got the error.
They have had this issue with the users ever since they used BAL to upgrade to 12.2.5, it has not worked since the upgrade, either updating existing users or creating new ones. They also made a data model change on Jan 29. They have changed the date setting (Forward vs backward) that the BAL reset to a value they didn't want. However this issue was happening before they rebuilt the model and there were no errors encountered when rebuilding.
Enabling the LOG_IT for the procedure API_CREATE_ORA_DEM_USER does not write anything to the LOG_API_CREATE_ORA_DEM_USER table.
However they can make the change from the command line by way of
The above works and even writes to the LOG_API_CREATE_ORA_DEM_USER table (uploaded).
It is only when they make the change from the Business Modeler it neither works nor writes to the LOG_API_CREATE_ORA_DEM_USER table or to the db_exception_log
Verified that the table user_id have salt column in the user_id table
Also the BM version is 18.104.22.168
Further updates from the customer
I just updated one of the users that was failing. I changed the encryption type back to SHA-1 and changed the password via SQL update and was then able to make changes. Changing the password set the encryption type back to SHA-2-512-SALT and I could no longer update the user name, password, etc. I then changed the password via SQL update to a shorter length and I was again able to update the user details.
So the fact that encryption_type being SHA-2 is causing the issue indirectly. The length of the password is causing the issue. An encrypted password that is 81 characters long works, at 82 characters it throws the error message.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms