11g health monitor新特性 DBMS_HM.RUN_CHECK

简介: 11g health monitor新特性,DBMS_HM.RUN_CHECK一例

11g health monitor新特性,DBMS_HM.RUN_CHECK一例


BEGIN
  DBMS_HM.RUN_CHECK('Dictionary Integrity Check', 'my_run');
END;
/


检查结果


SQL> select dbms_hm.get_run_report('my_run') from dual;
DBMS_HM.GET_RUN_REPORT('MY_RUN')
--------------------------------------------------------------------------------
Basic Run Information
 Run Name        : my_run



run_check结构:


PROCEDURE RUN_CHECK
 Argument Name                  Type                    In/Out Default?
 ------------------------------ ----------------------- ------ --------
 CHECK_NAME                     VARCHAR2                IN
 RUN_NAME                       VARCHAR2                IN     DEFAULT
 TIMEOUT                        NUMBER                  IN     DEFAULT
 INPUT_PARAMS                   VARCHAR2                IN     DEFAULT

check_name:数据库检查名,这是一个强制参数必须被指定。可以在视图


v$hm_check


中的name自动查询到该参数的值。12.1共34个值。

run_name:可选参数,指定一个检查名。

timeout:可选参数,可以设置老化时间。

params:输入参数,用于控制检查的执行。

SQL> select name from v$hm_check where name like '%Block%';
NAME
----------------------------------------------------------------
CF Block Integrity Check
Data Block Integrity Check
Logical Block Check
Block IO Revalidation Check
SQL> exec   DBMS_HM.RUN_CHECK('Data Block Integrity Check', 'my_run2');
BEGIN DBMS_HM.RUN_CHECK('Data Block Integrity Check', 'my_run2'); END;
*
ERROR at line 1:
ORA-48615: Parameter [BLC_DF_NUM] value not specified
ORA-06512: at "SYS.DBMS_HM", line 191
ORA-06512: at line 1




看到有Data Block Integrity Check检查,赶紧试了一下,结果发现一次只能检查一个block,很不方便,还是 validate database 吧。


相关文章
|
3月前
|
监控
{"level":"warn","ts":"2023-11-07T00:35:53.400+0800","caller":"etcdserver/server.go:2048",&
{"level":"warn","ts":"2023-11-07T00:35:53.400+0800","caller":"etcdserver/server.go:2048",&
|
5月前
|
Linux 开发工具
You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofi
linux配置环境变量操作失误出现:/usr/libexec/grepconf.sh: line 5: grep: command not found 的解决办法
169 2
|
7月前
|
测试技术
Could not proxy command to the remote server. Original error: timeout of 240000ms exceeded 的解决办法
Could not proxy command to the remote server. Original error: timeout of 240000ms exceeded 的解决办法
249 0
|
网络安全 开发工具
【解决方案】A session ended very soon after starting. Check that the command in profile “XXX” is correct.
【解决方案】A session ended very soon after starting. Check that the command in profile “XXX” is correct.
1055 0
【解决方案】A session ended very soon after starting. Check that the command in profile “XXX” is correct.
|
NoSQL MongoDB 数据安全/隐私保护
OCI runtime exec failed: exec failed: unable to start container process: exec: "mongo": executable file not found in $PATH: unknown
OCI runtime exec failed: exec failed: unable to start container process: exec: "mongo": executable file not found in $PATH: unknown
1148 0
OCI runtime exec failed: exec failed: unable to start container process: exec: "mongo": executable file not found in $PATH: unknown
|
关系型数据库 数据库 PostgreSQL
pg_ctl: server did not start in time
postgresql 启动超时异常,可怎么解决
pg_ctl: server did not start in time
|
存储 NoSQL Linux
redis异常 Commands that may modify the data set are disabled, because this instance is
MISCONF Redis配置为保存RDB快照,但目前无法在磁盘上持久化。可能修改数据集的命令被禁用,因为该实例被配置为在RDB快照失败时报告错误(stop-write -on-bgsave-error选项)。请检查Redis的日志RDB错误的详细信息.
redis异常 Commands that may modify the data set are disabled, because this instance is
‘Client‘ is not allowed to run in parallel.Would you like to stop the running one?
‘Client‘ is not allowed to run in parallel.Would you like to stop the running one?
577 0
‘Client‘ is not allowed to run in parallel.Would you like to stop the running one?