01
壞塊概述
02
壞塊檢測
dbv help=y
DBVERIFY: Release 12.2.0.1.0 - Production on Tue Jan 19 17:24:26 2021
Copyright (c) 1982, 2017, 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 file=+DATADG/xxx/DATAFILE/system.1135.1061813741
blocksize=8192 USERID=sys/xxxx
logfile=system.1135.1061813741.1.log
03
壞塊修復(fù)
RECOVER DATAFILE 8 BLOCK 13 DATAFILE 2 BLOCK 19;
RECOVER CORRUPTION LIST;(V$DATABASE_BLOCK_CORRUPTION)
By default, RMAN first searches for good blocks in the real-
time query physical standby database, then flashback logs
and then blocks in full or level 0 incremental backups.
<https://docs.oracle.com/database/121/BRADV/rcmblock.htm#BRADV89782>
REM Create the repair table in a given tablespace:
BEGIN
DBMS_REPAIR.ADMIN_TABLES (
TABLE_NAME => REPAIR_TABLE,
TABLE_TYPE => dbms_repair.repair_table,
ACTION => dbms_repair.create_action,
TABLESPACE => &tablespace_name);
END;
/
REM Identify corrupted blocks for schema.object (it also can be done at partition level with parameter PARTITION_NAME):
set serveroutput on
DECLARE num_corrupt INT;
BEGIN
num_corrupt := 0;
DBMS_REPAIR.CHECK_OBJECT (
SCHEMA_NAME => &schema_name,
OBJECT_NAME => &object_name,
REPAIR_TABLE_NAME => REPAIR_TABLE,
corrupt_count => num_corrupt);
DBMS_OUTPUT.PUT_LINE(number corrupt: || TO_CHAR (num_corrupt));
END;
/
REM Optionally display any corrupted block identified by check_object:
select BLOCK_ID, CORRUPT_TYPE, CORRUPT_DESCRIPTION
from REPAIR_TABLE;
REM Mark the identified blocks as corrupted
DECLARE num_fix INT;
BEGIN
num_fix := 0;
DBMS_REPAIR.FIX_CORRUPT_BLOCKS (
SCHEMA_NAME => &schema_name,
OBJECT_NAME=> &object_name,
OBJECT_TYPE => dbms_repair.table_object,
REPAIR_TABLE_NAME => REPAIR_TABLE,
FIX_COUNT=> num_fix);
DBMS_OUTPUT.PUT_LINE(num fix: || to_char(num_fix));
END;
/
REM Allow future DML statements to skip the corrupted blocks:
BEGIN
DBMS_REPAIR.SKIP_CORRUPT_BLOCKS (
SCHEMA_NAME => &schema_name,
OBJECT_NAME => &object_name,
OBJECT_TYPE => dbms_repair.table_object,
FLAGS => dbms_repair.SKIP_FLAG);
END;
/
alter system set events=10231 trace name context forever,level 10’;
alter system set events=10231 trace name context off;
04
總 結(jié)
文章版權(quán)歸作者所有,未經(jīng)允許請勿轉(zhuǎn)載,若此文章存在違規(guī)行為,您可以聯(lián)系管理員刪除。
轉(zhuǎn)載請注明本文地址:http://www.ezyhdfw.cn/yun/129681.html
摘要:微軟正在繼續(xù)向提交潛在的新規(guī)范。微軟方面表示,預(yù)計(jì)在未來幾個月內(nèi)完成規(guī)范,并在今年晚些時候推出。此外,微軟還在推進(jìn)另一個開放計(jì)算貢獻(xiàn)的項(xiàng)目。去年年底,微軟推出了加密微控制器標(biāo)準(zhǔn)。微軟正在繼續(xù)向Open Compute Project提交潛在的新規(guī)范。在美國圣何塞舉行的Open Compute Project(OCP)美國峰會上,微軟推出了Project Denali,一項(xiàng)用于SSD固件接口標(biāo)...
摘要:記錄總結(jié)一下的中引入圖片路徑的幾種書寫方式中靜態(tài)資源的引入機(jī)制關(guān)于靜態(tài)資源的官方文檔靜態(tài)資源可以通過兩種方式進(jìn)行處理在被導(dǎo)入或在中通過相對路徑以開頭被引用。如果是一個絕對路徑,例如,它將會被保留不變。 vue --version 3.6.3記錄總結(jié)一下的Vue中引入圖片路徑的幾種書寫方式 vue中靜態(tài)資源的引入機(jī)制 Vue.js關(guān)于靜態(tài)資源的官方文檔 靜態(tài)資源可以通過兩種方式進(jìn)行處理...
摘要:比如域的頁面通過嵌入了一個域的頁面,可以通過以下方法實(shí)現(xiàn)和的通信通過跨域以上幾種都是雙向通信的,即兩個,頁面與或是頁面與頁面之間的,下面說幾種單項(xiàng)跨域的一般用來獲取數(shù)據(jù),因?yàn)橥ㄟ^標(biāo)簽引入的是不受同源策略的限制的。 跨域整理@(前端筆記) 跨域 只要協(xié)議、域名、端口有任何一個不同,都被當(dāng)作是不同的域。由于瀏覽器的同源策略,其限制之一是不能通過ajax的方法情趣請求不同源的文檔。第二個限制...
摘要:一總覽本文章不對日志組件進(jìn)行優(yōu)劣評價,只是對關(guān)系進(jìn)行對比。在日志中組件中存在這樣的幾種關(guān)系,這幾種關(guān)系理解清楚,有助于我們對日志的引入和使用。 一、 總覽 本文章不對日志組件進(jìn)行優(yōu)劣評價,只是對關(guān)系進(jìn)行對比。在日志中組件中存在這樣的幾種關(guān)系, 這幾種關(guān)系理解清楚, 有助于我們對日志的引入和使用。 showImg(https://segmentfault.com/img/bVbow7o?...
閱讀 1459·2023-01-11 13:20
閱讀 1812·2023-01-11 13:20
閱讀 1263·2023-01-11 13:20
閱讀 2005·2023-01-11 13:20
閱讀 4226·2023-01-11 13:20
閱讀 2879·2023-01-11 13:20
閱讀 1488·2023-01-11 13:20
閱讀 3807·2023-01-11 13:20