Friday 29 August 2014

Unable to change GUEST Password in 11i

Issue : Application login user password not accepting.


Investigation :



Upon received the mails from users, I started investigated the issue and found username and password was not accepted. So I went and checked the JVM logs and found the below error which is mostly related to GUEST user password.

Below is the error log on /oar2/oracle/oar2ora/iAS/Apache/Jserv/logs/jvm/OACoreGroup.0.stderr

Exception in static block of jtf.cache.CacheManager. Stack trace is: oracle.apps.jtf.base.resources.FrameworkException: oracle.apps.fnd.common.PoolException: Not able to create new database connection: FNDSECURITY_APPL_LOGIN_FAILED
at oracle.apps.jtf.cache.CacheManager.initCache(CacheManager.java:718)
at oracle.apps.jtf.cache.CacheManager.<clinit>(CacheManager.java:378)

Then verified the Guest user password validation which is failed, Then manually  updated the GUEST password to XML file and ran autoconfig  but it did not updated to any of the configuration files and to the database. Upon search of multiple oracle notes and forums, I found the below forum and then executed the action plan.

To verify the guest user password "GUEST1" then it should result in application DBC file and Database  level.

sqlplus apps/apps

SQL> select fnd_profile.value('GUEST_USER_PWD') from dual;

FND_PROFILE.VALUE('GUEST_USER_PWD')
--------------------------------------------------------------------------------
GUEST/WELCOME

SQL> SELECT fnd_web_sec.validate_login('GUEST','WELCOME') FROM dual;

FND_WEB_SEC.VALIDATE_LOGIN('GUEST','WELCOME')
--------------------------------------------------------------------------------
N

Welcome is the wrong password and the fnd_web_sec.validata_login also failed with welcome. Verify the dbc file in $FND_SECURE/OAC2_oadbc2.dbc

Even after updating the s_guest_password in Context_file and run autoconfig then please execute the below action plan.mentioned in one of the oracle forum.


2)      Downloaded and Applied the patch 6496781  “This appears to be an issue with ATG rup6”
3)      Run autoconfig on DB and Application servers
4)      Started the application services and did the sanity checks.
5)      Make sure password looks like case sensitive


Hope the  above solution will fix your  Login issue.

--- Sudhakar.

No comments:

Post a Comment