ORACLE使用dbv工具檢驗數(shù)據(jù)文件是否有壞塊

dbv工具可以用來驗證數(shù)據(jù)文件的有效性，在數(shù)據(jù)庫恢復(fù)之前可以使用該命令對備份文件進行有效性檢查，

十余年的雷山網(wǎng)站建設(shè)經(jīng)驗，針對設(shè)計、前端、開發(fā)、售后、文案、推廣等六對一服務(wù)，響應(yīng)快，48小時及時工作處理。成都營銷網(wǎng)站建設(shè)的優(yōu)勢是能夠根據(jù)用戶設(shè)備顯示端的尺寸不同，自動調(diào)整雷山建站的顯示方式，使網(wǎng)站能夠適用不同顯示終端，在瀏覽器中調(diào)整網(wǎng)站的寬度，無論在任何一種瀏覽器上瀏覽網(wǎng)站，都能展現(xiàn)優(yōu)雅布局與設(shè)計，從而大程度地提升瀏覽體驗。創(chuàng)新互聯(lián)從事“雷山網(wǎng)站設(shè)計”,“雷山網(wǎng)站推廣”以來，每個客戶項目都認(rèn)真落實執(zhí)行。

防止因備份文件本身的問題導(dǎo)致數(shù)據(jù)庫無法恢復(fù)。

當(dāng)然，dbv命令也可以對在線的數(shù)據(jù)文件進行檢查。

注意，dbv工具只可以對數(shù)據(jù)文件進行檢查，無法使用它完成控制文件和日志文件的檢查。

1.dbv命令語法

dbverify ::=

dbv [ USERID=username/password ]

FILE = filename

| { START = block_address | END = block_address }

| BLOCKSIZE = integer

| HIGH_SCN = integer

| LOGFILE = filename

| FEEDBACK = integer

| HELP = { Y | N }

| PARFILE = filename

End of description.

參考自O(shè)racle官方文檔

2.查看幫助文檔

從語法定義中我們看到“HELP = { Y | N }”選項，我們可以使用它查看dbv的幫助信息。

ticket@secDB /home/oracle$ dbv help=y

DBVERIFY: Release 11.2.0.1.0 - Production on Wed Mar 31 19:47:36 2010

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

Keyword Description (Default)

----------------------------------------------------

FILE File to Verify (NONE)

START Start Block (First Block of File)

END End Block (Last Block of File)

BLOCKSIZE Logical Block Size (8192)

LOGFILE Output Log (NONE)

FEEDBACK Display Progress (0)

PARFILE Parameter File (NONE)

USERID Username/Password (NONE)

SEGMENT_ID Segment ID (tsn.relfile.block) (NONE)

HIGH_SCN Highest Block SCN To Verify (NONE)

(scn_wrap.scn_base OR scn)

幫助信息中描述了dbv命令的使用方法，不贅述。

3.體驗dbv工具的效果

1）查看系統(tǒng)中的數(shù)據(jù)文件名稱

sys@ticket col name for a60

sys@ticket select name from v$datafile;

NAME

------------------------------------------------------------

/oracle/ora11gR2/oradata/ticket/system01.dbf

/oracle/ora11gR2/oradata/ticket/sysaux01.dbf

/oracle/ora11gR2/oradata/ticket/undotbs01.dbf

/oracle/ora11gR2/oradata/ticket/users01.dbf

2）使用dbv工具對users01.dbf進行檢查

（1）使用最簡單的參數(shù)

sys@ticket !dbv file=/oracle/ora11gR2/oradata/ticket/users01.dbf

DBVERIFY: Release 11.2.0.1.0 - Production on Wed Mar 31 19:50:59 2010

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

DBVERIFY - Verification starting : FILE = /oracle/ora11gR2/oradata/ticket/users01.dbf

DBVERIFY - Verification complete

Total Pages Examined : 35520

Total Pages Processed (Data) : 33029

Total Pages Failing (Data) : 0

Total Pages Processed (Index): 20

Total Pages Failing (Index): 0

Total Pages Processed (Other): 402

Total Pages Processed (Seg) : 0

Total Pages Failing (Seg) : 0

Total Pages Empty : 2069

Total Pages Marked Corrupt : 0

Total Pages Influx : 0

Total Pages Encrypted : 0

Highest block SCN : 9291961 (0.9291961)

在實際使用中重點關(guān)注以下信息：

Total Pages Failing (Data) : 0

Total Pages Failing (Index): 0

Total Pages Failing (Seg) : 0

Total Pages Marked Corrupt : 0

如果以上信息返回結(jié)果不為0，需要重點關(guān)注！及時排查原因。

（2）如果指定logfile參數(shù)，檢查結(jié)果將只記錄在日志文件中，屏幕上不顯示

sys@ticket !dbv file=/oracle/ora11gR2/oradata/ticket/users01.dbf logfile=dbv_users01.log

DBVERIFY: Release 11.2.0.1.0 - Production on Wed Mar 31 19:52:20 2010

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

此時可以使用SQL*Plus的edit命令查看生成的日志文件內(nèi)容。

