10 Replies Latest reply on May 14, 2015 6:31 PM by 2846585

    concurrent manager inactive after upgrade from R12.0.4 to R12.1.3

    Williams Oluwafemi

      hi all,

       

      can anyone please help on this issue, after upgrading from R12.0.4 to R12.1.3 concurrent manager became inactive, what could be the problem what is the solution? please.

       

      thanks.

        • 1. Re: concurrent manager inactive after upgrade from R12.0.4 to R12.1.3
          Bashar.

          Hi,

           

          Check the internal manager's log for any errors.

           

          Regards,

          Bashar

          • 2. Re: concurrent manager inactive after upgrade from R12.0.4 to R12.1.3
            Williams Oluwafemi

            this is a screen shot for more details thanks.

             

            concurrent.PNG

            • 3. Re: concurrent manager inactive after upgrade from R12.0.4 to R12.1.3
              Bashar.

              Hi,

               

              1. Go to the system administrator responsibility.
              2. Go to Concurrent -> Manager -> Administer.
              3. Click on Processes button.
              4. Click on view log
              5. Save the output as a text file and upload it.

               

              Regards,

              Bashar

              • 4. Re: concurrent manager inactive after upgrade from R12.0.4 to R12.1.3
                Williams Oluwafemi

                Bashar thanks, would have love to do what you asked but all the solution i have been doing is from the back end. i havent been able to launch forms, downloaded the j2se but wouldnt work and my users have been waiting for my solution. i would really appreciate if you can tell me what to do

                 

                thanks.

                • 5. Re: concurrent manager inactive after upgrade from R12.0.4 to R12.1.3
                  Williams Oluwafemi

                  @Bashar

                  thanks, would have love to do what you asked but all the solution i have been doing is from the back end. i havent been able to launch forms, downloaded the j2se but wouldnt work and my users have been waiting for my solution. i would really appreciate if you can tell me what to do

                   

                  thanks.

                  • 6. Re: concurrent manager inactive after upgrade from R12.0.4 to R12.1.3
                    ;) ApPsMasTi ;)

                    Relink the FND binary FNDLIBR :

                     

                    Use adadmin and relink the FND module

                     

                    bounce EBS

                     

                    Stop all middle tier services including the concurrent managers.

                    Please make sure that no FNDLIBR, FNDSM, or any dead process is running !!!

                    Check the last CP process to exit/terminate, the Internal Manager, with the Unix command: ps -ef | grep FNDLIBR

                     

                     

                    1)stop application tier

                    2)Stop the database and start it.

                    3)start application tier

                     

                    ApPsMaStI

                    sharing is Caring

                    • 7. Re: concurrent manager inactive after upgrade from R12.0.4 to R12.1.3
                      Bashar.

                      Hi,

                       

                      Execute the following command to get the name of the most recent log file. Open the file and review the errors at the end.

                      If you could not find anything, upload the file.

                       

                      ls -lrt $APPLCSF/log/<SID>*.mgr |tail -1

                       

                      Substitute <SID> with your system SID.

                       

                      Regards,

                      Bashar

                      • 8. Re: concurrent manager inactive after upgrade from R12.0.4 to R12.1.3
                        Williams Oluwafemi

                        @Bashar

                        thank you, here is the content of the later part of the file, i hope its not too much imformation.

                         

                        Check that your system has enough resources to start a concurrent manager process. Contact your system : 13-MAY-2015 14:07:14

                        Starting STANDARD Concurrent Manager               : 13-MAY-2015 14:07:14

                         

                         

                        CONC-SM TNS FAIL

                        Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /d03/oracle/TRAIN/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.

                         

                         

                        Check that your system has enough resources to start a concurrent manager process. Contact your system : 13-MAY-2015 14:07:14

                        Routine AFPEIM encountered an error while starting concurrent manager OAMCOLMGR.

                        The manager is not able to start properly. 

                        The manager has been put on a SYSTEM HOLD to allow the system administrator to address the issue. 

                        When addressed, the "Fixed" button on the Administer Managers screen can be pressed to restart the manager.

                         

                         

                        Starting OAMCOLMGR Concurrent Manager              : 13-MAY-2015 14:07:14

                         

                         

                        CONC-SM TNS FAIL

                        Routine AFPEIM encountered an error while starting concurrent manager OAMCOLMGR with library /d03/oracle/TRAIN/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.

                         

                         

                        Check that your system has enough resources to start a concurrent manager process. Contact your syste : 13-MAY-2015 14:07:19

                        Routine AFPEIM encountered an error while starting concurrent manager WMSTAMGR.

                        The manager is not able to start properly. 

                        The manager has been put on a SYSTEM HOLD to allow the system administrator to address the issue. 

                        When addressed, the "Fixed" button on the Administer Managers screen can be pressed to restart the manager.

                         

                         

                        Starting WMSTAMGR Concurrent Manager               : 13-MAY-2015 14:07:19

                         

                         

                        CONC-SM TNS FAIL

                        Routine AFPEIM encountered an error while starting concurrent manager WMSTAMGR with library /d03/oracle/TRAIN/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.

                         

                         

                        Check that your system has enough resources to start a concurrent manager process. Contact your system : 13-MAY-2015 14:07:19

                        Routine AFPEIM encountered an error while starting concurrent manager AMSDMIN.

                        The manager is not able to start properly. 

                        The manager has been put on a SYSTEM HOLD to allow the system administrator to address the issue. 

                        When addressed, the "Fixed" button on the Administer Managers screen can be pressed to restart the manager.

                         

                         

                        Starting AMSDMIN Concurrent Manager                : 13-MAY-2015 14:07:19

                         

                         

                        CONC-SM TNS FAIL

                        Routine AFPEIM encountered an error while starting concurrent manager AMSDMIN with library /d03/oracle/TRAIN/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.

                         

                         

                        Check that your system has enough resources to start a concurrent manager process. Contact your system  : 13-MAY-2015 14:07:19

                         

                         

                        Starting Internal Concurrent Manager Concurrent Manager : 13-MAY-2015 14:07:19

                        CONC-SM TNS FAIL

                        : ICM failed to start for target EBSAPPS.  Review ICM log files for additional information.

                                             Process monitor session ended : 13-MAY-2015 14:07:19

                         

                         

                                           Process monitor session started : 13-MAY-2015 14:09:19

                        CONC-SM TNS FAIL

                        Call to PingProcess failed for FNDCPGSC

                        CONC-SM TNS FAIL

                        Call to StopProcess failed for FNDCPGSC

                        CONC-SM TNS FAIL

                        Call to PingProcess failed for FNDOPP

                        CONC-SM TNS FAIL

                        Call to StopProcess failed for FNDOPP

                        CONC-SM TNS FAIL

                        Call to PingProcess failed for FNDOPP

                        CONC-SM TNS FAIL

                        Call to StopProcess failed for FNDOPP

                        CONC-SM TNS FAIL

                        Call to PingProcess failed for FNDOPP

                        CONC-SM TNS FAIL

                        Call to StopProcess failed for FNDOPP

                        CONC-SM TNS FAIL

                        Call to PingProcess failed for FNDOPP

                        CONC-SM TNS FAIL

                        Call to StopProcess failed for FNDOPP

                        CONC-SM TNS FAIL

                        Call to PingProcess failed for FNDOPP

                        CONC-SM TNS FAIL

                        Call to StopProcess failed for FNDOPP

                         

                         

                         

                         

                        Starting Internal Concurrent Manager Concurrent Manager : 13-MAY-2015 14:09:21

                        CONC-SM TNS FAIL

                        : ICM failed to start for target EBSAPPS.  Review ICM log files for additional information.

                                             Process monitor session ended : 13-MAY-2015 14:09:21

                        • 9. Re: concurrent manager inactive after upgrade from R12.0.4 to R12.1.3
                          ;) ApPsMasTi ;)

                          please see

                           

                          Manager Status Shows System Hold, Fix Manager before resetting counters (Doc ID 1507580.1)

                           

                           

                          ApPsMaStI

                          sharing is Caring

                          • 10. Re: concurrent manager inactive after upgrade from R12.0.4 to R12.1.3
                            2846585

                            Follow the document id: 1312632.1

                             

                            Regards

                            Arizuddin