Question

Apps9 printing error

  • 28 October 2021
  • 2 replies
  • 222 views

Userlevel 4
Badge +10

Hi All,

 

I have logged in as various users and the below fault is intermittent. It generally happens the first time you go to run the Work Order report that has been written in Crystal Reports. I am at a loss of where to look to try to prevent this from happening - any ideas you wonderfully clever individuals?

 

Server error messages:
9ec596ec-3c47-4924-a728-5e2aa6d3b44c

Ifs.Fnd.FndSystemException: Unexpected error while calling server method ExploreReports/NewClientReport ---> Ifs.Fnd.FndServerFaultException: ORA-04068: existing state of packages has been discarded

Failed executing statement (ORA-04068: existing state of packages has been discarded
ORA-04061: existing state of  has been invalidated
ORA-06512: at "IFSAPP.REPORT_SYS", line 3294
ORA-04061: existing state of package body "IFSAPP.PART_SERIAL_CATALOG_API" has been invalidated
ORA-06512: at "IFSAPP.WO_SEP_RPI", line 1199
ORA-04065: not executed, altered or dropped package body "IFSAPP.PART_SERIAL_CATALOG_API"
ORA-06512: at "IFSAPP.WO_SEP_RPI", line 436
ORA-06512: at "IFSAPP.WO_SEP_RPI", line 436
ORA-06512: at line 1
ORA-06512: at "IFSAPP.REPORT_SYS", line 3290
ORA-06512: at "IFSAPP.REPORT_SYS", line 687
ORA-06512: at "IFSAPP.ARCHIVE_API", line 2882
ORA-06512: at "IFSAPP.ARCHIVE_API", line 2889
ORA-06512: at "IFSAPP.ARCHIVE_API", line 2066
ORA-06512: at "IFSAPP.ARCHIVE_API", line 2071
ORA-06512: at line 1)
   at Ifs.Fnd.AccessProvider.FndConnection.ParseErrorHeader(FndBuffer buffer, FndManualDecisionCollection decisions)
   at Ifs.Fnd.AccessProvider.FndConnection.UnMarshalResponseHeader(Stream responseStream, FndManualDecisionCollection decisions)
   at Ifs.Fnd.AccessProvider.FndConnection.HandleHttpSuccessResult(HttpWebResponse result, FndManualDecisionCollection decisions, String operation, FndBodyType responseBodyType, Object responseBody)
   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(Object requestBody, Object responseBody, String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Boolean forcedSync)
   --- End of inner exception stack trace ---
   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(String intface, String operation, Object requestBody, Object responseBody, FndRequestContext requestContext, Boolean forcedSync)
   at Ifs.Fnd.AccessProvider.Activity.FndActivityContext.Invoke(String intface, String operation, Object request, Object response)
   at Ifs.Fnd.AccessProvider.Activity.FndActivityCommand.ExecuteNonQuery(Object body)
   at Ifs.Application.InfoServicesFramework.ServerInterface.Ifs.Application.InfoServicesFramework.IExploreReports.NewClientReport(Double& resultKey, String reportAttributes, ReportParametersTable parameters, String distributionList, String printAttribute)
   at Ifs.Application.InfoServicesFramework.InfoServicesService.OrderNewReport(String reportAttr, Dictionary`2 parameters, List`1 distributionList, String printAttribute)


This topic has been closed for comments

2 replies

Userlevel 3
Badge +5

Hmm… My (outdated?) technical knowledge tells me that these kind of error messages usually happens once you run and try to use the PL/SQL package (like "IFSAPP.PART_SERIAL_CATALOG_API") the first time after there has been some deployment of code in the database. 

Usually after a code delivery, the deployment process should contain a “re-compile” step so that all packages gets recompiled and refreshed. But I can also see that there seems to be something regarding global variables etc. in this thread - https://stackoverflow.com/questions/1761595/frequent-error-in-oracle-ora-04068-existing-state-of-packages-has-been-discarde

Does it usually happens after an update of the code to your system? Say after weekends or in the mornings?

Userlevel 4
Badge +10

@ola.nissen - its a new report as we are just starting to use the service and maintenance module. It happens nearly every time you go back to the page, first time you RMB print, print work order the error occurs, do it a second time, no error. Navigate away to another page then return to print again and the error may or may not appear - there doesn’t seem to be any constancy as when it occurs.