Related to Unused compression in RMAN backup for 10.2.0.4 database

Hi
I recently read through one of the document related to Unused compression in RMAN backup for 10.2.0.4 database. According to this
Unused Block Compression is done, if all of the following conditions apply:
+ The COMPATIBLE initialization parameter is set to 10.2
+ There are currently no guaranteed restore points defined for the database
+ The datafile is locally managed
+ The datafile is being backed up to a backup set as part of a full backup or a level 0 incremental backup
+ The backup set is being created on disk.
I have two queries
1) What is meant by "uaranteed restore points defined for the database"
2) If backup is being directly taken to tape, this feature would not be used
Rgds
Harvinder

1. Normal and Garanteed Restore Points
2. No

Similar Messages

Rman backup for rac by oem

Br,Hi,
DB : 10.2 and 11.2
How to schedule rman backup for cluster in OEM?How to schedule without OEM?
If one of the node failed,Is it possible to run in another node automatcially?
How to schduel export/datadump in rac by oem?
Br,
Raj

I Am not using oem, without oem you should write several scripts....
for linux hot backup(archive log enabled):
bck.sh
set ORACLE_SID=mydb
set ORACLE_HOME=....
rman target sys/.... @'.../bck.ora'
bck.ora
run
BACKUP AS COMPRESSED BACKUPSET FORMAT "..../db_%d_%T_%s_%p_%U.bak" INCREMENTAL LEVEL 0 DATABASE PLUS ARCHIVELOG DELETE INPUT FORMAT "...../archivelogBackup/arch_%d_%T_%s_%p_%U.bak";
delete force noprompt obsolete redundancy 3;
backup FORMAT '..../ctl_%d_%T_%s_%p_%U' current controlfile spfile;
And create executable job which instance_id=1 and will run your bck.sh script and create schedule for this job, when first node will down you must change instance_id attribute to second one, and be sure that all backup paths exists in all nodes.
Ramin Hashimzade

RMAN backup for two databases with similar DBID

We have two databases with SID 'uiivc' and 'uiivc1' running from one of the HP Unix 11.11 PA-RISC server. I did configured RMAN backup for both databases. But it is found that both databases have same DBID [connected to target database: UIIVC (DBID=3005194057) for UIIVC & connected to target database: UIIVC1 (DBID=3005194057) for UIIVC1] and backup configured via crontab seen running fine with full backup at weekend and archivelog backup at daily for both databases. Now my query is that will it create any issues at time of restoration since both databases have similar DBID? Does RMAN uses DBID to distinguish databases?
Kindly help to clarifiy
Regards
Manoj Thakkan
[email protected]

Hi Tycho,
I configured RMAN to store controlfile backups in different folders on each database.
UIIVC database:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/hot_backups/rmanbkp/uiivc/cf%F';
UIIVC1 database:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/hot_backups/rmanbkp/uiivc1/cf%F';
Server output:
uii-79:uiivc1 > ls -lrt /hot_backups/rmanbkp/uiivc
total 43904816
-rw-r----- 1 oracle dba 21144928256 Jul 15 10:58 8rkk68p5_1_1
-rw-r----- 1 oracle dba 287110144 Jul 15 13:41 8tkk6sfv_1_1
-rw-r----- 1 oracle dba 862700544 Jul 16 08:00 90kk8sel_1_1
-rw-r----- 1 oracle dba 152350720 Jul 16 08:09 92kk8tgg_1_1
-rw-r----- 1 oracle dba 32145408 Jul 16 08:09 cfc-3005194057-20090716-01
uii-79:uiivc1 > ls -lrt /hot_backups/rmanbkp/uiivc1
total 24186112
-rw-r----- 1 oracle dba 6373965824 Jul 13 13:10 83kk1ftf_1_1
-rw-r----- 1 oracle dba 784803840 Jul 13 13:46 85kk1j5e_1_1
-rw-r----- 1 oracle dba 1022674944 Jul 13 23:07 87kk2kjs_1_1
-rw-r----- 1 oracle dba 1814230016 Jul 14 23:46 89kk591i_1_1
-rw-r----- 1 oracle dba 1211042816 Jul 15 23:06 8bkk7tc0_1_1
-rw-r----- 1 oracle dba 1165975552 Jul 15 23:10 8ckk7tnr_1_1
-rw-r----- 1 oracle dba 10534912 Jul 15 23:10 cfc-3005194057-20090715-00
And I saw backups are placing in the respective folders too. So with these settings, can I safely assume there is no issues with RMAN backup and restore having similar DBID for two databases running on same server?
Regards
Manoj Thakkan