sys@ticket ed dbv_users01.log

Oracle數(shù)據(jù)庫打不開 該怎么辦？我們公司的oracle數(shù)據(jù)庫壞了 打不開了，該如何處理？

如果自己搞不定可以找詩檀軟件專業(yè)ORACLE數(shù)據(jù)庫修復(fù)團隊成員幫您恢復(fù)!

詩檀軟件專業(yè)數(shù)據(jù)庫修復(fù)團隊

Oracle的損壞/壞塊 主要分以下幾種：

ORA-1578

ORA-8103

ORA-1410

ORA-1499

ORA-1578

ORA-81##

ORA-14##

ORA-26040

ORA-600 Errors

Block Corruption

Index Corruption

Row Corruption

UNDO Corruption

Control File

Consistent Read

Dictionary

File/RDBA/BL

Error Description Corruption related to:

ORA-1578 ORA-1578一般為Oracle檢測到存在物理壞塊問題，包括其檢測數(shù)據(jù)塊中的checksum不正確，或者tail_chk信息不正確等。 ORA-1578 is reported when a block is thought to be corrupt on read.

Block

數(shù)據(jù)塊

OERR: ORA-1578 “ORACLE data block corrupted (file # %s, block # %s)” Master Note

OERR: ORA-1578 “ORACLE data block corrupted (file # %s, block # %s)”

Fractured Block explanation

Handling Oracle Block Corruptions in Oracle7/8/8i/9i/10g/11g

Diagnosing and Resolving 1578 reported on a Local Index of a Partitioned table

ORA-1410

ORA-1410錯誤常見于從INDEX或其他途徑獲得的ROWID,到數(shù)據(jù)表中查詢發(fā)現(xiàn)沒有對應(yīng)的記錄。

該錯誤可能因為數(shù)據(jù)表與其索引存在不一致，也可能是分區(qū)的數(shù)據(jù)表本身存在問題。

This error is raised when an operation refers to a ROWID in a table for which there is no such row.

The reference to a ROWID may be implicit from a WHERE CURRENT OF clause or directly from a WHERE ROWID=… clause.

ORA 1410 indicates the ROWID is for a BLOCK that is not part of this table.

Row

數(shù)據(jù)行

Understanding The ORA-1410

Summary Of Bugs Containing ORA 1410

OERR: ORA 1410 “invalid ROWID”

ORA-8103

該ORA-8103可能由多個BUG引起，例如LOB在10.2.0.4之前可能會由于BUG覆蓋了另一張表的segment header，導(dǎo)致出現(xiàn)ORA-8103錯誤。

診斷該問題可以從數(shù)據(jù)表的segment header和data_object_id入手。

The object has been deleted by another user since the operation began.

If the error is reproducible, following may be the reasons:-

a.) The header block has an invalid block type.

b.) The data_object_id (seg/obj) stored in the block is different than the data_object_id stored in the segment header. See dba_objects.data_object_id and compare it to the decimal value stored in the block (field seg/obj).

Block

數(shù)據(jù)塊

ORA-8103 Troubleshooting, Diagnostic and Solution

OERR: ORA-8103 “object no longer exists” / Troubleshooting, Diagnostic and Solution

ORA-8102 ORA-8102常見于索引鍵值與表上存的值不一致。 An ORA-08102 indicates that there is a mismatch between the key(s) stored in the index and the values stored in the table. What typically happens is the index is built and at some future time, some type of corruption occurs, either in the table or index, to cause the mismatch.

Index

索引

OERR ORA-8102 “index key not found, obj# %s, file %s, block %s (%s)

ORA-1499 對表和索引做交叉驗證時發(fā)現(xiàn)問題 An error occurred when validating an index or a table using the ANALYZE command.

One or more entries does not point to the appropriate cross-reference.

Index

索引

ORA-1499. Table/Index row count mismatch

OERR: ORA-1499 table/Index Cross Reference Failure – see trace file

ORA-1498 Generally this is a result of an ANALYZE … VALIDATE … command.

This error generally manifests itself when there is inconsistency in the data/Index block. Some of the block check errors that may be found:-

a.) Row locked by a non-existent transaction

b.) The amount of space used is not equal to block size

c.) Transaction header lock count mismatch.

While support are processing the tracefile it may be worth the re-running the ANALYZE after restarting the database to help show if the corruption is consistent or if it ‘moves’.

Send the tracefile to support for analysis.

If the ANALYZE was against an index you should check the whole object. Eg: Find the tablename and execute:

ANALYZE TABLE xxx VALIDATE STRUCTURE CASCADE; Block

OERR: ORA 1498 “block check failure – see trace file”

ORA-26040 由于采用過nologging/unrecoverable選項的redo生成機制，且做過對應(yīng)的recover，導(dǎo)致數(shù)據(jù)塊中被填滿了0XFF，導(dǎo)致報錯ORA-26040。 Trying to access data in block that was loaded without redo generation using the NOLOGGING/UNRECOVERABLE option.

This Error raises always together with ORA-1578

Block

數(shù)據(jù)塊

