To migrate an Informatica Domain to a new server and database, Do the following:

1. On the existing server machine backup the domain.

Syntax

The BackupDomain command uses the following syntax:

infasetup BackupDomain <-da database_hostname:database_port | -cs database_connection_string> -du database_user_name

-dp database_password -dt database_type [-ds database_service_name] bf backup_file_name [<-Force|-f>] -dn domain_name

Example

The following is an example of a domain in an Oracle database with connection string (-cs) option:

infasetup BackupDomain -cs "jdbc:informatica:oracle://ora10gDB:1521;ServiceName=ORCL" -du Ora_User -dp Ora_PW -dt

Oracle -bf INFA_Domain_Ora.mrep -dn domain_name

2. Copy the backup file to the new machine.

3. Install Informatica on the new machine.
Note: You must cancel the install before configuring the domain.
To cancel, click Quit when the install prompts you to create or join domain.
4. Copy the files in the <INFA_HOME>/server/infa_shared directories on the original machine to the
new machine. For 9.6.0 and later versions: Copy the siteKey on the original machine to the new
machine.
By default this is in the <INFA_HOME>/isp/config/keys directory (9.6.1 and later,
<INFA_HOME>/isp/config/secret in 9.6.0).
5. Restore the domain in a new database or database schema. Restore the domain using the infasetup
RestoreDomain command and the domain backup. When restoring the domain, make sure to include
the -ca option.
Syntax
The RestoreDomain command uses the following syntax:
RestoreDomain <-da new_database_hostname:new_database_port | -cs
new_database_connection_string> -du new_database_user_name -dp database_password -dt
new_database_type [-ds new_database_service_name] -bf backup_file_name –ca
Example
infasetup.sh RestoreDomain -cs "jdbc:informatica:oracle://ora10gDB:1521;ServiceName=ORCL" -du
database_user_name -dp database_password -dt Oracle -bf backup_file_name –ca
Q: If DBA will migrate the oracle 11g repository DB to oracle 12c can we use the same database
schema domain and repository of previous server (11g)
 6. Run the infasetup DefineGatewayNode command on the new machine to change the entries in the
nodemeta.xml file.
7. All entries (such as host name and database information) must be configured for the new machine
and database. The DefineGatewayNode command uses the following syntax:
8. DefineGatewayNode <-da new_database_hostname:new_database_port | -cs
new_database_connection_string> -du new_database_user_name -dp new_database_password -dt
new_database_type [-ds new_database_service_name] -dn domain_name -nn node_name -na
new_hostname:portnumber -mi min_process_port ??-ma max_process_port -ld
<INFA_HOME>/isp/logs -rf <INFA_HOME>/isp/bin/nodeoptions.xml
Do we need to copy INFA_HOME to the new server or is it ok to copy
<INFA_HOME>/server/infa_shared directories on the original machine to the new machine?
9. Note: It is recommend to include the -mi and -ma options. If they are not specified the defaults will
be set. The default minimum service process port is 11000 and the maximum service process port is
11999.
10. infasetup.sh DefineGatewayNode -cs "jdbc:informatica:oracle://ora11gDB:1521;ServiceName=ORCL"
-du new_ora_uname -dp new_ora_pword -dt Oracle -dn domain_name -nn node_name -na
newhostname:6005 -mi 6013 -ma 6113 -ld <INFA_HOME>/isp/logs -rf
<INFA_HOME>/isp/bin/nodeoptions.xml
11. Start the Informatica Services on the new machine using the infaservice.sh startup command.
12. Start all PowerCenter Services (Repository Services, Integration Services, and so on).

If you restore the domain into a database other than the original backup database, you must restore the
following tables manually:
ISP_RUN_LOG
ISP_MASTER_ELECT_LOCK
ISP_MASTER_ELECTION

To migrate the PowerCenter Repository:

1. Backup the repository using the Informatica Administration Console.

2. Create a new schema for the new repository.
3. Create a new Repository Service (referencing the new database schema).
4. Select the Do not create content option.
5. Enable the new Repository Service.
6. It will display a message stating that the repository does not have any content.
7. Restore the backup (from step 1) using this new Repository Service.
8. Enable the new Repository Service to confirm that the restore is successful.
9. After the restore is successful, you will have two identical repositories (with different names) in the
domain.
10. Disable the new Repository Service.
11. Using the Informatica Administrator, enable the new Repository Service (created in Step 4.).
12. The Repository Service will display a message indicating that an upgrade is required.
13. Select Action > Repository Contents > Upgrade.
14. This will start the upgrade of the repository contents.
15. Change the repository mode from Exclusive to Normal.