1 2 3 4 5 Previous Next 71 Replies Latest reply: Aug 9, 2013 3:46 PM by user11016624 Go to original post RSS
      • 15. Re: Essabse ASO write-back send data
        user11016624

         

         

          <?xml version="1.0" encoding="UTF-8" standalone="no" ?>

        - <EASFrameworkTransferObject>

        - <Partition>

        - <transparent comment="" direction="to" outline="reverse" replace="yes">

          <sourcedb application="BSO" database="PLANNING" password="2l0fKnpc78AIKpmB/I08qA==" server="VMSDCW230:1423" usernme="admin@Native Directory" />

          <targetdb application="ZZZ_CNSL" database="PLANNING" password="2l0fKnpc78AIKpmB/I08qA==" server="VMSDCW230:1423" usernme="admin@Native Directory" />

          <areaspec sourcealias="sourcearea1" sourcearea="@IDESCENDANTS("Scenarios")" targetalias="targetarea1" targetarea="@IDESCENDANTS("Scenarios")" />

          </transparent>

          </Partition>

          </EASFrameworkTransferObject>

        • 16. Re: Essabse ASO write-back send data
          Evgeniy.Rasyuk

          >>>@IDESCENDANTS("Scenarios")" targetalias="targetarea1" targetarea="@IDESCENDANTS("Scenarios")"

              u need create LEVEL0 sliece for all Dimension !

            @RELATIVE(Scenarios,0) and so ON



          • 17. Re: Essabse ASO write-back send data
            user3055639

            Hi Evgeniya

            I know we have to create LEVLE0 slice for all Dimensions.  In partition manager, in the AREA tab:

             

            SOURCE                                                      TARGET

            @RELATIVE(Scenarios,0)                            @RELATIVE(Scenarios,0)     (this was accepted)

            @RELATIVE(Accounts,0)                             @RELATIVE(Accounts,0)    (this was not accepted and gave me the following error:

                                                                                                                         Target - Partition definition is not valid : Area 1 overlaps with Area 2


            How can I get all my dimensions in the partition script?

            • 18. Re: Essabse ASO write-back send data
              Evgeniy.Rasyuk

              1) Don't use wizard with "User Member Selection tool" . Work with "USe text editor"

              2) you must place all commands in ONE partition definition.

              3) Create partition for ONE slice (cell)

                        after that ,  step-by-step - enlarge script for all model

              • 19. Re: Essabse ASO write-back send data
                user11016624

                Hello  Evgeniya

                 

                we was able to update partition with all dimensions except “Time periods” and “Delivery Channels”  .  It does not like dimension names with 2 words (or the space between them)??? Could it be or something elese

                • 20. Re: Essabse ASO write-back send data
                  Evgeniy.Rasyuk

                  Do you using " in the names.?

                  • 21. Re: Essabse ASO write-back send data
                    user11016624

                    yes thet helped,

                     

                    we created the following partition

                    @RELATIVE(Scenarios,0),@RELATIVE(Departments,0),@RELATIVE(Accounts,0),@RELATIVE(Entities,0),@RELATIVE(Locations,0),@RELATIVE(Products,0),@RELATIVE(Intercompany,0),@RELATIVE(Years,0),@RELATIVE("Time Periods",0),@RELATIVE(DeliveryC,0)

                     

                    and now getting the follwoing error while retviing data from ASO

                     

                    Request grid size is more then allowed limit [2147483647]. Increase it using the config settiong MAX_REQUEST_GRID_SIZE

                     

                    I set the MAX_REQUEST_GRID_SIZE in essbase.cfg to increase still this is not helping,

                    Is soemthing wrong the way we did patition?

                    • 22. Re: Essabse ASO write-back send data
                      GlennS_3

                      Did you restart the Essbase service after making that setting?

                      • 23. Re: Essabse ASO write-back send data
                        user11016624

                        I put this in cfg file MAX_REQUEST_GRID_SIZE ZZZ_CNSL 400000000000

                         

                        and retrated

                         

                        the log showing:

                         

                        [Fri Aug 02 15:54:16 2013]Local/ZZZ_CNSL/PLANNING/admin@Native Directory/6140/Info(1023132)
                        Waiting for data from the source VMSDCW230:1423:BSO:PLANNING of grid size 3.0. Approximately one second is needed to fetch a grid of size one million cells with non missing cell density of 7% from the source.

                        [Fri Aug 02 15:54:16 2013]Local/ZZZ_CNSL/PLANNING/admin@Native Directory/6140/Info(1023133)
                        Density of the grid  1.000 of fetch size 3

                        [Fri Aug 02 15:54:16 2013]Local/ZZZ_CNSL/PLANNING/admin@Native Directory/6140/Info(1023132)
                        Waiting for data from the source VMSDCW230:1423:BSO:PLANNING of grid size 3.0. Approximately one second is needed to fetch a grid of size one million cells with non missing cell density of 7% from the source.

                        [Fri Aug 02 15:54:16 2013]Local/ZZZ_CNSL/PLANNING/admin@Native Directory/6140/Info(1023133)
                        Density of the grid  1.000 of fetch size 3

                        [Fri Aug 02 15:54:16 2013]Local/ZZZ_CNSL/PLANNING/admin@Native Directory/6140/Info(1023132)
                        Waiting for data from the source VMSDCW230:1423:BSO:PLANNING of grid size 3.0. Approximately one second is needed to fetch a grid of size one million cells with non missing cell density of 7% from the source.

                        [Fri Aug 02 15:54:16 2013]Local/ZZZ_CNSL/PLANNING/admin@Native Directory/6140/Info(1023133)
                        Density of the grid  1.000 of fetch size 3

                        [Fri Aug 02 15:54:16 2013]Local/ZZZ_CNSL/PLANNING/admin@Native Directory/6140/Info(1023132)
                        Waiting for data from the source VMSDCW230:1423:BSO:PLANNING of grid size 3.0. Approximately one second is needed to fetch a grid of size one million cells with non missing cell density of 7% from the source.

                        [Fri Aug 02 15:54:16 2013]Local/ZZZ_CNSL/PLANNING/admin@Native Directory/6140/Info(1023133)
                        Density of the grid  1.000 of fetch size 3

                        [Fri Aug 02 15:54:17 2013]Local/ZZZ_CNSL/PLANNING/admin@Native Directory/6140/Error(1023134)
                        Request grid size is more than allowed limit [2147483647]. Increase it using the config setting MAX_REQUEST_GRID_SIZE


                        [Fri Aug 02 15:54:17 2013]Local/ZZZ_CNSL/PLANNING/admin@Native Directory/6140/Error(1020004)
                        An error [1023134] occurred in Spreadsheet Extractor.

                        • 24. Re: Essabse ASO write-back send data
                          Evgeniy.Rasyuk

                          Use in partition slice one version one scenario

                          • 25. Re: Essabse ASO write-back send data
                            Evgeniy.Rasyuk

                            And one more opportunity )

                               You can use Replicated partition instant transparent.  And replicated only "changes".  

                            • 26. Re: Essabse ASO write-back send data
                              user11016624

                              meanign:

                               

                              BSO will have replicated partition instead transperent between ASO? will improve retrive performance, will it be latest data without dealyes?

                              • 27. Re: Essabse ASO write-back send data
                                Evgeniy.Rasyuk

                                you can replicate via running calculation.

                                 

                                   Run MAxl from CDF Essbase function.

                                • 28. Re: Essabse ASO write-back send data
                                  user11016624

                                  manualy each time, or it does on fly? why transpatent pratition not good any more ? beacse isseu with MAX_REQUEST_GRID_SIZE?

                                  • 29. Re: Essabse ASO write-back send data
                                    Evgeniy.Rasyuk

                                    >>manualy each time, or it does on fly?

                                    on the planning form ?

                                      or from any other event.

                                     

                                    >> why transpatent pratition not good any more ?

                                       because TP  good for simple small model, like Sample Basic. 

                                      You are in  on  the cross with this ways

                                          1)  Use BSO with TP with simples model (or slice)

                                          2)  Use BSO with RP with source model ( Replicate can work for only changes )

                                         

                                    p.s.

                                    Do you merge data in the source case ?

                                    alter database  APP.DB  merge incremental data remove_zero_cells;


                                      


                                    p.s. p.s. ASO also can work like ROLAP ( I don't use it in production only in learning case)  -> Agregation in ASO -> Data in SQL DWH