Clarity PPM

Expand all | Collapse all

Load DWH full load job fails after a custom object  is deleted in the Clarity system

Jump to Best Answer
  • 1.  Load DWH full load job fails after a custom object  is deleted in the Clarity system

    Posted 09-29-2017 09:57 AM

    Load DWH full load job fails after custom object a is deleted in the Clarity system. Referencing the invalid view related to the custom object browse...

     

    Caused by: java.sql.SQLException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-04063: view "CLARPRD.DWH_LKP_XXXXX_BROWSE__00_V" has errors

    I thought the Full load job takes care of the deleted objects. 

    Any ideas or Work around how to fix this?



  • 2.  Re: Load DWH full load job fails after a custom object  is deleted in the Clarity system

    Posted 09-30-2017 01:51 PM

    Hi Venu,

     

    Can you go to PPM and check the look up if they are ensuring DWH look up standard are met and doesn't have duplicates.

     

    Regards

    Suman Pramanik 



  • 3.  Re: Load DWH full load job fails after a custom object  is deleted in the Clarity system

    Posted 10-01-2017 04:10 PM

    This is the out of the box lookup for the custom object.



  • 4.  Re: Load DWH full load job fails after a custom object  is deleted in the Clarity system

    Posted 10-02-2017 09:53 AM

    Yes not all out of box look up are DWH complaint though. Which look up you are using?



  • 5.  Re: Load DWH full load job fails after a custom object  is deleted in the Clarity system
    Best Answer

    Posted 10-02-2017 05:30 PM

    Hi Venu

     

    Was the custom object completely deleted from the system with this same lookup attribute and it's no longer in use anywhere?

     

    If yes, you can go ahead and drop the view after taking a backup of the DDL. Then try running the Load DWH - Full again.

     

    If the lookup is also used on other objects, then try compiling the view

    CLARPRD.DWH_LKP_XXXXX_BROWSE__00_V

    and see what are the exact Oracle errors thrown.

     

    You could also try unchecking the attribute and running the Load DWH job (provided it's in use on another object).

     

     

    Hope this helps -Nika