11G執行oracle自帶的檢查 check
How to run Health Checks Manually
========================
We can run Health Monitor manually in following 2 ways
# By using the DBMS_HM PL/SQL package
# By using the Enterprise Manager interface, found on the Checkers subpage of the Advisor
Central page
How to run Health Checks Using the DBMS_HM(DBMS_HM.RUN_CHECK) PL/SQL Package
----------------------------------------------------------------------------
The DBMS_HM has procedure called RUN_CHECK . To call RUN_CHECK,
We need to supply the name of the check and a name for the run, as follows:
BEGIN
DBMS_HM.RUN_CHECK('Dictionary Integrity Check', 'my_run');
END;
To obtain a list of health check names, run the following query:
SELECT name FROM v$hm_check WHERE internal_check='N';
NAME
----------------------------------------------------------------
DB Structure Integrity Check
Data Block Integrity Check
Redo Integrity Check
Transaction Integrity Check
Undo Segment Integrity Check
Dictionary Integrity Check
Most of health checks accept input parameters. You can view parameter names and
descriptions with the V$HM_CHECK_PARAM view. Some parameters are mandatory while
others are optional. If optional parameters are omitted, defaults are used. The following query displays parameter information for all health checks:
SELECT c.name check_name, p.name parameter_name, p.type,
p.default_value, p.description
FROM v$hm_check_param p, v$hm_check c
WHERE p.check_id = c.id and c.internal_check = 'N'
ORDER BY c.name;
The Input parameters are passed in the input_params argument as name/value pairs
separated by semicolons (;). The following example illustrates how to pass the transaction ID as a parameter to the Transaction Integrity Check:
BEGIN
DBMS_HM.RUN_CHECK (
check_name => 'Transaction Integrity Check',
run_name => 'my_run',
input_params => 'TXN_ID=7.33.2');
END;
How to Run Health Checks Using Enterprise Manager
------------------------------------------------
Enterprise Manager provides an interface for running Health Monitor checkers.
To run a Health Monitor Checker using Enterprise Manager:
1. On the Database Home page, in the Related Links section, click Advisor Central.
2. Click Checkers to view the Checkers subpage.
3. In the Checkers section, click the checker you want to run.
4. Enter values for input parameters or, for optional parameters, leave them blank to
accept the defaults.
5. Click Run, confirm your parameters, and click Run again.
========================
We can run Health Monitor manually in following 2 ways
# By using the DBMS_HM PL/SQL package
# By using the Enterprise Manager interface, found on the Checkers subpage of the Advisor
Central page
How to run Health Checks Using the DBMS_HM(DBMS_HM.RUN_CHECK) PL/SQL Package
----------------------------------------------------------------------------
The DBMS_HM has procedure called RUN_CHECK . To call RUN_CHECK,
We need to supply the name of the check and a name for the run, as follows:
BEGIN
DBMS_HM.RUN_CHECK('Dictionary Integrity Check', 'my_run');
END;
To obtain a list of health check names, run the following query:
SELECT name FROM v$hm_check WHERE internal_check='N';
NAME
----------------------------------------------------------------
DB Structure Integrity Check
Data Block Integrity Check
Redo Integrity Check
Transaction Integrity Check
Undo Segment Integrity Check
Dictionary Integrity Check
Most of health checks accept input parameters. You can view parameter names and
descriptions with the V$HM_CHECK_PARAM view. Some parameters are mandatory while
others are optional. If optional parameters are omitted, defaults are used. The following query displays parameter information for all health checks:
SELECT c.name check_name, p.name parameter_name, p.type,
p.default_value, p.description
FROM v$hm_check_param p, v$hm_check c
WHERE p.check_id = c.id and c.internal_check = 'N'
ORDER BY c.name;
The Input parameters are passed in the input_params argument as name/value pairs
separated by semicolons (;). The following example illustrates how to pass the transaction ID as a parameter to the Transaction Integrity Check:
BEGIN
DBMS_HM.RUN_CHECK (
check_name => 'Transaction Integrity Check',
run_name => 'my_run',
input_params => 'TXN_ID=7.33.2');
END;
How to Run Health Checks Using Enterprise Manager
------------------------------------------------
Enterprise Manager provides an interface for running Health Monitor checkers.
To run a Health Monitor Checker using Enterprise Manager:
1. On the Database Home page, in the Related Links section, click Advisor Central.
2. Click Checkers to view the Checkers subpage.
3. In the Checkers section, click the checker you want to run.
4. Enter values for input parameters or, for optional parameters, leave them blank to
accept the defaults.
5. Click Run, confirm your parameters, and click Run again.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/500314/viewspace-1066098/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Oracle 11g RAC 檢查各部分執行狀態Oracle
- Oracle 11g 系統自帶任務的檢視和更改Oracle
- check whether the crystal report runtime is exists 檢查crystalreport執行時是否存在
- 【Azure 應用服務】App Service 執行狀況健康檢查功能簡介 (Health check)APP
- oracle job使用詳解及job不執行的檢查方法Oracle
- oracle 11g 新特性 磁碟組檢查Oracle
- 對ORACLE的SGA 進行檢查Oracle
- 檢查sql or session 執行的進度SQLSession
- Oracle EBS Applications 11i Health Check(健康檢查11項)OracleAPP
- Windows 98 禁止登錄檔檢查器自動執行(轉)Windows
- ORACLE執行計劃的檢視Oracle
- java自帶的四種執行緒池Java執行緒
- 執行caffe自帶的mnist例項教程
- Oracle 11g 檢查 RMAN 備份的有效性Oracle
- oracle 正在執行的物件查詢Oracle物件
- oracle檢視執行最慢與查詢次數最多的sql語句OracleSQL
- Oracle 11g dataguard check real time applyOracleAPP
- Oracle檢視執行計劃的命令Oracle
- oracle檢視執行計劃的方法Oracle
- Oracle 檢視SQL的執行計劃OracleSQL
- python自帶pip怎麼執行Python
- Oracle檢視正在執行的SQL以及執行計劃分析OracleSQL
- 【Oracle】-【索引-HINT,執行計劃】-帶HINT的索引執行計劃Oracle索引
- Oracle“並行執行”——監控檢視Oracle並行
- 查詢Oracle正在執行和執行過的SQL語句OracleSQL
- SQL語句執行進度檢查SQL
- 自適應查詢執行:在執行時提升Spark SQL執行效能SparkSQL
- 檢視ORACLE的實際執行計劃Oracle
- 檢視oracle系統的執行時間Oracle
- Oracle檢視執行計劃(五)Oracle
- Oracle檢視執行計劃(六)Oracle
- Oracle檢視執行計劃(一)Oracle
- Oracle檢視執行計劃(二)Oracle
- Oracle檢視執行計劃(三)Oracle
- Oracle檢視執行計劃(四)Oracle
- oracle如何檢視執行計劃Oracle
- 檢視oracle執行計劃 - 轉Oracle
- 查詢Oracle正在執行的SQL語句OracleSQL