Skip to main content
Solved

Compile Invalid Objects not working

  • February 26, 2024
  • 5 replies
  • 355 views

Curious_User
Sidekick (Customer)
Forum|alt.badge.img+8

Hello Community,

 

Our Business has run into an issue where we ended up with 2 Invalid Objects that can no longer be compiled, where IFS provides and Application Error.

Impacted Objects are: 

FND_TRK_LU_DMO_Q_N - Rule Set

FND_TRK_LU_DMO_Q_R - Rule Set

 

when trying to compile we get this error 

here is the Detail of the error: 

Ifs.Fnd.FndSystemException: Explorer: An Unhandled Exception has occurred ---> Ifs.Fnd.FndSystemException: Unexpected error while calling server method CompileInvalidObjects/CompileInvalidObjects ---> Ifs.Fnd.FndServerFaultException: ORA-00940: invalid ALTER command

Failed executing statement (ORA-00940: invalid ALTER command
ORA-06512: at "AGIL1APP.DATABASE_SYS", line 3213
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, Boolean integrationGateway)
   --- End of inner exception stack trace ---
   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(Object requestBody, Object responseBody, String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Boolean forcedSync, Boolean integrationGateway)
   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(String intface, String operation, Object requestBody, Object responseBody, FndRequestContext requestContext, Boolean forcedSync, Boolean integrationGateway)
   at Ifs.Fnd.AccessProvider.Activity.FndActivityContext.Invoke(String intface, String operation, Object request, Object response)
   at Ifs.Fnd.AccessProvider.Activity.FndActivityCommand.ExecuteNonQuery(Object request, Object response)
   at Ifs.Application.ManageInvalidObjects.ServerInterface.Ifs.Application.ManageInvalidObjects.ICompileInvalidObjects.CompileInvalidObjects(OracleUserObjectTable oracleUserObjects)
   at Ifs.Application.ManageInvalidObjects.CompileInvalidObjects.commandCompileAll_Execute(Object sender, FndCommandExecuteEventArgs e)
   at Ifs.Fnd.Windows.Forms.FndCommand.OnExecute(Component component)
   at Ifs.Fnd.Windows.Forms.FndContextMenuStrip.ExecuteCommand(ToolStripMenuItem menuItem, EventArgs e)
   at Ifs.Fnd.Windows.Forms.FndToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   --- End of inner exception stack trace ---

 

This happened after we applied IFS 10 UPD 21 into our IFS Test environment but did not occur during our IFS Development Update. 

Any help is much appreciated. (we are at a loss on this one)

Best answer by Curious_User

Vageesan wrote:

Hi @Curious_User ,

Try using the PLSQL developer and re-compile the invalid objects and refresh. If these invalid objects aren’t cleared might need to create a ticket and investigate with the related vertical since there were no issues occurred during the IFS Development Update.

Thanks & Regards,

Vageesan

Thank you @Vageesan ,

 

We ran the below and it fixed the issue. (Note needs to be run as sys or sysdba)


 

SET SERVEROUTPUT ON SIZE UNLIMITED
SET FEEDBACK OFF

DECLARE
  err_count NUMBER;
BEGIN
  SELECT COUNT(*) INTO err_count FROM dba_errors;
  IF err_count > 0 THEN
    DBMS_OUTPUT.PUT_LINE('Invalid objects found: ' || err_count);
    DBMS_OUTPUT.PUT_LINE('Recompiling...');
    UTL_RECOMP.RECOMP_SERIAL;
    DBMS_OUTPUT.PUT_LINE('Compilation completed.');
  ELSE
    DBMS_OUTPUT.PUT_LINE('No invalid objects found.');
  END IF;
END;
/

 


 

View original
Did this topic help you find an answer to your question?

5 replies

Forum|alt.badge.img+4
  • Do Gooder (Employee)
  • 14 replies
  • March 1, 2024

Hi @Curious_User ,

Try using the PLSQL developer and re-compile the invalid objects and refresh. If these invalid objects aren’t cleared might need to create a ticket and investigate with the related vertical since there were no issues occurred during the IFS Development Update.

Thanks & Regards,

Vageesan


Curious_User
Sidekick (Customer)
Forum|alt.badge.img+8
  • Author
  • 26 replies
  • Answer
  • May 6, 2024
Vageesan wrote:

Hi @Curious_User ,

Try using the PLSQL developer and re-compile the invalid objects and refresh. If these invalid objects aren’t cleared might need to create a ticket and investigate with the related vertical since there were no issues occurred during the IFS Development Update.

Thanks & Regards,

Vageesan

Thank you @Vageesan ,

 

We ran the below and it fixed the issue. (Note needs to be run as sys or sysdba)


 

SET SERVEROUTPUT ON SIZE UNLIMITED
SET FEEDBACK OFF

DECLARE
  err_count NUMBER;
BEGIN
  SELECT COUNT(*) INTO err_count FROM dba_errors;
  IF err_count > 0 THEN
    DBMS_OUTPUT.PUT_LINE('Invalid objects found: ' || err_count);
    DBMS_OUTPUT.PUT_LINE('Recompiling...');
    UTL_RECOMP.RECOMP_SERIAL;
    DBMS_OUTPUT.PUT_LINE('Compilation completed.');
  ELSE
    DBMS_OUTPUT.PUT_LINE('No invalid objects found.');
  END IF;
END;
/

 


 


AUIFENNW
Do Gooder (Customer)
Forum|alt.badge.img+3
  • Do Gooder (Customer)
  • 8 replies
  • February 3, 2025

Hi,

we encountered this issue as well.

Apart from the described fix, does anybody know what might be the reason for this? Has this already been analyzed from IFS?

 

Thank you!

Wolfgang


Curious_User
Sidekick (Customer)
Forum|alt.badge.img+8

@AUIFENNW ,

 

I was told a while back that this was supposed to be permanently resolved in the Newest UPD for IFS Apps 10. 


Abises Weerasekera
Do Gooder (Employee)
Forum|alt.badge.img+5

Hi ​@Curious_User , ​@AUIFENNW 

 

Yes, we reported this issue to our RnD and IFS Fixed Version is APP10UPD27. Modified the code to handle the RULE SET type invalids.
 

Thank you & Regards,

Abises Weerasekera


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings