6 Replies Latest reply: Oct 20, 2014 4:22 AM by Thiagarajan -Oracle RSS

    Conflict Resolution Manager R12.2

    sober_sandy

      Dear Experts,

       

      I've installed R12.2 on Windows Server 2008.

      All the concurrent managers are up except Conflict Resolution Manager (CRM).

      Its showing Actual - 0 and Target -1.

       

      I've tried sh adrelink.sh force=y "fnd fndcrm"

      but its still not getting up.

       

      Regards,

      Sandeep

        • 1. Re: Conflict Resolution Manager R12.2
          Thiagarajan -Oracle

          Hi Sandeep,

           

          Please upload the CRM Manager log as well as ICM and Service Manager logs for review.

           

          Regards,

          Thiagarajan.

          • 2. Re: Conflict Resolution Manager R12.2
            sober_sandy

            Dear Thiagarajan,

             

            I've new to the R12.2 installation. Could you pls tell me where to find these logs.

             

             

            Thanks a lot !!

            Sandeep

            • 3. Re: Conflict Resolution Manager R12.2
              sober_sandy

              Any body who can help me on this ?

              • 4. Re: Conflict Resolution Manager R12.2
                Thiagarajan -Oracle

                Hi Sandeep,

                 

                You can get the Manager logs via Front end only. Navigate to System Administrator > Concurrent > Manager > Administer > Click on respective manager > Click on Processes button > You will have 2 buttons

                 

                Click on 'Internal Manager Log' button to get the ICM log.

                Click on 'Manager Log' to get the respective manager log.

                 

                Else, You can get the logs from back from your $APPLCSF/$APPLLOG directory the manager logs will be ending with .mgr.

                 

                Regards,

                Thiagarajan.

                • 5. Re: Conflict Resolution Manager R12.2
                  sober_sandy

                  Hi Thiagarajan,

                   

                  Thanks for your help.

                   

                  In Administer Concurrent Managers Window after selecting Conflict Resolution Manager, when I clicked on Processes button, there are 3 processes running with Status Initializing. Following is the Internal Manager Log (IML) of it.

                   

                  ==================================================================================================================

                   

                   

                   

                   

                  Found dead process: spid=(6108:6008), cpid=(2729317), ORA pid=(33), manager=(0/1)

                   

                   

                  +---------------------------------------------------------------------------+

                  Application Object Library: Concurrent Processing version 11.5

                   

                  Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.

                   

                  Internal Concurrent Manager started : 01-JUL-2014 19:08:15

                   

                  +---------------------------------------------------------------------------+

                   

                                     Process monitor session started : 01-JUL-2014 19:08:17

                   

                   

                  Starting RCVOLTM14 Concurrent Manager              : 01-JUL-2014 19:08:18

                   

                   

                  Starting CRPINQMGR Concurrent Manager              : 01-JUL-2014 19:08:20

                   

                   

                  Starting INVTMRPM Concurrent Manager               : 01-JUL-2014 19:08:20

                   

                   

                  Starting RCVOLTM Concurrent Manager                : 01-JUL-2014 19:08:20

                   

                   

                  Starting PODAMGR Concurrent Manager                : 01-JUL-2014 19:08:20

                   

                   

                  Starting FFTM Concurrent Manager                   : 01-JUL-2014 19:08:20

                   

                   

                  Starting FNDCPOPP Concurrent Manager               : 01-JUL-2014 19:08:21

                   

                   

                  Starting DownloadProcessorNormalMode Concurrent Manager : 01-JUL-2014 19:08:30

                   

                   

                  Starting WFWSSVC Concurrent Manager                : 01-JUL-2014 19:08:30

                   

                   

                  Starting WFALSNRSVC Concurrent Manager             : 01-JUL-2014 19:08:31

                   

                   

                  Starting WFMLRSVC Concurrent Manager               : 01-JUL-2014 19:08:31

                   

                   

                  Starting FNDCRM Concurrent Manager                 : 01-JUL-2014 19:08:32

                   

                  Internal manager failed to spawn manager process : usdsop cannot create a new process

                   

                  Cause: usdsop encountered an error creating a new process. [Reason].

                   

                  Action: Check that your system had enough resources to start a new process. Contact your system administrator to obtain more resou (RE

                  An error occured in client-side routine afpsmcsm for Service Manager FNDSM_KHURANA_VIS.  The routine returned code 1.

                   

                  Check for preceding errors and as well as the service manager log file for further details."

                   

                  Routine AFPEIM encountered an error while starting concurrent manager FNDCRM with library C:\oracle\VIS\fs1\EBSapps\appl\fnd\12.0.0\bin\FNDCRM.

                   

                  Check that your system has enough resources to start a concurrent manager process. Contact your system adminis : 01-JUL-2014 19:08:32

                   

                  Starting STANDARD Concurrent Manager               : 01-JUL-2014 19:08:32

                  Starting STANDARD Concurrent Manager               : 01-JUL-2014 19:08:33

                  Starting STANDARD Concurrent Manager               : 01-JUL-2014 19:08:33

                   

                   

                  Starting OAMCOLMGR Concurrent Manager              : 01-JUL-2014 19:08:33

                   

                   

                  Starting MRPMGR Concurrent Manager                 : 01-JUL-2014 19:08:33

                   

                   

                  Starting INVMGR Concurrent Manager                 : 01-JUL-2014 19:08:34

                   

                   

                  Starting PASMGR Concurrent Manager                 : 01-JUL-2014 19:08:34

                   

                                       Process monitor session ended : 01-JUL-2014 19:08:34

                   

                                     Process monitor session started : 01-JUL-2014 19:28:35

                  Found dead process: spid=(4932), cpid=(2729330), Service Instance=(1095)

                  Found dead process: spid=(4848), cpid=(2729331), Service Instance=(1096)

                  Found dead process: spid=(6132), cpid=(2729329), Service Instance=(1134)

                  Found dead process: spid=(1852), cpid=(2729327), Service Instance=(2158)

                  Found dead process: spid=(4236), cpid=(2729328), Service Instance=(31528)

                   

                   

                  Starting WFMLRSVC Concurrent Manager               : 01-JUL-2014 19:28:37

                   

                   

                  Starting WFALSNRSVC Concurrent Manager             : 01-JUL-2014 19:28:37

                   

                   

                  Starting DownloadProcessorNormalMode Concurrent Manager : 01-JUL-2014 19:28:37

                   

                   

                  Starting WFWSSVC Concurrent Manager                : 01-JUL-2014 19:28:38

                   

                   

                  Starting FNDCPOPP Concurrent Manager               : 01-JUL-2014 19:28:38

                   

                   

                  Starting FNDCRM Concurrent Manager                 : 01-JUL-2014 19:28:38

                   

                  Internal manager failed to spawn manager process : usdsop cannot create a new process

                   

                  Cause: usdsop encountered an error creating a new process. [Reason].

                   

                  Action: Check that your system had enough resources to start a new process. Contact your system administrator to obtain more resou (RE

                  An error occured in client-side routine afpsmcsm for Service Manager FNDSM_KHURANA_VIS.  The routine returned code 1.

                   

                  Check for preceding errors and as well as the service manager log file for further details."

                   

                  Routine AFPEIM encountered an error while starting concurrent manager FNDCRM with library C:\oracle\VIS\fs1\EBSapps\appl\fnd\12.0.0\bin\FNDCRM.

                   

                  Check that your system has enough resources to start a concurrent manager process. Contact your system adminis : 01-JUL-2014 19:28:38

                                       Process monitor session ended : 01-JUL-2014 19:28:38

                   

                  ==================================================================================================================

                   

                  When I clicked on Manager Log. An error says "No log file exists for process 2729196"

                   

                   

                  Sandeep

                  • 6. Re: Conflict Resolution Manager R12.2
                    Thiagarajan -Oracle

                    Hi Sandeep,

                     

                    It seems that the issue is caused due to lack of resources on your EBS CP Node.

                     

                    The error message "Check that your system has enough resources to start a concurrent manager process" clearly says that.

                     

                    Request you to check your OS resource usage like CPU and Memory and parameters like Processes etc. and make sure that there are enough resources available on Server before starting the EBS Services.

                     

                    Regards,

                    Thiagarajan.

                     

                    Please mark any update as "Correct Answer" or "Helpful Answer" if that update helps/answers your question, so that others can identify the Correct/helpful update between many updates.