Introduction

When deploying Essbase 21c on OCI Marketplace or Independent Deployment, an RCU database is configured. This RCU database requires a password, which may expire if configured to do so. If this is the case, the RCU database password needs to be reset

Problem

When the RCU database password expires, one of the symptoms could be that end users are not able to log into the Essbase Web UI. When this is reported to the Essbase admin, the Essbase Admin should check the essbase_server1.out log for the following error:

The DBMS driver exception was: ORA-28001: the password has expire

Solution

To reset the RCU database password, follow the official Essbase documentation

Marketplace Stack Deployment

https://docs.oracle.com/en/database/other-databases/essbase/21/essad/fix-expired-rcu-passwords-that-use-autonomous-database-repository.htm

Independent Deployment

https://docs.oracle.com/en/database/other-databases/essbase/21/essoa/reset-essbase-repository-database-schema-password.htm

Summary

Essbase 21c deployments include configuring an RCU database, which the password can expire if configured to do so. If the Essbase Admin does not change the RCU database password before it expires, end users may not be able to log onto the Essbase Web UI. The Essbase Admin can confirm that the login issue is related to the RCU database password expired by checking the essbase_server1.out log. Once the root cause has been identified – that the RCU database password expired, follow the documentation links above to correct or reset the RCU database password. Once the password has been changed, check that the Essbase Web UI login access is successful.