![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Another strange thing I noticed: 1. When doing export backup, export backup reports about corrupted blocks. |
|
2. When I do expdp no errors are reported. So question is why is exp command checking empty blocks? |
#3
| |||
| |||
|
|
I am using Oracle 11.1.0.7.1 on HP UNIX 11i. On several occasions, I have been seen that block corruptions are reported by rman. I have never seen this problem in previous release of databases; but I have seen it more than once in Oracle 11g. However, when I run dbv command; I do not see any corruption in data and index blocks; so my conclusion is block corruption is in empty pages. Anyone has ideas why block corruption occurs in Oracle 11g. Has Oracle’s algorithm for checking block corruption have changed in 11g; I.e.; these corruptions existed in older Oracle releases but not reported by rman, Another strange thing I noticed: 1. When doing export backup, export backup reports about corrupted blocks. 2. When I do expdp no errors are reported. So question is why is exp command checking empty blocks? Any insights in above will be appreciated. |
#4
| |||
| |||
|
|
I am using Oracle 11.1.0.7.1 on HP UNIX 11i. On several occasions, I have been seen that block corruptions are reported by rman. I have never seen this problem in previous release of databases; but I have seen it more than once in Oracle 11g. However, when I run dbv command; I do not see any corruption in data and index blocks; so my conclusion is block corruption is in empty pages. Anyone has ideas why block corruption occurs in Oracle 11g. Has Oracle’s algorithm for checking block corruption have changed in 11g; I.e.; these corruptions existed in older Oracle releases but not reported by rman, Another strange thing I noticed: 1. When doing export backup, export backup reports about corrupted blocks. 2. When I do expdp no errors are reported. So question is why is exp command checking empty blocks? Any insights in above will be appreciated. |
#5
| |||
| |||
|
|
On Aug 4, 11:08*pm, zigzagdna <zigzag... (AT) yahoo (DOT) com> wrote: I am using Oracle 11.1.0.7.1 on HP UNIX 11i. On several occasions, I have been seen that block corruptions are reported by rman. I have never seen this problem in previous release of databases; but I have seen it more than once in Oracle 11g. However, when I run dbv command; I do not see any corruption in data and index blocks; so my conclusion is block corruption is in empty pages. Anyone has ideas why block corruption occurs in Oracle 11g. Has Oracle’s algorithm for checking block corruption have changed in 11g; I.e.; these corruptions existed in older Oracle releases but not reported by rman, Another strange thing I noticed: 1. When doing export backup, export backup reports about corrupted blocks. 2. When I do expdp no errors are reported. So question is why is exp command checking empty blocks? Any insights in above will be appreciated. If the rman backup and expdp are identifying corrupted blocks what does the following query show? set echo off -- -- Display corrupt block information -- -- 20100105 *Mark D Powell * Save 4 future use -- select * * from * v$database_block_corruption order by * file# *,block# / You can find the object idenfified by this query by looking at dba_extents for the extent that the identified files and blocks are held within. HTH -- Mark D Powell --- Hide quoted text - - Show quoted text - |
#6
| |||
| |||
|
|
On Wed, 04 Aug 2010 20:08:15 -0700, zigzagdna wrote: Another strange thing I noticed: 1. When doing export backup, export backup reports about corrupted blocks. Export is not a backup. 2. When I do expdp no errors are reported. So question is why is exp command checking empty blocks? Because it's doing full table scans. Full table scan stops at HWM, not before. Also, exp utility is deprecated in 11.2. Do not use it. --http://mgogala.byethost5.com |
#7
| |||
| |||
|
|
On Wed, 04 Aug 2010 20:08:15 -0700, zigzagdna wrote: Another strange thing I noticed: 1. When doing export backup, export backup reports about corrupted blocks. Export is not a backup. |
|
2. When I do expdp no errors are reported. So question is why is exp command checking empty blocks? Because it's doing full table scans. Full table scan stops at HWM, not before. Also, exp utility is deprecated in 11.2. Do not use it. |
#8
| |||
| |||
|
|
Yes, tis query shows some block corruptions but it does not tell you corrupted blocks are empty. When I run dbv it does not show any corruption in data or indexes. So I am assuming that corruption is in empty pages. |
#9
| |||
| |||
|
|
On Aug 5, 12:59*pm, zigzagdna <zigzag... (AT) yahoo (DOT) com> wrote: Yes, tis query shows some block corruptions but it does not tell you corrupted blocks are empty. When I run dbv it does not show any corruption in data or indexes. So I am assuming that corruption is in empty pages. You don't have to assume, just dump the block reported by RMAN as being corrupt. |
#10
| |||
| |||
|
|
On Aug 5, 9:51 pm, Steve Howard <stevedhow... (AT) gmail (DOT) com> wrote: On Aug 5, 12:59 pm, zigzagdna <zigzag... (AT) yahoo (DOT) com> wrote: Yes, tis query shows some block corruptions but it does not tell you corrupted blocks are empty. When I run dbv it does not show any corruption in data or indexes. So I am assuming that corruption is in empty pages. You don't have to assume, just dump the block reported by RMAN as being corrupt. Soory, don't undestand why do you mean by dump the block. |
![]() |
| Thread Tools | |
| Display Modes | |
| |