Version 13.0 Updates › Known Issues for Version 13.0

Known Issues for Version 13.0

Duplicate Cost Plan Code Error

The duplication of a plan code within a financial plan can cause the upgrade process to fail. The plan code for each plan type within the investment must be unique. For example, you can have a cost plan with the code MasterPlan2011 and a budget plan with same code, but you cannot have two cost plans with code MasterPlan2011 for the same investment. The unique database constraint for this rule was added in v13.0.

Due to concurrency issues, there may be a data issue in previous versions. In the case where a duplicate plan type code exists within a single financial plan, the upgrade process fails with an appropriate error message. You must correct the data issue before resuming the upgrade process.

Run the following query to identify possible data issues before you start the upgrade:

SELECT p1.id, p1.code, p1.name 
FROM fin_plans p1, fin_plans p2 
WHERE p1.id != p2.id 
AND p1.object_id = p2.object_id 
AND p1.code = p2.code 
AND p1.plan_type_code = p2.plan_type_code

If this query returns any rows, it indicates issues with fin_plans table data.

CA recommends that you review all such records and rename the codes for duplicate records. Leave all other data intact. A sample query is available to fix the data issues. Because this known issue deals with financial information, review the query carefully before deciding to use it. The following query appends _<internalId> to the duplicate plan code.

<!-- Oracle --> 
UPDATE fin_plans 
SET code = code || '_' || to_Char(id) 
WHERE id IN 
    ( SELECT p1.id 
                              FROM fin_plans p1, fin_plans p2 
                              WHERE p1.id != p2.id 
                AND p1.object_id = p2.object_id 
                AND p1.code = p2.code 
                AND p1.plan_type_code = p2.plan_type_code 
                ) 


<!-- Mssql --> 
UPDATE fin_plans 
SET code = code + '_' + CAST(id AS VARCHAR) 
WHERE id IN ( SELECT p1.id 
                                FROM fin_plans p1, fin_plans p2 
                                WHERE p1.id != p2.id 
                AND p1.object_id = p2.object_id 
                AND p1.code = p2.code 
                AND p1.plan_type_code = p2.plan_type_code 
) 

Missing Data for Resource Financials

If the Resource Class or Transaction Class fields are null for Resource financials, the upgrade process fails. The data must be corrected before you resume the upgrade process.

The not null database constraint for columns RESOURCE_CLASS and TRANSCLASS in table PAC_MNT_RESOURCES was added in v13.0. If you are upgrading from a previous version of CA Clarity PPM, it is possible the information may be missing.

CA recommends running the following query to identify records with this data issue before starting the upgrade.

Select * from pac_mnt_resources where RESOURCE_CLASS is null OR transclass is null

If this query returns any rows, it indicates issues with the PAC_MNT_RESOURCES table data. CA recommends reviewing all returned records and updating the records with valid transaction class and resource class values.

Upgrade Fails if the Default Language for the Admin User Is Not English

A portion of the upgrade relies on the English locale when it is importing content using the XML Open Gateway. This import fails if the default language of the admin user is not set to English. The workaround is to set the admin user language to English. (CLRT-21964)

Resume Capability During Upgrade

The ability to resume during an upgrade is not supported in this CA Clarity PPM version. It will be supported in a future release. If your upgrade to v13.0 fails, review the logs to determine the reason for the failure, restore your working pre-upgrade version and database, correct the failure, and restart the upgrade.