Dear CA PPM Experts
We are in the process of upgrading CA PPM from 15.2 to 15.5. Although the upgrade was successful, when I executed "admin content csk" as part of the upgrade and verified the admin.log came across the below error lines.
9/14/18 4:02 AM (admin) ERROR 14-09 04:02:44,044 - Attribute cop_cost_eft_status is not updated because lookup type cannot be changed.
9/14/18 4:02 AM (admin) ERROR 2018-09-14 04:02:44,044 [main] xql2.xbl Attribute cop_cost_eft_status is not updated because lookup type cannot be changed.
9/14/18 4:02 AM (admin) ERROR 14-09 04:02:48,670 - Attribute cop_schedule_status is not updated because lookup type cannot be changed.
9/14/18 4:02 AM (admin) ERROR 2018-09-14 04:02:48,670 [main] xql2.xbl Attribute cop_schedule_status is not updated because lookup type cannot be changed.
9/14/18 4:02 AM (admin) ERROR 14-09 04:02:48,771 - Attribute cop_scope_status is not updated because lookup type cannot be changed.
9/14/18 4:02 AM (admin) ERROR 2018-09-14 04:02:48,771 [main] xql2.xbl Attribute cop_scope_status is not updated because lookup type cannot be changed
Also the Load DWH job fails with the below error. There is a case already raised with CA Support and their analysis is in progress. In the mean time, thought of to post it here as well for a quicker fix. Please help.
2018/09/14 05:06:26 - Slices - ERROR (version 5.0.2, build 1 from 2013-12-04_15-52-25 by buildguy) : An error occurred executing this job entry :
2018/09/14 05:06:26 - Slices - Couldn't execute SQL: BEGIN^M
2018/09/14 05:06:26 - Slices - DWH_CFG_ADDIN_EXTRAS_SP(P_DBLINK => 'CLARITYDBLINK');^M
2018/09/14 05:06:26 - Slices - DWH_PROC_NEW_VIEWS_SP (P_DBLINK => 'CLARITYDBLINK');^M
2018/09/14 05:06:26 - Slices - END;
2018/09/14 05:06:26 - Slices -
2018/09/14 05:06:26 - Slices - [CA Clarity][Oracle JDBC Driver][Oracle]ORA-00904: "R"."SR_COST_EFFORT_STATUS_KEY": invalid identifier
The problem seems to be with Status report object, it could be a mismatch in the DWH_META_COLUMNS where this attribute SR_COST_EFFORT_STATUS_KEY is not making it to Data Warehouse.
Thanks for responding. How can this be fixed?
if you query select * from dwh_meta_columns where src_table_name = 'dwh_cop_prj_statusrpt_v';
There is a column called IS_DELETED and it should be 0 and if thats 1 it needs to be updated and compared with Vanila system to see what all status object attributes have these issues.
From what version you are upgrading and did the DWH ran before ?
I applied patch 126.96.36.199 on 188.8.131.52 and then upgraded to 15.5. Load DWH Job was completing successfully until patch 184.108.40.206 and after upgrade the first run itself failed.
I could not see any rows in that table where IS_DELETED=0.
What do you think of this link with steps for Augustin to try?
Appreciate you both sharing this experience online and will be open to your suggestions for how we might help future admin users performing their upgrade by posting some tips or recommended procedures at docops.ca.com/ppmop.
I hope the PMO was installed in 15.2 and then again on 15.5 and we had a but in 15.2 but that was fixed, so need we need find out why this attribute was missing.
Yes it was installed in both the versions. I have a CA Ticket raised for them to look into it.
I gone through the link you posted and I see the error there is different from what I experience.
Sure, will post my suggestions in docops.ca.com/ppmop.
I see you are working with the team, if the line item with below is missing then its something to be investigated on how this was missed. Did you had this as line item prior to upgrade and post upgrade this was missing.
select * from dwh_meta_columns where src_table_name = 'dwh_cop_prj_statusrpt_v';
I am sorry, I should have posted my comment as "I could not see any rows in that table where IS_DELETED=1" instead of "I could not see any rows in that table where IS_DELETED=0".
I mean, there are rows in the dwh_meta_columns table where is_deleted=0 only.
Lines 44 and 50 are the ones causing errors. If those are replaced with 45 and 51, the job completes successfully.
You shouldn't change the codes, the problem will be the status object details will not make it to data warehouse. We need to fix the meta columns and meta tables and fix it and we need to find out why its missing.
Hello - I am planning for an upgrade (currently on 15.3) and analyzing which version I should upgrade to (15.4x or 15.5). Can you share your lesson learn of upgrading to 15.5 with me?
a) Here are few Project tabs/sub-pages/fields that are missing in new UI. This will make users to keep switching between new and old UI. This is a big show stopper for us.
1) Budget Plans
2) Sub Pages
3) Sub Objects – Similar to Funding subpage
4) Custom Objects
5) Fields that does not exist in Blueprints
· % Complete Calculation Method
· Time Varying
· Actual Cost
· Blueprint Active ID
· Budgeted Capital Cost
· Budgeted Cost Finish (date)
· Budgeted Cost Start (date)
· Budgeted Cost Total
· Budgeted Operating Cost
· Currency Code
· EAC Sum for Labor Resources
· ETC Sum for Labor Resources
· Investments Using
· Last Used
· Page Layout
· Planned Cost Total
· Project Category
· Status Indicator
6) Processes tab in Projects edit layout
7) Process-locked-fields icon
9) XOG feature
10) Project’s Progress field
11) Team Member roles
12) Versioning of documents
13) Edit Layouts in Risks, Issues and Change Requests
14) Sub Pages in Change Requests
16) Project specific Action Items
17) Audit Trail
b) Load DWH job fails with a DB error which has been raised with CA and they are yet to find a fix.
Augustin Samraj M | IS PMO | Nissan North America | Mobile: +91 994-008-3138
Thanks for sharing Augustin. We have not roll out the new UX yet but I am concern about the status report object missing attributes and the Load DWH job. I will make sure to monitor these two.