Clarity PPM1

Expand all | Collapse all

CA PPM 15.2 Data Warehouse Options Error

Jump to Best Answer
  • 1.  CA PPM 15.2 Data Warehouse Options Error

    Posted 08-02-2017 02:40 PM

    Hi all,

     

    We have installed CA PPM 15.2 Patch 01( Version: 15.2.0.213 01 39). When we set the Entity for Fiscal Periods of Data Warehouse Option in System Option, we received the error: System error. Contact system administrator.

    Error in logfile:
    Caused by: java.sql.SQLException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-04063: package body "NIKU_IDA.CRV_SQL_CURVE_PKG" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "NIKU_IDA.CRV_SQL_CURVE_PKG"

    We found that the TYPE CRV_PREIOD and CRV_SLICE are being used with one additional column group_by and these type definiations don't have that column.

    Package compilation the error:

    Error(910,32): PLS-00306: wrong number or types of arguments in call to 'CRV_PERIOD'
    Line 910 in CRV_SQL_CURVE_PKG
     v_calendar(idx) := CRV_PERIOD( v_period, v_start, v_temp_date, DATE_TO_JULIAN( v_start ), DATE_TO_JULIAN( v_temp_date ), v_period_type, v_calendar_key, v_conversion, v_group_by );
     
    If we see the CRV_PERIOD definition, it doesn't have group by column
    CREATE OR REPLACE TYPE "CRV_PERIOD" FORCE
    AS
      OBJECT
      (
        PERIOD NUMBER,
        START_DATE DATE,
        FINISH_DATE DATE,
        JULIAN_START   INTEGER,
        JULIAN_FINISH  INTEGER,
        PERIOD_NAME    VARCHAR2(32),
        CALENDAR_KEY   VARCHAR(20) NULL,
        FTE_CONVERSION NUMBER );

     

    Thanks

    Giri



  • 2.  Re: CA PPM 15.2 Data Warehouse Options Error

    Posted 08-02-2017 06:18 PM

    Hi

     

    better to compile clarity and DWH schema after installed clarity 15.1 and try to configure system settings. This will help to recompile invalid database object after restoration.

     

    command:

     

    admin compile db

    admin db compile -Ddb.id=Datawarehouse

     

     

    Thanks

    Senthil



  • 3.  Re: CA PPM 15.2 Data Warehouse Options Error
    Best Answer

    Posted 08-03-2017 10:10 AM

    Thanks Senthil,

     

    CA Support suggested rebuild the Data Warehouse using below command, that resolved the issue.

    Am not sure why do we need to rebuild for new installations too

     

    admin db dwh-upgrade -Dupgrade.phase=maintenance

     

    http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1889227.aspx

     

    Regards

    Giri



  • 4.  Re: CA PPM 15.2 Data Warehouse Options Error

    Posted 08-04-2017 03:31 AM

    Hi Giri,

     

    The only reason i can think of rebuilding is if your DWH upgrade during patch 1 of 15.1 has gone wrong, do you have the install log where I can take a look.

     

    Regards

    Suman Pramanik 



  • 5.  Re: CA PPM 15.2 Data Warehouse Options Error

    Posted 08-07-2017 03:04 PM
      |   view attached

    Hi Suman,

     

    There were no errors in patch01 installation. please find the attached install.log

     

    Running this command resolved the issue - admin db dwh-upgrade -Dupgrade.phase=maintenance

     

    Thanks

    Giri

    Attachment(s)

    zip
    install.log.zip   4K 1 version


  • 6.  Re: CA PPM 15.2 Data Warehouse Options Error

    Posted 08-03-2017 12:33 AM

    Seems like this is happening because application is not going to support the user called "NIKU_IDA". Can you please drop this user, and use another one? I guess that will be helpful. 

     

    Thanks,

    Abhisek Dhar



  • 7.  Re: CA PPM 15.2 Data Warehouse Options Error

    Posted 08-03-2017 01:57 AM

    Hi Giri,

     

    Can you please check the date format set in the database for PPM as well as DWH? There is an existing thread on this same topic Load Data Warehouse Job fails 

     

    Regards

    Suman Pramanik 



  • 8.  Re: CA PPM 15.2 Data Warehouse Options Error

    Posted 08-03-2017 08:48 PM

    Hi Giri.

     

    Some of the DB objects may not be compiled when you restoring the Database dump. For best practice, better to recompile the database objects after restoration has completed.

     

    Thanks

    Senthil