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. 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.
This release 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 are present:
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.
Some special characters in OBS unit names, department names, or location names are automatically replaced with hyphens (-) during the preinstallation check before an upgrade.
The following special characters are replaced:
If you do not want hyphens placed in names with special characters, update the names before you begin the upgrade process. You can also manually replace the hyphens with the special characters after the upgrade is done.
You can run the following query to identify the OBS names that contain special characters. 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 determine whether to update them.
For MSSQL:
SELECT * FROM PRJ_OBS_UNITS
WHERE NAME LIKE '%/%' OR
NAME LIKE '%:%' OR
NAME LIKE '%["]%' OR
lower(NAME) LIKE '%&' + '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 '%&' || '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 '%&' + '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 '%&' || 'quot;%' OR
lower(units.name) LIKE '%&' || 'gt;%' OR
lower(units.name) LIKE '%&' || 'lt;%' OR
units.name LIKE '%>%' OR
units.name LIKE '%<%' )
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 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:
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 or 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). 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, 13.3, or 14.1 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 a Chrome browser, 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.
During an upgrade from a 12.x release to a 13.0 or higher release, the Rate Matrix Extraction job’s scheduled instances and job logs are deleted.
Upgrade action: Reschedule the Rate Matrix Extraction job.
Service Pack 1 for Microsoft Project 2013 has a known issue that affects how it works with CA Clarity PPM. The following behavior results when the service pack is installed:
For more information, see the following Knowledge Base articles on CA Support Online: TEC610737, TEC615024.
Upgrade Action: Do not apply Service Pack 1 to Microsoft Project 2013. If you have applied this service pack, roll back to Microsoft Project 2013 without any service packs.
|
Copyright © 2014 CA.
All rights reserved.
|
|