Not able to create new database connection: FND^@SECURITY_APPL_LOGIN_FAILED^@ when starting Concurrent Managers

Hi,

Recently we faced a issue after cloning R12 environment

Issue Description:

-----------------

The concurrent managers were not coming up after cloning

Workflow Agent Listener Service

Workflow Mailer Service

Workflow Document Web Service

Email Center Download Processor

Output Post Processor

When checking the manager logs for each of the managers I found the below error

Not able to create new database connection: FND^@SECURITY_APPL_LOGIN_FAILED^@

Troubleshooting:

---------------

Quick list of managers which were not started showed us that the mangers using the
framework were the ones affected.

Error pointed issue with the GUEST user.

Hence we checked the GUEST password in the dbc file $FND_SECURE/CDEV.dbc on CM node
and found the below entry

GUEST_USER_PWD=GUEST/CPRD

Also when we checked the context file $CONTEXT_FILE on CM node we found the parameter
s_guest_pass set to CPRD

Now we wanted to validate GUEST password at database base level

1. Conn to database as apps

2. Find the password at database level

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

FND_PROFILE.VALUE('GUEST_USER_PWD')

——————————————————————————

GUEST/CDEV

Here we found that in the database the password for GUEST was different

3. Then we checked if the guest user was working fine with the password at database level

SQL> select FND_WEB_SEC.VALIDATE_LOGIN('GUEST','CDEV') from dual;

FND_WEB_SEC.VALIDATE_LOGIN('GUEST','CDEV')

——————————————————————————–-----

Y

4. We also found that mismatch in database and the CM node was because, as this is a multi
node architecture the autoconfig was not run last on the CM node but some other node which
had the value for s_guest_pass as CDEV. Hence we inferred that the database was updated
with the password for GUEST user with the value of s_guest_pass in the context file of the
node on which the autoconfig was run last

Solution:

--------

We can resolve this issue in two ways

Method 1

-----------

The traditional way of changing the GUEST password is to edit the parameter s_guest_pass in
the context file and running autoconfig

In our case as only the context file on the CM node had the wrong entry, we just need to make
the change in the context file on CM node and run autoconfig to fix the issue.

If you have more nodes where the context file is having the wrong password, then you need to correct the entry and run autoconfig on all those nodes

Method 2

-----------

In this method we can avoid running the autoconfig. We followed this method to fix the issue

i. Open the adgendbc.sh at $INST_TOP/admin/install and change the GUEST password to the
right password

ii. Take backup of the dbc file at location $FND_SECURE

iii. Run adgendbc.sh from location $INST_TOP/admin/install. It will prompt for Apps
username and password

iv. Check the new dbc file generated at location $FND_SECURE and see if the correct GUEST
password is generated

v. Do steps i to iv on all nodes where the dbc file has the wrong GUEST password

vi. Restart the concurrent managers

vii. Make the change in the conext file on the all nodes were the above steps i to iv were done,
so that the next autoconfig will generate the right dbc file

Regards,

Tanveer