Known Issues for Release 13.2

Release 13.2 Updates › Known Issues for Release 13.2

Known Issues for Release 13.2

This section provides known issues for CA Clarity PPM.

Duplicate Cost Plan Code Error

This issue applies only to upgrades from a 12.x release to Release 13.2.

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 the same code. However, you cannot have two cost plans with code MasterPlan2011 for the same investment. The unique database constraint for this rule was added in Version 13.0.

Due to concurrency issues, there can be a data issue in previous versions. When 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. An upgrade check script runs and alerts you that this problem exists.

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.

We recommend that you rename the codes for duplicate records. Do not change the other data. 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

This issue applies only to upgrades from a 12.x release to Release 13.2.

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. An upgrade check script runs and alerts you that this problem exists.

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

We recommend 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 that there are issues with the PAC_MNT_RESOURCES table data. We recommend 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.

Resume Capability During the Upgrade

This release does not support the ability to resume during an upgrade. If your upgrade fails, review the logs to determine the reason for the failure, restore the working pre-upgrade version and database, correct the failure, and restart the upgrade.

Potential Infinite URL Redirect Issue

Potential infinite URL redirect issues can arise when you run CA Clarity PPM in SSL mode. To avoid these issues, we recommend entering the same host name in the following locations:

The URL to access the application (https://<hostname>:<ssl_port>/niku/nu)
The HTTPS Entry URL field in the Application subtab under the Properties tab in Clarity System Administration

Complete these steps if you see the infinite URL redirect issue while operating in SSL mode:

Stop the product.
Review the HTTPS Entry URL field in CSA.
Correct the entry if needed and restart the application service.

Export Icons in Resource Planning Tabs Not Functioning

Export to Excel and Export to PowerPoint icons on a Resource Planning tab give an error when you click them.

Note: This issue applies only to WebSphere application servers.

As a workaround, use the Export to Excel and Export to PowerPoint links available from the Options icon in the individual portlets on the tabs.

Missing General Action Menu After Upgrade

In some cases, the General Action menu may not appear after an upgrade. This issue occurs on the Project object when the following conditions are present:

In the edit properties view (Layout:Edit), a display condition is defined on the General subpage.
The General object actions menu for the view is not customized.

You can correct the issue before the upgrade, or you can upgrade and then correct the issue in the new upgraded product.

To correct the issue before the upgrade:

Remove the display conditions on the General subpage before the upgrade and redefine the display conditions after the upgrade.

Note: If the preupgrade server is on Version 13.0 or a later service pack, you can handle the issue in a different manner. Before you start the upgrade, edit the General Action menu. Move any action that is listed there from the Available Actions list to the Selected Actions list and save. After the upgrade is complete, you can remove any unwanted actions.

To correct the issue after the upgrade:

Create an action menu with following details:
- Menu Name: General
- Menu Code: general
- Description: General
Move the following out-of-the-box actions from the Available Actions to the Selected Actions list:
- Add to My Projects
- Copy Project from Template
- Remove from My Projects
- Go to Links Page
- Go to Notes Page

Note: For more information about creating an action menu, see the Studio Developer Guide.

Upgrade Stops if OBS Unit Names Have Special Characters

If the OBS unit names, department names, or location names include special characters, the upgrade to Release 13.2 stops during the pre-installation checker step. This case applies to an upgrade to Release 13.2 from any previous release.

The following special characters cannot be used in OBS unit names, department names, or location names:

Slash (/)
Colon (:)
Double quote (")
Less than (<)
Greater than (>)

We recommend running the following query to identify the OBS names with the special characters before starting the upgrade. If the query returns any rows, OBS names with special characters are present in the PRJ_OBS_UNITS table. We recommend that you review all returned OBS unit, department, or location names and update them with valid names.

For MSSQL:

   SELECT * FROM PRJ_OBS_UNITS 
        WHERE NAME LIKE '%/%' OR 
		      NAME LIKE '%:%' OR 
			  NAME LIKE '%["]%' OR
			  lower(NAME) LIKE '%&amp;' + 'quot;%' OR
			  lower(NAME) LIKE '%&' + 'gt;%'  OR 
			  lower(NAME) LIKE '%&' + 'lt;%' OR  
			  NAME LIKE '%<%' OR 
			  NAME LIKE '%>%'

For Oracle:

   SELECT * FROM PRJ_OBS_UNITS 
		WHERE NAME LIKE '%/%' OR 
			  NAME LIKE '%:%' OR 
			  NAME LIKE '%"%' OR
			  lower(NAME) LIKE '%&amp;' || 'quot;%'  OR 
			  lower(NAME) LIKE '%&' || 'gt;%'  OR 
			  lower(NAME) LIKE '%&' || 'lt;%' OR  
			  NAME LIKE '%<%' OR 
			  NAME LIKE '%>%'

To review the use of special characters in the filter expressions (power filters), we also recommend using the following query. Update any OBS names the query returns with the appropriate valid names.

For MSSQL:

  SELECT * FROM ODF_FILTER_EXPRESSIONS exprs, prj_obs_units units
  WHERE exprs.expression like '%'+cast(units.id as nvarchar)+'%'+units.name+'%'
    and (units.name LIKE '%/%' OR
		  units.name LIKE '%:%' OR
		  units.name LIKE '%["]%' OR
		  lower(units.name) LIKE '%&amp;' + 'quot;%' OR
		  lower(units.name) LIKE '%&' + 'gt;%'   OR
		  lower(units.name) LIKE '%&' + 'lt;%' OR 
		  units.name LIKE '%>%'  OR
  units.name LIKE '%<%' )

For Oracle:

  SELECT * FROM ODF_FILTER_EXPRESSIONS exprs, prj_obs_units units
  WHERE exprs.expression like '%'||units.id||'%'||units.name||'%'
    and (units.name LIKE '%/%' OR
                                  units.name LIKE '%:%' OR
		  units.name LIKE '%"%' OR
		  lower(units.name) LIKE '%&amp;' || 'quot;%'  OR
		  lower(units.name) LIKE '%&' || 'gt;%'   OR
		  lower(units.name) LIKE '%&' || 'lt;%' OR 
		  units.name LIKE '%>%'  OR
		  units.name LIKE '%<%' )

Automatic Update to OBS Names During Upgrade

If an OBS name contains a left curly bracket ({) or a right curly bracket (}), left or right parentheses replace the characters during the upgrade.

Example: The OBS name External{Department} becomes External(Department) after the upgrade.

Report Instance Export from the Report Library

You cannot export report instances from the report library when the BusinessObjects server is configured with CA Clarity PPM installed on a Windows 2012 server. BusinessObjects Enterprise 3.1 SP5 is not supported for Windows 2012.

Note: Installing the BusinessObjects server on a supported configuration does not avoid this issue. The .jar files that are used for the CA Clarity PPM integration are not compatible with Windows 2012.

Orphan Records in Table CMN_SEC_ASSGND_OBJ_PERM for MSSQL Users

A recent change prevents the creation of orphan records in the table CMN_SEC_ASSGND_OBJ_PERM. However, for MSSQL users, pre-existing orphan records can sometimes remain. You can search for orphan records and can remove them from the table after the upgrade to Release 13.2 is complete.

To verify that orphan records exist in the table, run the following query:

select COUNT(*)  from (select object_instance_id from cmn_sec_assgnd_obj_perm p
    where p.object_ID = 50680 and object_instance_id not in 
(select ID from BPM_RUN_PROCESSES)) q

The number value that the query returns indicates the number of orphan records.

To clean up orphan records, invoke the following upgrade script from <clarity_install_dir>/bin using dbpatch:

POSTUPGRADE_57954_MSSQL_DEL_PROC_INST_ASSGND_OBJ_PERM.xml

Use the following command:

dbpatch -install -file <CLARITY_INSTALL_DIR>\upgrade\13.2.0\component\postupgrade\POSTUPGRADE_57954_MSSQL_DEL_PROC_INST_ASSGND_OBJ_PERM.xml -apply

Note: The length of time the query runs is dependent on the number of orphan records to be deleted.

CA Clarity PPM Upgrade and Oracle Enterprise Table Compression

If you are using the Oracle Enterprise Edition compression feature, disable the compression feature before starting the CA Clarity PPM upgrade. If the compression feature is enabled, the upgrade fails with the following Oracle database error:

[CA Clarity][Oracle JDBC Driver][Oracle]ORA-39726: unsupported add/drop column operation on compressed tables

The following procedure explains how to get ready for the upgrade by disabling compression. Once the procedure is complete, you can proceed with the upgrade. When the upgrade has successfully completed, you can compress the tables again.

To prepare for the upgrade, complete the following steps:

Identify compressed tables by executing the following query:

SELECT TABLE_NAME, COMPRESSION FROM USER_TABLES WHERE COMPRESSION='ENABLED';

Disable compression. Run the output of this query. Keep this list handy, so that these tables can be compressed again after the upgrade.
```
SELECT 'ALTER TABLE ' || TABLE_NAME || ' MOVE NOCOMPRESS;'  FROM USER_TABLES WHERE COMPRESSION='ENABLED';
```

Rebuild the unusable indexes. Run the output of this query:

SELECT 'ALTER INDEX ' || INDEX_NAME || ' REBUILD;' FROM USER_INDEXES WHERE STATUS='UNUSABLE';