This section provides known issues for CA Clarity PPM.
This issue applies only to upgrades from a 12.x release to the current release.
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 are required to correct the data issue before resuming the upgrade process. An upgrade check script runs and alerts you that this problem exists.
To identify possible data issues before you start the upgrade, run the following query:
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
)
This issue applies only to upgrades from a 12.x release to the current release.
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 that the information is 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.
A portion of the upgrade relies on the English locale when it is importing content using the XML Open Gateway (XOG). 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.
CA Clarity PPM does not support the ability to resume during an upgrade. We recommend that you run the Checkinstall utility and review the reports that it generates before starting. To reduce the possibility of a failure, correct any errors that the Checkinstall reports indicate.
If your upgrade fails, review the logs and the Checkinstall post-installation reports to determine the reason for the failure. Then, restore the working preupgrade version and database, correct the failure, and restart the upgrade.
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.
In some cases, the General Action menu does not appear after an upgrade. This issue occurs on the Project object when the following conditions exist:
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:
Note: For more information about creating an action menu, see the Studio Developer Guide.
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.
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.
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 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.3.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.
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 prepare 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:
SELECT TABLE_NAME, COMPRESSION FROM USER_TABLES WHERE COMPRESSION='ENABLED';
SELECT 'ALTER TABLE ' || TABLE_NAME || ' MOVE NOCOMPRESS;' FROM USER_TABLES WHERE COMPRESSION='ENABLED';
SELECT 'ALTER INDEX ' || INDEX_NAME || ' REBUILD;' FROM USER_INDEXES WHERE STATUS='UNUSABLE';
In some instances, when auditing is enabled for specific attributes on the Project object, only the insert operation is reported in the audit trail. The update operation does not show for the attributes. The affected attributes include:
During a generic J2EE installation, the nsa.ear file installs CA Clarity System Administration. Once you start CA Clarity System Administration, you can see the database information after you specify your database credentials. However, if you are installing on WebSphere, the database information is not available. Neither the Install History page nor the Installation Overview page in CA Clarity System Administration shows the database as installed, even though it is.
This behavior does not affect your ability to complete the installation and use the application.
Upgrade Action: To get details of the database, run the query CMN_INSTALL_HISTORY.
An error is received during an upgrade for a Generic J2EE application server (IBM WebSphere or Oracle WebLogic). Because the vendor is generic, the prompt for the J2EE home directory does not appear and the j2ee.home property is not set. Without a j2ee.home setting, an error occurs in the installation process.
Upgrade Action:
Set the following values in the <installer>/install.properties file:
If you are upgrading to Release 13.2 or 13.3 with a non-RAC database, the network between the application server and the database disconnects during the upgrade. You see the following error:
FATAL 2013-07-17 13:14:46,376 [main] union.persistence Failed to initialize Context properties 7/17/13 1:14 PM (admin) java.sql.SQLNonTransientConnectionException: [CA Clarity][Oracle JDBC Driver]Connection reset 7/17/13 1:14 PM (admin) at com.ca.clarity.jdbc.oraclebase.ddcg.b(Unknown Source) 7/17/13 1:14 PM (admin) at com.ca.clarity.jdbc.oraclebase.ddcg.a(Unknown Source) 7/17/13 1:14 PM (admin) at com.ca.clarity.jdbc.oraclebase.ddcf.b(Unknown Source) 7/17/13 1:14 PM (admin) at com.ca.clarity.jdbc.oraclebase.ddcf.a(Unknown Source) 7/17/13 1:14 PM (admin) at com.ca.clarity.jdbc.oraclebase.ddcf.a(Unknown Source) 7/17/13 1:14 PM (admin) at com.ca.clarity.jdbc.oracle.net8.dd g.b(Unknown Source)
Upgrade Action:
Before you start the upgrade, complete the following steps:
The JDBC text box appears.
ConnectionRetryCount=400;ConnectionRetryDelay=3
The following CA Clarity PPM issues occur for users who are using this particular version of Chrome (Version 30.0.1599.66 m):
These issues do not appear in other browsers and have been found only in this version of Chrome.
If you use Chrome, the following issues can occur when you print a Gantt chart:
This issue does not occur in Internet Explorer or Firefox.
Setting the Maximum XML Node Limit value to -1 in CA Clarity System Administration disables the XOG Governor limit. Currently, entering this value causes XOG write operations to throw the following error:
XOG-9060: The system cannot import this instance with the current configuration. Increase the 'Maximum XML Nodes' value in the CSA and try again.
Workaround: Set the Maximum XML Node Limit to 10^15.puttin
This section provides add-in enhancements for Release 13.3.
The following Release 13.3 changes were made for the Microsoft Project Interface:
The CA Microsoft Project Interface supports the Microsoft Project Resource Leveling feature. If you do resource leveling in Microsoft Project and save the project into CA Clarity PPM, the resource leveling information is kept in the CA Clarity PPM database. The next time that you open the project in Microsoft Project from CA Clarity PPM, the resource leveling information that you entered is available.
Note: See the Microsoft Project documentation for more information about resource leveling.
The Microsoft Project Interface was tuned to improve performance in the following areas:
Smaller projects show performance improvements for the import and export actions. Projects that have large time-scaled value data such as Assignment Actuals and ETC, or Baseline Cost and Usage Curve may not show the expected improvement.
CA Clarity PPM provides a specific Java Runtime Environment (JRE) for use by Microsoft Project. The JRE is copied to the hard drive in the Microsoft Project Interface installation directory on the end-user workstation. The JRE is used for the Microsoft Project Interface integration and is independent of the JRE used for the Windows workstation.
The Microsoft Project Interface uses only the internal JRE version that is provided which we certify to be compatible. This approach eliminates issues that arise when the workstation Windows installation of the JRE is not the correct version or the JRE is missing. An IT department no longer has to update a JRE version when deploying the Microsoft Project Interface.
In this release, the Microsoft Project Interface can be installed silently without any user intervention.
In previous releases, when you ran the Microsoft Project add-in setup, the Windows operating system displayed a message that the publisher could not be verified. You were then asked if you wanted to install the customization.
This message is no longer displayed. You receive a confirmation message after the add-in is successfully installed. The Microsoft Project Interface add-in setup closes the installer window automatically.
The Microsoft SharePoint Connector Release 3.0.0 is new. If you have the Connector for Microsoft SharePoint Release 2.0.2 or earlier installed, you cannot upgrade the existing connector. You are required to install the new Release 3.0.0 connector. The existing connector was based on SharePoint 2010, and the new Release 3.0.0 connector is based on SharePoint 2013.
This section provides Administration enhancements for Release 13.3.
When the License Information portlets were first introduced in Release 12.1, the License Type Names were defined as:
Effective with Release 13.2 Generic Patch 4 and Release 13.3, the labels for the License Type names are changing. The functionality and use remain the same.
|
Old Name |
New Name |
Functionality |
|---|---|---|
|
Managers |
Full |
Users have the full use of product functionality. |
|
Team Members |
Restricted |
Users have specified limited use of product functionality. |
|
Enterprise Visibility Option |
View Only |
Users can view information but cannot create or edit information except for ideas and incidents. |
One extra user type is available for customers who own CA Clarity Agile. Vision Timesheet users have the right to enter time through the CA Clarity PPM and Agile Vision integration. All users are named, not concurrent. Only active users are counted as licensed users.
To see the new user types, open the Administration menu, and under Organization and Access, click License Information.
Upgrade Action: None
A process monitor has been added to CA Clarity PPM. The monitor ensures certain process types that are known to cause systemic problems are identified and put on hold automatically to prevent a system interruption. A message displays on the process validation page for processes that are flagged as problematic by the process engine.
Upgrade Action: None
The Global Audit Trail page was updated for this release. This page is available in the Data Administration section of the Administration menu. The updates do not affect the instance audit trail pages available to users.
The following updates were made:
Upgrade Action: None
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|