Oracle 12c - rman backup for all PDB

Do we have any ready commands that will take backup for all the attached PDB in oracle 12c (container managed db)?

To backup your entire container DB, connect to your CDB & issue a full backup:
rman> backup database;
Backing up your pdb, either connect to the target itself & issue a backup or
rman> backup pluggable database porcl1;
Backing up only the root, connect to the target &
rman> backup database root;
always condensed nicely here: ORACLE-BASE - Multitenant : Backup and Recovery of a Container Database (CDB) and a Pluggable Database (PDB) in Oracle D…

Is it necessary to take RMAN backup for ASM

Hi all
I also know we need RMAN to take backup for ASM . But i also seen its possible to take backup by using dd command itself on ASM . Why we need RMAN rather than this method . What is the specific reason we using RMAN,

its possible to take backup by using dd command itself on ASM Very bad idea.
1. You'll run into the classic "fractured block" issue when attempting a recover or reading a block after the restore
2. RMAN can be used to
a relocate individual datafiles,
b duplicate / clone database,
c restore to an alternate server,
d copy / move from ASM to filesystem
e verify for corruption
f generate reports on backups taken
None of which dd of ASM will do reliably (depending on the skills of the DBA/SA).
Hemant K Chitale
Edited by: Hemant K Chitale on Feb 19, 2013 9:56 AM
Added the words : "reliably (depending on the skills of the DBA/SA)"

Rman backup for tablespaces

Dear,
i want to use rman to backup the tablespaces. I have write a pram file as below.
owner=database
file=c:/backup/database.dmp
log=database.log
buffer=81920
How can i run this file from rman
ManyThanks

It appears that you have created a parfile for the export utility and NOT for RMAN. The basic command to backup a tablespace in RMAN is:
RMAN> BACKUP TABLESPACE USERS;If you are looking to actually export a tablespace, you can save the following to a file called user_parfile.txt
userid=system
file=d:\user_exp.dmp
log=d:\user_exp.log
tablespaces=users
buffer=81920and execute as:
exp parfile=d:\user_parfile.txt

RMAN Backups for archive logs

