6 Replies Latest reply on May 26, 2017 4:05 PM by mdtaylor

    CM not active after running cmclean.sql

    Beauty_and_dBest

      Hi ALL,

       

      EBS R12.13

      OL5

      .

      We have been running cmclean everytime we refresh our instance weekly. It is a part of the refresh script.

      But today our CM in not active after we bounce refresh the apps and database plus the cmclean

      Below is the log.

      Capture.PNG

      Capture2.PNG

      Capture3.PNG

      Capture4.PNG

       

      Please help...

       

       

      Kind regards,

      jc

        • 1. Re: CM not active after running cmclean.sql
          mdtaylor

          Hi jc,

           

          Did you execute rapid clone or autoconfig as part of your refresh?  Did you execute fnd_conc_clone.setuo_clean?  You should execute that then run autoconfig on dbTier and appTier.  If it still fails to start, execute the concurrent manager recovery wizard in Oracle Applications Manager.

           

          What do you see when you run adcmctl.sh start apps/apps_pw?

           

          Please click on Internal Manager, Processes, then Internal Manager Log for the most recent log.

           

          Please type:

           

          tail -50 $INST_TOP/logs/appl/admin/log/adcmctl.txt

           

          Regards,

          Michael

          • 2. Re: CM not active after running cmclean.sql
            Kanda-Oracle

            Hi,

             

            Need to check the log file of the Internal Concurrent Manager to determine whey the managers are not coming up.

             

            Thanks!

             

            N Kandasamy

            • 3. Re: CM not active after running cmclean.sql
              Beauty_and_dBest

              Thank Michael and Kanda,

               

               

              What is the format name of the internal manager log?

              It is the the one listed below?

              Capture.GIF

              Is it okay to delete all the xml file in alert folder > /fin_db/DEV2/db/tech_st/11.1.0/admin/DEV2_oraproc/diag/tnslsnr/oraproc/dev2/alert?

              Capture4.GIF

               

              Kind regards,

              • 4. Re: CM not active after running cmclean.sql
                mdtaylor

                Hi jc,

                 

                The highlighted file should be the Internal Manager log from 5/25/17.

                 

                You can purge the alert files and I also recommend deleting files from $ORACLE_HOME/rdbms/audit as that folder can grow by tens of GB.

                 

                Regards,

                Michael

                • 5. Re: CM not active after running cmclean.sql
                  Beauty_and_dBest

                  Hi Michael,

                   

                  Re: What do you see when you run adcmctl.sh start apps/apps_pw?

                  Below is what we saw, at first in upper message, it says Internal Concurrent Manager is Active, but then at lower message it also says Internal Concurrent Manager is not Active at this time.

                  Capture3.GIF

                   

                  Re: Please click on Internal Manager, Processes, then Internal Manager Log for the most recent log.

                  It produces error: Internal Concurrent Manager is not Active

                  Capture5.GIF

                   

                   

                  Kind regards,

                  • 6. Re: CM not active after running cmclean.sql
                    mdtaylor

                    Hi jc,

                     

                    Since you have 0 target and actual processes, also check for FNDLIBR and FNDSM processes on the appTier.  If you have any kill -9 their PIDs.  If your apps password is apps, run adcmctl.sh start apps/apps.  Then check the Administer Manager form.  If they do not start, please post the contents of the Internal Manager log form either the filesystem and shown or the form from View Processes->Internal Manager Log as also described.

                     

                    I also recommend shutting down the applications with adstpall.sh, then relink fnd executables in adadmin, then restart the applications with adstrtal.sh and then see if the concurrent managers start.

                     

                    Regards,

                    Michael