AnsweredAssumed Answered

Manager ID as decimal number - can't save PM on project

Question asked by matej256 on Jan 11, 2017
Latest reply on Jan 16, 2017 by Dave_3.0

Hi All, 

 

I've quite an urgent issue which I'd like to ask for your help. 
I know the root-cause but have no clue where it's coming from. 

 

Here is my analysis (We are on Clarity 13.3):

 

When tried to update PM at project, we got an error:

 

When checked app logs, following error is it:

ERROR 2017-01-11 15:03:23,071 [http-bio-29082-exec-346] niku.xql2 (clarity:admin:86798863__3E6E8816-7A1F-42AA-A33C-545FBB7AC171:projmgr.projectPropertiesPost) Internal Processing exception
com.niku.union.persistence.PersistenceException:
SQL error code: 1422
Error message: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01422: exact fetch returns more than requested number of rows
ORA-06512: at "NIKU.ODF_AUD_5003062_FCT", line 5
ORA-06512: at "NIKU.T_PROJECT_IINV_INVESTMENTS", line 56
ORA-04088: error during execution of trigger 'NIKU.T_PROJECT_IINV_INVESTMENTS'

Executed:
/*clarity\admin|projmgr.projectPropertiesPost|odf-pmd.project.update.map|odf-pmd.project.update.inv_investments*/
update inv_investments set schedule_start = decode(?, 2, schedule_start, ?), ......MANAGER_ID = decode(?, 2, MANAGER_ID, ?), RISK = decode(?, 2, RISK, ?) ....
.
.
.
Using input:
{forecast_mirr=, planned_cst_capital_total=.... manager_id=5295796.0, last_updated_by_p=5005745.0, forecast_cst_total=, last_updated_date=Tue Jan 10 17:03:23 ...... hen_project_hist_com=, hen_main_benef=, odf_pk=5752583.0}

 

The root-cause of this error is Manager_ID value which instead of standard number(integer) value has a decimal value instead! There ale also other decimal values instead of number (last_updated_by, odf_pk). 

 

Note: Trigger NIKU.T_PROJECT_IINV_INVESTMENTS where the log mentioned the error contained update of CMN_AUDITS table where Project Manager attribute is audited. It is executed function NIKU.ODF_AUD_5003062_FCT there behind which is a query which selects Project managers from cmn_sec_users table. IDs in cmn_sec_users table are standard type number and we haven't done any changes there of course

 

Have you ever seen that and do you know what source/setting this can come from? 

 

Thanks a lot for your hints!

 

Matej

Outcomes