Showing posts with label RMAN. Show all posts
Showing posts with label RMAN. Show all posts

Saturday, 20 February 2016

Transport Tablespace from RMAN backupsets

Transportable Tablespace from RMAN backupsets:
Transportable tablespace supports the fastest method of copying set of tablespaces from one Oracle database to another.
In general, tablespaces must be kept in read only mode before being transported. It will be difficult task to put bigger size tablespaces and 24x7 accessed high availability tablespaces in the read only mode for longer time. This could prove a potential problem with the high availability databases.

Thursday, 18 February 2016

RMAN (Recovery Manager) Commands in Oracle.

rman commands
Start RMAN from the OS command line.

rman
[ TARGET [=] ['] [userid][/[password]][@net_service_name] [']
| {CATALOG [=] ['] [userid][/[password]][@net_service_name] [']
| LOG [=] [']filename['] [APPEND]
...
]...

Duplicate RAC Database Using RMAN

Oracle provides following methods to convert a single instance database to RAC. You can choose any method based upon your convince.
1. Manual (Using RMAN)
2. Enterprise Manager
3. DBCA
4. RCONFIG (from 10gR2)

RMAN-06100 or RMAN-06102 during restore/duplicate

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Information in this document applies to any platform.

SYMPTOMS

Backups on the production site are written to tape and disk on separate days.
We want to use the backup on disk for an RMAN duplicate or restore to new host but RMAN does not appear to be finding these backups for use.

Configuring the RMAN Environment


Contents

1.     Overview
2.     Viewing Values
3.     Using Substitution Variables
4.     Using the configure Command to Clear Values
5.     PARAM:   Retention Policy  
6.     PARAM:   Backup Optimization
7.     PARAM:   Default Device Type  
8.     PARAM:   Controlfile Autobackup  
9.     PARAM:   Controlfile Autobackup Format  
10. PARAM:   Parallelism
11. PARAM:   Database Backup Copies
12. PARAM:   Archivelog Backup Copies
13. PARAM:   Channel Configuration  
14. PARAM:   Maxsetsize
15. PARAM:   Snapshot Controlfile
16. PARAM:   Exclude Tablespace

Steps to clone a database using RMAN

 1: Create a password file on the destination server

2: Establish connectivity between the target and destination server (tnsnames.ora, 

     sqlnet.ora)

3: Create the directories for the database files

4: Take the RMAN backup from the target server and copy it to the destination 

      server.

5: Startup the destination database in nomount mode

6: Run the RMAN duplicate database command

RMAN Virtual Private Catalog

In Oracle 11g, we can grant restricted access to the RMAN catalog to some users so that they can only access a limited set of databases that are registered in the RMAN catalog.