3 Replies Latest reply on Mar 14, 2012 10:42 AM by Alee

    Data Forms: Error detected while attempting to run job

    Alee
      Hi Team Members,

      I am experiencing Issue while opening a Data Form *"Error detected while attempting to run job: 5.1_XXX_Rev_Mig"*

      Reference:
      1: "5.1_XXX_Rev_Mig" is a Business Rule Name.
      2: Business rule is validating successfully.
      3: Data Form is working fine without above rule attached at level "run/execute on Load".
      4: Data Form is working fine with above rule attached at level "run/execute on Save".

      I created above rule via calculation manager and attach to Data form execute on Load & Execute on Save, it was working fine
      but as we start creating more forms with same option due to requirements. 1 day above mentioned error just pop-up.

      Note:* Data Form is good to proceed after load (showing above mentioned error at top) its accepting data, saving it but not executing
      the business rule when hit save. When rule is D-attached from form at level "execute on load"_ & refresh
      the form error is gone means something is with attaching the Business Rule at level "run/execute on Load".

      I think i am looking at some kind of performance issue WRT data forms loading thing...

      please share your views & possible area to look for.

      Regards,
      Alee
        • 1. Re: Data Forms: Error detected while attempting to run job
          JG_Gone
          Have you checked the planning logs and the essbase application log to look for more information at the tim4e of the error.

          Cheers

          John
          http://john-goodwin.blogspot.com/
          1 person found this helpful
          • 2. Re: Data Forms: Error detected while attempting to run job
            912065
            This error usually occurs when there are few resources to execute business, to check this go to:

            Tools --> Job Console
            and check the status of business rule that runs on form load if the business rule failed to execute then check the reason if it states something about block size then the error is due to lack of resources and in such case you have to make performance tunning of your application.
            1 person found this helpful
            • 3. Re: Data Forms: Error detected while attempting to run job
              Alee
              Hi team members,

              thanks for your support, issue is solved after reviewing the below logs and consulting some manuals & yes application needs some performance tuning at Essbase level.
              please find below the logs and workout.

              Note:_ workout is for a basic level application, please change the setting as per your application needs.

              Planning Logs:_

              FATAL calcmgr.launch - Date/Time Ended:     2012/03/08:11:05:24.561 AFT     Server/Application/Database:     localhost/Rev/Plan1     Business Rule Name:     5.1_XXX_Rev_Mig     By Planning user:     admin.Exception:     com.hyperion.planning.InvalidCalcException: An error occurred while running the specified calc script. Check the log for details.


              Essbase Log for Respective Application:_

              [Tue Mar 13 15:14:09 2012]Local/Revenue/Plan1/admin@Native Directory/489/Error(1012700)
              Dynamic calc processor cannot allocate more than [38] blocks from the heap. Please increase CalcLockBlock setting and then retry

              [Tue Mar 13 15:14:09 2012]Local/Revenue/Plan1/admin@Native Directory/489/Error(1200467)
              Error executing formula for [Subscriber]: status code [1012700] in function [@_VAL]

              [Tue Mar 13 15:14:09 2012]Local/Revenue/Plan1/admin@Native Directory/489/Warning(1080014)
              Transaction [ 0x3c30001( 0x4f5f24f9.0x6d081 ) ] aborted due to status [1012700].

              [Tue Mar 13 15:14:09 2012]Local/Revenue/Plan1/admin@Native Directory/489/Info(1012550)
              Total Calc Elapsed Time : [0.03] seconds

              Essbase Error Message:_

              Error#1012700
              Reason: Dynamic calc processor cannot allocate more than number blocks from the heap. Please increase CalcLockBlock setting and then retry

              Workout:_

              Increase the number of blocks that Essbase can allocate for a calculation:
              1.Set the maximum number of blocks that Essbase can allocate to at least 500:
              a.If ESSBASEPATH/bin/ essbase.cfg does not exist on the server computer, create one using a text editor.
              b.In the essbase.cfg file on the server computer, set CALCLOCKBLOCKHIGH to 500.
              c.Stop and restart Essbase Server.

              2.Add the SET LOCKBLOCK HIGH command to the beginning of the calculation script.
              3.Set the data cache large enough to hold all blocks specified in the CALCLOCKBLOCKHIGH setting.

              •Determine the block size.
              •Set the data cache size.


              Regards,
              Alee