1 2 Previous Next 16 Replies Latest reply: Nov 4, 2013 6:48 PM by SreekumarHariharan RSS

    Unable to create new Essbase app in a MSCS envi

    RamyaS

      We are unable to create Essbase apps on Prod. We are using Microsoft Clustering for Essbase failover. Every time we try to create an app, essbase crashes giving out a .xcp file.

        • 1. Re: Unable to create new Essbase app in a MSCS envi
          955124

          Need more information on this . Did you try to check the .xcp file ? What does the log in EAS say ?

          • 2. Re: Unable to create new Essbase app in a MSCS envi
            RamyaS

            The XCP file has the below

             

            ----- Exception Error Log Begin -----

             

             

            Current Date & Time:   Mon Sep 16 13:17:45 2013

            Process Type:          Server

            Application Name:     

            Database Name:        

            Exception Log File:    C:\Oracle\Middleware\user_projects\epmsystem_148\diagnostics\logs\essbase\essbase_0\log00008.xcp

            Current Thread Id:     9440

            Exception Code:        0xC0000005=Access Violation

            Exception Flags:       0x00000000=Continuable

            Exception Address:     0x00000000614E3BC4

            Exception Parameters:  2

            Exception Parameter 0: 0x00000000=Read Violation

            Exception Parameter 1: 0x00000000 (Virtual Address)

             

             

            ----- Machine Registers -----

             

             

            General Registers:

               RAX=0x0000000000000000  RBX=0x0000000000000000  RCX=0xFFFFFFFFFFFFFFFF

               RDX=0x000000000000000C  RSI=0x0000000005B4A630  RDI=0x0000000000000000

               RBP=0x00000000614D9600  R08=0x530003430020000F  R09=0x5300034400240010

               R10=0x000000000000000C  R11=0x0000000005B4A630  R12=0x0000000000367CB0

               R13=0x000000002645D2D0  R14=0x0000000005ABEC18  R15=0x000000000DB769C0

             

             

            Control Registers:

               CS=0x0033  RIP=0x00000000614E3BC4  EFlg=0x00010246

            • 3. Re: Unable to create new Essbase app in a MSCS envi
              RamyaS

              The EAS log says

               

              [wuk-essbase-prd.ds.wolseley.com.YE13_Act]  Create application September 5, 2013 3:46:53 PM BST          Failed

              Error: 1042013 Network error [10054]: Cannot Receive Data

              Error: 1042012 Network error [10054]: Cannot Send Data

              • 4. Re: Unable to create new Essbase app in a MSCS envi
                955124

                Looks like a Database corruption . You said , you are not able to create application right !! But in Dev/QA are you able to do the same ? If so why dont you compare the settings between the two environments .

                 

                Usually this is a Corruption in db of an already existing app , but in your case App itself is in the mode of creation. Why dont you try and restart the services and Essbase server ?

                 

                Ramya : It is evident that the cube is not getting built in a right way . Can you please provide information about your cube architecture also . ASO or BSO settings etc .

                • 5. Re: Unable to create new Essbase app in a MSCS envi
                  RamyaS

                  The issue is only on Prod, other environments work fine but they do not have failover configured.

                   

                  The error is irrespective of application type, ASO/BSO, EPMA/Planning, through EAS or through MaxL.

                   

                  This issue has been there for a long time, I am getting involved now and investigating in detail.

                  • 6. Re: Unable to create new Essbase app in a MSCS envi
                    955124

                    Ok , so can you go to the APS as well as Essbase server . In APS check if all the services are Up and Running.

                    In Essbase server look at the EAS logs in the Diagnostics. This will give you some decent information about the Deployment Failure.

                    • 7. Re: Unable to create new Essbase app in a MSCS envi
                      SreekumarHariharan

                      Its appear that Your essbase cube got corrupted.Raise sr with oracle .Might be an patch needs to be applied.

                       

                       

                      In your log file you got two network related issues

                       

                       

                      A)1042012 Network error message: Cannot Send Data,B)1042013 Network error message: Cannot Receive Data

                       

                       

                      Possible Solutions:Increase the values for NETDELAY and NETRETRYCOUNT in your essbase.cfg and restart the essbase server

                      Do make sure that your essbase server is running after making the changes

                       

                       

                       

                       

                       

                       

                      Thanks,

                      Sreekumar Hariharan

                      • 8. Re: Unable to create new Essbase app in a MSCS envi
                        RamyaS

                        Thanks for the suggestions,

                        Apparently, the network error is a result of the crash not the cause

                        Yes, have raised an SR, wondered if anyone else had encountered this issue before

                        Restarting services does not resolve it

                        • 9. Re: Unable to create new Essbase app in a MSCS envi
                          955124

                          What is the status of EAS service in APS server ?

                          • 10. Re: Unable to create new Essbase app in a MSCS envi
                            RamyaS

                            Not sure I understand your question I am afraid, EAS service is not impacted.

                             

                            As far as APS is concerned, that is certainly not impacted either.

                            • 11. Re: Unable to create new Essbase app in a MSCS envi
                              955124

                              Ok . Lets start from scratch . You have teh Node for Administration Sever ,Correct which si mentioned Properly ? That IS APS

                               

                              Next lest go to the Essbase Server node , that is also mentioned correctly right ?

                               

                              So when you drill down Essbase server you will see Test Apps when no App has been created . From there you are trying to create New App , correct ? Is it ASO or BSO ?

                              • 12. Re: Unable to create new Essbase app in a MSCS envi
                                RamyaS

                                I should have mentioned this before. It is an Active/Passive configuration, so node 2 comes up only in a failover scenario.

                                 

                                Only Essbase is active/passive and that does not include EAS and APS .

                                 

                                So you connect to the cluster ( with only node 1 active) and create an application and that causes essbase to crash.

                                • 13. Re: Unable to create new Essbase app in a MSCS envi
                                  955124

                                  I have a feeling that the server where you are trying to create App may be Passive for some reason and causing the Crash .  I am just making few guesses here.

                                  Is it possible that you make  Active - Active and try creating the Application and later make one of the Essbase server passive.

                                  • 14. Re: Unable to create new Essbase app in a MSCS envi
                                    RamyaS

                                    Are you suggesting that the application is trying to get created on the passive node and hence it is failing. Possible, but still wondering why would that cause the active node to crash.

                                    1 2 Previous Next