Upgrade from PC 7.x to PC 8.6.

0
Points to note:
Server upgrade:

Upgrading from PC 7.x requires installation of PC 8.6 and then use an administration console
to upgrade the PC server and Repository server.

Client upgrade:

To upgrade the PC 7.x to 8.6, uninstalls the previous version of the PC 7.x client and then
install the new version of PC.

Pre-Installation Tasks:

A. Verifying Pre-requisites:

License Key:
Before we install the software, verify that we have the license key available. We
can get the license key in the following ways:

o Installation DVD: If we receive the PowerCenter installation files in a DVD,

the license key file is included on the PowerCenter License Key CD.

o FTP download: If we have download the PowerCenter installation files from

the Informatica FTP site, the license key is in an email message. Copy the
license key file to a directory accessible to the user account installing
PowerCenter.
Note: Contact Informatica Global Customer Support if we do not have a license
key or if we have an incremental license key and we want to create a domain.

Minimum System Requirements:

For us this
is needed.
We need two Database Requirements:
of these:

PC Domain &
PC
Repository

Temporary Disk Space Requirements:

Below one lists the temporary disk space requirements for installation:

I guess we can meet the requirement.

B. Creating the Domain Configuration Database
Create a domain configuration database and set up a database user account.
Note: The domain configuration database stores metadata for the domain.

Rules and guidelines when we set up the domain configuration database:

o The database must be accessible by all gateway nodes in the PowerCenter

domain.

o The database codepage must be compatible with the code page of the
PowerCenter repository and the Metadata Manager repository.

o The PowerCenter installer uses JDBC to communicate with the domain

configuration database.

o On IBM DB2, make sure the primary table space for the domain
configuration database has a default page size of 16k and a temp table
space size of 16k.

o On Sybase ASE, enable the ‘DDL in trans’ option for the database.
Note: We need to follow first three rules/guidelines only, others are not needed.

Rules and guidelines when we set up a database user account:

o The database user account must have permissions to create and drop
tables, indexes, and views, and to select, insert, update, and delete data
from tables.

o When we create the password for the account, use 7-bit ASCII.

o We can store the domain configuration in the same database as the

PowerCenter repository, Metadata Manager, or Data Analyzer repository if
we use the same database user name.

o If we create more than one domain, each domain configuration database

must have a separate user account.
Note: First three are applicable. On guideline number third, we should keep domain and
repository database separate so that it will be easy for us to differentiate the respective
tables and also will help to analyze them easily.

C. Establishing the Installation Environment

For each domain we create, establish the number of nodes in the domain and the
port numbers available on each node. The node and services in the domain must
have unique names.

The new domain cannot have the same name as any PowerCenter Server we
upgrade. When we create a domain, verify that it does not use the same name as
the PowerCenter Server.

When we upgrade PowerCenter 7.x, we can assign the Repository Service and
Integration Service to run on a node in a domain.

We need to identify the nodes to run the application services and install
PowerCenter on the nodes before we can upgrade an existing Repository Server or
PowerCenter Server.
Establish Port Numbers:

When we install PowerCenter, we can use the default port numbers for the
services, or we can use other available port numbers. Determine the port numbers
to use, and verify that the ports are available on the machines where you install
PowerCenter.

The default port numbers used by PowerCenter:

Note: For our upgrade activity, domain and node will be on same VM and port will be
6001. We will have only one node (created by default during installation) which will act as
gateway node with port number 6001.

Information Required During Installation:

When we install PowerCenter, we need to enter information about the domain:

D. Preparing the PowerCenter Repository for Upgrade
Complete the following steps to prepare a PowerCenter repository for upgrade:

Step 1: Optimize Upgrade Performance

Complete the following tasks to optimize the repository and increase performance
when we upgrade:

o Purge unnecessary versions from the repository. If our repository is

enabled for version control, the repository can quickly grow very large
depending on the frequency and number of versions added to the repository.
Each version of an object occupies the same amount of space in the
repository database. If the repository is very large, determine if there are
versions that we do not need and purge these versions.

o Truncate the workflow and session log file: Use the Repository
Manager or the pmrep Truncate Log command to truncate the workflow and
session log file and delete run-time information we do not need. For
example, we can delete all log events older than one month before
upgrading the repository.

o Update statistics: PowerCenter identifies and updates the statistics of all

repository tables and indexes when we upgrade a repository. we can update
the statistics before upgrading the repository to increase upgrade
performance.

Step 2: Configure PowerCenter Sessions:

If the PowerCenter repository contains sessions with Custom transformations and if

the deterministic property for the transformation and the session recovery strategy
are not configured correctly, the sessions will not run after we upgrade.

To correctly configure the session recovery strategy and deterministic property,

