RMAN logical backup containing unused blocks

Dear Experts
When i taking logical backup of datafile from RMAN utility i notify that it will also backed up all unused blocks from datafile, so what i need to do, how to avoid that unused block from being backed up while taking logical backup of datafiles.
System details as follows
HP Itanium server
OS - Redhet Linux 5
DB - Oracle10g
Suggest me urgent.

Here i am gonna show you the backup statistics for only those problematic datafiles
DFNAME                                    DATAFILE_BLCKS     BLOCKS          DIFF
/san_index/oradata/orcl/rajemitra_index1.dbf     1695744     9818          1685926
/san_index/oradata/orcl/rajemitra_index2.dbf     1716224          8527          1707697
/san_index/oradata/orcl/rajemitra_index3.dbf     1622016          9727          1612289
/san_index/oradata/orcl/rajemitra_index4.dbf     1622016          9808          1612208
/san_index/oradata/orcl/rajemitra_index1.dbf     1695744          24823          1670921
/san_index/oradata/orcl/rajemitra_index2.dbf     1716224          19891          1696333
/san_index/oradata/orcl/rajemitra_index3.dbf     1622016          20591          1601425
/san_index/oradata/orcl/rajemitra_index4.dbf     1622016          17026          1604990
/san_index/oradata/orcl/rajemitra_index1.dbf     1695744          21239          1674505
/san_index/oradata/orcl/rajemitra_index2.dbf     1716224          17843          1698381
/san_index/oradata/orcl/rajemitra_index3.dbf     1622016          19820          1602196
/san_index/oradata/orcl/rajemitra_index4.dbf     1622016          14429          1607587
/san_index/oradata/orcl/rajemitra_index1.dbf     1695744          33885          1661859
/san_index/oradata/orcl/rajemitra_index2.dbf     1716224          41480          1674744
/san_index/oradata/orcl/rajemitra_index3.dbf     1622016          32338          1589678
/san_index/oradata/orcl/rajemitra_index4.dbf     1622016          26288          1595728
/san_index/oradata/orcl/rajemitra_index1.dbf     1695744          10504          1685240
/san_index/oradata/orcl/rajemitra_index2.dbf     1716224          18169          1698055
/san_index/oradata/orcl/rajemitra_index3.dbf     1622016          16195          1605821
/san_index/oradata/orcl/rajemitra_index4.dbf     1622016          11974          1610042
/san_index/oradata/orcl/rajemitra_index1.dbf     1695744          16938          1678806
/san_index/oradata/orcl/rajemitra_index2.dbf     1716224          25688          1690536
/san_index/oradata/orcl/rajemitra_index3.dbf     1622016          30653          1591363
/san_index/oradata/orcl/rajemitra_index4.dbf     1622016          20611          1601405
/san_index/oradata/orcl/rajemitra_index1.dbf     1695744          965385          730359
/san_index/oradata/orcl/rajemitra_index2.dbf     1716224          1010354          705870
/san_index/oradata/orcl/rajemitra_index4.dbf     1622016          1004034          617982
/san_index/oradata/orcl/rajemitra_index1.dbf     1695744          1695397          347
/san_index/oradata/orcl/rajemitra_index2.dbf     1716224          1713435          2789
/san_index/oradata/orcl/rajemitra_index3.dbf     1622016          1621255          761
/san_index/oradata/orcl/rajemitra_index4.dbf     1622016          1620287          1729
/san_index/oradata/orcl/rajemitra_index1.dbf     1695744          1695397          347
/san_index/oradata/orcl/rajemitra_index5.dbf     1171456          1170831          625
/san_index/oradata/orcl/rajemitra_index1.dbf     1695744          1695397          347
/san_index/oradata/orcl/rajemitra_index2.dbf     1716224          1713470          2754
/san_index/oradata/orcl/rajemitra_index3.dbf     1622016          1621261          755
/san_index/oradata/orcl/rajemitra_index4.dbf     1622016          1620364          1652
/san_index/oradata/orcl/rajemitra_index5.dbf     1171456          48547          1122909
/san_index/oradata/orcl/rajemitra_index1.dbf     1695744          47875          1647869
/san_index/oradata/orcl/rajemitra_index2.dbf     1716224          19725          1696499
/san_index/oradata/orcl/rajemitra_index3.dbf     1622016          26205          1595811
/san_index/oradata/orcl/rajemitra_index4.dbf     1622016          56040          1565976
/san_index/oradata/orcl/rajemitra_index5.dbf     1171456          31859          1139597
/san_index/oradata/orcl/rajemitra_index1.dbf     1695744          29509          1666235
/san_index/oradata/orcl/rajemitra_index2.dbf     1716224          20767          1695457
/san_index/oradata/orcl/rajemitra_index3.dbf     1622016          13210          1608806
/san_index/oradata/orcl/rajemitra_index4.dbf     1622016          31411          1590605

