Clarity PPM1

Expand all | Collapse all

CA PPM Upgrade from 14.2 to 15.1 with errors.

  • 1.  CA PPM Upgrade from 14.2 to 15.1 with errors.

    Posted 03-22-2017 01:07 PM
      |   view attached

    Hello Everyone,

     

    I just did an upgrade from version 14.2 on 15.1 and it ended after 156 minutes with two errors below.

    Postcheck-results.xml:

     <tr class="fail">
                   <td>check-upgrade-complete.xml</td>
                   <td>ERROR</td>
                   <td>Upgrade phase for release 14.3.0 was completed, Upgrade phase for release 14.4.0 was completed, Upgrade phase for release
                      15.1.0 was not completed
                   </td>
                </tr>
                <tr class="fail">
                   <td>check-upgrade-exception.xml</td>
                   <td>ERROR</td>
                   <td>UPGRADE FAILED WITH THE FOLLOWING EXCEPTION: ${exception.msg} The following error occurred while executing this line:
                      /services/niku/temp/15.1/install15_1/install.xml:538: The following error occurred while executing this line:
                      /services/niku/temp/15.1/install15_1/install.xml:896: exec returned: 1. Please check install.log for more details.

     

    So I did a little research in the install.log and found an error and first exit code.

    Process - mview: DWH_X_INV_BEN_PER_FACTS_MV.xml
    3/22/17 4:58 PM (ExecTask) com.ca.clarity.jdbc.oraclebase.ddc: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-00955: name is already used by an existing object
    3/22/17 4:58 PM (ExecTask)

    Caused by: /services/niku/clarity/.setup/scripts/db.macros.xml:44: Java returned: 1

     

    After that, I don't have a clue, where is the problem, because the errors are without any specification what caused them.

    Example:

    3/22/17 4:59 PM (Sequential) Task "try" finished with error.
    /services/niku/temp/15.1/install15_1/install.xml:1188: exec returned: 1

     

    Do you know where could be the problem?


    Thank you.

    Best regards,

    Pavel Michalec

    Attachment(s)

    zip
    install.log.zip   39K 1 version


  • 2.  Re: CA PPM Upgrade from 14.2 to 15.1 with errors.

    Posted 03-23-2017 02:03 AM

    Hi Pavel,

     

    Can you please attach the install log, so that I can take a look

     

    Regards

    Suman Pramanik 



  • 3.  Re: CA PPM Upgrade from 14.2 to 15.1 with errors.

    Posted 03-23-2017 05:02 AM

    Hello Suman,


    yes of course I can and I attached that log to my main post. I deleted from the log the DB SID and URL.

     

    Thank you for your answer and time.

     

    Best regards,

     

    Pavel Michalec



  • 4.  Re: CA PPM Upgrade from 14.2 to 15.1 with errors.

    Posted 03-23-2017 05:23 AM

    Hi Pavel,

     

    Thanks for the logs and it looks like there is problem in dataware house and the error is below 

     

    3/22/17 4:58 PM (ExecTask) MATERIALIZED VIEW DWH_X_INV_BEN_PER_FACTS_MV ( INVESTMENT_KEY, PERIOD_KEY, PLAN_BENEFIT, BDGT_BENEFIT, PLAN_ACTUAL_BENEFIT, BDGT_ACTUAL_BENEFIT, DW_UPDATED_DATE ) AS
    3/22/17 4:58 PM (ExecTask) SELECT f.investment_key,
    3/22/17 4:58 PM (ExecTask) f.period_key,
    3/22/17 4:58 PM (ExecTask) SUM(CASE WHEN c.fin_plan_type_key = 'FORECAST' THEN f.benefit ELSE 0 END) plan_benefit,
    3/22/17 4:58 PM (ExecTask) SUM(CASE WHEN c.fin_plan_type_key = 'BUDGET' THEN f.benefit ELSE 0 END) bdgt_benefit,
    3/22/17 4:58 PM (ExecTask) SUM(CASE WHEN c.fin_plan_type_key = 'FORECAST' THEN f.actual_benefit ELSE 0 END) plan_actual_benefit,
    3/22/17 4:58 PM (ExecTask) SUM(CASE WHEN c.fin_plan_type_key = 'BUDGET' THEN f.actual_benefit ELSE 0 END) bdgt_actual_benefit,
    3/22/17 4:58 PM (ExecTask) MAX(f.dw_updated_date) dw_updated_date
    3/22/17 4:58 PM (ExecTask) FROM dwh_fin_benefit_period_facts f
    3/22/17 4:58 PM (ExecTask) INNER JOIN dwh_fin_benefit_plan b ON f.benefitplan_detail_key = b.benefitplan_detail_key
    3/22/17 4:58 PM (ExecTask) INNER JOIN (SELECT DISTINCT plan_key, fin_plan_type_key, benefitplan_key
    3/22/17 4:58 PM (ExecTask) FROM dwh_fin_plan
    3/22/17 4:58 PM (ExecTask) WHERE is_plan_of_record = 1) c ON b.benefitplan_key = c.benefitplan_key
    3/22/17 4:58 PM (ExecTask) WHERE 1=1
    3/22/17 4:58 PM (ExecTask) GROUP BY f.investment_key, f.period_key
    3/22/17 4:58 PM (ExecTask) UNION ALL
    3/22/17 4:58 PM (ExecTask) SELECT i.investment_key,
    3/22/17 4:58 PM (ExecTask) p.period_key,
    3/22/17 4:58 PM (ExecTask) CASE WHEN p.plan_benefit_period_days <> 0 AND p.plan_benefit_total_days <> 0
    3/22/17 4:58 PM (ExecTask) THEN (i.plan_benefit / p.plan_benefit_total_days) * p.plan_benefit_period_days
    3/22/17 4:58 PM (ExecTask) ELSE 0 END plan_benefit,
    3/22/17 4:58 PM (ExecTask) CASE WHEN p.bdgt_benefit_period_days <> 0 AND p.bdgt_benefit_total_days <> 0
    3/22/17 4:58 PM (ExecTask) THEN (i.bdgt_benefit / p.bdgt_benefit_total_days) * p.bdgt_benefit_period_days
    3/22/17 4:58 PM (ExecTask) ELSE 0 END bdgt_benefit,
    3/22/17 4:58 PM (ExecTask) 0 plan_actual_benefit,
    3/22/17 4:58 PM (ExecTask) 0 bdgt_actual_benefit,
    3/22/17 4:58 PM (ExecTask) i.dw_updated_date dw_updated_date
    3/22/17 4:58 PM (ExecTask) FROM dwh_x_inv_sum_facts i
    3/22/17 4:58 PM (ExecTask) INNER JOIN (SELECT i.investment_key,
    3/22/17 4:58 PM (ExecTask) p.period_key,
    3/22/17 4:58 PM (ExecTask) p.period_end_date period_finish,
    3/22/17 4:58 PM (ExecTask) CASE WHEN i.bdgt_benefit_start <= p.period_end_date AND i.bdgt_benefit_finish >= p.period_start_date
    3/22/17 4:58 PM (ExecTask) THEN (LEAST(i.bdgt_benefit_finish, p.period_end_date) - GREATEST(i.bdgt_benefit_start, p.period_start_date)) + 1
    3/22/17 4:58 PM (ExecTask) ELSE 0 END bdgt_benefit_period_days,
    3/22/17 4:58 PM (ExecTask) (i.bdgt_benefit_finish - i.bdgt_benefit_start) + 1 bdgt_benefit_total_days,
    3/22/17 4:58 PM (ExecTask) CASE WHEN i.plan_benefit_start <= p.period_end_date AND i.plan_benefit_finish >= p.period_start_date
    3/22/17 4:58 PM (ExecTask) THEN (LEAST(i.plan_benefit_finish, p.period_end_date) - GREATEST(i.plan_benefit_start, p.period_start_date)) + 1
    3/22/17 4:58 PM (ExecTask) ELSE 0 END plan_benefit_period_days,
    3/22/17 4:58 PM (ExecTask) (i.plan_benefit_finish - i.plan_benefit_start) + 1 plan_benefit_total_days
    3/22/17 4:58 PM (ExecTask) FROM dwh_x_inv_sum_facts i
    3/22/17 4:58 PM (ExecTask) INNER JOIN dwh_cmn_period p ON p.period_type_key = 'FISCAL'
    3/22/17 4:58 PM (ExecTask) AND LEAST(i.bdgt_benefit_start, i.bdgt_benefit_start, i.plan_benefit_start, i.plan_benefit_start) <= p.period_end_date
    3/22/17 4:58 PM (ExecTask) AND GREATEST(i.bdgt_benefit_finish, i.bdgt_benefit_finish, i.plan_benefit_finish, i.plan_benefit_finish) >= p.period_start_date
    3/22/17 4:58 PM (ExecTask) WHERE i.plans_exist = 0) p ON i.investment_key = p.investment_key
    3/22/17 4:58 PM (ExecTask)
    3/22/17 4:58 PM (ExecTask)
    3/22/17 4:58 PM (ExecTask) Note: Foreign Keys and Triggers have been enabled

     

    So below is the next action I propose

     

    1. Roll back to 14.2, ensure you have correct patch for upgrade to 15.1 

    2. Delete the DWH schema and reimport the blank schema

    3. Upgrade the DWH schema by running the command admin db dwh-upgrade -Dupgrade.phase=maintenance

    4. Run the Load DWH job in full mode and ensure it completes 

    5. Rerun the upgrade

     

    Regards

    Suman Pramanik 



  • 5.  Re: CA PPM Upgrade from 14.2 to 15.1 with errors.

    Posted 03-23-2017 09:22 AM

    Hello Suman,

     

    thank you, I think you are right, because the ORA error pops up when it does the DWH_X_INV_BEN_PER_FACTS_MV.xml. Today I did a new upgrade and again get the ORA error, but after post-check I get only a one error for exception. And you can see that the upgrade 15.1.0 was completed, but the build failed because the another error.

     

      <result name="check-upgrade-complete.xml" value="INFO">
        <resultinfo>Upgrade phase for release 15.1.0 was completed</resultinfo>
      </result>
      <result name="check-upgrade-exception.xml" value="ERROR">
        <resultinfo>UPGRADE FAILED WITH THE FOLLOWING EXCEPTION: ${exception.msg} The following error occurred while executing this line:
    /services/niku/temp/15.1/install15_1/install.xml:538: The following error occurred while executing this line:
    /services/niku/temp/15.1/install15_1/install.xml:849: The following error occurred while executing this line:
    /services/niku/temp/15.1/install15_1/install-packages/15.1.0/install.xml:196: The following error occurred while executing this line:
    /services/niku/temp/15.1/install15_1/install-packages/15.1.0/install.xml:236: The following error occurred while executing this line:
    /services/niku/temp/15.1/install15_1/install-packages/15.1.0/install.xml:727: The following error occurred while executing this line:
    /services/niku/temp/15.1/install15_1/install-packages/15.1.0/install.xml:911: exec returned: 1. Please check install.log for more details.</resultinfo>

     

    I am not sure, if we do a rollback the backup and recreate the DB shema for DWH, that I don't end up in this problem again.



  • 6.  Re: CA PPM Upgrade from 14.2 to 15.1 with errors.

    Posted 03-23-2017 09:34 AM

    Hi Pavel,

     

    Any error in upgrade can result to multiple problems, so I would always recommend a roll back and although if you are sure there is not problem then you can import the DWH schema and run the job.

     

    Regards

    Suman Pramanik 



  • 7.  Re: CA PPM Upgrade from 14.2 to 15.1 with errors.

    Posted 04-12-2017 02:27 AM

    are your database properties all ok?

    NameValue
    Character SetAL32UTF8
    National Character SetUTF8/AL16UTF16
    nls_date_formatYYYY-MM-DD HH24:MI:SS
    nls_sortBINARY
    nls_compBINARY
    query_rewrite_enabledtrue
    Cursor_sharingFORCE

    14.2 was ok with UTF8