Clarity

  • 1.  The portlet projmgr.weeklyDetail throws System Error when accessed via Home->Resource Planning->By Time Period

    Posted Apr 13, 2015 10:35 AM

    Hi Team,

     

    We have recently upgraded from 12.1.1 to 14.1, as a part of general testing we found an issue in Resource Planning->By Time Period tab.

    When we navigate to Home->Resource Planning->By Time Period Tab, the following error is thrown -

    "System Error. Contact System Administrator"

    This page gets the data from the Portlet projmgr.weeklyDetail, which in turn gets data from the Data Provider - Team Allocations.

     

    The app-ca.log contains the following error -

    ERROR 2015-04-13 08:21:28,682 [http-bio-9980-exec-680] niku.xql2 (clarity:X877935:26257222__CD8B93A0-4961-42DD-BB07-9BC53A7F71E2:5151498) Exception in processing

    java.lang.ArrayIndexOutOfBoundsException

    ERROR 2015-04-13 08:21:28,682 [http-bio-9980-exec-680] niku.xql2 (clarity:X877935:26257222__CD8B93A0-4961-42DD-BB07-9BC53A7F71E2:5151498) Exception in processing

    java.lang.ArrayIndexOutOfBoundsException

    ERROR 2015-04-13 08:21:28,682 [http-bio-9980-exec-680] niku.xql2 (clarity:X877935:26257222__CD8B93A0-4961-42DD-BB07-9BC53A7F71E2:5151498) Internal Processing exception

    java.lang.ArrayIndexOutOfBoundsException

    ERROR 2015-04-13 08:24:40,429 [http-bio-9980-exec-690] niku.xql2 (clarity:X877935:26257222__CD8B93A0-4961-42DD-BB07-9BC53A7F71E2:nna_alloc_time_period) Exception in processing

    java.lang.ArrayIndexOutOfBoundsException

    ERROR 2015-04-13 08:24:40,429 [http-bio-9980-exec-690] niku.xql2 (clarity:X877935:26257222__CD8B93A0-4961-42DD-BB07-9BC53A7F71E2:nna_alloc_time_period) Exception in processing

    java.lang.ArrayIndexOutOfBoundsException

    ERROR 2015-04-13 08:24:40,429 [http-bio-9980-exec-690] niku.xql2 (clarity:X877935:26257222__CD8B93A0-4961-42DD-BB07-9BC53A7F71E2:nna_alloc_time_period) Internal Processing exception

    java.lang.ArrayIndexOutOfBoundsException

     

    I think this is a OOTB functionality which is failing only after upgrade, could someone please let us know what could be the issue here.

     

    Regards,

    Syed



  • 2.  Re: The portlet projmgr.weeklyDetail throws System Error when accessed via Home->Resource Planning->By Time Period
    Best Answer

    Broadcom Employee
    Posted Apr 13, 2015 10:53 AM

    Hi Syed,

     

    This looks to be a data specific issue. It will probably be related to some dates that are out of the bounds. Check if all projects start and finish dates look alright in inv_investments table.

    To troubleshoot it best I would recommend you to raise a case with CA Support.

     

    Kind Regards

     

    Nika Hadzhikidi

    CA Technologies

    Principal Support Engineer



  • 3.  Re: The portlet projmgr.weeklyDetail throws System Error when accessed via Home->Resource Planning->By Time Period

    Posted Apr 15, 2015 06:12 AM

    Hi Nika,

     

    Thank you Nika for the Quick response.

     

    We are getting this issue post upgrade, in 12.1.1.1208 we did not get any such issue, but after we upgraded to 14.1 we are facing this issue.

    Also regarding the start and finish dates of the investments, what exactly do I need to check.

     

    I will raise a CA ticket as suggested.

     

    Thanks and Regards,

    Syed



  • 4.  Re: The portlet projmgr.weeklyDetail throws System Error when accessed via Home->Resource Planning->By Time Period

    Broadcom Employee
    Posted Apr 23, 2015 04:17 PM

    Hi Syed,

     

    I saw you already solved the issue, glad it worked for you. Normally we would check that no start/finish date on an investment is going outside of the range. What you could do (or anyone that has a similar issue in future) is run a query on the projects:

     

    Example for Oracle:

     

    select * from prj_projects p, inv_investments i where

    p.prid=i.id

    and

    p.prstart not between to_date('1980-01-01','YYYY-MM-DD')   

             and to_date('2080-12-31','YYYY-MM-DD')

    or p.prfinish not between to_date('1980-01-01','YYYY-MM-DD')   

             and to_date('2080-12-31','YYYY-MM-DD')

     

     

    Usually we see typos such as year 2105 or similar, and this is causing the issue.

     

    Kind Regards

     

    Nika Hadzhikidi

    CA Technologies

    Principal Support Engineer



  • 5.  Re: The portlet projmgr.weeklyDetail throws System Error when accessed via Home->Resource Planning->By Time Period

    Posted Apr 23, 2015 11:07 PM

    Thanks for sharing this, Nika

     

    Regards

    NJ



  • 6.  Re: The portlet projmgr.weeklyDetail throws System Error when accessed via Home->Resource Planning->By Time Period

    Posted Apr 24, 2015 07:35 AM

    Hello Nika,

     

    Thanks a lot for the query but i checked all the projects in last week itself and one project start date was showing as '03/20/0215'

     

    I changed the start date and the issue got resolved.

     

    Can we check the same for tasks, resources, plans with Dates inserted like this with Query??

     

    Could you please help me in this regard.

     

    Regards

    Syed



  • 7.  Re: The portlet projmgr.weeklyDetail throws System Error when accessed via Home->Resource Planning->By Time Period

    Broadcom Employee
    Posted Apr 24, 2015 10:47 AM

    Hi Syed,

     

    Glad to hear your issue is resolved, and it was indeed caused by a typo in the project start date.

    Unfortunately there are too many tables for tasks, resources, plans etc. to make a sense for me to create queries for all of them. I would advise you to use the query above as example, you can transform it like this (replace TABLENAME, START_COLUMN, FINISH_COLUMN with the corresponding ones for the tables you want to check):

     

    select * from TABLENAME where START_COLUMN not between to_date('1980-01-01','YYYY-MM-DD')    and to_date('2080-12-31','YYYY-MM-DD')
    or FINISH_COLUMN not between to_date('1980-01-01','YYYY-MM-DD')   and to_date('2080-12-31','YYYY-MM-DD')

     

    Since now there are way too many tables to go through for such a checkup, you should not worry to verify anything else if you have no error appearing in Clarity. This issue is quite rare, and is most usually happening on projects. If the error reoccurs again, or on another portlet, etc. , feel free to raise a case with us in Support : we will get traces and see which field exactly is affected, without you having to go through and check everything table by table.

     

    Hope this helps,

     

    Kind Regards

     

    Nika Hadzhikidi
    CA Technologies
    Principal Support Engineer



  • 8.  Re: The portlet projmgr.weeklyDetail throws System Error when accessed via Home->Resource Planning->By Time Period

    Posted Apr 24, 2015 01:39 PM

    Thanks a lot Nika..

     

    But I have a question..

     

    Do we have any constrain in clarity like the start date and finish date should be in limits..?

     

    If so then what is the date limit CA recommends..?

     

    If it goes beyond the limit (too far old dates) and we get these kind of error..?

     

    Could you please confirm on this..

     

    Thanks in advance.

     

    Regards

    Syed



  • 9.  Re: The portlet projmgr.weeklyDetail throws System Error when accessed via Home->Resource Planning->By Time Period

    Broadcom Employee
    Posted Apr 27, 2015 06:03 PM

    Hi Syed,

     

    There is no comprehensive list of the date limits in Clarity. We recommend you to ensure you use common sense, you would not need projects before y.1900, in example.

    Again, those issues are really rare and always result from a user typo rather than not following the practices.

     

     

    I hope this helps,

     

    Kind Regards

    Nika Hadzhikidi

    CA Technologies

    Principal Support Engineer



  • 10.  Re: The portlet projmgr.weeklyDetail throws System Error when accessed via Home->Resource Planning->By Time Period

    Posted Apr 28, 2015 05:02 AM

    Thanks a lot Nika

     

    I will update users not to use out of range dates..

     

    Regards

    Syed