http://docwiki.cisco.com/w/index.php?title=Purge_command_did_not_purge_data&feed=atom&action=historyPurge command did not purge data - Revision history2015-08-02T23:05:38ZRevision history for this page on the wikiMediaWiki 1.16.0http://docwiki.cisco.com/w/index.php?title=Purge_command_did_not_purge_data&diff=29707&oldid=prevPshree: New page: == Purge command did not purge data == {| border="1" |- ! '''Problem Summary''' | After doing 'purge now' from appadmin, data did not get deleted from database |- ! '''Error Message''' |T...2010-05-04T08:12:51Z<p>New page: == Purge command did not purge data == {| border=&quot;1&quot; |- ! &#39;&#39;&#39;Problem Summary&#39;&#39;&#39; | After doing &#39;purge now&#39; from appadmin, data did not get deleted from database |- ! &#39;&#39;&#39;Error Message&#39;&#39;&#39; |T...</p>
<p><b>New page</b></p><div>== Purge command did not purge data ==<br />
<br />
{| border=&quot;1&quot;<br />
|-<br />
! '''Problem Summary'''<br />
| After doing 'purge now' from appadmin, data did not get deleted from database<br />
|-<br />
! '''Error Message'''<br />
|The SQL Server cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users or ask the system administrator to check the SQL Server lock and memory configuration.<br />
|-<br />
! '''Possible Cause'''<br />
| This error occurs when there are not enough system locks to complete the current command. SQL Server then attempts to obtain a LOCK block to represent and control the desired lock. When dynamically configured, the lock limit is determined by the available memory. When statically configured, the lock limit is determined by the sp_configure setting. <br />
|-<br />
! '''Recommended Action'''<br />
| Either execute the command again when activity on the server is low, or have the system administrator increase the number of locks by executing sp_configure from the master database. <br />
<br />
To view the current configuration:<br />
<br />
sp_configure locks<br />
GO<br />
This reports the minimum, maximum, current run, and configuration values. A config value of 0 indicates that SQL Server manages locks dynamically. If the value is non-zero, we can increase the number of locks by running sp_configure again, specifying the number of locks to be configured. For example, to configure 10,000 locks:<br />
<br />
sp_configure locks, 10000<br />
GO<br />
RECONFIGURE WITH OVERRIDE<br />
GO<br />
<br />
Stop and restart SQL Server so the changes can take effect. Locks are allocated at system startup.<br />
<br />
If the number of locks cannot be increased at the current time, and the single action requires more locks than the server is currently configured for, you may be able to reduce the number of locks required for the operation. For Example, instead of purging data older than 30 months, we can break it into several steps as, <br />
-purge data older than 60 months<br />
-purge data older than 50 months<br />
-purge data older than 40 months<br />
-purge data older than 30 months<br />
|-<br />
! '''Release'''<br />
| all windows release<br />
|-<br />
! '''Associated CDETS #'''<br />
| None<br />
|-<br />
|}<br />
<br />
<br />
[[Category:Unified CCX, Release 7.0]]</div>Pshree