Similar Messages

OSB Unused block compression and Undo backup compression

Dear all.
I know that osb backup software is faster than other vendor software especially oracle database backup area.
There are two special method (Unused block compression and Undo backup compression)
But, normally in case of comparable product using same RMAN API(Veritas/Legato etc...), they only backup used block and skip unused block, right?
I'm confused, what is different from used block only backup and unused block compression.
Please explain detail about unused block compression and Undo backup compression.
Sorry about my poor knowledge.
Thanks.

This is explained in detail in the OSB technical white paper:
http://www.oracle.com/technetwork/products/secure-backup/learnmore/osb-103-twp-166804.pdf
Let me know if you have any questions
Donna

Rman backup with corrupted block

Hello,
Firstly - I have problem on non-production database 11.2.0.1.0, so I am not deeply worried about data. But I need to understand what happened with database backups and how to prevent such things in future.
So - I have EM scheduled weekly full backup and daily incremental backups. Later there was problem with hardware and some corrupted blocks in database were found. The weekly backup ran without error and obsolete backups were deleted. Now it is not possible to "recover corruption list" because no backup without corruption exists (RMAN-06023: no backup or copy of datafile 6 found to restore). I am not worried about the lost data, but I need to find out how come the backup contains corrupted block.
I have checked the data file using dbv utility
DBVERIFY - Verification starting : FILE = /opt/oracle/oradata/orcl/users03.dbf
DBV-00200: Block, DBA 27525766, already marked corrupt
csc(0x0001.7b01729f) higher than block scn(0x0000.00000000)
Page 2359942 failed with check code 6054
DBVERIFY - Verification complete
Total Pages Examined         : 3840000
Total Pages Processed (Data) : 453896
Total Pages Failing   (Data) : 1
Total Pages Processed (Index): 2959104
Total Pages Failing   (Index): 0
Total Pages Processed (Other): 424025
Total Pages Processed (Seg) : 0
Total Pages Failing   (Seg) : 0
Total Pages Empty            : 2975
Total Pages Marked Corrupt   : 1
Total Pages Influx           : 0
Total Pages Encrypted        : 0
Highest block SCN            : 2156227446 (1.2156227446)As you can see the datafile 6 - user03.dbf has errors. Also backups now contain errors.
1) So how is it possible that the EM scheduled backup ran without problems and the backup now contains corrupted blocks. How to prevent this in future ? I know there is setting MAXCORRUPT. How can I check its current value ? How can I configure it using EM scheduled backups ?
2) Secondly, meanwhile I studied the RMAN commands. So I have suspended EM backup jobs, and executed follwing command. And backup ran without error again. How is this possible, if data file users06.dbf has corrupted block ?
Thanks !
RMAN> run {
set MAXCORRUPT for datafile 6 to 0;
backup as compressed backupset datafile 6;
2> 3> 4>
executing command: SET MAX CORRUPT
Starting backup at 07-NOV-12
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
using channel ORA_DISK_5
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
channel ORA_DISK_1: starting piece 1 at 07-NOV-12
channel ORA_DISK_1: finished piece 1 at 07-NOV-12
piece handle=/opt/oraBackup/rman/nrnpo0sg_1_1 tag=TAG20121107T200120 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 01:13:05
Finished backup at 07-NOV-12
Starting Control File and SPFILE Autobackup at 07-NOV-12
piece handle=/opt/oraBackup/rman/c-1253245572-20121107-03 comment=NONE
Finished Control File and SPFILE Autobackup at 07-NOV-12

I have updated database to 11.2.0.3
However, the problem still persists. rman backup went ok on broken file
oracle@orcl-cluster:~> sqlplus
SQL*Plus: Release 11.2.0.3.0 Production on Tue Nov 20 09:24:11 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Enter user-name: system
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select * from V$DATABASE_BLOCK_CORRUPTION;
     FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
         6    2359942          1                  0 FRACTURED
        25    1855622          1                  0 FRACTURED
oracle@orcl-cluster:~> rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue Nov 20 08:04:57 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1253245572)
RMAN> backup as compressed backupset datafile 6;
Starting backup at 20-NOV-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1596 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=1568 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=2357 device type=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: SID=2341 device type=DISK
allocated channel: ORA_DISK_5
channel ORA_DISK_5: SID=86 device type=DISK
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
channel ORA_DISK_1: starting piece 1 at 20-NOV-12
channel ORA_DISK_1: finished piece 1 at 20-NOV-12
piece handle=/opt/oraBackup/rman/2rnqovpp_1_1 tag=TAG20121120T080513 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 01:10:35
Finished backup at 20-NOV-12
Starting Control File and SPFILE Autobackup at 20-NOV-12
piece handle=/opt/oraBackup/rman/c-1253245572-20121120-00 comment=NONE
Finished Control File and SPFILE Autobackup at 20-NOV-12
RMAN> backup validate datafile 6;
Starting backup at 20-NOV-12
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
using channel ORA_DISK_5
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
channel ORA_DISK_1: backup set complete, elapsed time: 00:03:05
List of Datafiles
=================
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
6    OK     1              2975         3840000         6489027926
File Name: /opt/oracle/oradata/orcl/users03.dbf
Block Type Blocks Failing Blocks Processed
Data       0              453912
Index      0              2959091
Other      0              424022
Finished backup at 20-NOV-12Edited by: kamilp on Nov 20, 2012 12:23 AM

