Clarity

  • 1.  Problem with Load Data Warehouse

    Posted Nov 10, 2017 02:23 PM

    Hi there, we are running a fresh environment on the SaaS 15.2, and setting thing up on the job Load Data Warehouse we got the following issue:

     

    ClarityDB - isOracle? - An error occurred executing this job entry :  Couldn't execute SQL: BEGIN  CMN_GATHER_TABLE_STATS_SP( 'DWH_CMN_PERIOD' ,100); CMN_GATHER_TABLE_STATS_SP( 'DWH_FIN_BENEFIT_PLAN' ,100); CMN_GATHER_TABLE_STATS_SP( 'DWH_FIN_PLAN' ,100); CMN_GATHER_TABLE_STATS_SP( 'DWH_INV_ASSIGNMENT' ,100); CMN_GATHER_TABLE_STATS_SP( 'DWH_INV_INVESTMENT' ,100); CMN_GATHER_TABLE_STATS_SP( 'DWH_INV_TASK' ,100); CMN_GATHER_TABLE_STATS_SP( 'DWH_INV_TEAM' ,100); CMN_GATHER_TABLE_STATS_SP( 'DWH_RES_RESOURCE' ,100); CMN_GATHER_TABLE_STATS_SP( 'DWH_TME_SHEET' ,100); CMN_GATHER_TABLE_STATS_SP( 'DWH_TME_ENTRY' ,100); CMN_GATHER_TABLE_STATS_SP( 'DWH_TME_PERIOD' ,100);  UPDATE DWH_CFG_AUDIT SET DW_LOAD_START_DATE = (SELECT SYSDATE FROM DUAL@SC51951dDWH_SC51951d) WHERE TABLE_NAME = 'DWH_INV_TASK_HIERARCHY'; DWH_INV_TASK_HIERARCHY_SP( P_DBLINK => 'SC51951dDWH_SC51951d',P_ARRAY_SIZE => 50000); UPDATE DWH_CFG_AUDIT SET DW_LOAD_END_DATE = (SELECT SYSDATE FROM DUAL@SC51951dDWH_SC51951d) WHERE TABLE_NAME = 'D

    We check and its seams okey the configuration, also on health report, the database is giving a object error value 46, dont know the meaning.

    thanks in advance!
    Pablo


  • 2.  Re: Problem with Load Data Warehouse

    Posted Nov 12, 2017 04:45 PM

    Hi Pablo,

     

    Can you please share the bg-dwh logs, which has the complete failure logs.

     

    Regards,

    Srikanth G



  • 3.  Re: Problem with Load Data Warehouse

    Posted Jan 10, 2018 09:36 AM

    Do you always get this error when the job runs?  Does this happen when you run the incremental or full load job? 



  • 4.  Re: Problem with Load Data Warehouse

    Posted Feb 23, 2018 04:14 PM

    Hi there, first of all, sorry for this late response.

     

    We were working with support on this case, the general problem was solve aplying the service pack 4 of ppm 15.2.

     

    It toke a log time to figure it out, almost a month.

     

    So thank you all!

    cheers,

    Pablo