PDCRADMIN.PDCR_PPI_Maintenance_All functionality and behavior.

Tools & Utilities

PDCRADMIN.PDCR_PPI_Maintenance_All functionality and behavior.

Hi Team,

 

I have one doubt .

 

The procedure  “ CALL PDCRADMIN.PDCR_PPI_Maintenance_All(NULL, '2019-12-31', MESSAGE); executed scusessfully.  I can see the changes on pdcrdata.PDCR_Table_Retention but the partition extensions are not reflected on table DDL. Can you share the  value behavior of (NULL, '2019-12-31', MESSAGE) input and output Messages.

 

 PDCR_PDCR_PPI_Maintenance_All.jpg

CREATE SET TABLE PDCRDATA.TDWMUtilityStats_Hst ,FALLBACK ,

     NO BEFORE JOURNAL,

     NO AFTER JOURNAL,

     CHECKSUM = DEFAULT,

     DEFAULT MERGEBLOCKRATIO

     (

      LogTimestamp TIMESTAMP(0) WITH TIME ZONE NOT NULL,

      UtilityType CHAR(10) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL COMPRESS ('ARC       ','BAR       ','CSP FLoad ','FLoad     ','FastExport','JDBC FExp ','JDBC FLoad','JDBC MLoad','ML/FL     ','MLoad     ','SA FExp   ','SA FLoad  ','SA MLoad  ','TPT Export','TPT Load  ','TPT Update'),

      UtilityCount SMALLINT NOT NULL COMPRESS (0 ,1 ,2 ,3 ,4 ,5 ,6 ,7 ,8 ,9 ,10 ,11 ,12 ,13 ,14 ,15 ),

      UtilityLimit SMALLINT NOT NULL COMPRESS (0 ,1 ,2 ,3 ,4 ,5 ,6 ,7 ,8 ,9 ,10 ,11 ,12 ,13 ,14 ,15 ))

PRIMARY INDEX NUPI_TDWMUtilityStats_Hst ( LogTimestamp )

PARTITION BY RANGE_N(CAST((LogTimestamp ) AS DATE AT TIME ZONE INTERVAL '0:00' HOUR TO MINUTE ) BETWEEN DATE '2014-01-01' AND DATE '2019-12-31' EACH INTERVAL '1' DAY );