Service Operations Insight

Hi,

We were testing the soitoolbox utility.

Ran the purge alert history command(effective alerts were 19990), and later compared the tables and rows; found some tables with higher values than earlier.

did the command not completely delete the existence of those alerts??

Thanks

Deepika

Hi Deepika,

which tables did you look at that have higher values?

Did the soitoolbox command possibly run into a timeout?  For long running jobs you have to increase the timeout value, using parameter -t (or --timeout).  The default is 7200 seconds (e.g. 2 hours).

MichaelBoehm

Hi Deepika, Can you give us exact command you used. Which tables we are talking here showing higher in number is terms of rows after you ran command. Thanks, Ashay

Hi Ashay,

Below are the tables: 

Command ran:

soitoolbox -x --purgeClearedAlerts=55

@Michael,

No the command did not timeout, it ran well within 2000 seconds.

Thanks,

Deepika

Hi Deepika, That is because you have not executed 'ALL' commands to clean DB. You also need to execute other command to clean History data, please see link below for more details https://wiki.ca.com/display/SOI33/_Clean+Up+History+Data_2144701 --purgeClearedAlerts will clear alerts from following tables ActionHistory, AlertHistory, AlertImpact, AlertAnnotation, Alerts, ca_ssa_tags,ca_ssa_notebooks_timestamp, ca_ssa_ci_timestamp, ca_ssa_ci_detail --cleanHistoryData will clear data from following tables CIChangeHistory, CIHealth, CIQuality, CIRisk, DbAvailHistory, DbRiskHistory, DbQualityHistory Thanks, Ashay

Hi Ashay,

We were testing the feasibility of purging without having to stop SOI services and avail a downtime; our DB team does this activity as of now. The other commands require a stop and start of services, so we wanted to test only this one and compare results.

So I understand those tables' rows did not get deleted/removed, but how did they increase the count, it should have been the same without any change.

Thanks

Deepika

Hi Deepika, As you said you have not stopped SOI Service while trying 'soitoolbox -x --purgeClearedAlerts=55' so you are not deleting data from those table but as the same time SOI is running and it is expected it to enter data in tables. Thanks, Ashay

Hi Ashay,

Which of the technical docs might have details about these tables..any idea ?

This is in order to figure out how much of difference/impact (as compared to DB's standard purging process) we might face if we skip the restart of services and move forward with this offline purging.

Thanks

Deepika

Hi Deepika, Database Schema is CA internals and not available publically. But have you checked this. https://support.ca.com/cadocs/1/CA%20Service%20Operations%20Insight%20r3%200-ENU/Bookshelf_Files/HTML/Administration%20Guide/index.htm?toc.htm?purge_cleared_alerts_from_the_persistent_store.html?zoom_highlight=ca_ssa_ci_timestamp Thanks, Ashay