Clarity: PMO Accelerator Project Manager Schedule Dashboard Portlet generates an error message

Document ID : KB000049688
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

When we go into the General Overview > Project Dashboard, the Project Manager Schedule Dashboard Portlet is only showing a red 'Error' message. No other error message details are seen on the page. In the application log file, a more descriptive error message is shown:

ORACLE

ERROR 2012-06-11 18:15:08,306 [http-14001-29] dal.NSQLClient
(clarity:usertest:5336120__81A009DB-998D-443D-926B-B7AAF6C573E0:copProjectManagerDashboar)
Unable to retrieve NSQL cube. NSQLException was thrown.
com.niku.union.persistence.nsql.NSQLException:
com.niku.union.persistence.PersistenceException:
SQL error code: 1476
Error message: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01476: divisor is equal to zero
ORA-06512: at "CLARITY.COP_DAYS_LATE_PCT_FCT", line 56

MSSQL ERROR

NPT-0103: Error when trying to execute the query. Native message: [CA Clarity][SQLServer JDBC Driver][SQLServer]Divide by zero error encountered.

Here is one use-case reported by a customer that seems to generate this error message.

Steps to Reproduce:

  1. Login to Clarity v13.0 with PMO Accelerator 3.0 installed

  2. Perform a XOG write action to create a project that has a Finish Date BEFORE the Start Date (ie. Start Date = 6/13/2012, Finish Date = 6/12/2012)

    NOTE: It is not possible to have a Finish Date BEFORE a Start Date in the application user interface. The project XOG write action sets the date/timestamp to 00:00:00 and is allowing the Finish Date to be set before the Start Date

  3. Navigate to General Overview > Project Dashboard Tab

Expected Result: The portlet should display the project data without any errors
Actual Result: The portlet does not display project data and shows an error message

Solution:

Workaround:
Contact CA Technical Support for a workaround to implement an update to the database function on the portlet. Reference PMO-870.

Status/Resolution:
This issue is documented as PMO-870 and is resolved in PMO 3.1

Keywords: CLARITYKB, PMO-870, clarity13resolved, pmo31resolved.