DWH Incremental fails with ORA-00600 on a custom TSV on Cost Plan
search cancel

DWH Incremental fails with ORA-00600 on a custom TSV on Cost Plan

book

Article ID: 383339

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Custom TSV fields will fail DWH Incremental as they are taken as NK_CURVE in 16.2.3 although there is no support for SQL Curve functionality in DWH yet

STEPS TO REPRODUCE:
1.    On a new vanilla environment go to Studio – Objects – Cost Plan Detail
2.    Create a new field Test_TSV - Time-varying – Fiscal
3.    Add API attribute ID
4.    Now add the attribute to the Create view for Cost Plan Detail
5.    On a project create a new cost plan, add a manual entry to it and fill the values
6.    Enable the field for DWH

Expected Results : The field to be added and DWH to run successfully

Actual Results: Load Data Warehouse - Incremental fails with error 

Error in logs:

ORA-04052: error occurred when looking up remote object NIKU.DWH_COSTPLAN_V@PPMDBLINK
ORA-00600: internal error code, arguments: [17200], [TEST_TSV], [121], [], [], [], [], [], [], [], [], []

This was working on 16.2.2 and does not on 16.2.3

Environment

16.2.3

Cause

Starting 16.3.0 we are adding Beta support for SQL curve fields and there will be a Include Sql Curve Data (Beta) flag in System Options that you can check to make your field come as NK_CURVE. Then the field will also go into a specific table that is used just for the curves, DWH_FIN_PLAN_CRV_FACTS.

This is a reproducible issue with TSV fields being added to the DWH_COSTPLAN_V as NK_CURVE, this is a bug which is no longer reproducible in 16.3.0. We are adding support for SQL curve in 16.3.0 and before that it should not be doing this.

Resolution

Fixed in 16.3.0 as part of adding Beta support for SQL curve fields 

  • On 16.3.0 you can still keep Sql Curve Data (Beta) flag option unchecked and use the fields as fact data. On 16.3.0 DWH_COSTPLAN_V does not get the fields if SQL Curve Data system option is unchecked

Workaround on 16.2.3:

Option 1: Disable the field from DWH

Option 2: 

  1. Check the field to set it to enabled in DWH
  2. Edit the DDL for DWH_COSTPLAN_V:  remove the custom field from DWH_COSTPLAN_V
  3. Save and Recompile the view DWH_COSTPLAN_V
  4. Run Load Data Warehouse Full and Incremental Load