Issue With RM_USER Table Showing Incorrect D_LAST_VALID_LOGIN
(Doc ID 2421198.1)
Last updated on DECEMBER 26, 2019
Applies to:Hyperion Data Relationship Management - Version 188.8.131.52.343 and later
Information in this document applies to any platform.
The D_LAST_VALID_LOGIN field in the RM_USER table shows a time that is 4 hours off the actual time.
For example, when logging into DRM at 7:47:27 in the morning, the RM_USER table shows 6/22/2018 11:47:27.613899 AM
Why is the time showing a difference?
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