|Applies To||RSA Product Set: ECAT|
RSA Product/Service Type: Server, Client, SQL Database
RSA Version/Condition: 4.x
Platform (Other): Microsoft SQL Server
|Issue||The purpose of this KB article is to help make the ECAT upgrade process a seamless experience and to avoid data loss if the upgrade should fail.|
|Resolution||Before performing an upgrade, it is strongly recommended to do the following:|
Sufficient free space for the transaction log file to grow. You need 2x the current size of the transaction log file. This is very important, if the transaction log cannot grow, the upgrade will fail and the database will be in an unrecoverable state.
Steps to perform prior to the upgrade:
Note: if you are upgrading to 4.1.x from any version and using MSSQL 2008 database.
Contact RSA Customer support for further directions. There are specific steps needed in order to prepare the database for upgrades to 4.1 and higher versions of ECAT.
If an upgrade fails, contact RSA Support and quote this article number for assistance with restoring from the backup.
First a word about the naming convention, the numbering system is built on 4 numbers separated by dots (periods). The first digit is the major release number, followed by the minor number, the third digit is the service pack version and the forth the hot fix number. To illustrate, you have ECAT version 18.104.22.168
The number 4, is the major release, number 1 is the minor release version, 1. Is the service pack and the last number 1 is the hot fix number. For ECAT version 22.214.171.124 the breakdown as follows; 4 major release, 1 is minor, 2 is the service pack number since the number is 0. (There have not been any hot fixes released for this version)