Simple steps to backup and restore the Repository and Domain configuration

-

  •   For domain backup you can use the infasetup.sh script with  BackupDomain parameter.

sh $INFA_HOME/server/infasetup.sh BackupDomain -da database_hostname:port -du domain_db_user -dp domain_db_password -dt oracle -ds db_service_name -bf DomainBackup.xml.mrep -dn Domain_name

•   To restore the domain use the infasetup.sh script with RestoreDomain parameter.

sh $INFA_HOME/server/infasetup.sh RestoreDomain -da database_hostname:port -du database_db_user -dp domain_db_password -dt oracle -ds db_service_name -bf DomainBackup.xml.mrep

•  You can backup the repository in two ways.

  •  Form Adminconsole

1) Login to admin console.
2) Select Repository service
3) Select Backup contents under Actions menu to take backup by default          Adminconsole creates the .rep file in to $INFA_HOME/server/infa_shared/Backup/
4) Restore contents under Actions menu to restore.

  • From pmrep utility on command line.

•  Step1 : Connect to Informatica Repository Database Using pmrep utility.

$ pmrep connect -r REP_NAME -d DOMAIN_NAME -n Administrator -x PASSWORD

Informatica(r) PMREP, version [8.1.1 SP5], build [135.0129], SOLARIS 32-bit
Copyright (c) Informatica Corporation 1994 - 2008
All Rights Reserved.
This Software may be protected by U.S. Patent Numbers 6,208,990; 6,044,374; 6,014,670; 6,032,158; 5,794,246; 6,339,775, 6,850,947; 6,895,471, and other U.S. Patents Pending.

Invoked at Thu Jun 20 07:45:14 2013

Connected to repository REP_NAME in DOMAIN_NAME as user Administrator
connect completed successfully.

• Step 2 : Use the backup command to backup the repository.

By default pmrep utility backup the .rep file in to $INFA_HOME/server/infa_shared/Backup/
in case if you want to replace the existing .rep backup file use the -f option with the backup command. pmrep backup -o REP_NAME.rep -f which will replace the existing backup files in above directory.

$ pmrep backup -o REP_NAME.rep

Informatica(r) PMREP, version [8.1.1 SP5], build [135.0129], SOLARIS 32-bit
Copyright (c) Informatica Corporation 1994 - 2008
All Rights Reserved.
This Software may be protected by U.S. Patent Numbers 6,208,990; 6,044,374; 6,014,670; 6,032,158; 5,794,246; 6,339,775, 6,850,947; 6,895,471, and other U.S. Patents Pending.

Invoked at Thu Jun 20 07:45:37 2013

Back Up Contents operation on repository [REP_NAME] started at 06/20/2013 07:45:38.
Backing up repository contents to file [/application/informatica/infauser/PowerCenter9.1.1/server/infa_shared/Backup/REP_NAME.rep].  

Backing up table OPB_SUBJECT  

Backing up table OPB_DBD 

Backing up table OPB_SCHEMA  

Backing up table OPB_TARGINDEX  

Backing up table OPB_TARGINDEXFLD  

Backing up table OPB_PICDSC  

Backing up table OPB_SRC_FLD  

Backing up table OPB_SRC

•  Step 3 : To restore the .rep file to repository.

pmrep restore -i REP_NAME.rep -u Admin_User -p Admin_Password







Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more