3 Replies Latest reply on May 11, 2018 6:15 PM by JohnGoodwin

    EPMA service is taking more time to start

    3532261

      Hi All,

       

      We are using 11.1.2.4 Hyperion and our EPMA server installed in windows VM. All of the sudden when we restart the EPMA service it is taking around 35 min to start after modifying BPMA_Server_Config file. we have applied regular PSU patches on the database in all the environments at the same time but only this environment is causing the problem.

       

      When we looked in to the dimensionserverstartup logs the service is consuming more time at the step " Loading Master Library" .

       

      [2018-05-09T04:18:40.178-04:00] [Debug] Loading Master Library...

      [2018-05-09T04:39:36.213-04:00] [Debug] Processing System Metadata file...

       

      Please let me know your thoughts why this step taking more time... or what exactly is happening at this step.

       

      Thanks,

      Rajesh

        • 1. Re: EPMA service is taking more time to start
          JohnGoodwin

          Have you had a look to  see if purging transaction history helps with performance - Purging Transaction History

           

          Cheers

           

          John

          • 2. Re: EPMA service is taking more time to start
            3532261

            We are also thinking of the same.. but the database is of very less size and complete backup of the database itself is not taking 15 min.

             

            Do you know what these transactions are? why would it cause delay in startup?

             

            Appreciate your help on understanding this step.

             

            Thanks,

            Rajesh

            • 3. Re: EPMA service is taking more time to start
              JohnGoodwin

              3532261 wrote:

               

              Do you know what these transactions are?

              From the link I provided - "Performance Management Architect creates transactions in the Performance Management Architect database. This database is automatically created during installation and configuration. Since Performance Management Architect does not delete these artifacts, the database size can increase over time. The Performance Management Architect Transaction History Purge Utility enables you to remove transactions from the database to reduce database size."

               

              Whether this helps your situation I can't say but it is worth investigating.

              You also say that EPMA is installed on a VM, have you checked with the team that manages the VM infrastructure to see whether there is any resource connection that be causing severe performance degradation.