Upgrading from Version 10.2 (10.5.5)

10.5.5
- 10.5.5.1
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0

Back Next

Migrating to a Different Database

After you upgrade the domain and services, configure the supported database for the existing services.

Create a supported database. For more information about creating a database, see the

Informatica Application Service Guide

Back up the domain and repositories.

To back up the domain, enter the following command:

infasetup BackupDomain

To back up the PowerCenter repository, enter the following command:

pmrep backup

To back up the Model Repository Service, enter the following command:

infacmd mrs BackupContents

Restore, update, and start the domain.

To restore the domain to a supported database, enter the following command and update the database type and schema name:

infasetup RestoreDomain

To update the domain name, node name, and the supported database name, enter the following command:

infacmd isp UpdateGatewayNode

To start the domain, enter the following command:

infaservice Startup

Update the database for the PowerCenter Repository Service, recycle, and restore the PowerCenter repository.

To update the PowerCenter Repository Service with the supported database, enter the following command:

infacmd isp UpdateRepositoryService

To recycle the service, enter the following command:

infacmd isp EnableService

To restore the PowerCenter repository with the supported database type, enter the following command:

pmrep restore

Update the database for the Model Repository Service, recycle, and restore the Model Repository Service.

To update the Model Repository Service with the supported database, enter the following command:

infacmd mrs UpdateServiceOptions

To recycle the service, enter the following command:

infacmd isp EnableService

To restore the Model Repository Service with the supported database type, enter the following command:

infacmd mrs restoreContents

Set the database-specific environment variables for the required service.

For example, set the following environment variable for PostgreSQL for the PowerCenter Repository Service:

PGSERVICE: Set to the location of the pg_service.conf file:
<pg_service.conf file directory>/pg_service.conf
PGHOME: Set to PostgreSQL client install location. For example, /usr/pgsql -10
Add to PATH: $PGHOME/bin:${PATH}
Add to LD_LIBRARY_PATH: $PGHOME/lib:${LD_LIBRARY_PATH}

For Oracle, set the following environment variable for Oracle for the PowerCenter Repository Service:

ORACLE_HOME: Set to Oracle client install location. For example, /u01/app/oracle/product/19.0.0.0
Add to PATH: $ORACLE_HOME/bin:${PATH}
Add to LD_LIBRARY_PATH: $ORACLE_HOME/lib:${LD_LIBRARY_PATH}
Add TNS_ADMIN. The TNS entries are in the oratns folder. For example, /misc/platqa/ISPAutomation/oratns

For DB2, set the following environment variable for DB2 for the PowerCenter Repository Service:

DB2DIR: Set to DB2 client install location. For example, /opt/ibm/db2/V11.1
DB2INSTANCE: Instance name of the DB2 client.
Add to PATH: $DB2DIR/bin:${PATH}
Add to LD_LIBRARY_PATH: $DB2DIR/lib:${LD_LIBRARY_PATH} OR $DB2DIR/lib64:${LD_LIBRARY_PATH}

For SQL Server with DSN, create the DSN entry on the machine where you run the Informatica services. You can enable the DSN and specify the DSN name in the Administrator tool.

For SQL Server on Linux, set the following environment variable for SQL Server for the PowerCenter Repository Service:

ODBCHOME=$INFA_HOME/ODBC<version>
ODBCINI=$INFA_HOME/ODBC<version>/odbc.ini
ODBCINST=$INFA_HOME/ODBC<version>/odbcinst.ini

Rename Saved Search

Table of Contents

Upgrading from Version 10.2 (10.5.5)

Upgrading from Version 10.2 (10.5.5)

Migrating to a Different Database

Migrating to a Different Database