How to upgrade Compliance Accelerator (CA) 5.1 or Discovery Accelerator (DA) 5.0.

Article:TECH55344  |  Created: 2007-01-06  |  Updated: 2008-01-12  |  Article URL http://www.symantec.com/docs/TECH55344
Article Type
Technical Solution

Product(s)

Environment

Issue



How to upgrade Compliance Accelerator (CA) 5.1 or Discovery Accelerator (DA) 5.0.

Error



Event 42077: Cause:System.Exception: System.Data.SqlClient.SqlException: CREATE INDEX terminated because a duplicate key was found for index ID 2. Most significant primary key is '2'.

Solution



The upgrade process for CA 5.1 and DA 5.0 is outlined below

NOTE: When upgrading to CA and DA version 2007,  all products (Enterprise Vault, Compliance Accelerator, Discovery Accelerator) must be at same version level.

NOTE: When this process is not followed the following error message is generated:

Event Type: Error
Event Source: EV Accelerator Service
Event Category: Devices
Event ID: 42077
User: N/A
Description:

Error:
APP Undefined - Install Thread - worker thread (0)
Customer ID: 2
Number of tries: 1
Cause:System.Exception: System.Data.SqlClient.SqlException: CREATE <UNIQUE> INDEX terminated because a duplicate key was found for index ID 2. Most significant primary key is '2'.
The statement has been terminated.
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at KVS.Accelerator.Application.Install.RunScript(String ScriptName, SqlCommand CMD, Boolean bRefreshViews, Int32 CustomerID) ---> System.Data.SqlClient.SqlException: CREATE <UNIQUE> INDEX terminated because a duplicate key was found for index ID 2. Most significant primary key is '2'.
The statement has been terminated.
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at KVS.Accelerator.Application.Install.RunScript(String ScriptName, SqlCommand CMD, Boolean bRefreshViews, Int32 CustomerID)
--- End of inner exception stack trace ---
at KVS.Accelerator.Common.AcceleratorEvent.LogError(String ErrorMessage, String Description, Boolean ThrowError, Int32 EventID, Exception e)
at KVS.Accelerator.Application.Install.RunScript(String ScriptName, SqlCommand CMD, Boolean bRefreshViews, Int32 CustomerID)
at KVS.Accelerator.Application.Install.RunScript(String ScriptName, SqlCommand CMD, Int32 CustomerID)
at KVS.Accelerator.Application.Install.UpdateDatabase(CustomerRow theCustomerRow)

Description:
Error Installing a Customer

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

----------------------------------------------------------------------------------------------------------------------
NOTE:     The time required to complete the processes below can vary greatly
depending on physical size of a database and environmental resources available.  
It is not uncommon for the upgrade process to take several hours especially when
large databases are involved.  It is also recommended a SQL Administrator be
involved, if available, to prep the database as described below.
----------------------------------------------------------------------------------------------------------------------


UPGRADING COMPLIANCE ACCELERATOR 5.1:

1. DATABASE PREP

a.     Stop the Enterprise Vault Compliance Accelerator Service

b.     Perform a database backup of current database.

c.     Use the "Download Now" link near the bottom of this article to obtain the zip file of all the
        files used below.

d.     Run FixJCDuplicates.sql against the Compliance Accelerator database.

FixJCDuplicates.sql will check the database for duplicates items.  Due to a known issue
with the Journal Connector in Compliance Accelerator 5.1, it is possible the database
may contain duplicate items.   This script is designed to remove these redundant search
items.   When this script is not used, the error described at the beginning of this article
can occur and the upgrade will fail.  At the end of the script, if all the duplicates have
not been fixed they will be displayed in the output.  When this occurs, contact Symantec
support.  

NOTE: FixJCDuplicates.sql sets the database into single user mode, the Enterprise Vault
ComplianceAccelerator Service MUST be stopped and all other connections to the
database must be closed before running FixJCDuplicates.sql.

e.     Run Etrack 618613.sql against the Compliance Accelerator database.

f.      Run Etrack 618613 Purge_SearchItems.sql against the Compliance Accelerator
        database.

These scripts correct an issue where missing indexes on key tables, tblIntDiscoveredItems
and tblSearchItems, were found to cause table scans resulting in poor performance.  In
addition, Compliance Accelerator returns more data than necessary when executing
particular stored procedures.  As a result, tblSearchItems table may contain orphaned
items. When upgrading from Compliance Accelerator 5.1, the duration of the upgrade
increases dramatically when these scripts are not used.

g.     Run a full database backup.

h.     Run Transaction log backup with truncate.

i.      Run Shrink database.  (Upgrade performs quicker on a smaller database)

2.  COMPLIANCE SERVER PREP

j.     Upgrade the Compliance application (binaries) on the Compliance Accelerator
       Server to Compliance Accelerator 6.0 Service Pack 3  (see Installing and
       Configuring Compliance Accelerator.pdf, page 38 under Related Documents).  
       Do not upgrade the pre-6.0 Compliance Accelerator database until the following
       steps are performed.

