Skip to main content

Hi All, I have noticed some BR related print jobs are failing with the following error and it is reoccurring:

 

ORA-04061: existing state of has been invalidated
ORA-04061: existing state of package "IFSAPP.APP_MESSAGE_PROCESSING_API" has been invalidated
ORA-04065: not executed, altered, or dropped package "IFSAPP.APP_MESSAGE_PROCESSING_API"
ORA-06508: PL/SQL: could not find program unit being called: "IFSAPP.APP_MESSAGE_PROCESSING_API"
ORA-06512: at "IFSAPP.APPLICATION_MESSAGE_JMS_TR", line 2
ORA-04088: error during execution of trigger 'IFSAPP.APPLICATION_MESSAGE_JMS_TR'

 

I reviewed the logs and observed the same error reported in the J2EE folder logs. Currently, there are no invalid objects on the server. Based on some knowledge sources, I found that objects like these can become invalid due to the "Rebuild indexes" database task. R&D has addressed this issue with bug fix 156423, which is included in UPD10.

Upon further investigation, I found another article suggesting that this issue occurs due to the Shrink Lob Segment job. However, this job is currently disabled.

https://ifsworld.service-now.com/csm?id=kb_article_view&table=kb_knowledge&sys_kb_id=f7593c09c3aa42142865d6af0501316c&searchTerm=KB0056807

Currently, the customer is on UPD24, and I believe this bug fix should already be applied to the Application. From my understanding, this issue affects other customer integrations as well.

Could you please advise on how this can be resolved?

 

 

There are some invalid APIs.

You need to recompile them.

For example with PL/SQL developer:

Or in IFS IEE client:

 

​@Link Yes, this works, but the issue recurs every Sunday at a specific time. Currently, I cannot identify any specific background job causing this problem.


The following is a list of invalid objects that reoccur every Sunday around 2:30 AM UK time. I have checked the scheduled jobs for that specific time but did not find anything related to this issue. Recompiling the objects resolves the problem temporarily, but the issue keeps recurring. Has anyone experienced a similar situation?

 

Reply


Terms & ConditionsCookie settings