Shared Services Repository Database User Account Gets Locked Out Periodically
(Doc ID 2226548.1)
Last updated on AUGUST 29, 2024
Applies to:
Hyperion BI+ - Version 11.1.2.2.500 and laterInformation in this document applies to any platform.
Symptoms
1. Periodically the Shared Services repository database account would get locked out. When that happens, the users would see the following symptoms -
When logging into Workspace, the following error is thrown - "The startup page cannot be displayed".
When logging into EAS, the "invalid login credentials" error is thrown.
When logging into DRM, the following error is thrown - Login failed for user <HSS_Repository_db_user> because account is currently locked out.
2. DB trace logs -
<Date> Logon "Login failed for user <HSS_Repository_db_user>".Reason: Password did not match that for the login provided. [CLIENT: xxx.xx.xxx.xx]
The Client IP mentioned in the database trace for the error is the server where the HFM product is installed.
3. The following error in seen in the InteropJava.log located in \Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\hfm folder on one of the HFM servers -
com.hyperion.hit.registry.exceptions.RegistryException: com.hyperion.hit.registry.exceptions.RegistryException: java.lang.OutOfMemoryError: Java heap space
at com.hyperion.hit.registry.Registry.lookupWithException(Registry.java:540)
at com.hyperion.hit.registry.Registry.lookup(Registry.java:585)
at com.hyperion.hfm.HITRegistryInterop.getDataSourceProperty(Unknown Source)
Caused by: com.hyperion.hit.registry.exceptions.RegistryException: java.lang.OutOfMemoryError: Java heap space
at com.hyperion.hit.registry.Registry.lookupComponentsWithException(Registry.java:1333)
at com.hyperion.hit.registry.Registry.lookupWithException(Registry.java:508)
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 |
Cause |
Solution |
References |