Various RMAN Backup Commands.

1)Full Database Backup:------------------------------RMAN>BACKUP DATABASE;2)Individual Tablespaces Backup:------------------------------------To Backup tablespace data01 and data02 only to tape,BACKUP DEVICE TYPE sbt TABLESPACE data01,data02;3)Individual Datafiles and Datafile Copies with RMAN--------------------------------------------------------------To Backup datafile 1 through 4 to tape and to backup datafile system01.dbf located in /oradata from disk to tape use the following,BACKUP DEVICE TYPE sbt DATAFILE 1,2,3,4 DATAFILECOPY '/oradata/system01.dbf';4)Backing Up Control Files---------------------------------•If CONFIGURE CONTROLFILE AUTOBACKUP is ON (by default it is OFF), then RMAN automatically backs up the control file and server parameter file after every backup and after database structural changes.•Manually controlfile can be backed up by BACKUP CURRENT CONTROLFILE;•Also manually it is backed up when we use BACKUP TABLESPACE users INCLUDE CURRENT CONTROLFILE;•Manually, when we back up datafile 1, RMAN automatically includes the control file and SPFILE in backups of datafile 1. But if the control file block size is not the same as the block size for datafile 1, then the control file cannot be written into the same backup set as the datafile. RMAN writes the control file into a backup set by itself if the block size is different.•When controlfile is backed up manually (the above three), the only RMAN repository data for backups within the current RMAN session is in the control file backup, and also a manually backed-up control file cannot be automatically restored.5)Backing Up SP Files:------------------------------•If CONFIGURE CONTROLFILE AUTOBACKUP is ON (by default it is OFF), then RMAN automatically backs up the control file and server parameter file after every backup and after database structural changes.•Explicitly SPfile can be backed up by BACKUP SPFILE;•If database is not started with SPfile then SPfile can't be backed up.6)Backing Up Archived Redo Logs------------------------------------------BACKUP ARCHIVE ALL DELETE INPUT;-This command will backup just one archivelog and delete just one log archive destination.BACKUP ARCHIVE ALL DELETE ALL INPUT;-This command will backup just one archivelog and delete all log archive destination.BACKUP DATABASE PLUS ARCHIVELOG;-This command backs up the database and all archived logs.-If CONFIGURE BACKUP OPTIMIZATION ON is set then RMAN skips backups of archived logs that have already been backed up to the specified device.

Comments

Post a Comment

Popular posts from this blog

ORA-04062: timestamp of procedure has been changed

Problem Description In the database I have created one procedure named a as below. create or replace procedure a(a number) as begin insert into t1 values(1); commit; end; / Now after creating database link using remote database machine whenever I access this procedure "A" it executes successfully and I get value "1" in table t1. Like below in example where orastdby_m is the database link, shaik is the schema name and value 1 is the argument value though argument value is not used in the procedure. SQL> exec shaik.a@orastdby_m(1); PL/SQL procedure successfully completed. Now in the source database machine I changed the procedure as below. Though you can change anything like any literal; adding space or remove space. I changed value to be inserted from 1 to 2. create or replace procedure a(a number) as begin insert into t1 values(2); commit; end; / Now in the other database whenever I execute the procedure using database link it throws error ORA-04062. But subseq...
Read more

ORA-00939: too many arguments -when case arguments exceed 255

Problem Description In all Oracle 10.1g and oracle 10.2.0.1, 10.2.0.2, 10.2.0.3 whenever there is more than 255 arguments inside CASE statements then following error is returned. ORA-00939: too many arguments for function But surprisingly on Oracle 9.2 database the same code does not return any error. Cause of the Problem As we see the same code return error in 10g but it is well on 9.2. In fact this is problem of oracle 9.2 that it does not return any error. It should return error if there is more than 255 arguments inside CASE statements. In oracle 9.2 this is bug number 2909927 and this bug is fixed in oracle 10.1 and 10.2. That's why in 10.2 and 10.1 error returns if arguments exceed 255. Up to Oracle 10.2.0.3 and earlier version, the arguments of CASE statement is limit to 255 and it does not support exceed over 255 and hence error return if it exceed. However in Oracle 10.2.0.4 and later the arguments limit of CASE statement has increased to 32767. Solution of the Problem Opt...
Read more

ORA-31655: no data or metadata objects selected for job

Problem Description You are going to do data pump export operation in order to export objects based on filtering via EXCLUDE or INCLUDE parameter of expdp. In this example you wanted tables 'ACCOUNT_GROUP','ADDRESS','AREA_GROUP' and all the tables starting with word CV(like 'CV', 'CV_EXPERIENCE', 'CV_EDUCATION' etc) Your parameter file is like below. userid=smilebd/a directory=d dumpfile=b.dmp include =TABLE:"IN('ACCOUNT_GROUP','ADDRESS','AREA_GROUP')" include =TABLE:"LIKE 'CV%' " And you invoke expdp as expdp parfile=d:\parfile.txt from command line. But it fails with below message on my windows PC. C:\>expdp parfile=d:\parfile.txt Export: Release 10.1.0.4.2 - Production on Thursday, 29 January, 2009 14:53 Copyright (c) 2003, Oracle. All rights reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc tion With the Partitioning, OLAP and Data Mining ...
Read more