Regarding RMAN n Logical Backup

Hi All,
Will Select query affect the RMAN n logical Backup????

hi yingkuan..
VERSION
10.1.0.5.0
Its a select query which contain lots of conditions....
please find below the query
select distinct cci.consmr_no ,vin
from lead_info li,
lead_std_address lsa,
cdr_consmr_info cci,
cdr_address ca,
cdr_product_info cpi
where li.household_id=lsa.household_id and
cci.consmr_no=ca.consmr_no and
cci.consmr_no=cpi.consmr_no and
cpi.extract_dt between '22-DEC-2005' and '31-DEC-2006' and
li.last_name=cci.last_name and
lsa.address_1=ca.address and
lsa.city_name=ca.city_name and
lsa.state=ca.state and
lsa.zip=ca.zip and
li.family_id is not null and
cpi.family_id is null

RMAN 10.2 "unused" block compression

Has anyone tested for the unused block compression. I realize the docs say it is the case now in 10.2 that rman only backs up currently used blocks, and not blocks that belonged to dropped or truncated tables. I can't proove it on my own system.
I tried...
1) creating a tbsp 100mb, with an 80mb table. Backed it up as a backupset
2) Dropped the 80mb table and purged it from the recyclebin. Backed it up as a backupset.
Both backupsets were the exact same size, indicating only that rman doesn't back up "never" used blocks.
I did the same test AS COMPRESSED BACKUPSET and got the same result, both were compressed but were of equal size.
Thanks,
A

Okay, no luck. I've tried every which way to backup...
1.4GB db with a 720MB table...
BACKUP INCREMENTAL LEVEL 0 AS COMPRESSED BACKUPSET DATABASE results in a 230.6MB backupset file.
DROP TABLE <720mb table> PURGE;
Same backup commands. Same backup size 230.6MB.
Doesn't work as far as I can tell.
A

User hot and Rman hot backup

During user mode hot backup lots of redo gets generated as the entire block is written when any changes are made to a block which is in hot backup mode.But during Rman hot backup less redo are generated why is this so and whatz the logic invloved? and how oracle recovers the file that has been backed up through Rman.
Could you please explain me regarding this in detail it will be really helpful.
kumaresh

