4 Replies Latest reply on Dec 5, 2018 9:12 AM by 3032819

    emsg:was terminated by signal 11

    3032819

      RDF report in Oracle R12 is getting error out with below error message for specific value of parameters.

       

      stat_low = B

      stat_high = 0

      emsg:was terminated by signal 11

        • 1. Re: emsg:was terminated by signal 11
          Kanda-Oracle

          Hi,

           

          Can you provide more details.

           

          1. Only one report (or) all the reports are failing ?

          2. Is the report failing consistently (or) randomly ?

          2.1 To isolate , if the data volume is the cause, can you run the report with less volume of day (for example for 2 days; instead of a year)

          3. Please check ulimit setting in the server where concurrent manager is running.

          ulimit -a

           

          Thanks

          N Kandasamy

          • 2. Re: emsg:was terminated by signal 11
            Kanda-Oracle

            Hi,

             

              Please check reports.log located under $APPLCSF/$APPLLOG has reached the maximum file size  Refer to Note 844976.1 for more details.

             

            Thanks!

            • 3. Re: emsg:was terminated by signal 11
              Kanda-Oracle

              Hi

               

              signal 11 ; Please check does it generate CORE file anywhere in the $APPL_TOP,  $ADMIN_SCRIPTS_HOME , $APPLCSF/$APPLLOG ,  $APPLCSF/$APPLOUT

               

              Thanks

              • 4. Re: emsg:was terminated by signal 11
                3032819

                Hi Kanda,

                 

                Thank you for the suggestions, I will explore these options.

                 

                1. Only one report (or) all the reports are failing ?

                --> Only one custom report is failing and when output format is excel, its working fine for output as PDF

                2. Is the report failing consistently (or) randomly ?

                --> randomly and when output format is excel

                2.1 To isolate , if the data volume is the cause, can you run the report with less volume of day (for example for 2 days; instead of a year)

                --> There is option to run it with date parameter

                3. Please check ulimit setting in the server where concurrent manager is running.

                --> I will check this one