Weblogic: "ORA-28001: the password has expired" error when starting up the ServiceManager Follow

Symptom: "ORA-28001: the password has expired" exception in FODomain.log (the console/admin-log display an unhelpful generic error). The ServiceManager won't start in weblogic.

AdminServer.log:

Caused By: java.lang.NoClassDefFoundError: 
Could not initialize class com.auraplayer.config.context.ApplicationContextHolder
at com.auraplayer.dal.dao.factories.DaoFactoryImpl.getServiceDao(DaoFactoryImpl.java:30)
at com.auraplayer.repositories.service.ServiceRepository.<init>(ServiceRepository.java:30)
at com.auraplayer.repositories.service.ServiceRepository.<clinit>(ServiceRepository.java:27)

FODomain.log

com.oracle.cie.servicetable.external.ServiceTableException: 
weblogic.jdbc.extensions.ConnectionDeadSQLException: 
weblogic.common.resourcepool.ResourceDeadException:
0:weblogic.common.ResourceException:
Could not create pool connection for datasource 'LocalSvcTblDataSource'.
The DBMS driver exception was: ORA-28001: the password has expired

Solution:

1. Identify Weblogic's DB user
   Open the WebLogic Admin Console (http://<host>:7101/console).
   Navigate to Services > Data Sources > Select LocalSvcTblDataSource > Configuration > Connection Pool.
   The "Properties" line will display the user (e.g. DEV_STB).
   
   

2. Sanity check: verify that the password has expired
   Open a cmd window on the server, and run:
   sqlplus sys as sysdba
   Enter the sysdba password (on AuraPlayer servers, see Desktop/PW.txt).
   Run:
   SELECT username, account_status FROM dba_users WHERE username = 'DEV_STB';
   
   

3. Update the password for the corresponding database user
   (continue on the same cmd window from the previous step)
   ALTER USER DEV_STB IDENTIFIED BY new_password;
   You may now run the sanity check again to see that the status is no longer EXPIRED.
   
   

4. Set the new password in Weblogic console
   (continue on the same Weblogic console screen from step 1)
   Enter the new password in the Password and Confirm Password fields, then Save.
   
   
5. Restart WebLogic Server
   Full WebLogic restart is required.