Unisoft Technologies Nagpur

Purpose of RMAN TSPITR Recovery Manager (RMAN) TSPITR enables quick recovery of one or more tablespaces in a database to an earlier time without affecting the rest of the tablespaces and objects in the database. RMAN TSPITR is most useful for the following situations: To recover a logical database to a point different from the rest of the physical database, when multiple logical databases exist in separate tablespaces of one physical database. For example, you maintain logical databases in the orders and personnel tablespaces. An incorrect batch job or data manipulation language (DML) statement corrupts the data in only one tablespace. To recover data lost after data definition language (DDL) operations that change the structure of tables. You cannot use Flashback Table to rewind a table to before the point of a structural change such as a truncate table operation. To recover a table after it has been dropped with the PURGE option. To recover from the logi...

RMAN has the ability to duplicate, or clone, a database from an active database. I t is possible to create a duplicate database on a remote server with the same file structure, a remote server will a different file structure or the local server with a different file structure.

About Virtual Private Catalogs By default, all of the users of an RMAN recovery catalog have full privileges to insert, update, and delete any metadata in the catalog. For example, if the administrators of two unrelated databases share the same recovery catalog, each administrator could, whether inadvertently or maliciously, destroy catalog data for the other's database. In many enterprises, this situation is tolerated because the same people manage many different databases and also manage the recovery catalog. But in other enterprises where clear separation of duty exists between administrators of various databases, as well as between the DBA and the administrator of the recovery catalog, you may desire to restrict each database administrator to modify only backup metadata belonging to those databases that they are responsible for, while still keeping the benefits of a single, centrally-managed, RMAN recovery catalog. This goal can be achieved by implementing v...

Oracle 11g New Feature - Duplicating a Oracle Database Using 11g RMAN Backup Location Option but Without Connection to Target or  Recovery Catalog We have Target Database name as ORCL And we are creating a duplicate database using RMAN Auxiliary Instance with name as AUXDB by using the backup location but without making connection to target database and recovery catalog database while the duplication process is running. Note :- This practical need same directory structures and it is performed on same server. Just the database name is different so we are converting the path with respect to dbname only.  Image Source - docs.oracle.com Your Target Database can be in any log mode. Take RMAN Backup based on your Database Log Mode. A) Archivelog Mode - Take a Whole Hot Backup C:\set ORACLE_SID=orcl C:\rman target / RMAN> backup database plus archivelog; B) Noarchivelog Mode - Take a Whole Cold Backup C:\set ORACLE_SID=orcl C:\rman targe...

Oracle 11g New Feature - Duplicating a Database Using 11g RMAN From Active Database Option without ANY BACKUP We have Target Database name as ORCL And we are creating a Auxiliary database with name as AUXDB    Image Source - docs.oracle.com Check log_mode of Target Database. Target must be in archivelog mode. Otherwise put the database in archivelog mode. shutdown immediate startup mount alter database archivelog; alter database open; Create Pfile from Target Database Spfile C:\set ORACLE_SID=orcl C:\sqlplus / as sysdba SQL> create pfile='C:\app\Administrator\product\11.2.0\dbhome_1\database\initauxdb.ora' from spfile; Open pfile with notepad and replace (Ctrl + H) all orcl to auxdb except for parameter local_listener. SQL> host notepad C:\app\Administrator\product\11.2.0\dbhome_1\database\initauxdb.ora On Windows Platform You need to Create a new Instance for auxdb which also creates a password file for the same. SQL> hos...

Duplicating Target Database Using RMAN Auxiliary Instance on Oracle 10g                                                   or Creating Duplicate Database on the Same Server Using RMAN Backup. We have Target Database name as ORCL And we are creating a Auxiliary database with name as AUXDB  Fig :- Backup-Based Duplication with a Target Connection Image Source - docs.oracle.com 1.Take Whole Hot/Cold Backup of Target Database RMAN> backup database plus archivelog; 2.Create Pfile from Target Database Spfile SQL> create pfile='C:\ORACLE\PRODUCT\10.2.0\DB_1\Database\initauxdb.ora' from spfile; 3.Open pfile with notepad and replace (Ctrl + H) all orcl to auxdb SQL> host notepad C:\ORACLE\PRODUCT\10.2.0\...