From Article Note:76736.1 RMAN FAQ: Recovery Manager -- Frequently Asked
To understand why RMAN does not require extra logging or backup mode,
you must first understand why those features are required for non-RMAN
online backups.
A non-RMAN online backup consists of a non-Oracle tool, such as cp or
dd, backing up a datafile at the same time that DBWR is updating the
file. We can't prevent the tool from reading a particular block at the
exact same time that DBWR is updating that block. When that happens,
the non-Oracle tool might read a block in a half-updated state, so that
the block which is copied to the backup media might only have been
updated in its first half, while the second half contains older data.
This is called a "fractured block". If this backup needs to be restored
later, and that block needs to be recovered, recovery will fail because
that block is not usable.
The 'alter tablespace begin backup' command is our solution for the
fractured block problem. When a tablespace is in backup mode, and a
change is made to a data block, instead of logging just the changed
bytes to the redo log, we also log a copy of the entire block image
before the change, so that we can reconstruct this block if media
recovery finds that this block was fractured. That block image logging
is what causes extra redo to be generated while files are in backup
mode.
The reason that RMAN does not require extra logging is that it
guarantees that it will never back up a fractured block. We can make
that guarantee because we know the format of Oracle data blocks, and we
verify that each block that we read is complete before we copy it to the
backup. If we read a fractured block, we read the block again to obtain
a complete block before backing it up. non-Oracle tools are not able to
do the same thing because they do not know how to verify the contents of
an Oracle data block.
Backup mode has another effect, which is to 'freeze' the checkpoint in
the header of the file until the file is removed from backup mode.
We do this because we cannot guarantee that the third-party backup
tool will copy the file header prior to copying the data blocks.
RMAN does not need to freeze the file header checkpoint because we
know the order in which we will read the blocks, which enables us to
capture a known good checkpoint for the file.

Quesion about the Basic concept of RMAN incremental backup

I have a problem in understanding the basic concept of two types RMAN Incremental backup ie. Differential and Cumulative. I just don't understand how cumulative incremental backup consumes more space than Differential backup.
Have a look at the scenario in which Differential backup is used.
1. On Sunday midnight, a LEVEL0 backup is taken.
2. On Monday midnight all the blocks that was changed since Sunday midnight are stored in the backup media (tape or disk)
3. On Tuesday midnight all the blocks that was changed since monday midnight are stored in the backup media.
4. On Wednesday midnight, all the blocks that was changed since tuesday midnight are stored in the backup media.
At this point, in the backup media, you have all the changed blocks from sunday midnight to wednesday midnight eventhough it was stored in a daily basis. If you had taken a cumulative backup at wednesday midnight the backup media would have contained the same changed blocks from sunday midnight(LEVEL0) to wednesday midnight, but all at one go instead of daily basis. I don't understand how cumulative backup consumes more space when the backup media contains the same amount of changed blocks as it were in the case of the Differential backup.

Considering the Scenario you given:
Sunday : Level 0 backup.
Monday : You have taken an incremental backup then there will not be any difference in size of backup set for differential or cumulative as the changes from last Level0 backup are considered.
Tuesday : A cumulative backup (n-1) will have changed blocks since Sunday's Level0 backup but a differential backup(n) will only have changed blocks since Monday. So definitely there will be more space consumed by cumulative backups compared to differentials.
Hope it helps ...
Bhupinder

Logical backup and recovery using export/import

Hi,
Anyone provide me the clear steps and command to take logical backup and recovery using the import and export method...??.
im using oracle 9i database and redhat linux server version 4.0.........???.
thanks,
vasanth.......

user12864080 wrote:
Hi,
Anyone provide me the clear steps and command to take logical backup and recovery using the import and export method...??.
im using oracle 9i database and redhat linux server version 4.0.........???.
thanks,
vasanth.......Vasant,
Though you have got links already for using the exp/imp , I would strongly suggest that when you mention backup/recovery, RMAN is the tool that you should be using. Exp/imp is/was never considered as a backup tool. You should read this paper to get the answer of "why rman" ?
http://www.evdbt.com/TD_Rman.pdf
Aman....

Rman hot backup

