MDX queries : BW statistics are inconsistents

Hello,
We are implementing BO on top of SAP BW 3.5.
We had some major performance issues , and now we're tryning to investigate in detail.
The queries were first launched on BO only, and afeterwards on SAP BW, using the transaction MDXTEST, we measured a similar amount of time.
Now now want to have a closer look at the distribution of the time spent. (DB%,Frontend%;Network%, etc...)
The problem is that when we have a look at transaction ST03 in BW analysis, the statistics of MDX
queries are inconsistents :
I've join a concrete example :
The left column is a BO statistic executed on SAP using MDXTEST,
The right column is a traditional BEX query.
When I do the addition of the different time %(percent total) the results is 100 % for the Bex query ...and 44% for the MDX query.
I know that many fixes for MDX have been delivered on BI.7, but what about 3.5, I searched the sap notes but I couldn't find any note descrybing this symptom, nor any fix for our BW release.
Do you know how I should interpret thoses results, in other worlds, where ar the missing percentages in MDX queries ?
thank you in advance for your help.
Regards.
InfoCube Name                                         Cube C      Cube C
Name of Query                                Query A(BO)        Query B(BEX)
Number of Navigation Steps                        1     1
Total Runtime (s)                                       534,9     39,8
Total Runtime / Navigation Step (s)     534,9     39,8
Median of Total Runtime (s)                      534,9     39,8
Initialization Time (s)                                        0,2     0,4
Initialization Time / Total Runtime (%)     0,04     1,01
Ø Initialization Time (s)                     0,2     0,4
OLAP Runtime (s)                                    0,9     2,1
OLAP Time / Total Runtime (%)                  0,17     5,28
OLAP Runtime / Navigation Step (s)     0,9     2,1
Database Runtime (s)                                  197,0     22,4
Database Runtime / Total Runtime (%)     36,83     56,28
DB Runtime per Navigation Step (s)     197,0     22,4
Frontend Runtime (s)                                    33,9     4,8
Frontend Runtime / Total Runtime (%)     6,34     12,06
Frontend Time per Navigation Step (s)     33,9     4,8
Master Data Runtime (s)                    5,6     10,1
Master Data Time / Total Runtime (%)     1,05     25,38
Ø Master Data Time per Navigation Step     5,6     10,1
Number of records selected                  18620     899
Number of Transferred Records                10037     629
Ratio of Selected to Transferred Records     1,9     1,4
Database Time per Selected Record (ms)     10,6     24,9
Number of Cells                                       162060     7295
Cells per Transferred Records                   16,1     11,6
Number Formatted                                     0     72
Ratio of Formattings to Number of Cells     0,0     0,0
percent Total     :                     44,43% for MDX              and  100,01% as expected for BEX
time                                             237,8     40,2
Edited by: Raoul Shiro on Feb 5, 2009 6:54 PM

Hi Raoul,
in regards to the BW statistics values I would suggest you open a OSS case.
in regards to the performance improvements - correct they are done for BI7 and the XI 3.1 release.
Ingo

