Thursday, November 14, 2019

PLS-00302: component 'PURGE_BUSINESS_EXCEPTIONS' must be declared

In my environment we are using R12.2.5. Recently after a fresh clone of the application tier, before releasing the instance, performed the post clone activity and sanity works. As a part of this tasks, ran the concurrent program 'Purge Debug Log and System Alerts' to remove the log files.

After submission, the program has completed with error.


From the log file observed the below error:
"Cause: FDPSTP failed due to ORA-06550: line 1, column 20:
PLS-00302: component 'PURGE_BUSINESS_EXCEPTIONS' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored"


"Purge Debug Log and System Alerts" is the name of the old purge program that was used in Oracle Application Release 11i, "Purge Logs and Closed System Alerts" is name of new one introduced in Release 12. Both of them do basically same thing, that is purge logs and alerts. "Purge Diagnostic and Log Messages" is no longer used in R12. If someone runs concurrent program "Purge Diagnostic and Log Messages" then it will error out with below error message in concurrent program logfile :  

Error:
ORACLE error 6550 in FDPSTP
Cause: FDPSTP failed due to ORA-06550: line 1, column 20:
PLS-00302: component 'PURGE_BUSINESS_EXCEPTIONS' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored 

To overcome the above error "Purge Logs and Closed System Alerts [FNDLGPRG]" should be run instead of "Purge Debug Log and System Alerts" in Release 12.

To disable Concurrent program "Purge Diagnostic and Log Message" in Release 12 do the following:



Query for the concurrent program 'Purge Diagnostic and Log Messages'


Uncheck the 'Enabled' checkbox and save the program.


Now run the program 'Purge Logs and Closed System Alerts' to purge the messages.


Ref : How to Purge/Troubleshoot the FND_LOG_MESSAGES table (Doc ID 735138.1)

****************************நன்றி****************************

No comments:

Post a Comment

IAS Cache initialization failed

 Today I faced an Issue in R12.2 instance. The solution I followed to overcome the issue is very simple, but they are more than one solution...