I cannot understand the idea of critical database user like DEV_OPSS, on which weblogic server is based on, to be setup by default to expire.
This is how one day I got locked out, not being able to startup the weblogic server facing a message like this:
<Warning> <JDBC> <winavm64> <AdminServer> <Policy change scanner> <<anonymous>> <> <062b60ba-d378-4e2a-9745-84422a67d750-00000001> <1414637475380> <BEA-001129> <Received exception while creating connection for pool “opss-data-source”: ORA-28001: the password has expired .
The solution below is valid, if there is a backup of the database available, however it would be good idea to set the user’s password not to expire, as I do below, before you encounter such a problem:
First export the user from the backup database:
select
dbms_metadata.get_ddl('USER', 'DEV_OPSS') || '/' usercreate
from
dba_users;
CREATE USER "DEV_OPSS" IDENTIFIED BY VALUES 'S:82203FA77A8627F48AA01ECFA469C93361FFED946881E9848601F8C1DEFB;H:60FE4D6E80A4BEFFF1498F976BF62A35;42A2ED599C2B479A'
DEFAULT TABLESPACE "DEV_IAS_OPSS"
TEMPORARY TABLESPACE "DEV_IAS_TEMP"
PASSWORD EXPIRE/
Then fix the user in the current version of weblogic database:
sqlplus / as sysdba
alter profile default limit password_life_time unlimited;
alter USER "DEV_OPSS" IDENTIFIED BY VALUES 'S:82203FA77A8627F48AA01ECFA469C93361FFED946881E9848601F8C1DEFB;H:60FE4D6E80A4BEFFF1498F976BF62A35;42A2ED599C2B479A' profile default;
alter USER "DEV_OPSS" account unlock;
I never learned which was the password, I tried with oracle, welcome1, dev_opss, but it did not work.