10 Replies Latest reply: Nov 15, 2012 4:46 AM by user640494 RSS

    Essbase Crashes with 7506 code When Refreshing Planning Database

    user640494
      Hi All,

      When I do Planning refresh (after addition of sparse element), sometimes an Essbase crash occurs, with message:

      Assertion Failure - id=7506 condition='((( pDatCb->usFixCount == 0 )))'
      - line 9674 in file kernel/datbuffm.c
      - arguments [0] [0] [0] [0]

      What could be the reason of this behavior?

      Data cache size changed many times, but problem persists
        • 1. Re: Essbase Crashes with 7506 code When Refreshing Planning Database
          JohnGoodwin
          What does the essbase application log have in it at the time of the crash.

          Cheers

          John
          http://john-goodwin.blogspot.com/
          • 2. Re: Essbase Crashes with 7506 code When Refreshing Planning Database
            user640494
            Hi, John,

            Please see the log contents before crash:

            -----

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/2252/Info(1013091)+
            +Received Command [Restructure] from user [admin@Native Directory]+

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1002140)+
            Application Budget1 database Drxxxxxx has MaxTotalActiveTransactions=4 MaxActiveUpdateTransactions=4.

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1019017)+
            +Reading Parameters For Database [Drxxxxxx]+

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1019012)+
            +Reading Outline For Database [Drxxxxxx]+

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1019024)+
            +Reading Outline Transaction For Database [Drxxxxxx]+

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1007043)+
            Declared Dimension Sizes = [11 7 16 11 104 6 10 27 216 504 28 282 1432 1598 ]

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1007042)+
            Actual Dimension Sizes = [11 7 16 7 83 6 10 25 108 504 28 281 1403 1598 ]

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1007125)+
            The number of Dynamic Calc Non-Store Members = [0 0 0 4 10 0 0 2 0 0 0 0 6 0 ]

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1007126)+
            The number of Dynamic Calc Store Members = [0 0 0 0 0 0 0 0 0 0 0 0 0 0 ]

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1007127)+
            The logical block size is [6391]

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1010008)+
            Maximum Declared Blocks is [560839899180320690000] with data block size of [8008]

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1010007)+
            Maximum Actual Possible Blocks is [274937572361431220000] with data block size of [5621]

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1012710)+
            Essbase needs to retrieve [1] Essbase Kernel blocks in order to calculate the top dynamically-calculated block.

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1012736)+
            +The Dyn.Calc.Cache for database [Drxxxxxx] can hold a maximum of [407] blocks.+

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1012737)+
            +The Dyn.Calc.Cache for database [Drxxxxxx], when full, will result in [allocation from non-Dyn.Calc.Cache memory].+

            +[Wed Oct 31 17:05:15 2012]Local/Budget1/Plan/admin@Native Directory/9064/Info(1007044)+
            +Restructuring Database [Plan]+

            +[Wed Oct 31 17:05:15 2012]Local/Budget1///9064/Info(1008108)+
            Essbase Internal Logic Error [7506]

            +[Wed Oct 31 17:05:15 2012]Local/Budget1///9064/Info(1008106)+
            +Exception error log [D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\essbase\essbase\app\Budget1\log00001.xcp] is being created...+

            +[Wed Oct 31 17:05:16 2012]Local/Budget1///9064/Info(1008107)+
            Exception error log completed D:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\essbase\essbase\app\Budget1\log00001.xcp please contact technical support and provide them with this file

            +[Wed Oct 31 17:05:16 2012]Local/Budget1///9064/Info(1002089)+
            RECEIVED ABNORMAL SHUTDOWN COMMAND - APPLICATION TERMINATING

            -------
            • 3. Re: Essbase Crashes with 7506 code When Refreshing Planning Database
              user640494
              I forget to say about version: 11.1.2.2

              Essbase: 11.1.2.2.101 patch
              Planning 11.1.2.2.302 patch
              • 4. Re: Essbase Crashes with 7506 code When Refreshing Planning Database
                JohnGoodwin
                I take it you have read the following doc in Oracle Support - "Essbase Internal Logic Error [7506] When Restructuring Database. [ID 965942.1]"

                Cheers

                John
                http://john-goodwin.blogspot.com/
                • 5. Re: Essbase Crashes with 7506 code When Refreshing Planning Database
                  user640494
                  Thanks John,

                  I've read this article, and set the specified 8192-divisible data cache size (for example, 57344 KB), but the problem remains the same.
                  The application works normally a few days, then an element added. During refresh, the crash occurs.

                  All member formulas (on dense and sparse dimensions) are valid, and database itself is also valid.
                  The question is, how to reproduce this issue, as it seems to occur without any cause.

                  Regards.
                  • 6. Re: Essbase Crashes with 7506 code When Refreshing Planning Database
                    JohnGoodwin
                    It might be also worth exporting all the data, clearing and reloading.
                    Also if you have not already log it with Oracle.

                    Cheers

                    John
                    htp://john-goodwin.blogspot.com/
                    • 7. Re: Essbase Crashes with 7506 code When Refreshing Planning Database
                      user640494
                      Hi John,

                      Already did (nevertheless, will try again). In metalink article you mentioned, there is a "+memory issue at the time of the restructure+". What is this "memory issue", and may be it somehow connected with outline stricture?

                      Regards.
                      • 8. Re: Essbase Crashes with 7506 code When Refreshing Planning Database
                        JohnGoodwin
                        If you have followed all the steps in the document "Essbase Internal Logic Error [7506] When Restructuring Database. [ID 965942.1]" and you are still experiencing issues then log it with Oracle.

                        Cheers

                        John
                        http://john-goodwin.blogspot.com/
                        • 10. Re: Essbase Crashes with 7506 code When Refreshing Planning Database
                          user640494
                          Hi All,

                          The problem was in shared member, that preceded its prototype. After aggregation calc with that shared member, some internal arrays in Essbase got overflowed. When new member added, application crashes during refresh.

                          See Warning: shared member precedes its prototype

                          Regards.