MDP_MATRIX Table Not Null Columns Getting Changed After Re-org (Doc ID 2248996.1)

Last updated on JUNE 05, 2017

Applies to:

Oracle Demantra Demand Management - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

In the MDP_MATRIX table , LOCATION_ID and ITEM_ID columns should be not null . But it was found out to be Null = Y after doing a table re org. Customer tried to make it Not Null . There we 2 constraints on these 2 columns. SO they dropped them and made them not null.


Again we performed re-org , and we can see the Null =Y on these 2 columns and also 2 new constraints are created. Could you provide permanent solution on this ?

Steps done change before reorg to make columns not null.

SQL> alter table dem.mdp_matrix modify location_id number(10) not null;
alter table dem.mdp_matrix modify location_id number(10) not null
  *
ERROR at line 1:
ORA-01442: column to be modified to NOT NULL is already NOT NULL


SQL> alter table dem.MDP_MATRIX drop CONSTRAINT SYS_C002240019;

Table altered.

SQL> alter table dem.mdp_matrix modify location_id number(10) not null;

Table altered.

SQL> alter table dem.mdp_matrix modify item_id number(10) not null;
alter table dem.mdp_matrix modify item_id number(10) not null
  *
ERROR at line 1:
ORA-01442: column to be modified to NOT NULL is already NOT NULL


SQL> alter table dem.MDP_MATRIX drop CONSTRAINT SYS_C002240020;

Table altered.

SQL> alter table dem.mdp_matrix modify item_id number(10) not null;

Table altered.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms