Cisco Cisco Prime Service Catalog 10.0 Installation Guide

Page of 176
 
3-7
Cisco Prime Service Catalog Installation Guide
OL-31035-01
Chapter 3      Upgrade Guide
  Upgrading Service Catalog
Step 7
Back up all customization scripts or files. The upgrade process will not preserve any customizations on 
your existing installation. Therefore, after the upgrade, you may need to reapply some or all of these 
customizations on your system if they are still applicable.
Step 8
Back up the installation directory. Back up the directory where you originally installed the Service 
Catalog software.
Step 9
Proceed to the 
 section below.
II.  Preparing the Upgrade Environment
Skip this section if you are ready to perform the upgrade on your production environment.
In this section, you will be creating a sandbox environment which you will use to perform the dry run 
exercise for the upgrade process. Once you are comfortable with the upgrade process and are armed with 
the technical notes that you have collected during the dry run exercise, you can then begin the upgrade 
procedures on the actual production system.
To prepare a sandbox environment:
Step 1
Restore the production database backups onto another set of databases. 
Note
Since SQL Server 2005 database and Oracle 10g database are no longer supported in this release, you 
must restore your database backups onto a brand new SQL Server 2008 R2 database or an Oracle 11g 
database.
Step 2
If you are using Oracle DBMS, it is recommended that you execute recompile the statistics for each 
database after it is restored. This step is essential for enhancing the performance of upgrade processes 
on large databases.
Step 3
If your database is SQL Server, you must activate the READ_COMMITTED_SNAPSHOT by 
performing the following:
a.
Connect to your SQL Server as the “sa” user, and set the SQL Server in single-user mode.
b.
Execute the following commands. Replace <database_name> with the name of your RequestCenter 
database.
ALTER DATABASE <database_name> SET READ_COMMITTED_SNAPSHOT ON
GO
ALTER DATABASE <database_name> SET COMPATIBILITY_LEVEL=100
GO
c.
Put the SQL Server back in multiuser mode.
Step 4
Grant the additional permissions for the database user "RCUser", as described in the 
Configuring 
Databases
 section in Chapter 1. If you are not sure that "RCUser" has all of the necessary permissions 
for this release, you can execute the commands described in the Configuring Databases section again; 
these commands can be executed multiple times without causing any issues.
Step 5
Review the list of supported platforms and the prerequisite information as described in 
Cisco Prime 
Service Catalog Compatability Matrix and in Chapter 1
. If your platform is no longer supported, then 
make sure that for the sandbox environment, install the correct versions of application server, web server 
and JDK on a supported operating system.