Hi,

We have the Data Purge installed and configured to keep 2 days of data. We shut down Optimize and run DP, it runs for 3-6 hours and 2K-5K rows get inserted into the OPERATION_LOG table with the final row syaing the job completed.

However the row counts after the DP is the exact same as the row counts before the DP for all the BAM tables. There is data still in all the tables for over a month.

Has anyone else experienced this? What are we missing or doing wrong? Any ideas?

Thanks in advance

We have begun to run MDP on our Optimize For Infrastructure deployment Oracle database. The OPERATION_PARAMETER table lets me set various values to the scope of the purge. Our database TS is small about 2GB for now. I assume you’ve got those MASSIVE DATA PURGE | CONTROL DATE settings made? Number of days of data to retain in… Your OPERATION_LOG shows results? DROP OLD TABLES is set to YES?

Hi All,

Can you please let me know the steps do we need to follow for executing the MDP process and also the script which we need to execute.

Below are the details which had been set,

In MWS page Business Days To Retain, Data Maintenance Interval and Days To Retain Processes the values are set.

Do we need to set any values in operation_parameter table and alos le t me the process for configuring the massive data purge.

Your help is appreciated.

Thankyou.

Same issue we are also facing where in MDP script exists with message but data still remains in the tables.

When chekced with teh DBA they are getting below error message
ORA-12012: error on auto execute of job 79
ORA-01031: insufficient privileges
ORA-06512: at “WMDEV1.SWAPOPS”, line 726
ORA-06512: at “WMDEV1.SWAPOPS”, line 1447
ORA-06512: at “WMDEV1.SWAPOPS”, line 1705
ORA-06512: at “WMDEV1.FULLINSERTJOBMGMT”, line 21

Also we got th below message once in OPERATION_LOG table
Alert timeout has occurred (180 minutes)

These jobs did not complete:

BAM_AGG_ANALYTI_V1/8285201594

BAM_AGG_ANALYTI_V11/8285201453

BAM_AGG_ANALYTI_V12/8285201610

BAM_AGG_ANALYTI_V13/8285201266

BAM_AGG_FACTAGG_V1/8285201141

BAM_AGG_GARBAGE_V1/8285201500

BAM_AGG_INFLIGH_V1/8285200766

BAM_AGG_OPTIMIZ_V1/8285201563

BAM_AGG_PERFORM_V1/8285200828

BAM_AGG_PREDICT_V1/8285201047

BAM_AGG_PREDICT_V11/8285201203

BAM_AGG_PROCESS_V1/8285201328

BAM_AGG_QUEUEME_V1/8285201235

BAM_AGG_ROUTING_V1/8285200797

BAM_AGG_STEP_ME_V1/8285200969

BAM_AGG_WEBSERV_V1/8285200906

BAM_ALG_MONITORB/ > 5860678

BAM_DIM_JOIN_TMP/TMP_ID > 0

BAM_DIM_TMPBAM_D/TMP_ID > 0

BAM_DIM_TMP_ATTR/TTR_ID > 0

BAM_FACT_ANALYTI_V1/2045201250

BAM_FACT_ANALYTI_V1/2045201406

BAM_FACT_ANALYTI_V1/2045201578

BAM_FACT_ANALYTI_V1/2045201594

BAM_FACT_FACTAGG_V1/2045201125

BAM_FACT_GARBAGE_V1/2045201469

BAM_FACT_INFLIGH_V1/2045200750

BAM_FACT_OPTIMIZ_V1/2045201547

BAM_FACT_PERFORM_V1/2045200813

BAM_FACT_PREDICT_V1/2045201031

BAM_FACT_PREDICT_V1/2045201156

BAM_FACT_PROCESS_V1/2045201281

BAM_FACT_QUEUEME_V1/2045201219

BAM_FACT_ROUTING_V1/2045200781

BAM_FACT_STEP_ME_V1/2045200938

BAM_FACT_WEBSERV_V1/2045200875

BAM_RULE_COMPLIANCE/D > 167952

BAM_RULE_VIOLATION/ION_ID > 0

Thanks in Advance,
Prabha