complete the following tasks before upgrade:
o Get the nondeterministic_resumable_pre860.sql SQL script from Informatica
Global Customer Support.
o Run the SQL script on the PowerCenter repository we want to upgrade.
The script generates a list of sessions that contain Custom transformations with
the Output is Deterministic property disabled and the session recovery strategy
configured to resume from last checkpoint.

o For each session, determine if the output is deterministic. Make the following
changes on the PowerCenter repository objects:
 If the output is deterministic, enable the Output is Deterministic property in the
custom transformations for the session.
 If the output is not deterministic, configure the session recovery strategy to
restart or fail the session and continue the workflow.

Step 3: Create a Copy of a Repository.

We can create a copy of a repository by copying the repository to another

database or by restoring a backup of the repository to another database.

We cannot upgrade a repository or Repository Service that has the same name as
the domain or that uses the following characters in the name:
 ?":<>*/\|

Copy the Repository:

Use the following steps to copy the repository to another database:

o Have all users close all PowerCenter Client repository connections.

o Release residual locks.

o Use the existing version of PowerCenter to copy the repository to another

database.

o When we copy multiple repositories in a repository domain, register the local

repositories with the global repository after we copy the repositories.

Back Up and Restore the Repository

Use the following steps to back up and restore the repository:

o Have all users close all PowerCenter Client repository connections.

o Release residual locks.

o Use the existing version of PowerCenter to back up the existing repository.

o Use the existing version of PowerCenter to restore the repository backup file
to another database.

o When we restore multiple repositories in a repository domain, register the

local repositories with the global repository after we restore the repositories.

Step 4: Stop All Services

Need to stop Informatica server and repository service corresponding to PC

version 7.x before upgrade.

E. Creating a System User Account:

Create a system user account to perform the installation and to run the Informatica
Services service or daemon.
Note: When we upgrade PowerCenter, use the same account to upgrade and run
the new version as the accounts that we used to install and run the previous
version.

I guess while installing PC 7.x we must have used administrator account on VM.
So we can go with the same during upgrade as well.

The user accounts require the following permission to run the installer or run the
Informatica Services service:

o Logged in user account: The user account must be a member of the

Administrators group and have the Log on as service permission. Log in with
this user account before you install PowerCenter.

o Another user account: The user account must be a member of the

Administrators group and have Log on as a service and Act as operating
system permissions. We do not have to log in with this user account before
 we install PowerCenter. During installation, we can specify the user account
to run the Informatica Services service.
Note: On Windows, we can install Informatica Services with the user account
logged in to the machine and run Informatica Services with another user account.
We can create a local account or a domain account to install PowerCenter or run
the Informatica Services service.

F. Configuring Environment Variables

Environment Variables to Configure for PowerCenter:

G. Clearing Environment Variables:

Clear environment variables from previous PowerCenter versions before you install
or upgrade.
Note: Incorrectly configured environment variables can cause the PowerCenter
domain or nodes to fail to start or can cause connection problems between the
PowerCenter Client and the domain.

Only change need for upgrade from 7.x is:

Clear PATH statements: Verify that the existing environment variables do not
contain earlier versions of PowerCenter in the PATH or library path environment
variables and that the path does not contain double quotes.

H. Setting Up the Keystore File:

During installation, we can configure PowerCenter to use SSL certificates for secure
communication between the Administration Console and the Service Manager. The
installer can generate a self-signed certificate, or we can provide a certificate
signed by a certification authority. We can use the keytool utility to generate a
keystore file to store the SSL keys and certificates.

Generating a Keystore File:

keytool is a key and certificate management utility to generate and administer SSL
keys and certificates. The keys and certificates are stored in a keystore file.

We can find the keytool utility in one of the following directories:

o %JAVA_HOME%\jre\bin

o <PowerCenterInstallDir>\java\bin

I. Backing Up and Uninstalling the Web Services Provider:

If the PowerCenter 7.x installation includes the Web Services Hub, back up the Web
Services configuration before you upgrade. We create and configure a Web
Services Hub in the PowerCenter Administration Console after we install
PowerCenter.

Note: We cannot upgrade an existing Web Services Hub.

Before we install PowerCenter, complete the following tasks:

o Back up the Web Services Hub configuration file: Copy the Web
Services Hub configuration file to a temporary directory. Then use the
settings in the configuration file as reference when we create another Web
Services Hub. The configuration file is named WSHConfig.xml and is located
in the WSH_HOME/config directory.

o Uninstall the Web Services Provider: After we back up the configuration

file, we can uninstall the Web Services Provider.

Use the settings in the Web Services Hub configuration file of PowerCenter 7.x as
reference when we configure the new Web Services Hub.