The Applications System names per the APPL_TOP and the database are different

Metalink id's * --
=========

Adpatch Fails : 'The Applications System names per the APPL_TOP and the database are different.' (Doc ID 213339.1)
Unable to Patch a Cloned Environment Because of Wrong Applications System Names (Doc ID 202483.1)


We recently faced an issue after development instance cloned from production.

adpatch Failed with the below errors.

The Applications System names per the APPL_TOP and the database are different.
Applications System name per the APPL_TOP: EBSDEV
Applications System name per the database: EBSOLTP
If you continue, the Applications System name per the APPL_TOP will be ignored.

Do you wish to continue [No] ?


Cause *:--  The APPLICATIONS_SYSTEM_NAME field in the FND_PRODUCT_GROUPS table was still filled with the value of the old environment.

NOTE * ;-
When we run FND_CONC_CLONE.SETUP_CLEAN it will clean FND_PRODUCT_GROUPS table and really not sure why the name of the production
instance appear in the table.

SQL> select APPLICATIONS_SYSTEM_NAME from FND_PRODUCT_GROUPS;

APPLICATIONS_SYSTEM_NAME
——————————
EBSOLTP



Solution *:--

update FND_PRODUCT_GROUPS set APPLICATIONS_SYSTEM_NAME =’EBSDEV' ;
commit;

Then we restarted adpatch and it got succeeded.

QUOTE OF THE DAY.
Either you run the day, or the day runs you. –Jim Rohn