3 Replies Latest reply: Nov 13, 2012 10:45 PM by 953987 RSS

    Background Engine is down

    953987
      Hi All,

      I am new to Apps DBA.

      We have EBS version 12.1.3 and it is running fine. But in workflow, Background Engine is down. Please help How I can start this.Pleas see the below values.


      Notification Mailers - Up
      Background Engines - Down
      Agent Listeners - Up
      Purge - Up
      Service Components - Up
      Control Queue Cleanup - Up


      Please let me know the reason for this and how this will affect the instance.


      Thanks,
      Sam
        • 1. Re: Background Engine is down
          Srini Chavali-Oracle
          Pl see this MOS Doc on how to schedule workflow background processes

          Recommended Schedule For Workflow Background Process For Order Management [ID 971925.1]

          HTH
          Srini
          • 2. Re: Background Engine is down
            Hussein Sawwan-Oracle
            We have EBS version 12.1.3 and it is running fine. But in workflow, Background Engine is down. Please help How I can start this.Pleas see the below values.


            Notification Mailers - Up
            Background Engines - Down
            Agent Listeners - Up
            Purge - Up
            Service Components - Up
            Control Queue Cleanup - Up


            Please let me know the reason for this and how this will affect the instance.
            Was this working before? If yes, any changes been done recently?

            Can you find any errors in the Workflow/Database log files?

            Please go through (Introductory Questions About Workflow Background Engine [ID 156187.1]). Also, please run the test in (12.0.6+: Oracle Workflow Cartridge (WF): Background Engine Setup Diagnostic Test [VIDEO] [ID 1174449.1]) and see if it returns any error/warning messages.

            Thanks,
            Hussein
            • 3. Re: Background Engine is down
              953987
              Thanks Hussein for the reply.

              I was on vacation and this issue resolved after creating a concurrent request for the same.


              Thanks,