hello
i am using rman hot backup script to take backup database everyday but the problem is it is working but not deleting old backup older than 2 days .
also i have question .. my database is in archive log mode and everyday about 6-7 .arch files generating in my archive directory.
it is not deleting the old files but generating new files everyday so adding up to the space.
SQL> show parameter archive
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string /u03/archive_logs/DEVL
log_archive_dest_1 string
also should i set dest_1 as archive location or just log_archive_dest
whats is the difference.?
my rman script is
RMAN Hot backup.unix script
The RMAN hot backup script rman_backup.sh:
# !/bin/bash
# Declare your environment variables
export ORACLE_SID=DEVL
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
export PATH=$PATH:${ORACLE_HOME}/bin
# Start the rman commands
rman target=/ << EOF
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/backup/autobackup_control_file%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
run {
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
allocate channel d4 type disk;
ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
CROSSCHECK BACKUP;
BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/u03/backup/databasefiles_%d_%u_%s_%T';
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/u03/backup/archivelogs_%d_%u_%s_%T' DELETE INPUT;
BACKUP AS COMPRESSED BACKUPSET CURRENT CONTROLFILE FORMAT '/u03/backup/controlfile_%d_%u_%s_%T';
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT EXPIRED BACKUP;
RELEASE CHANNEL RMAN_BACK_CH01;
EXIT;
EOF
thanks

Ahmer Mansoor wrote:
RMAN never deletes the Backups unless there is a space pressure in the Recovery Area. Instead it marks the Backups as OBSOLETE based on Retention Policy (in your case it is 2 Days),
To confirm it SET DB_RECOVERY_FILE_DEST_SIZE to some smaller value, the RMAN will remove all the Obsolete Backups automatically to reclaim space.Be very careful with this. If you generate a LOT of archivelog files and you exceed this size, on the next archivelog switch your database will hang with "cannot continue until archiver freed". RMAN will not automatically remove anything. RMAN only removes stuff when you program it in your script.
See:
http://docs.oracle.com/cd/E14072_01/backup.112/e10642/rcmconfb.htm#insertedID4 Retention Policy (recovery window or redundancy)
things like:
set retention window and number of copies
crosscheck backup
delete obsolete <-- delete old, redundant, no longer necessary backups/archivelogs
delete expired <-- NOTE: If you manually delete files and do not execute delete expired (missing file), the DB_RECOVERY_FILE_DEST_SIZE remains the same. So, you can clean out the space and oracle will still say the location is "full".
Understand that if you also set this parameter too small and your backup recovery window/redundancy are incorrectly set, you can also exhaust the "logical" space of this location again, putting your database at risk. Your parameter could be set to 100G on a 400G file system and even though you have 300G available, Oracle will see the limit of this parameter.
My suggestion, get in a DEV/TEST environment and test to see how to best configure your environment for RMAN database backups/control file, archivelog backups also taking into consideration OS tape backup solutions. I always configure DISK for RMAN backups, then have some other tape backup utility sweep those locations to tape ensuring that I have sufficient backups to reconstitute my database - I also include a copy of the init.ora file, password file as well as the spfile backup in this location.
>
In case of Archivelogs, It is better to create and execute a Purge Job to remove Archivelogs after backup them on tape.I almost agree. I try to keep all archivelogs necessary for recovery from last full backup online. I try to keep a full backup online as well. much faster at restoring stuff instead of trying to locate it on tape.

Cloning DB on a different server from RMAN Tape backup

RDBMS version           : 11.2.0.2 on Solaris 10
Media Management Layer : Netbackup v7
I have done only backups to Tape. I have never done restore,recovery from Tape.
We have a production DB named NEHPROD running on server qualmh214. Every Monday morning an RMAN Full backup for NEHPROD is taken to Tape.
Production server : qualmh214        DB Name:NEHPROD
run
ALLOCATE CHANNEL c1 TYPE 'SBT_TAPE';
SEND 'NB_ORA_CLIENT=qualmh214,NB_ORA_POLICY=qualmh214_rman,NB_ORA_SERV=qualmh238,NB_ORA_SCHED=Daily';
backup database   FORMAT 'NEHPROD_%d_%U_%t.rbk' tag='NEHPROD_full';
}I need to create a Test DB in a different server (qualmh199) by restoring directly from NEHPROD's Full backup in tape .
From qualmh199, how can I connect to the Tape Media server ?
Even If I do connect to the Tape media server, how can i get access to tape backups of another DB? In the RMAN run block you can't specify a DB name. Right?
Even if I get access to another DB's backup , How can i specify which Date's Full backup I need to use to restore ?

From qualmh199, how can I connect to the Tape Media server ?You have to allocate channels to tape & need to mention NB parameters as example below.
in RMAN script
ALLOCATE CHANNEL CH1 DEVICE TYPE SBT_TAPE PARMS 'SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64';
SEND 'NB_ORA_SERV=<server.com>, NB_ORA_CLIENT=<target.server>';
Even If I do connect to the Tape media server, how can i get access to tape backups of another DB? In the RMAN run block you can't specify a DB name. Right?If the libraries are installed and you able to perform, you can go for either duplicate database or simple RMAN restore. You can mention other DB names also
Ex: duplicate target database to 'test';
Even if I get access to another DB's backup , How can i specify which Date's Full backup I need to use to restore ?You can mention TAG's if you are using RMAN restore.

