We can purge the versioned items using purgingService.
We have to modify two properties
1)maxAge
2)preciseSummaryReports =true
3)scheduler
If there is huge data, it will take time to purge also. might be 20 hrs also even if we configure BCC JVM as -Xms6g -Xmx10g.
If we configure the preciseSummaryReports=true, system will generate report after purging.
On demand screen
In the below screen, we have set the number days(for cut off), the click on show metric button.
Screen1
Screen2
In the below screen, we can opt either cancel or submit purge.
Once purging is successfully ran, the following screen will be displayed
The log after purging is over at BCC logs.
Tally
Once purging is done, to tally we have to query against the primary tables the compare. And also if require, we have to share number of table record updated as part of purging
We have to modify two properties
1)maxAge
2)preciseSummaryReports =true
3)scheduler
If there is huge data, it will take time to purge also. might be 20 hrs also even if we configure BCC JVM as -Xms6g -Xmx10g.
If we configure the preciseSummaryReports=true, system will generate report after purging.
On demand screen
In the below screen, we have set the number days(for cut off), the click on show metric button.
Screen1
Screen2
In the below screen, we can opt either cancel or submit purge.
Once purging is successfully ran, the following screen will be displayed
The log after purge successfully done
The log after purging is over at BCC logs.
/atg/epub/purge/PurgingService Publishing Data Purging finished successfully.
/atg/epub/purge/PurgingService
/atg/epub/purge/PurgingService +---------------------------------------------------------------------------------------------------
/atg/epub/purge/PurgingService |Metric Value
/atg/epub/purge/PurgingService |---------------------------------------------------------------------------------------------------
/atg/epub/purge/PurgingService |Purge Cutoff Time (Inclusive) Thursday, February 16, 2017 12:00:00
AM IST (Older than 3 days)
/atg/epub/purge/PurgingService |---------------------------------------------------------------------------------------------------
/atg/epub/purge/PurgingService |Repositories Affected /atg/commerce/catalog/SecureProductCatalog
/atg/epub/purge/PurgingService
/atg/epub/purge/PurgingService |---------------------------------------------------------------------------------------------------
/atg/epub/purge/PurgingService |File Systems Affected None
/atg/epub/purge/PurgingService
/atg/epub/purge/PurgingService |---------------------------------------------------------------------------------------------------
/atg/epub/purge/PurgingService |Project summary
/atg/epub/purge/PurgingService | Total number projects 16
/atg/epub/purge/PurgingService | Purged Projects 0
/atg/epub/purge/PurgingService | Remaining Projects 16
/atg/epub/purge/PurgingService |---------------------------------------------------------------------------------------------------
/atg/epub/purge/PurgingService |Asset summary
/atg/epub/purge/PurgingService | Total number assets 2,975,655
/atg/epub/purge/PurgingService | Total number asset versions 2,996,136
/atg/epub/purge/PurgingService | Purged Repository Asset Versions 12,429 (0%)
/atg/epub/purge/PurgingService | Purged File Asset Versions 0 (0%)
/atg/epub/purge/PurgingService | Remaining Asset Versions 2,983,607 (100%)
/atg/epub/purge/PurgingService |---------------------------------------------------------------------------------------------------
/atg/epub/purge/PurgingService |Validation Check
/atg/epub/purge/PurgingService
/atg/epub/purge/PurgingService | Supported Database: Passed
/atg/epub/purge/PurgingService | Deployment Server: Passed
/atg/epub/purge/PurgingService | Current Deployment: Passed
/atg/epub/purge/PurgingService | Incomplete Process: Passed
/atg/epub/purge/PurgingService | Undeployed Process: Passed
/atg/epub/purge/PurgingService | Valid Deployed Snapshot: Passed
/atg/epub/purge/PurgingService | Deployed Snapshot Date: Passed
/atg/epub/purge/PurgingService | Scheduled Deployment: Passed
/atg/epub/purge/PurgingService +---------------------------------------------------------------------------------------------------
/atg/epub/purge/PurgingService
/atg/dynamo/service/ClientLockManager The useLockServer property of: /atg/dynamo/service/ClientLockManager
is false and so global locking is disabled
/atg/epub/purge/PurgingService Requesting read lock named PurgingServiceLock : Thread[[ACTIVE] ExecuteThread:
'0' for queue: 'weblogic.kernel.Default (self-tuning)':ipaddr=172.21.22.69;path=/dyn/admin/nucleus/atg/epub/purge/PurgingService/;sessionid=QX9fZNB017rNZkSu9grNkF3bUBEX9NQMp6TwavFEw_ZGqMt0QVng!580895035!1487659126900,5,Pooled
Threads] : Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)':ipaddr=172.21.22.69;path=/dyn/admin/nucleus/atg/epub/purge/PurgingService/;sessionid=QX9fZNB017rNZkSu9grNkF3bUBEX9NQMp6TwavFEw_ZGqMt0QVng!580895035!1487659126900,5,Pooled
Threads]
/atg/epub/purge/PurgingService ClientLockManager not using global lock server -- accepting local lock
instead. : Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)':ipaddr=172.21.22.69;path=/dyn/admin/nucleus/atg/epub/purge/PurgingService/;sessionid=QX9fZNB017rNZkSu9grNkF3bUBEX9NQMp6TwavFEw_ZGqMt0QVng!580895035!1487659126900,5,Pooled
Threads] : Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)':ipaddr=172.21.22.69;path=/dyn/admin/nucleus/atg/epub/purge/PurgingService/;sessionid=QX9fZNB017rNZkSu9grNkF3bUBEX9NQMp6TwavFEw_ZGqMt0QVng!580895035!1487659126900,5,Pooled
Threads]
/atg/epub/purge/PurgingService Requesting read lock named PurgingServiceLock : Thread[[ACTIVE] ExecuteThread:
'1' for queue: 'weblogic.kernel.Default (self-tuning)':ipaddr=172.21.22.69;path=/dyn/admin/nucleus/atg/epub/purge/PurgingService/;sessionid=QX9fZNB017rNZkSu9grNkF3bUBEX9NQMp6TwavFEw_ZGqMt0QVng!580895035!1487659126900,5,Pooled
Threads] : Thread[[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)':ipaddr=172.21.22.69;path=/dyn/admin/nucleus/atg/epub/purge/PurgingService/;sessionid=QX9fZNB017rNZkSu9grNkF3bUBEX9NQMp6TwavFEw_ZGqMt0QVng!580895035!1487659126900,5,Pooled
Threads]
/atg/epub/purge/PurgingService ClientLockManager not using
global lock server -- accepting local lock instead. : Thread[[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)':ipaddr=172.21.22.69;path=/dyn/admin/nucleus/atg/epub/purge/PurgingService/;sessionid=QX9fZNB017rNZkSu9grNkF3bUBEX9NQMp6TwavFEw_ZGqMt0QVng!580895035!1487659126900,5,Pooled
Threads] : Thread[[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)':ipaddr=172.21.22.69;path=/dyn/admin/nucleus/atg/epub/purge/PurgingService/;sessionid=QX9fZNB017rNZkSu9grNkF3bUBEX9NQMp6TwavFEw_ZGqMt0QVng!580895035!1487659126900,5,Pooled
Threads]
Tally
Once purging is done, to tally we have to query against the primary tables the compare. And also if require, we have to share number of table record updated as part of purging