Plan Partition Corruption - Plan Partitions that exist in ALL_TAB_PARTITIONS but do not exist in MSC_PLAN_PARTITIONS
Last updated on MARCH 09, 2018
Applies to:Oracle Advanced Supply Chain Planning - Version 22.214.171.124 and later
Information in this document applies to any platform.
When running the following SQL, we've noticed that we have Plan Partitions information in the ALL_TAB_PARTITIONS table that does not exist in MSC_PLAN_PARTITIONS:
select distinct substr(partition_name,instr(partition_name,'_',-1,1)+1) "Partition Number", DECODE(INSTR(partition_name,'__'),0,'PLAN','INST') "Partition Type"
where table_name like 'MSC_%'
AND table_name NOT IN
(SELECT DISTINCT table_name
WHERE table_name LIKE 'MSC%F')
and partition_name not like ('ST_%')
and DECODE(INSTR(partition_name,'__'),0,'PLAN','INST') = 'PLAN'
and TO_NUMBER(substr(partition_name,instr(partition_name,'_',-1,1)+1)) != ALL(select distinct PLAN_ID from msc_plan_partitions)
and substr(partition_name,instr(partition_name,'_',-1,1)+1) NOT IN ('0','999999');
We would like to clean this information up to prevent errors when running ASCP Plans and to prevent errors when trying to create new Plan Partitions.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms