NetIQ has discovered a serious issue introduced in Secure Configuration
Manager 5.9.1 Hotfix 7015965, posted in March 2015. The issue affects a
small number of customers under specific circumstances. If affected,
customers will experience permanent data loss of report data older than
90 days.

All supported versions of Secure Configuration Manager (SCM) have a disk
space management feature that purges reports from the database after a
user-configurable period that defaults to 90 days. Fully enabling this
feature also requires the SQL Server database administrator to
start/enable the SQL Server Agent Service. With extremely large
databases, this cleanup operation can be very slow. To address this, a
bulk purge feature was introduced in SCM 5.9.1 Hotfix 7015965 to improve
performance. Unfortunately, a bug was introduced along with this
performance improvement. The bug results in a situation where the report
is purged after 90 days regardless of the configured data retention
settings in the SCM. This occurs regardless if a longer retention period
is configured or the purge is disabled.

You are at risk of unintentional data loss after 90 days if:

- You applied Hotfix 7015965 to an SCM 5.9.1 system.
- AND the SQL Server Agent Service is enabled/started. (This is
disabled in a default installation.)
- AND one or more of the following conditions apply:

- You attempted to disable purging in the SCM user interface (before
or after applying Hotfix 7015965).
- You attempted to set the data retention policy to greater than 90
days (before or after applying Hotfix 7015965)

You are also at risk of unintentional data loss after 90 days if you
meet the conditions above and then upgraded to SCM 6.0.

You are not at risk of unintentional data loss if:

- You have never applied Hotfix 7015965.
- OR You have not manually enabled the SQL Server Agent Service.
- OR Your intended report retention period is 90 days or less.

NetIQ makes the following urgent recommendations. Choose any one of the
applicable options:

Option1: If you are planning to install SCM 5.9.1 Hotfix 7015965 and
have not installed yet, then do not install it.

Download and install one of the following Hotfixes from the' NetIQ
Secure Configuration Manager Hotfixes'
page, as per your SCM version:

- For SCM 5.9.1: 'Hotfix 7016729' (http://tinyurl.com/ple7b5u)
- For SCM 6.0: Hotfix 7016730 (going to be available soon)

These Hotfixes will correct the problem and may have additional,
unrelated fixes.

Option 2: If you have applied SCM 5.9.1 Hotfix 7015965, or upgraded to
SCM 6.0 after applying SCM 5.9.1 Hotfix 7015965, delete the Bulk_purging
job manually by performing the following procedure, to avoid data loss:

- Log in to SQL Server.
- Start the SQL Server Agent if it is not running already. Ensure that
the Bulk_purging job is not scheduled when you start the SQL Server
Agent service. By default, the Bulk_purging job is scheduled to run at
12.00 p.m. every day.
- In the *SQL Server Agent*, go to *Jobs*.
- Right-click the *Bulk_purging* job and select *Delete*.

For more information, please contact 'Technical Support'
(https://www.netiq.com/support/). We are working to address this issue
as quickly as possible and will post the new Hotfixes as soon as they're
fully tested.

Thanks & regards,
NetIQ Secure Configuration Manager Team

pshrilatha's Profile: https://forums.netiq.com/member.php?userid=10286
View this thread: https://forums.netiq.com/showthread.php?t=54099