OERR ORA-26040 Data block was loaded using the NOLOGGING option

ORA-1578 / ORA-26040 Corrupt blocks by NOLOGGING – Error explanation and solution

ORA-1578 ORA-26040 in a LOB segment – Script to solve the errors

ORA-1578 ORA-26040 in 11g for DIRECT PATH with NOARCHIVELOG even if LOGGING is enabled

ORA-1578 ORA-26040 On Awr Table

Errors ORA-01578, ORA-26040 On Standby Database

Workflow Tables ORA-01578 ORACLE data block corrupted ORA-26040 Data block was loaded using the NOLOGGING option

ORA-1578, ORA-26040 Data block was loaded using the NOLOGGING option

ORA-600[12700]

從索引獲得的ROWID，對應(yīng)到數(shù)據(jù)表時發(fā)現(xiàn)不存在數(shù)據(jù)行錯誤。

一把是一致性度consistent read問題

Oracle is trying to access a row using its ROWID, which has been obtained from an index.

A mismatch was found between the index rowid and the data block it is pointing to. The rowid points to a non-existent row in the data block. The corruption can be in data and/or index blocks.

ORA-600 [12700] can also be reported due to a consistent read (CR) problem.

Consistent Read

一致性讀

Resolving an ORA-600 [12700] error in Oracle 8 and above.

ORA-600 [12700] “Index entry Points to Missing ROWID”

ORA-600[3020] 主要問題是redo和數(shù)據(jù)塊中的信息不一致 This is called a ‘STUCK RECOVERY’.

There is an inconsistency between the information stored in the redo and the information stored in a database block being recovered. Redo

ORA-600 [3020] “Stuck Recovery”

Information Required for Root Cause Analysis of ORA-600 [3020] (stuck recovery)

ORA-600[4194] 主要是redo記錄與回滾rollback/undo的記錄不一致 A mismatch has been detected between Redo records and rollback (Undo) records.

We are validating the Undo record number relating to the change being applied against the maximum undo record number recorded in the undo block.

This error is reported when the validation fails. Undo

ORA-600 [4194] “Undo Record Number Mismatch While Adding Undo Record”

Basic Steps to be Followed While Solving ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter

ORA-600[4193] 主要是redo記錄與回滾rollback/undo的記錄不一致 A mismatch has been detected between Redo records and Rollback (Undo) records.

We are validating the Undo block sequence number in the undo block against the Redo block sequence number relating to the change being applied.

This error is reported when this validation fails. Undo

ORA-600 [4193] “seq# mismatch while adding undo record”

Basic Steps to be Followed While Solving ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter

Ora-600 [4193] When Opening Or Shutting Down A Database

ORA-600 [4193] When Trying To Open The Database

ORA-600[4137] transaction id不匹配，問題可能存在與回滾段中或者對象本身存在訛誤 While backing out an undo record (i.e. at the time of rollback) we found a transaction id mis-match indicating either a corruption in the rollback segment or corruption in an object which the rollback segment is trying to apply undo records on.

This would indicate a corrupted rollback segment. Undo/Redo

ORA-600 [4137] “XID in Undo and Redo Does Not Match”

ORA-600[6101] Not enough free space was found when inserting a row into an index leaf block during the application of undo. Index

ORA-600 [6101] “insert into leaf block (undo)”

ORA-600[2103] Oracle is attempting to read or update a generic entry in the control file.

If the entry number is invalid, ORA-600 [2130] is logged. Control File

ORA-600 [2130] “Attempt to access non-existant controlfile entry”

ORA-600[4512] Oracle is checking the status of transaction locks within a block.

If the lock number is greater than the number of lock entries, ORA-600 [4512] is reported followed by a stack trace, process state and block dump.

This error possibly indicates a block corruption. Block

ORA-600 [4512] “Lock count mismatch”

ORA-600[2662] 主要是發(fā)現(xiàn)一個數(shù)據(jù)塊的SCN甚至超過了當(dāng)前SCN，常規(guī)解決途徑有調(diào)整SCN等，但11.2以后Oracle公司使較多調(diào)整SCN的方法失效了 A data block SCN is ahead of the current SCN.

The ORA-600 [2662] occurs when an SCN is compared to the dependent SCN stored in a UGA variable.

If the SCN is less than the dependent SCN then we signal the ORA-600 [2662] internal error. Block

ORA-600 [2662] “Block SCN is ahead of Current SCN”

ORA 600 [2662] DURING STARTUP

ORA-600[4097] 訪問一個回滾段頭以便確認(rèn)事務(wù)是否已提交時，發(fā)現(xiàn)XID有問題 We are accessing a rollback segment header to see if a transaction has been committed.

However, the xid given is in the future of the transaction table.

This could be due to a rollback segment corruption issue OR you might be hitting the following known problem. Undo

如何使用rman 檢查oracle數(shù)據(jù)庫壞塊

如何使用rman 檢查oracle數(shù)據(jù)庫壞塊

oracle檢測壞塊的方式：

1、利用oracle的RMAN工具

2、利用dbv工具檢測

3、利用 exp/imp工具檢測