Hi @User_C0PIC,

Check the DB Username status. Most probably the DB Schema Owner's Passwords are expired. You can get more information in the AdminServer.log file.

Hi,

the reason for this error message were expired passwords for OAS schemas. As @SparcSeven-Oracle suggested, the below error will be outputted in AdminServer.log file:

java.sql.SQLException: ORA-28001: the password has expired

There are a lot of guides, how to unlock, but for completeness sake, I'll provide details that worked for us here:

• Login to OAS database with SYS.
• Check if it's actually expired, by running below (there will be EXPIRED, EXPIRED (GRACE) statuses)

SELECT username, account_status, expiry_date

FROM dba_users

WHERE username like '<your_OAS_prefix>%' -- if unsure about prefix, remove this filter

Find schemas with WLS_RUNTIME, IAU_VIEWER, BIPLATFORM, MDS suffixes and check the prefix. Use this prefix in the selects below instead of <our_OAS_prefix> (do not remove %).

• Create UNLIMITED_PASSWORD profile:

CREATE PROFILE UNLIMITED_PASSWORD LIMIT PASSWORD_LIFE_TIME UNLIMITED;

ALTER PROFILE UNLIMITED_PASSWORD LIMIT

  CONNECT_TIME UNLIMITED

  COMPOSITE_LIMIT UNLIMITED

  CPU_PER_CALL UNLIMITED

  CPU_PER_SESSION UNLIMITED

  FAILED_LOGIN_ATTEMPTS 3

  IDLE_TIME UNLIMITED

  INACTIVE_ACCOUNT_TIME UNLIMITED

  LOGICAL_READS_PER_CALL UNLIMITED

  LOGICAL_READS_PER_SESSION UNLIMITED

  PASSWORD_GRACE_TIME 7

  PASSWORD_LOCK_TIME 1

  PASSWORD_REUSE_MAX 5

  PASSWORD_REUSE_TIME 365

  PASSWORD_VERIFY_FUNCTION ORA12C_STRONG_VERIFY_FUNCTION

  PRIVATE_SGA UNLIMITED

  SESSIONS_PER_USER UNLIMITED;

• Create ALTER Commands for UNLIMITED_PROFILE using below SQL:

SELECT 'ALTER USER '|| username ||' PROFILE UNLIMITED_PASSWORD;' from DBA_USERS where username like '<your_OAS_prefix>%';

• Copy result, and execute all commands to set schemas to UNLIMITED_PROFILE. NOTE: If passwords, haven't expired yet, this is enough to make them never to expire.

Since you are reading this, passwords most likely expired, so we have to re-open the schemas.

• Run below to create ALTER commands to re-open the schemas (with existing passwords)

SELECT 'ALTER USER '|| name ||' IDENTIFIED BY VALUES '''|| spare4 ||';'|| password ||''';' FROM sys.user$ WHERE name like '<your_OAS_prefix>%';

• Copy the ALTER commands provided by result of above query and execute them all.
• By running first SELECT again, confirm that schemas are OPEN, do not have Expire date, and have UNLIMITED_PASSWORD profile assigned

SELECT * from dba_users where username like '<your_OAS_prefix>%';

On my end it was NOT required to restart OAS services - users were able to log into Analytics straight away; but bounce the services and check AdminServer.log again in case it's not working for you.

Hope this helps.

Regards,

Sašo

That is true - check with your DBAs first and use above suggestion with care.