search cancel

Datamart Job Failing - value too long / Bulk Bind

book

Article ID: 224444

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Datamart Extraction Job Failing after upgrade to 15.9.3 - Error in NBI_PROJECT_CURRENT_FACTS_SP - Inserting into NBI_PROJECT_CURRENT_FACTS: value too long for type character varying(240)

PostgreSQL error message:

Error in NBI_PROJECT_CURRENT_FACTS_SP - Inserting into NBI_PROJECT_CURRENT_FACTS: value too long for type character varying(240)

Oracle error message: 

java.sql.SQLException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-20000: Error in NBI_EXTRACT_SP - Executing  NBI_EXTR_PCF_SP: ORA-20000: Error in NBI_EXTR_PCF_SP - executing NBI_PROJECT_CURRENT_FACTS_SP: ORA-20000: Error in NBI_PROJECT_CURRENT_FACTS_SP - Calling NBI_PROJECT_FORECAST_SP since there are projects with Forecast: ORA-06502: PL/SQL: numeric or value error: Bulk Bind: Truncated Bind
ORA-06512: at "NIKU.NBI_EXTRACT_SP", line 362
ORA-06512: at line 1

Steps to Reproduce: 

  1. Create an Investment with Name length 256 characters as per UI allowance (This issue is with any investment name that is longer than 240 characters) 
  2. Run Datamart Extraction job 

Expected Results: Datamart Extraction job should succeed. 

Actual Results: Datamart Extraction job is failing with the errors above. 

Cause

DE62599 

Workaround:

  • To find out which Investment is causing the problem, run the query:

select odf_object_code, code,length(name) 
from inv_investments
order by length(name)desc

  • Any length over 240 character will not work, please update the name to shorten it and run Datamart Extraction again.

Environment

Release : 15.9.3

Resolution

  • Fixed in Release 16.0.0
  • Fixed in Release 15.9.3 Patch #1 (15.9.3.1) 

Additional Information

Powered by Wolken Software