Have you ever encountered this challenge ? . The shared connection pools like apex.xml etc is not holding the correct passwords to connect with database is the cause of it.
Every connection pool is having a direct user credentials and they are expected to be matched with database.
Sample users :
SYS> select username,account_status from dba_users where username like '%APEX%';
USERNAME ACCOUNT_STATUS
------------------------------ --------------------------------
APEX_200200 EXPIRED & LOCKED
APEX_INSTANCE_ADMIN_USER OPEN
APEX_LISTENER OPEN
APEX_PUBLIC_USER OPEN
APEX_REST_PUBLIC_USER OPEN
SYS> select username,account_status from dba_users where username like '%ORDS%';
------------------------------ --------------------------------
APEX_200200 EXPIRED & LOCKED
APEX_INSTANCE_ADMIN_USER OPEN
APEX_LISTENER OPEN
APEX_PUBLIC_USER OPEN
APEX_REST_PUBLIC_USER OPEN
SYS> select username,account_status from dba_users where username like '%ORDS%';
USERNAME ACCOUNT_STATUS
------------------------------ --------------------------------
ORDS_METADATA EXPIRED & LOCKED
ORDS_PUBLIC_USER OPEN
SYS>
------------------------------ --------------------------------
ORDS_METADATA EXPIRED & LOCKED
ORDS_PUBLIC_USER OPEN
SYS>
the solution is to have them re-set again in Database and run this command in web server ( where you have the ords workdir / war file is installed)
java -jar ords.war validate
Note: clear browser cache.
Your comments are invited. Cheers !

Comments
Post a Comment