k.    Rename Program Files\Enterprise Vault Business Accelerator\
       AcceleratorDatabaseUpdateV6_1.sql  with a .old extension.

l.     Copy AcceleratorDatabaseUpdateV6_1.sql (Provided in the zip file)  
            to the: Program Files\Enterprise Vault Business Accelerator directory AFTER
            upgrading the Compliance Accelerator binaries (see step j).

Compliance Accelerator 6.x no longer allows a Null value for the SearchVauldID column.  
In Compliance Accelerator 5.1, it was possible for SearchVaultID to contain Null values;
this results in the upgrade failing.  The new version of
AcceleratorDatabaseUpdateV6_1.sql changes the Null values to -1 and allows the
upgrade to complete successfully.

m.    Restart the Enterprise Vault Accelerator Manager Service

n.     Refer to page 38 of the Installing and Configuring Compliance Accelerator.pdf  to
        create the new Compliance Configuration database, as well as to upgrade the
        existing pre-6.0 Compliance Accelerator database.

o.     Once the upgrade to Compliance Accelerator 6.0 SP3 is complete, refer to the
        Compliance Accelerator 2007 Installing and Configuring Compliance
        Accelerator.pdf, page 26 to upgrade to that version (see related documents below).  
        No extra scripts are required to upgrade to version 2007, the pdf  provides the
        details necessary to complete the transition to Compliance Accelerator 2007.  

*If desired, Compliance Accelerator 6.0 can be upgraded to Compliance Accelerator 7.0 in
lieu of version 2007.  However, Symantec software recommends staying current with the
latest builds to take advantage of any fixes and/or improvements to the product.


NOTE: When upgrading to CA and DA version 2007,  all products (Enterprise Vault, Compliance Accelerator, Discovery Accelerator) must be at same version level.

UPGRADING DISCOVERY ACCELERATOR 5.0:

1. DATABASE PREP

a.     Stop the Enterprise Vault Discovery Accelerator Service

b.     Run full db backup.

c.     Run Transaction log backup with truncate.

d.     Run Shrink database.  (Upgrade performs quicker on a smaller database)


2.  DISCOVERY SERVER PREP

e.     Upgrade the Discovery application (binaries) on the Discovery Accelerator Server to
        Discover Accelerator 6.0 Service Pack 2 (see Installing and Configuring Discovery
        Accelerator.pdf, page 38 under Related Documents).  Do not upgrade the pre-6.0
        Discovery Accelerator database until the following steps are performed.

f.      Rename Program Files\Enterprise Vault Business
        Accelerator\AcceleratorDatabaseUpdateV6_1.sql  with a .old extension.

g.     Copy AcceleratorDatabaseUpdateV6_1.sql  (Provided in the zip file; use the Download
        Now link) to the: Program Files\Enterprise Vault Business Accelerator directory
        AFTER upgrading the Discovery Accelerator binaries (see step e).

Discovery Accelerator 6.x no longer allows a Null value for the SearchVauldID column.  In
Discovery Accelerator 5.0, it was possible for SearchVaultID to contain Null values; this
results in the upgrade failing.  The new version of AcceleratorDatabaseUpdateV6_1.sql
changes the Null values to -1 and allows the upgrade to complete successfully.

h.    Restart the Enterprise Vault Accelerator Manager Service

i.     Refer to page 21, of the Installing and Configuring Compliance Accelerator.pdf
       to create the new Discovery Configuration database as well as to upgrade
       the existing pre-6.0 Discovery Accelerator database.

j.     Once the upgrade to Discovery Accelerator 6.0 SP2 is complete, refer to the Discovery
       Accelerator 2007 Installing and Configuring Compliance Accelerator.pdf,
       page 21 to upgrade to that version (see related documents below).  

*If desired, Discovery Accelerator 6.0 can be upgraded to Discovery Accelerator 7.0 in lieu
of version 2007.  However, Symantec software recommends staying current with the latest
builds to take advantage of any fixes and/or improvements to the product.

NOTE: When upgrading to CA and DA version 2007,  all products (Enterprise Vault, Compliance Accelerator, Discovery Accelerator) must be at same version level.



Attachments

Upgrade_293866.zip (54 kBytes)

Supplemental Materials

SourceETrack
Value1089546
DescriptionSystem.Exception: System.Data.SqlClient.SqlException: CREATE UNIQUE INDEX terminated because a duplicate key was found

SourceEvent ID
Value42077
DescriptionCause:System.Exception: System.Data.SqlClient.SqlException: CREATE INDEX terminated because a duplicate key was found for index ID 2. Most significant primary key is '2'.

SourceETrack
Value618613
DescriptionTable scans causing poor performance resulting in orphaned database entries


Legacy ID



293866


Article URL http://www.symantec.com/docs/TECH55344


Terms of use for this information are found in Legal Notices