Blog dedicated to Oracle Applications (E-Business Suite) Technology; covers Apps Architecture, Administration and third party bolt-ons to Apps

Monday, July 14, 2008

Fndfxwho.Sql Fails during TXK or ATG patches

Recently while applying TXK Rollup S and ATG patches, one of the workers running fndfxwho.sql failed:

FAILED: file fndfxwho.sql on worker 8 for product fnd username APPLSYS.

adwork008.log showed:

Start time for file is: Wed Jul 09 2008 17:38:27

sqlplus -s APPS/***** @/gpscd140/erpapp/appl/fnd/11.5.0/patch/115/sql/fndfxwho.s
ql NONE
DECLARE
*
ERROR at line 1:
ORA-20002: [WF_NO_USER] NAME=OPERATOR2 ORIG_SYSTEM=NULL ORIG_SYSTEM_ID=NULL
ORA-06512: at "APPS.WF_LOCAL_SYNCH", line 1890
ORA-06512: at line 154

Metalink Note 372651.1 advises skipping the failed worker and applying ATG RUP5 for the fix. However this error repeated itself when ATG RUP5 was being applied. Metalink Note 374105.1 advises applying ATG RUP6:

Symptoms

On 11.5.10.2, when attempting to apply Patch 4334965 ,
the following error occurs.

ERROR
Fndfxwho.sql fails when installing Patch 4334965

sqlplus -s APPS/*****
@$FND_TOP/11.5.0/patch/115/sql/fndfxwho.sql &un_fnd &pw_fnd
DECLARE
*
ERROR at line 1:
ORA-01422: exact fetch returns more than requested number of rows
ORA-06512: at line 36

Cause

In the current SQL statement that is executed a supplementary condition is needed:

Current statement:

select created_by, creation_date, last_updated_by, last_update_date
into createdby, creationdate, lastupdatedby,lastupdatedate
from fnd_user_resp_groups_old
where user_id = who_rec.user_id
and responsibility_id = who_rec.responsibility_id
and responsibility_application_id = who_rec.responsibility_application_id;

New condition:

select created_by, creation_date, last_updated_by, last_update_date
into createdby, creationdate, lastupdatedby,lastupdatedate
from fnd_user_resp_groups_old
where user_id = who_rec.user_id
and responsibility_id = who_rec.responsibility_id
and responsibility_application_id = who_rec.responsibility_application_id
and security_group_id = who_rec.security_group_id;


By adding the supplementary condtition the SQL statement will return just one row, as required by
the business model.

This fix is available in $Header: fndfxwho.sql 115.3 delivered in 11i.ATG_PF.H.delta.6
.

Solution

To implement the solution, please execute the following steps:

1. Obtain 11i.ATG_PF.H.delta.6
2. Review the pre-reqs for this patch and apply to test system

1 comment:

Anonymous said...

Hi,

I faced the same problem while upgrading to release 12.1.1, I added the following to the same where clause in the script
and fnd.user_name not <> 'USER_NAME'

The user was an old employee and was end dated