ASM and Logical backups

Is it possible to use ASM diskgroup as a destination
for logical backups? For example I have ASM diskgroup
for Flash Recovery Area and want to use its space for dumps too.

No,
only datafiles,
datafile copies,
controlfiles,
online redo log files,
archived online redo log files,
rman backup sets
ar possible as far as I know.
Not possible are:
alertlogs,
trace files,
password files,
binaries.
Regards,
Lutz

Track table that contains a block id

Friends
Is it possible to find wich table(s) contains data from a specific block?
I got stuck on a scenario that I'm not using RMAN and I got a block corruption and I need to fix it...
I have the block#, but I could not find a querie to track which table contains that data
Cheers

SQL> select file#, block#, CORRUPTION_CHANGE#, CORRUPTION_TYPE from V$DATABASE_B
LOCK_CORRUPTION;
FILE# BLOCK# CORRUPTION_CHANGE# CORRUPTIO
3 144438 0 CORRUPT
3 144277 0 CORRUPT
3 144446 0 CORRUPT
12 134018 0 CORRUPT
3 144501 0 CORRUPT
12 134714 0 CORRUPT
3 144493 0 CORRUPT
3 144293 0 CORRUPT
3 144309 0 CORRUPT
3 144325 0 CORRUPT
SQL> select segment_name, segment_type, owner
2 from dba_extents
3 where file_id = 12
4 and 134018 between block_id and block_id + blocks -1;
SEGMENT_NAME
SEGMENT_TYPE OWNER
PRODUCT
TABLE BLI
I'm not running rman :(

What else in logical backups

Hi, DBA Professionals,
If i take logical backup of full database, what else in the database to take backup.
is this logical backup will take only logical data or physical data?
if it takes logical only then what about row=y
and what is difference between isqlplus and oem
could you please clarify my doubts.
thanks a lot in advance.

805547 wrote:
thanks a lot for guided me,
i am using 10g R2 database.
if i take complete, incremental, cumulative backups of my database, if i loss whole database is it possible to recover it with logical backups. if it is yes, what is the method.
A "complete, incremental, cumulative backups" would be physical backups using rman. a "logical" backup would be an export (exp or expdp) dump. The logical backup can only be imported back into a working database, and would be a point-in-time snapshot of the data. With use of proper backup options, a proper physical backup can recover a database from a total loss, and to any point in time covered by the backups.
if i loss system datafile only what is the method to recover it using logical backups.There is none. That's why "logical" backups are only one part - and the least important part - of a complete backup/recovery strategy.

Tracking the logical backups' success

DB version:10.2.0.4
OS : Solaris 5.10
We have 45 schemas in one of our critical production DBs.
Apart from the RMAN backups, we take logical backups of all the business related 45 schemas.
A shell script is dynamically generated and executed every day to take EXP backups of all these 45 schemas
I need to create a PL/SQL code or Shell script which will notify us through email if any of the EXP commands have failed.
What is the 'professional' way to do this? We already have the Email sending PL/SQL procedure ready.

Y.Ramlet wrote:
Will Enterprise Manager send mails when individual schemas's backups have failed ?EM would send mail when the requested job is failed and you have configured another , backup job which would run and send an email. So the answer would be IMO, it depends .
HTH
Aman....

Logical backup?

Hi Guru's
i confused with terms ,can any body tell me what is logical backup ......or is it same as cold backup and hot backup??? please help me
Chetan ....

CHETAN YADAV wrote:
Hi Guru's
i confused with terms ,can any body tell me what is logical backup ......or is it same as cold backup and hot backup??? please help me
Chetan ....Logical backup is taking using exp/expdp utilities.
Cold backup can be take user managed so,you can shutdown immediate database and copy all control/data/online logs to other backup location,this is cold backup,also you can take this rman.
Hot backup can be take if database running in archivelog mode.You can use RMAN or user managed.from rman you can try just BACKUP DATABASE and that is enough.Or user managed you can use ALTER DATABASE BEGIN BACKUP or ALTER TABLESPACE BEGIN BACKUP then using OS commands you can copy datafiles to other backup location.
Finally these are different.

RMAN logical backup containing unused blocks

Similar Messages

Maybe you are looking for