Oracle Database

1. Compare first the data duplicate, the sample in below is the data duplicate occurred cause the WLF runs same file twice with different job_id, so you can compare first by job_id/p11 on table alerts.

2. Backup first data will be deleted with query below :

INSERT INTO ALERTS_BACKUP SELECT * FROM ALERTS WHERE P11=’<session>’;

3. Create a temporary table to accommodate which alerts_id is duplicate with the query below:

Create table alerts_delete as select alert_id from alerts where p11=’<session>’;

MSSQL Database

1.  Compare first the data duplicate the sample in below is the data duplicate occurred cause the WLF runs same file twice with different job_id, so you can compare first by job_id/p11 on table alerts. 

2. Backup first data will be deleted with query below : 

SELECT * INTO ALERTS_BACKUP FROM ALERTS  WHERE P11=’<session>’;

3. Create a temporary table to accommodate which alerts_id is duplicate with the query below:

SELECT alert_id INTO alerts_delete FROM ALERTS WHERE P11=’<session>’;


RCM Designer

4. Create Query deleteAlert on RCM Designer

5. Create delete_alert file , .sh(fpr Unix) .bat(for Windows) with command :

/home/installer/RCM_5.8.0_full_12570/Utilities/unix/delete_alerts.sh -acm=https://10.71.35.59:7002/RCM/ -user=ACTIMIZE dan -password=password  -acmQueryIdentifier=deleteAlert  -acmQueryParameters=  -physicalDelete=true -requiresAudit=false -forceDependency=true -continueOn Error=false

6. Running the previously created delete_alert file:

7. Check the alert is there already deleted or not.