1 2 3 Previous Next 42 Replies Latest reply on Jun 23, 2017 10:33 AM by Beauty_and_dBest Go to original post
      • 30. Re: Inactive No Manager
        Beauty_and_dBest

        But the other instance 12.1.3 which is running good, when I changed the timezone, it got the same error now

         

        Please help...

         

        Kind regards,

        • 31. Re: Inactive No Manager
          Beauty_and_dBest

          Hi ALL,

           

          The error now seem related to the hostname  more that 30 characters?

           

          10.106.140.34   a6dd6a.compute-a467305.oraclecloud.internal     a6dd6a

           

          Why is that my other 12.1.3 instance was good before I changed the timezone?

           

           

          Please help....

           

          Kind regards,

          • 32. Re: Inactive No Manager
            Kanda-Oracle

             

            • 33. Re: Inactive No Manager
              Kanda-Oracle
              type 'uname -n' from the Unix prompt 
              • 34. Re: Inactive No Manager
                Kanda-Oracle

                Hi ,

                 

                To resolve refer the below document (workaround is given under the section 2.7.2 )!

                 

                 

                Oracle E-Business Suite Technology Stack Release Notes for Release 12.1.3 (Doc ID 1098650.1)

                 

                 

                2.7.2 Host Name Length Restrictions

                 

                Hope this resolves!

                 

                Thanks


                N Kandasamy

                • 35. Re: Inactive No Manager
                  Beauty_and_dBest

                  Thanks Kanda and ALL,

                   

                  I now shorten the hostname to> a6dd6a.oraclecloud.com

                  Then I do the following:

                  1. Stop all middle tier services including the concurrent managers.

                  2. Bounce the DB

                  3. Perform the FND_CONC_CLONE.SETUP_CLEAN

                   

                  % sqlplus apps/<apps_password>

                  SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;

                  SQL> COMMIT;

                  SQL> EXIT;

                   

                  4. Run AutoConfig on all tier nodes. First on the DB tier then the APPS tiers to repopulate the

                  required system tables.

                  5. Run cmclean.sql

                  6. Restart all services/concurrent managers

                  7. Retest the issue.

                   

                   

                   

                  but still No Manager persist. But the error in iCM log was changed.

                   

                   

                  I have two(2) EBS R12.1.3 instances, the other one is working and the other one is not.

                   

                  This is the iCM log for the working instance:

                  Found dead process: spid=(12716), cpid=(2072813), Service Instance=(31528)

                  CONC-SM TNS FAIL

                  Call to PingProcess failed for IEMDPDEV

                  CONC-SM TNS FAIL

                  Call to StopProcess failed for IEMDPDEV

                  CONC-SM TNS FAIL

                  Call to PingProcess failed for IEMDPDEV

                  CONC-SM TNS FAIL

                  Call to StopProcess failed for IEMDPDEV

                  CONC-SM TNS FAIL

                  Call to PingProcess failed for IEMDPDEV

                  CONC-SM TNS FAIL

                  Call to StopProcess failed for IEMDPDEV

                  Starting FFTM Concurrent Manager                   : 23-JUN-2017 14:48:29

                  Starting RCVOLTM Concurrent Manager                : 23-JUN-2017 14:48:29

                  Starting RCVOLTM14 Concurrent Manager              : 23-JUN-2017 14:48:29

                   

                   

                  And this is the iCM log for the Instance which has No Manager.

                                     Process monitor session started : 23-JUN-2017 14:46:37

                                     Process monitor session ended : 23-JUN-2017 14:46:37

                                     Process monitor session started : 23-JUN-2017 14:48:37

                                     Process monitor session ended : 23-JUN-2017 14:48:38

                                     Process monitor session started : 23-JUN-2017 14:50:38

                                     Process monitor session ended : 23-JUN-2017 14:50:38

                                     Process monitor session started : 23-JUN-2017 14:52:38

                                     Process monitor session ended : 23-JUN-2017 14:52:38

                   

                   

                  Please help....

                  • 36. Re: Inactive No Manager
                    Kanda-Oracle

                    Please check the Manager availability from the front-end..

                    Sysadmin > Concurrent > Manager > Administer Screen

                    • 37. Re: Inactive No Manager
                      Beauty_and_dBest

                      Hi Kanda,

                       

                      I have been pointing out eversince that my issue is > no manager and this screen has been posted at the start of the page

                      You may need a good spanking

                      Capture.PNG

                      • 38. Re: Inactive No Manager
                        Kanda-Oracle

                        Just check out Service Manager is up and running. Ensure workshift is defined.

                          Concurrent > Manager > Define > Service Manager > workshift

                        • 39. Re: Inactive No Manager
                          Kanda-Oracle

                          also Check whether the Apps Listener is up and running. ; adalnctl.sh status

                          • 40. Re: Inactive No Manager
                            mdtaylor

                            Hi jc,

                             

                            If I read this right, even your working cloud instance is not starting GSM enabled managers. Please see if the listener.ora and tnanames.ora in 10.1.2 $TNS_ADMIN have the new hostnames and you can tnsping the FNDFS and FNDSM aliases.

                             

                            Regards,

                            Michael

                            • 41. Re: Inactive No Manager
                              Beauty_and_dBest

                              Issue resolved

                               

                              I compared the two output of two EBS R12.1.3  > select CONCURRENT_QUEUE_NAME,CONTROL_CODE,TARGET_NODE,NODE_NAME from FND_CONCURRENT_QUEUES

                               

                              On the correct one, followed update the wrong values of the affected instance.

                               

                              Sample updates: Similar given by Michael

                               

                              update fnd_concurrent_queues set target_node = NULL where target_node = 'ERP';

                              update fnd_concurrent_queues set target_node = 'A6DD6A' where target_node = 'A6DD6A.ORACLECLOUD.COM';

                              update fnd_concurrent_queues set node_name = NULL where node_name = 'ERP';

                              update fnd_concurrent_queues set control_code = NULL where control_code <> 'E';

                              update fnd_concurrent_queues set control_code = 'E' where CONCURRENT_QUEUE_NAME IN ('FNDTMTST','WFMGSMD','WFMGSMS','Debug_Service');

                              update fnd_concurrent_queues set control_code = NULL where target_node = 'A6DD6A' and CONCURRENT_QUEUE_NAME not like 'FNDIM%';

                               

                              Kind regards,

                              • 42. Re: Inactive No Manager
                                Beauty_and_dBest

                                Hi Micheal,

                                 

                                The working instance got affected by the long hostaname (more than 30+ chars).

                                Actual it was able to bypass it until I changed the timezone, it was the time it noticed that hostname is very long.

                                So I shortened my hostname. And then fix the invalid node_name carried from old server.

                                 

                                And now its all okay

                                 

                                Thank you all very very much !!!!!

                                1 2 3 Previous Next