Repository Backup
Repository backup is very important activity in the life of Informatica administrator .As all the metadata informatica maintains in repository we should have daily backups of repository with us which can help us in recovery activities faster .
Basically there are 2 ways ( Actually 3 ways ) to take informatica repository backup
1. From Admin Console
2. From Command prompt
3. Regular Database Backup ways ( In oracle Logical / Physical , using RMAN etc )
1. From Admin Console
Following are the steps to take backup using admin console .
1. Login to console using any user having admin rights
2. select by clicking on repository which you want to backup and select below mentioned option from Action menu
fill in the information in popped up screen
you will get all the backed up files as of now
Using the restore option we can restore the backups .
2. From Command prompt
following are the commands which can be used to take the backups
pmrep connect -r <Repository> -d <domain> -n <Userid> -x <passd>pmrep backup -o C:\Informatica\9.1.0\server\bin\Rep_Backup.rep –f
It will create a backup file in provided path in above case C:\Informatica\9.1.0\server\bin\
3. Regular Database Backup ways ( In oracle Logical / Physical )
Every database is having its own way or commands to take physical or logical backups . we can take the advantage of it to backup the schema where repository resides .
see following extract from Oracle files
For the examples to work
we must first unlock the SCOTT account and create a directory object it can
access. The directory object is only a pointer to a physical directory,
creating it does not actually create the physical directory on the file system
of the database server.
CONN
/ AS SYSDBA
ALTER
USER scott IDENTIFIED BY tiger ACCOUNT UNLOCK;
CREATE
OR REPLACE DIRECTORY test_dir AS '/u01/app/oracle/oradata/';
GRANT
READ, WRITE ON DIRECTORY test_dir TO scott;
Existing directories can
be queried using the ALL_DIRECTORIES view.
Note. Data Pump is a
server-based technology, so it typically deals with directory objects pointing
to physical directories on the database server. It does not write to the local
file system on your client PC.
Table Exports/Imports
The TABLES parameter is used to specify the tables that are
to be exported. The following is an example of the table export and import
syntax.
expdp
scott/tiger@db10g tables=EMP,DEPT directory=TEST_DIR dumpfile=EMP_DEPT.dmp
logfile=expdpEMP_DEPT.log
impdp
scott/tiger@db10g tables=EMP,DEPT directory=TEST_DIR dumpfile=EMP_DEPT.dmp
logfile=impdpEMP_DEPT.log
The TABLE_EXISTS_ACTION=APPEND parameter allows data to be imported into
existing tables.
Schema Exports/Imports
The OWNER parameter of exp has been replaced by the SCHEMAS parameter which is used to specify the schemas
to be exported. The following is an example of the schema export and import
syntax.
expdp
scott/tiger@db10g schemas=SCOTT directory=TEST_DIR dumpfile=SCOTT.dmp
logfile=expdpSCOTT.log
impdp
scott/tiger@db10g schemas=SCOTT directory=TEST_DIR dumpfile=SCOTT.dmp
logfile=impdpSCOTT.log
Database Exports/Imports
The FULL parameter indicates that a complete database
export is required. The following is an example of the full database export and
import syntax.
expdp
system/password@db10g full=Y directory=TEST_DIR dumpfile=DB10G.dmp
logfile=expdpDB10G.log
impdp
system/password@db10g full=Y directory=TEST_DIR dumpfile=DB10G.dmp
logfile=impdpDB10G.log