![primavera p3 process missing from startup primavera p3 process missing from startup](https://cdn.slidesharecdn.com/ss_thumbnails/82813533-6bd8-47b7-8ff6-c4cb487f239f-160613173909-thumbnail.jpg)
Partition inspection_pre_2008 values less than (to_date('','mm/dd/yyyy')), Partition inspection_pre_2007 values less than (to_date('','mm/dd/yyyy')), Partition inspection_pre_2006 values less than (to_date('','mm/dd/yyyy')), Partition inspection_pre_2005 values less than (to_date('','mm/dd/yyyy')), Partition inspection_pre_2004 values less than (to_date('','mm/dd/yyyy')), Partition inspection_pre_2003 values less than (to_date('','mm/dd/yyyy')), Partition inspection_pre_2002 values less than (to_date('','mm/dd/yyyy')), Partition inspection_pre_2001 values less than (to_date('','mm/dd/yyyy')), Partition inspection_pre_2000 values less than (to_date('','mm/dd/yyyy')), Subpartition by hash (inspection_Type_id) Partition by range (Actual_Start_Date) interval (NUMTOYMINTERVAL(1,'MONTH')) But now I am wondering what is going on with the stats.Īctual_Start_Date DATE default to_date('','mm/dd/yyyy'),ĬONSTRAINT PK_Inspection PRIMARY KEY (Inspection_ID),Ĭonstraint inspection_announced_check check (is_announced in ('Y','N')) Of course I could try to rethink my position on partitioning this table and whether or not it is the best solution. If I disable row movement and re-run stats everything still comes up as zeros.
#PRIMAVERA P3 PROCESS MISSING FROM STARTUP UPDATE#
If I enable row movement, update some records and re-run the stats, the num_rows column is always zero. If I gather table stats on the partitioned table, I get value. When you attempt to update the value you must first enable row movement and this is where I think my problem lies. However, the date isn't known at insert oracle doesn't know where to put the record - so I default the value. I have a table that is queried largely by a column titled actual_start_date - I would really like to partition this table by the actual start date to aid in performance.