Previous Topic: Upgrading RiskMinderNext Topic: Performing Pre-Upgrade Tasks (scenario)

CA RiskMinder Windows Installation Guide › Upgrading RiskMinder › Database Privileges Required for Upgrade

Database Privileges Required for Upgrade

The following table lists the database privileges that you must have for performing the database procedures that are related to upgrading to RiskMinder 3.1:

Database Type

Upgrade Privileges

Run time Privileges

Oracle

CREATE TABLE

CREATE TABLE

CREATE ANY INDEX

DML Privileges

CREATE ANY SEQUENCE

 

CREATE TABLESPACE (for Reports)

 

ALTER TABLESPACE

 

CREATE PROCEDURE

 

UNLIMITED TABLESPACE (for Reports, optional)

 

DROP TABLESPACE

 

ALTER ANY TABLE

 

DML Privileges (including CREATE SESSION privilege)

 

MS SQL Server

Note: UserID must also have the database role of ddladmin. If the database user is dbowner, then the database user already has ddladmin privileges.

CREATE TABLE

CREATE TABLE

CREATE INDEX

DML Privileges

CREATE PROCEDURE

 

EXECUTE PROCEDURE

 

REFERENCES

 

ALTER TABLE

 

DML Privileges

 

Upgrading to Release 3.1

Upgrading from 1.x to 3.1 is a two-stage procedure. You first upgrade from 1.x to 2.2.7 and then upgrade from 2.2.7 to 3.1. In contrast, if you are upgrading from 2.x or 3.0.x, you directly upgrade to 3.1.

Perform the following steps to upgrade to RiskMinder 3.1:

  1. Performing Pre-Upgrade Tasks
  2. If you are upgrading from 1.x, then perform the steps that are described in Migrating the Database to Release 2.2.7 for Arcot Common Components. Do not perform this step if you are upgrading from 2.x or 3.0.x.
  3. If you are upgrading from 1.x, then perform the steps that are described in Migrating the Database to Release 2.2.7 for RiskMinder Components. Do not perform this step if you are upgrading from 2.x or 3.0.x.
  4. Preparing for the Upgrade to Release 3.1
  5. Migrating the Database to Release 3.1 for Arcot Common Components
  6. Migrating the Database to Release 3.1 for RiskMinder Components
  7. Uninstalling the Existing Release of RiskMinder
  8. Reinstalling RiskMinder
  9. If you encounter any warnings during the Server startup and if your transactions fail, then perform the steps described in (In Error Scenario Only) Reverting to Your Initial Setup.
  10. Performing Post-Upgrade Tasks
  11. Replacing Deprecated Rules with New Rules
  12. Reviewing Configuration Changes After Upgrade