Concurrent Managers Fail to Start After Cloning with ATG RUP 5

We faced this issue in one of our first clones after ATG_PF.H RUP5. This issue is well documented in metalink note id 434613.1. A workaround has been given for altering the trigger code causing the issue. Just ensure that the value of support_cp is set to Y in FND_NODES table for the node which is erroring out in logs. A permanent fix is being made available in ATG_PF.H RUP6.

Copy paste from metalink:

Applies to:

Oracle Application Object Library - Version: 11.5.10.2
This problem can occur on any platform.
11i with ATG RUP 5
Release 12

Symptoms

After cloning, concurrent managers fail to start.

The logfile for Internal Manager shows following error:

Could not initialize the Service Manager FNDSM__. Verify that has been registered for concurrent processing.

Output of FNDCCMDiagnostics.sh shows that Service manager (FNDSM) and Internal Monitor (FNDIM) for concurrent node do not exist. Absence of Service Manager causes concurrent managers not to start.

Changes

Application of ATG RUP 5 on 11i

Cause

The cause of this problem has been identified in Bug 6085070. It is caused by change in FNDSM trigger body.

FNDSM trigger body is changed to:

CREATE OR REPLACE TRIGGER fndsm
AFTER INSERT ON FND_NODES
FOR EACH ROW

BEGIN

if ( :new.NODE_NAME <> 'AUTHENTICATION' ) then
if ( (:new.SUPPORT_CP='Y')
or (:new.SUPPORT_FORMS='Y')
or (:new.SUPPORT_WEB='Y') ) then
fnd_cp_fndsm.register_fndsm_fcq(:new.NODE_NAME);

end if;

if (:new.SUPPORT_CP = 'Y') then
fnd_cp_fndsm.register_fndim_fcq(:new.NODE_NAME);
end if;

end if;

END;


This causes the problem if database tier and concurrent tier are on the same node in cloned environment.

When autoconfig is run on db tier, it creates the node but FNDSM and FNDIM are not created
because support_CP, SUPPRT_FORMS and SUPPORT_WEB are set to 'N'. When autoconfig is run next for apps tier, these column as updated to 'Y' but the trigger is NOT fired as it in 'ON INSERT' trigger and not 'ON UPDATE' trigger.

This causes FNDSM and FNDIM not to be created for the node which results in concurrent managers
not to start after cloning.

Solution

To implement the solution, please execute the following steps:

1. Connect via sqlplus as APPS user

2. Execute the following to alter trigger FNDSM:

CREATE OR REPLACE TRIGGER fndsm
AFTER INSERT OR UPDATE ON FND_NODES
FOR EACH ROW
BEGIN
if ( :new.NODE_NAME <> 'AUTHENTICATION' ) then
if ( (:new.SUPPORT_CP='Y')
or (:new.SUPPORT_FORMS='Y')
or (:new.SUPPORT_WEB='Y') ) then
fnd_cp_fndsm.register_fndsm_fcq(:new.NODE_NAME);
end if;
if (:new.SUPPORT_CP = 'Y') then
fnd_cp_fndsm.register_fndim_fcq(:new.NODE_NAME);
end if;
end if;
END;
/
commit;

3. Clean FND_NODES by executing the following:

exec FND_CONC_CLONE.SETUP_CLEAN;

4. Run autoconfig.

5. Restart concurrent managers and retest.

6. To avoid the same problem for future cloning, execute step #2 on source environment to alter FNDSM trigger

OR

When available, apply Patch 5903765 (ATG RUP 6) which delivers the above code in aftcm046.sql version 115.20 to alter FNDSM trigger. Note that this patch was not available at the time of writing this document (June 2007).

References

Bug 6085070 - FNDSM TRIGGER CAUSES SERVICE MANAGER NOT TO BE CREATED AFTER CLONING SINGLE NODE

---