Hi,
We are taking daily backups using BCV's and archive backup to tapes using RMAN. Please note we are using RMAN only for archive backups.
We are changing our backup strategy and I need below information on RMAN.
1) Is there any benefit I will be getting if I use RMAN for archive backups ( like finding the courruption in the logs,health of the archive) etc? Any reference note for this would be great.
2) If I use multiplexing of archives using LOG_ ARCHIVE_DEST & LOG_ ARCHIVE_DUPLEX_DEST with this I want RMAN to take the backup of archives and delete from one location only ( Say from LOG_ ARCHIVE_DEST ). And I want the archives in LOG_ ARCHIVE_DUPLEX_DEST to maintain on my own ( Like different purge strategy to zip and keep for 7 days in this location.
If I use command "backup archivelog all delete input" it is picking and removing radomly from either of these locations. Is there a way I can configure RMAN so that it will not touch my secondary locaton?
Thanks in advance.
Thanks,
Varma

>
1) Is there any benefit I will be getting if I use RMAN for archive backups ( like finding the courruption in the logs,health of the archive) etc? Any reference note for this would be great.
You can use validate backupset command to check the health of backup.
2) If I use multiplexing of archives using LOG_ ARCHIVE_DEST & LOG_ ARCHIVE_DUPLEX_DEST with this I want RMAN to take the backup of archives and delete from one location only ( Say from LOG_ ARCHIVE_DEST ). And I want the archives in LOG_ ARCHIVE_DUPLEX_DEST to maintain on my own ( Like different purge strategy to zip and keep for 7 days in this location.
Yes, you can do that.
If I use command "backup archivelog all delete input" it is picking and removing radomly from either of these locations. Is there a way I can configure RMAN so that it will not touch my secondary locaton?
You can allocate channels for that.
regards

Rman backup for oracle11g database

Hi,
I want to take the rman backup of 11.2.0.1.0 database, but my catalog database is 10.2.0.1. So Is it possible to take it.
Please suggest me.
My target database : 11.2.0.1.0
OS: windows 2003 R2 server
My catalog database: 10.2.0.1
OS: windows 2003 R2 server

here you go : http://www.comp.dit.ie/btierney/oracle11gdoc/backup.111/b28273/compat.htm

Got RMAN error when running RMAN backup of archivelogs on physical standby database

Got below error when running RMAN backup of datafiles and archivelogs on physical standby database.
RMAN-06820: WARNING: failed to archive current log at primary database
ORACLE error from target database:
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-00942: table or view does not exist
Could anyone help me? Thanks,

Hello;
When you connect RMAN to the source database as TARGET you must specify a password even if RMAN uses operating system authentication.
So the errors ORA-17627 and ORA-00942 appear to be cause and effect.
What version of Oracle? ( 11.2.0.4 according to the tag )
Can you post your backup script?
Best Regards
mseberg
Update
According to :
Database Error Messages 11g Release 2 (11.2) E17766-03
RMAN-06820: WARNING: failed to archive current log at primary database
Cause: An attempt to switch the archived log at the primary database failed.
So I would check my Primary alert log for an issue.
Message was edited by: mseberg

Rman backup for 10g compresses?

Background Info:
10g production databases. 10.2.0
RedHat 4, 64 bit Linux
Use RMAN to backup to local, then backup software copies files to tape.
10 databases, DB size from 10gb - 200gb
Currently I perform: 2 * level 0 and 5 * level 2 per week.I have been using my 9i RMAN scripts (after doing many tests).
Right now I am thinking of using 10g feature 'Compressed Files'.
Does anyone know of any issues / side affect using this feature?
Same question for 'Block change feature', is it advisable to use on prod databases?
~
Many thanks for any response.

Compression saves disk space, but you have to pay for it. Statement from Oracle:
There is some CPU overhead associated with compressing backup sets. If the database being backed up is running at or near its maximum load, you may find the overhead from using AS COMPRESSED BACKUPSET unacceptable. In most other circumstances, compressing backupsets saves enough disk space to be worth the CPU overhead.
Block change feature is useful, if you plan to use incremental backups. It makes such backups faster, because RMAN knows in advance which blocks were changed and which not.
Werner

RMAN Backup for Failover_Yuvi

Hi All Pros,
I am a newbie in Oracle, presently using Oracle 11g XE. Just wanted to know that if i can create a Clone copy of Database to other physical server from the Backup taken by RMAN Script provided by default Start>All Programs>Oracle DB 11G Express>Backup Database in Archivelog mode.
If i can then how to do it as i have tried copying the Flash recovery area to target DB and using Start>All Programs>Oracle DB 11G Express>Restore Database in Archivelog mode
and if it is not the way then please suggest a way to do the same.
* Thanks in advance for your valuable comments
Regards////
Yuvraj

Hi Yuvraj,
Welcome to the forums!.
What you have done didn't worked? It looks that it should have worked.
I don't have a Windows XE instalation to test it, but feel free to post here any problem you may have encountered.
You can also check the official documentation about backup with XE here: http://docs.oracle.com/cd/E17781_01/server.112/e18804/backrest.htm
Regards.

RMAN backup for TDPO without catalog not working

Hi all,
We have configured IBM tivoli storage for Oracle backup(using RMAN).We did not configure Recovery catalog. Will tivoli support to keep the backups in tape without a catalog?
OS : IBM AIX 5.3
Database Version : 10.2.0.4
Tivoli client version : 5.5.0.0
Tivoli server version : 5.5.4.0
oracle API : 5.4.1.0
Regards.

Hi Rajesh,
Thanks for the reply.The script contains the controlfile autobackup option.I have deleted the SBT tape's old backups using RMAN. But the volume space not reduced. This is the script we are using for backup.
run
configure controlfile autobackup on;
crosscheck archivelog all;
allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/cli
ent/oracle/bin64/tdpo.opt)';
#allocate channel t2 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/cl
ient/oracle/bin64/tdpo.opt)';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
backup incremental level 1
filesperset 25
format 'full_%d.%t.bkp'
database;
backup
format 'arch_%d.%t.bkp'
archivelog all;
release channel t1;
regards.

Configuring rman backup for oracle on rac cluster

Hi GURUS
We are buying installation oracle rac on a two node server. We do backup our db using rman and TSM .
Does anyone have any guidance on using TSM scheduled TDP backups with
Oracle RAC multi-node?
More to that, is it possible to have multiple archive log destination?
Any advice would be appreciated.
David