Similar Messages

  • Mdx-queries: how to optimize their processing?

    hi there. I have a problem with mdx-queries processing. For now mdx-queries are processed as follows:
    if I refer a dimension in an mdx-query the OLAP processor while creating a cube downloads into internal memory the whole SID-table and then the whole P- and Q- tables for the corresponding charachteristic are being downloaded as well. And it doesn't take in account any filters used in a query on this stage, i.e. the whole axis is downloaded.
    Does anyone know if there is a possibility to optimize the mdx-queries processing in  SAP BW? How to make it take in account filters on the stage of downloading master data for the cube?
    We use the SAP BW 3.5 version.

    hi there. I have a problem with mdx-queries processing. For now mdx-queries are processed as follows:
    if I refer a dimension in an mdx-query the OLAP processor while creating a cube downloads into internal memory the whole SID-table and then the whole P- and Q- tables for the corresponding charachteristic are being downloaded as well. And it doesn't take in account any filters used in a query on this stage, i.e. the whole axis is downloaded.
    Does anyone know if there is a possibility to optimize the mdx-queries processing in  SAP BW? How to make it take in account filters on the stage of downloading master data for the cube?
    We use the SAP BW 3.5 version.

  • Reg MDX queries in BI

    Hi All,
    If anyone know about MDX queries in BI please share some documentation.
    We are using OBIEE as front end for BI for reporting purpose which uses MDX quries from SAP bi
    Thanks

    Hi Arun
    Thanks for ur reply
    I tried using MDXTEST
    But i need some more doumentation about that.

  • Tunning ASO cube for metada mdx queries

    Hi,
    I have some metadata mdx queries, for this kind of queries is there any special tunning which would be applied?

    Syntax has changed for ASO member formulas and semicolons are no longer used. Why would you want to use the semicolon? With the new syntax it is not necessary.

  • MDX Queries , Webservices in SAP BI7.0

    In BI we have a Query and that query is being used by .NET Application. Now we need to do some changes in the query. While i made a change in the query in Q-Sys that change is not reflecting in the .NET Application[Q-Sys]. From the .NET Person i received some MDX Queries which are using for retrieving the data from the query. I used the TCODE : MDXTEST while im going to give that MDX Query and run it is showing the data, but that data is not similar to the query o/p(changed query), it is showing the data (as of before modifying the query).
    Any one please help me out, regarding this MDX Queries, What is the WebService part in BW,
    When  XMLA, SOAP, WSDL ... come into picture as of BW side.

    check these
    http://help.sap.com/saphelp_nw2004s/helpdata/en/e8/2cd937651f1a13e10000009b38f8cf/content.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/c8/e92637c2cbf357e10000009b38f936/content.htm

  • MDX queries that used to work on SSAS 2008 not working on 2012

    Hello,
    We are still using the old PerformancePoint planning server which is writing MDX queries against a SSAS 2012 at this time.   What used to work against SSAS 2008 is now having issues.   I captured a profile and the part of the query which
    generates the error is this error:  The '' calculated member cannot be created because a calculated member with the same name already exists.    What has changed in SSAS 2012 where this would not work anymore?;  is there anyway to
    make the 2012 environment work with this code again?.   The code generation is out of my control so I need to find a way to enable backwards compatibility with the way the tool generates the MDX statements.
    WITH
      MEMBER [Account].[Staffing_V3].[] AS ""
      MEMBER [Account].[Staffing_V3].[] AS ""
      MEMBER [Account].[Staffing_V3].[] AS ""
      MEMBER [Account].[Staffing_V3].[] AS ""
      MEMBER [Account].[Staffing_V3].[] AS ""
      MEMBER [Account].[Staffing_V3].[] AS ""
      MEMBER [Account].[Staffing_V3].[] AS ""
      MEMBER [Account].[Staffing_V3].[] AS ""
      MEMBER [Account].[Staffing_V3].[] AS ""
      MEMBER [Account].[Staffing_V3].[] AS ""
      MEMBER [Account].[Staffing_V3].[] AS ""
      MEMBER [Account].[Staffing_V3].[] AS ""
      MEMBER [Account].[Staffing_V3].[] AS ""
      MEMBER [Account].[Staffing_V3].[] AS ""
    Thanks,
    Matt

    Hi Matt,
    According to your description, the MDX query which has the duplicate calculated member name can run success with out any problems in SSAS 2008, however the same query cannot work in SSAS2012 with the error below, right?
    The '' calculated member cannot be created because a calculated member with the same name already exists.
    I have tested it on my local environment, and the result turn out that this is the default change by Microsoft from SSAS 2008 R2 version. And I am afraid there is no any workarounds run this similar query in SSAS 2012. So in your scenario, you
    need to remove the duplicate members in the query.
    Thank you for your understanding.
    Regards,
    Charlie Liao
    TechNet Community Support

  • How to find the list of Queries/Reports which are using Exceptional Aggregation in SAP BI?

    Hi All,
    We are interested to know how to find the list of Queries/ Reports which are using Exceptional aggregation in SAP BI.
    Please let us know is there any table's to check the list of reports using Exceptional Aggregation in SAP BI.

    Hi,
    Here you go..
    1) Go to table RSZCALC and get list of ELTUID where AGGREXC is not INITIAL and AGGRCHA is not initial; now you get only exception aggregation set based on some chars. Also you can further add STEPNR = 1 since your intention is just to get query name , not the calculation details; this will reduce number of entries to lookup and save DB time for next steps.
    Here you will get list of exception aggregation UUID numbers from which you can get properties from RSZELTDIR.
    2) Pass list of RSZCALC-ELTUID to table RSZELTXREF - TELTUID and get list of RSZELTXREF -SELTUID - this table stores query to it's elements maping kind.
    3) Now again pass RSZELTXREF - SELTUID into same table but into different field RSZELTZREF - TELTUID and get RSZELTXREF - SELTUID
    This step you get query reference sheet or column or query general UUID for next step.
    4) Pass list of RSZELTXREF - SELTUID into RSZELTDIR - ELTUID with DEFTP as 'REP'. Now you get list of query names in RSZELTDIR - MAPNAME and description in TXTLG.
    Note: you can also get the reference chars used for exception aggregation from RSZCALC - AGGRCHA field.
    Hope this helps.
    Please keep in mind, it might take more time depends on how many query elements you have in the system...
    Comments added for better DB performance by: Arun Thangaraj

  • Query is not working properly when statistics are computed (XE 11g Windows 7 32 bits)

    Hi,
    We have an application with a Oracle XE 11.2 database on a Windows 7 32 bits plateform.
    We have a query wich access 4 tables end use a user defined package function.
    When the statistics are computed the query is returning no rows, (with the data in the tables it should return 349 rows).
    When the statistics are deleted (with ANALYZE TABLE xxx DELETE STATISTICS) the query is working fine.
    I tried different statistics calculation methods, and sometimes the query is working, sometimes it is not!
    I don't understand how the statistics caluclation method can change the query results.
    Has anybody already encountered such an issue?
    Regards,
    Yves

    I understand how the statistics are working.
    What i don't undestand is why the number of rows returned is different with or without statistics.
    I tried yesterday to had a hint /*+ RULE */ and with the hint, rows are correctly returned!
    Here is the query:
    SELECT l_activite.copaip, l_activite.nunati, l_activite.numeul, obsoff.dapaul,
                                        obsoff.lai24h / 10 * DECODE (coefat, NULL, 1, 0, 1, coefat / 200) lai24h, obsoff.etfeob, obsoff.tplaco / 10 tplaco,
                                        obsoff.tblaco / 10 tblaco, l_lactoff.nulact, obsoff.dapaul - l_lactoff.dadela + 1 dulact, l_lactoff.dadela,
                                        l_activite.dcenul,
                                        (  obsoff.tblaco
                                         / 10
                                         * (DECODE (obsoff.tblaco, 0, 0, NULL, 0, obsoff.lai24h * DECODE (coefat, NULL, 1, 0, 1, coefat / 200) / 10))
                                        ) mg,
                                        (  obsoff.tplaco
                                         / 10
                                         * (DECODE (obsoff.tplaco, 0, 0, NULL, 0, obsoff.lai24h * DECODE (coefat, NULL, 1, 0, 1, coefat / 200) / 10))
                                        ) mp,
                                        DECODE (obsoff.tblaco, 0, 0, NULL, 0, obsoff.lai24h * DECODE (coefat, NULL, 1, 0, 1, coefat / 200) / 10) lait_mg,
                                        DECODE (obsoff.tplaco, 0, 0, NULL, 0, obsoff.lai24h * DECODE (coefat, NULL, 1, 0, 1, coefat / 200) / 10) lait_mp,
                                        pck_f_valorises.f_present_mul (obsoff.etfeob,
                                                                       obsoff.nulact,
                                                                       (SELECT MAX (l_obsoff.dapaul)
                                                                          FROM l_obsoff
                                                                         WHERE TRIM (l_obsoff.copaip) = TRIM (l_activite.copaip)
                                                                           AND TRIM (l_obsoff.nunati) = TRIM (l_activite.nunati)
                                                                           AND l_obsoff.dapaul < obsoff.dapaul
                                                                           AND l_obsoff.etfeob <> 'T'),
                                                                       obsoff.dapaul,
                                                                       l_lactoff.dadela
                                                                      ) as OK
                                   FROM l_activite, l_obsoff obsoff, l_lactoff, l_passage
                                  WHERE TRIM (l_activite.copaul) = TRIM ('FR')
                                    AND TRIM (l_activite.numeul) = TRIM ('61323017') || '    0'
                                    AND TRIM (l_activite.copaip) = TRIM (obsoff.copaip)
                                    AND TRIM (l_activite.nunati) = TRIM (obsoff.nunati)
                                    AND TRIM (l_activite.copaip) = TRIM (l_lactoff.copaip)
                                    AND TRIM (l_activite.nunati) = TRIM (l_lactoff.nunati)
                                    AND TRIM (l_passage.copaul) = TRIM (l_activite.copaul)
                                    AND TRIM (l_passage.numeul) = TRIM (l_activite.numeul)
                                    AND (   (DECODE (l_activite.dacosu, TO_DATE ('01/01/0001', 'dd/MM/YY'), 'VIDE', NULL, 'VIDE', l_activite.dacosu) = 'VIDE')
                                         OR (l_activite.dacosu >= l_passage.dapaul)
                                    AND l_passage.dapaul = obsoff.dapaul
                                    AND obsoff.nulact = l_lactoff.nulact
                                    AND obsoff.dapaul >= l_activite.dcenul
                                    AND l_passage.dapaul <= to_date('24/04/2013')
                                    AND l_passage.dapaul >= to_date('24/04/2012') - 50
                                    AND pck_f_valorises.f_present_mul (obsoff.etfeob,
                                                                       obsoff.nulact,
                                                                       (SELECT MAX (l_obsoff.dapaul)
                                                                          FROM l_obsoff
                                                                         WHERE TRIM (l_obsoff.copaip) = TRIM (l_activite.copaip)
                                                                           AND TRIM (l_obsoff.nunati) = TRIM (l_activite.nunati)
                                                                           AND l_obsoff.dapaul < obsoff.dapaul
                                                                           AND l_obsoff.etfeob <> 'T'),
                                                                       obsoff.dapaul,
                                                                       l_lactoff.dadela
                                                                      ) = 1
    and the function :
    FUNCTION F_PRESENT_MUL(p_etat IN CHAR,p_nulact IN NUMBER,
    p_derniere_obs_lait IN DATE, p_date_passage IN DATE,p_dadela IN DATE)
    RETURN NUMBER IS
       NAME:       F_PRESENT_MUL
       PURPOSE:    Retourne 1 si présent MUL 0 sinon
       REVISIONS:
       Ver        Date        Author           Description
       1.0        01/12/2006  Mathieu GUIDEL        1. Created this function.
       NOTES:
    BEGIN
       IF p_derniere_obs_lait IS NULL THEN /* vache présente MUL */
        RETURN 1;
       END IF;
       IF p_etat='P' THEN /* vache présente MUL */
       RETURN 1;
       ELSE
        IF p_etat = 'N' THEN /* NC ou FV */
         IF (p_date_passage - p_dadela + 1) <= 7 THEN /* FV */
          IF p_nulact=1 THEN
          RETURN 0;
          ELSE /* considérée comme tarie */
           IF (p_date_passage - p_derniere_obs_lait) < 100 THEN /* derniere obs lait inférieur à 100 jour, présente MUL */
           RETURN 1;
           ELSE /* FV tarie depuis trop longtemps : non présente MUL */
           RETURN 0;
           END IF;
          END IF;
         ELSE /* NC */
         RETURN 1;
         END IF;
        ELSE
         IF p_etat = 'T' THEN /* Tarie */
          IF (p_date_passage - p_derniere_obs_lait) < 100 THEN /* derniere obs lait inférieur à 100 jour, présente MUL */
          RETURN 1;
          ELSE /* tarie depuis trop longtemps : non présente MUL */
          RETURN 0;
          END IF;
          ELSE /* etat différent de P, N, T donc etat = S */
          /*vérification du contrôle précédent non FV*/
          IF (p_derniere_obs_lait - p_dadela + 1) <= 7 THEN /* FV au contrôle précédent*/
          RETURN 0;
          ELSE
            IF (p_date_passage - p_derniere_obs_lait) < 30 THEN /* derniere obs lait ou NC inférieur à 30 jour, présente MUL */
            RETURN 1;
            ELSE /* sortie sans lait depuis trop longtemps : non présente MUL */
            RETURN 0;
            END IF;
          END IF;
         END IF;
        END IF;
       END IF;
    END F_PRESENT_MUL;
    Regards

  • Perfromance problem when using MDX queries in Crystal

    Dear All,
    I am using Crystal reports together with an MDX query from the BI system. When I run the report in the Web then it takes 60 seconds to get results. When I use this query through MDX into a crystal report the query runs very long and in most cases ends up with the message :
    Database connection error: 'No more storage space available for extending an internal table"
    It looks like there is something going on with the definition of the query on the database when using the MDX drivers. Is There a way to solve this ?
    I hear rumours that upgrading to EHP 1 Stack 3 solves performance problems arround MDX queries, but I cannot find prove anywhere. Without proof or an official statement I cannot advise the Customer.
    Please Help,
    Marcel

    Hi Ingo,
    This feature I did not use yet ;-).
    The MDX looks like :
    SELECT {[Measures].[4B78DNZSKX3JQCWJKSS9S421C]} ON COLUMNS,  NON EMPTY CROSSJOIN(EXCEPT([Z0TERR2__Z0SALEM].MEMBERS, {[Z0TERR2__Z0SALEM].[All]}), CROSSJOIN(EXCEPT([Z0CUST].MEMBERS, {[Z0CUST].[All]}), CROSSJOIN(EXCEPT([0DOC_NUMBER].MEMBERS, {[0DOC_NUMBER].[All]}), CROSSJOIN(EXCEPT([Z0TERR2].MEMBERS, {[Z0TERR2].[All]}), CROSSJOIN(EXCEPT([Z0ORDITEM__Z0CNVMAN].MEMBERS, {[Z0ORDITEM__Z0CNVMAN].[All]}), CROSSJOIN(EXCEPT([Z0CICL__Z0IMLG18].MEMBERS, {[Z0CICL__Z0IMLG18].[All]}), CROSSJOIN(EXCEPT([Z0DUMOVEN__Z0MOVDECR].MEMBERS, {[Z0DUMOVEN__Z0MOVDECR].[All]}), CROSSJOIN(EXCEPT([Z0BUSTRW].MEMBERS, {[Z0BUSTRW].[All]}), CROSSJOIN(EXCEPT([Z0BUSTSTW].MEMBERS, {[Z0BUSTSTW].[All]}), EXCEPT([Z0IBUSTRW].MEMBERS, {[Z0IBUSTRW].[All]})))))))))) DIMENSION PROPERTIES [Z0CUST].[20CITY], [Z0CUST].[2Z0CUST], [0DOC_NUMBER].[2Z0SALCRON] ON ROWS FROM [Z0SD_M04/Z0SD_M04_Q0021] SAP VARIABLES [0P_COAR] INCLUDING [0CO_AREA].[3100], [0P_COCD] INCLUDING [0COMP_CODE].[3110], [0GMFROM] INCLUDING [0FISCPER].[Y42009002], [0GMTO] INCLUDING [0FISCPER].[Y42009002], [!V000005] INCLUDING [Z0REJECFP].[Y42009002], [!V000006] INCLUDING [Z0REJECFP].[Y42009002], [ZP_CSDAT] INCLUDING [0CALDAY].[20090311]
    Running the query in MDXTEST transaction with Flattening gives data in 10 minutes.
    Running the query in multidimensional mode gives the same result.
    How to proceed ??
    Kind regards
    Marcel

  • Getting List of Workbooks or Queries by Info Area

    Hi All,
    I want to find and categorize all workbooks/queries by Info Area
    I understand that this information could be found under Metadata Repository.
    But there are 4000 workbooks/queries which I want to categorize and I was searching for for backend tables or a program where I could find a link between the Info Area and Workbooks/Queries so that I could get list of the workbooks/Queries sorted by Info Area in one go.
    Can you please help.
    Thanks,
    Gaurav

    Hi Gaurav
    Please check the below thread..you have answer
    List of Queries/Workbooks
    Regards,
    Venkatesh

  • Converting MDX queries to OBIEE 11g

    How can I convert MDX queries to OBIEE queries. Im migrating Hyperion/Brio reports to OBIEE 11g reports.

    You can always plug in your cubes as datasources into OBIEE and then create the analyses using Answers.
    A direct MDX-to-"OBIEE" path only exist if you copy your MDX queries and paste them into a direct database request which uses a conncetion pool pointing towards your cube. That said...you will miss out on a lot of vanilla functionality if you do this.
    Cheers,
    C.

  • How to tune the MDX queries to avoid memory pressure? Please Help!

    I tried to run the following mdx queries, but kept running into Memory pressure issue.  Could someone give me some suggestions to avoid the issue?
    Thanks a lot
    Executing the query ...
    Server: The operation has been cancelled due to memory pressure.
    Execution complete
    ======================Query 1=============================
    SELECT NON EMPTY { [Measures].[Net Purchased CPP] } ON COLUMNS, 
     NON EMPTY {  ([STATION].[Station Name].[Station Name].ALLMEMBERS 
     * [DAYPART].[Daypart Code].[Daypart Code].ALLMEMBERS 
     * [DEMOGRAPHIC].[Demo].[Demo].ALLMEMBERS ) }  ON ROWS
     FROM [SPOT]
     WHERE  ([ESTIMATE].[Estimate Number].&[3881] )
    ==================Query 2================================     
       SELECT NON EMPTY { [Measures].[Net Purchased CPP] } ON COLUMNS, 
     NON EMPTY {  ([STATION].[Station Name].[Station Name].MEMBERS 
     * [DAYPART].[Daypart Code].[Daypart Code].MEMBERS 
     * [DEMOGRAPHIC].[Demo].[Demo].MEMBERS ) }  ON ROWS
     FROM [SPOT]
     WHERE  ([ESTIMATE].[Estimate Number].&[3881] )
     =====================Query 3============================   
    SELECT NON EMPTY { [Measures].[Net Purchased CPP] } ON COLUMNS, 
     NON EMPTY { ([ESTIMATE].[Estimate Number].[Estimate Number].ALLMEMBERS 
     * [STATION].[Station Name].[Station Name].ALLMEMBERS 
     * [DAYPART].[Daypart Code].[Daypart Code].ALLMEMBERS 
     * [DEMOGRAPHIC].[Demo].[Demo].ALLMEMBERS ) } 
     ON ROWS FROM ( SELECT ( { [ESTIMATE].[Estimate Number].&[3881] } ) ON COLUMNS FROM [SPOT])

    Hi BI_Eric,
    The error occurs on the following scenario.
    You run a Multidimensional Expressions (MDX) query that contains a Data Analysis Expressions (DAX) measure in Microsoft SQL Server 2008 R2 Analysis Services (SSAS 2008 R2).
    The DAX measure has an expression that contains many levels of nested binary operators.
    Applying SQL Server 2008 R2 Service Pack 1 will fix the problem, please refer to the link below.
    http://support.microsoft.com/kb/2675230
    Besides, enough to seriously impair performance.you used CrossJoin function to join multiple dimensions which might cause the performance issue. If you crossjoin medium sized or large sized sets (e.g., sets that contain more than 100 items each), you can
    end up with a result set that contains many thousands of items enough to seriously impair performance.http://social.msdn.microsoft.com/Forums/sqlserver/en-US/337aea24-09ff-4354-b67d-8a90f67a13df/memory-pressure-error?forum=sqlanalysisservices
    Regards,
    Charlie Liao
    TechNet Community Support

  • Object statistics are locked

    All,
    Version : 11.2
    I have received following error while running sql script . I have found object statistics are locked for one schema and released using exec dbms_stats.unlock_schema_stats command later. Can any one tell me the possible cause for object statistics lock ?
    ERROR at line 1:
    ORA-20005: object statistics are locked (stattype = ALL)
    ORA-06512: at "SYS.DBMS_STATS", line 20338
    ORA-06512: at "SYS.DBMS_STATS", line 20361
    ORA-06512: at line 2
    Thanks in adavance.

    805877 wrote:
    All,
    Version : 11.2
    I have received following error while running sql script . I have found object statistics are locked for one schema and released using exec dbms_stats.unlock_schema_stats command later. Can any one tell me the possible cause for object statistics lock ?
    ERROR at line 1:
    ORA-20005: object statistics are locked (stattype = ALL)
    ORA-06512: at "SYS.DBMS_STATS", line 20338
    ORA-06512: at "SYS.DBMS_STATS", line 20361
    ORA-06512: at line 2
    Thanks in adavance.The object statistics would be locked only if some one has explicitly has issued the command to lock them. It doesn't happen by itself AFAIK. So I guess, you should check the auditing records of yours that who and when fired such command?
    HTH
    Aman....

  • SQL2314W  Some statistics are in an inconsistent state.  The newly collecte

    Hello,
    we have a DB2 V8.2.2. We are using the autmatic runstat feature. We sometimes get the following message in the db2diag.log
    Any idea?
    Regards,
    Alexander TUerk
    2006-12-13-08.12.48.738162+060 I2581966A567       LEVEL: Warning
    PID     : 913626               TID  : 1412        PROC : db2hmon 0
    INSTANCE: db2ph2               NODE : 000
    APPID   : *LOCAL.db2ph2.061213071307
    FUNCTION: DB2 UDB, Automatic Table Maintenance, AtmTable::runstats, probe:600
    MESSAGE : ZRC=0x0000090A=2314
    DATA #1 : <preformatted>
    AutoStats: Non zero (2314) return code from Runstats
    SQL2314W  Some statistics are in an inconsistent state.  The newly collected
    "TABLE" statistics are inconsistent with the existing "INDEX" statistics.
    SQLSTATE=01650

    Alexander,
    please look in the SAP Hint 533589.
    best regards,
    Joachim Müller

  • Statistics are locked

    Hi
    I am trying to execute the some of the mappings in 11g OWB.Mappings are failed with statistics are locked.
    How to resolve it?
    when this kind of errors will come?

    Plz tell me how to use FIX format to paste Query Output. It 11g Release 1. Total number of table are 19
    OWNer tableName
    SYS WRH$_SERVICE_WAIT_CLASS ALL
    SYS WRH$_SERVICE_WAIT_CLASS ALL
    SYS WRH$_SERVICE_STAT ALL
    SYS WRH$_TABLESPACE_STAT ALL
    SYS WRH$_ACTIVE_SESSION_HISTORY ALL
    SYS WRH$_SEG_STAT ALL
    SYS WRH$_PARAMETER ALL
    SYS WRH$_OSSTAT ALL
    SYS WRH$_SYS_TIME_MODEL ALL
    SYS WRH$_SYSSTAT ALL

Maybe you are looking for