While you can have archives going to different destinations, on different nodes, it is not advisable because if these destinations are not reachable in case of a node/system failure, you have no access to these archive logs.
Actually for easy accesibility it would be better to place the archive logs of all instnaces on shared storage. If you are using ASM and using a FRA disk group, you may want to have your archives go into this location.
NFS mounting filesystems could be slower and may have certain perforamance implications.

How do you plan RMAN backup for small and Large DBs ?

DB version:11.2.0.3/RHEL 5.8
I have 2 scenarios for which I was asked to come up with Backup strategies by the application stakeholders.
I have devised the following strategies . Any comments ?
Scenario 1
===========
I have a large DB of 4TB in size. This DB is very critical and acceptable downtime for this DB is only 30 minutes.My Backup strategy: Incrementally updated Backup using Image copy to FRA
Scenario2:
===========
DB sizes vary from 40gb to 800gb. Acceptable downtime : 1 hour
My Backup strategy : cumulative incremental backup to tape

Only testing you will get the answer.
I've seen many cases the technology is adequate but the procedure is wrong.
Oracle provides multiple ways to perform database recovery.
You need to create recovery scenario for each type of failure. (such as Storage failure, block corrupted, Human errors,etc)
Eg: The User deleted data from a table causing major outage in its application.
What is the procedure to be followed?
The simplest is to restore the data using flashback (based Undo) which can take seconds.
(note: Flashback using undo based does not need feature flashback database enabled).
Believe the main cause of failures in databases today are caused by human error and that sometimes can be resolved simply and quickly.
About Backup/Restore strategies:
"Speed" you usually depends on the hardware resources available to you achieving the desired time.
I can post here a ton of options, but I think your answer will be answered in the tests and procedures (scripts) already prepared to perform this restore.

Best pratices for RMAN backup management for many databases

Dear all,
We have many 10g databases (>40) hosted on multiple Windows servers which are backup up using RMAN.
A year ago, all backup's were implemented through Windows Scheduled Tasks using some batch files.
We have been busy (re)implementing / migrating such backup in Grid Control.
I personally prefer to maintain the backup management in Grid Control, but a colleague wants now to go back to the batch files.
What i am looking for here, are advices in the management of RMAN backup for multiple databases: do you guys use Grid Control or any third-party backup management tool or even got your home-made solution?
One of the discussion topic is the work involved in case that the central backup location changes.
Well... any real-life advices on best practices / strategies for RMAN backup management for many databases will be appreciated!
Thanks,
Thierry

Hi Thierry,
Thierry H. wrote:
Thanks for your reaction.
So, i understand that Grid Control is for you not used to manage the backups, and as a consequence, you also have no 'direct' overview of the job schedules.
One of my concern is also to avoid that too many backups are started at the same time to avoid network / storage overload. Such overview is availble in Grid Control's Jobs screen.
And, based on your strategy, do you recreate a 'one-time' Oracle scheduled job for every backup, or do your scripts create an Oracle job with multiple schedule?
You're very welcome!
Well, Grid Control is not an option for us, since each customer is in a separate infrastructure, and with their own licensing. I have no real way (in difference to your situation) to have a centralized point of control, but that on the other hand mean that I don't have to consider network/storage congestion, like you have to.
The script is run from a "permanent" job within the dba-scheduler, created like this:
dbms_scheduler.create_job(
        job_name        => 'BACKUP',
        job_type        => 'EXECUTABLE',
        job_action      => '/home/oracle/scripts/rman_backup.sh',
        start_date      => trunc(sysdate)+1+7/48,
        repeat_interval => 'trunc(sysdate)+1+7/48',
        enabled         => true,
        auto_drop       => false,
        comments        => 'execute backup script at 03:30');and then the "master-script", determines which level to use, based on weekday from the OS. The actual job schedule (start date, run interval etc) is set together with the customer IT/IS dept, to avoid congestion on the backup resources.
I have no overview of the backup status, run times etc, but have made monitoring scripts that will alert me if/when a backup either fails, or runs for too long. This, in addition with scheduled disaster/recovery tests makes me sleep rather well at night.. ;-)
I realize that there (might be) better ways of doing backup scheduling in your environment, since my requirements are so completely different than yours, but I guess that we all face the same challenges in unifying the environments as much as possible, to minimize the amount of actual work we have to do. :-)
Good luck!
//Johan

Related to Unused compression in RMAN backup for 10.2.0.4 database

Similar Messages

Maybe you are looking for