oracle使用adrci清理日志文件的操作指南(trace文件，incident文件，listener log文件)
更新時(shí)間：2024年05月10日 11:45:42 作者：dingxiaochao
oracle中通常有好多日志文件,遇到異常情況會(huì)產(chǎn)生大量日志,造成磁盤空間緊張,故需要清理對(duì)應(yīng)文件,包括trace文件,incident文件,listener log文件等,所以本文給大家介紹了oracle使用adrci清理日志文件的操作指南,需要的朋友可以參考下
介紹
oracle中通常有好多日志文件，遇到異常情況會(huì)產(chǎn)生大量日志，造成磁盤空間緊張。
故需要清理對(duì)應(yīng)文件。包括trace文件，incident文件，listener log文件等
11g中oracle提供了一個(gè)ADRCI的命令行工具來查看ADR中的alert日志和trace信息，可以批量刪除對(duì)應(yīng)的日志文件。
adrci的位置在$ORACLE_HOME/bin目錄下
詳細(xì)adrci介紹
1.刪除incident文件
- 調(diào)用adrci
[root@prod-idm-storage incident]# adrci ADRCI: Release 11.2.0.2.0 - Production on Tue May 7 15:19:08 2019 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. ADR base = "/app/oracle"
- 查看目錄
adrci> show home ADR Homes: diag/rdbms/orcl/orcl
存在多個(gè)home需要指定單個(gè)hone進(jìn)行操作
adrci> set homepath diag/rdbms/tyrz/tyrz
- 查看incident
adrci> show incident ADR Home = /app/oracle/diag/rdbms/orcl/orcl: ************************************************************************* INCIDENT_ID PROBLEM_KEY CREATE_TIME -------------------- ----------------------------------------------------------- ---------------------------------------- 243353 ORA 227 2018-08-31 09:22:40.871000 +08:00 262554 ORA 227 2018-08-31 09:34:26.395000 +08:00 339426 ORA 1578 2018-09-22 06:01:46.329000 +08:00 339370 ORA 1578 2018-09-22 10:07:49.852000 +08:00 339402 ORA 1578 2018-09-22 14:08:23.558000 +08:00 339386 ORA 1578 2018-09-22 18:08:47.587000 +08:00 339394 ORA 1578 2018-09-22 22:09:26.524000 +08:00 339410 ORA 1578 2018-09-23 06:01:17.392000 +08:00 339387 ORA 1578 2018-09-23 10:10:58.257000 +08:00 339411 ORA 1578 2018-09-23 14:11:21.786000 +08:00 339412 ORA 1578 2018-09-23 18:11:59.186000 +08:00 339413 ORA 1578 2018-09-23 22:12:19.998000 +08:00 339414 ORA 1578 2018-09-24 22:01:20.661000 +08:00 339434 ORA 1578 2018-09-25 22:01:21.496000 +08:00 339415 ORA 1578 2018-09-26 22:01:09.127000 +08:00 339442 ORA 1578 2018-09-27 22:01:26.124000 +08:00 339450 ORA 1578 2018-09-28 22:01:21.893000 +08:00 339403 ORA 1578 2018-09-29 06:01:25.350000 +08:00 339418 ORA 1578 2018-09-29 10:07:14.940000 +08:00 339388 ORA 1578 2018-09-29 14:07:53.091000 +08:00 339389 ORA 1578 2018-09-29 18:08:10.510000 +08:00 339404 ORA 1578 2018-09-29 22:08:50.151000 +08:00 339419 ORA 1578 2018-09-30 06:01:15.858000 +08:00 339390 ORA 1578 2018-09-30 10:10:21.898000 +08:00 339391 ORA 1578 2018-09-30 14:10:47.874000 +08:00 339371 ORA 1578 2018-09-30 18:11:24.833000 +08:00 339405 ORA 1578 2018-09-30 22:11:47.994000 +08:00 339372 ORA 1578 2018-10-01 22:01:17.620000 +08:00 339435 ORA 1578 2018-10-02 22:01:30.078000 +08:00 339451 ORA 1578 2018-10-03 22:01:23.725000 +08:00 339420 ORA 1578 2018-10-04 22:01:21.404000 +08:00 339416 ORA 1578 2018-10-05 22:01:15.775000 +08:00 339421 ORA 1578 2018-10-06 06:01:29.564000 +08:00 339417 ORA 1578 2018-10-06 10:08:21.342000 +08:00 339422 ORA 1578 2018-10-06 14:08:52.711000 +08:00 345607 ORA 1578 2018-10-06 18:09:17.919000 +08:00 345609 ORA 1578 2018-10-06 22:09:56.154000 +08:00 339436 ORA 1578 2018-10-07 06:01:18.502000 +08:00 339406 ORA 1578 2018-10-07 10:01:23.514000 +08:00 339407 ORA 1578 2018-10-07 14:01:46.542000 +08:00 339354 ORA 1578 2018-10-07 18:02:21.533000 +08:00 339355 ORA 1578 2018-10-07 22:02:45.654000 +08:00 339498 ORA 1578 2018-10-08 22:01:23.626000 +08:00 339466 ORA 1578 2018-10-09 22:01:21.970000 +08:00 339467 ORA 1578 2018-10-10 22:01:11.649000 +08:00 339499 ORA 1578 2018-10-11 22:01:17.955000 +08:00 339443 ORA 1578 2018-10-12 22:01:24.071000 +08:00 339423 ORA 1578 2018-10-13 06:01:17.901000 +08:00 339373 ORA 1578 2018-10-13 10:06:37.319000 +08:00 339374 ORA 1578 2018-10-13 14:07:14.910000 +08:00 First 50 rows fetched (*** more available ***)
- 刪除100天前的incident 14400=60min*24*100
adrci>purge -age 144000 -type incident
- 退出
adrci> exit
- 幫助
adrci> help purge
Usage: PURGE [[-i <id1> | <id1> <id2>] |
[-age <mins> [-type ALERT|INCIDENT|TRACE|CDUMP|HM|UTSCDMP]]]:
Purpose: Purge the diagnostic data in the current ADR home. If no
option is specified, the default purging policy will be used.
Options:
[-i id1 | id1 id2]: Users can input a single incident ID, or a
range of incidents to purge.
[-age <mins>]: Users can specify the purging policy either to all
the diagnostic data or the specified type. The data older than <mins>
ago will be purged
[-type ALERT|INCIDENT|TRACE|CDUMP|HM|UTSCDMP]: Users can specify what type of
data to be purged.
Examples:
purge
purge -i 123 456
purge -age 60 -type incident2.刪除listener log
3.刪除TRACE
- 查看trace
adrci> show tracefile
diag/rdbms/oam/oam/trace/oam_vkrm_10487.trc
diag/rdbms/oam/oam/trace/oam_vkrm_6627.trc
diag/rdbms/oam/oam/trace/oam_j003_26131.trc
diag/rdbms/oam/oam/trace/oam_m000_404.trc
diag/rdbms/oam/oam/trace/oam_m000_20336.trc
diag/rdbms/oam/oam/trace/oam_w000_3502.trc
diag/rdbms/oam/oam/trace/oam_vkrm_31062.trc
diag/rdbms/oam/oam/trace/oam_m000_14702.trc
diag/rdbms/oam/oam/trace/oam_j000_949.trc
diag/rdbms/oam/oam/trace/oam_vkrm_28172.trc
diag/rdbms/oam/oam/trace/alert_oam.log
diag/rdbms/oam/oam/trace/oam_vkrm_12182.trc
diag/rdbms/oam/oam/trace/oam_w000_31588.trc
diag/rdbms/oam/oam/trace/oam_j000_6363.trc
diag/rdbms/oam/oam/trace/oam_w001_8741.trc
diag/rdbms/oam/oam/trace/oam_m000_15978.trc
diag/rdbms/oam/oam/trace/oam_vkrm_15883.trc
diag/rdbms/oam/oam/trace/oam_m000_5141.trc
diag/rdbms/oam/oam/trace/oam_j001_15641.trc
diag/rdbms/oam/oam/trace/oam_j000_21062.trc
diag/rdbms/oam/oam/trace/oam_m000_24268.trc
diag/rdbms/oam/oam/trace/oam_m000_21366.trc
diag/rdbms/oam/oam/trace/oam_vkrm_14072.trcadrci> purge -age 8760 -type TRACE
以上就是oracle使用adrci清理日志文件的操作指南(trace文件，incident文件，listener log文件)的詳細(xì)內(nèi)容，更多關(guān)于oracle adrci清理文件的資料請(qǐng)關(guān)注腳本之家其它相關(guān)文章！
相關(guān)文章
這篇文章主要介紹了oracle中merge into用法及實(shí)例解析，小編覺得挺不錯(cuò)的，現(xiàn)在分享給大家，也給大家做個(gè)參考。一起跟隨小編過來看看吧2018-03-03![[Oracle] 淺析令人抓狂的ORA-01555問題](http://img.jbzj.com/images/xgimg/bcimg1.png)
首先要說明的一點(diǎn)是：ORA-01555錯(cuò)誤是一個(gè)“安全”的錯(cuò)誤，它不會(huì)造成數(shù)據(jù)丟失或損壞，只是會(huì)讓接收到該錯(cuò)誤的查詢無法繼續(xù)。以下就是對(duì)發(fā)生ORA-01555錯(cuò)誤的原因進(jìn)行了介紹，需要的朋友可以參考下2013-07-07
如何實(shí)現(xiàn)oracle中字段的自增，下面用一個(gè)例子來說明，有此需求的各位朋友可以參考下2013-11-11
Oracle 實(shí)現(xiàn) 一個(gè)關(guān)鍵字 匹配多個(gè) 字段的方法
這篇文章主要介紹了Oracle 實(shí)現(xiàn) 一個(gè)關(guān)鍵字 匹配多個(gè) 字段的方法，本文給大家提供兩個(gè)方案，非常不錯(cuò)，具有一定的參考借鑒價(jià)值 ,需要的朋友可以參考下2019-05-05
淺談入門級(jí)oracle數(shù)據(jù)庫數(shù)據(jù)導(dǎo)入導(dǎo)出步驟
這篇文章主要介紹了淺談入門級(jí)oracle數(shù)據(jù)庫數(shù)據(jù)導(dǎo)入導(dǎo)出步驟，文章通過步驟解析介紹的非常詳細(xì)，對(duì)大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價(jià)值，需要的朋友們下面隨著小編來一起學(xué)習(xí)學(xué)習(xí)吧2020-08-08
今天在使用oracle數(shù)據(jù)庫做項(xiàng)目時(shí)，突然報(bào)錯(cuò)：ORA-00257: archiver error. Connect internal only, until freed，該問題如何解決呢？經(jīng)過本人一番折騰此問題還要?dú)w檔于日志滿了，下面小編把Oracle歸檔日志寫滿(ora-00257)的解決辦法在此分享給大家供大家參考2015-10-10
ORACLE中dbms_output.put_line輸出問題的解決過程
最近用dbms_output.put_line來輸出變量的一些信息,卻總是看不到結(jié)果,所以這篇文章主要給大家介紹了關(guān)于ORACLE中dbms_output.put_line輸出問題的解決過程,需要的朋友可以參考下2022-06-06
Oracle數(shù)據(jù)庫sysaux文件損壞的數(shù)據(jù)恢復(fù)案例分享
一臺(tái)Oracle數(shù)據(jù)庫打開報(bào)錯(cuò),報(bào)錯(cuò)信息： “system01.dbf需要更多的恢復(fù)來保持一致性,數(shù)據(jù)庫無法打開”,本文給大家介紹了Oracle數(shù)據(jù)庫sysaux文件損壞的數(shù)據(jù)恢復(fù)案例,需要的朋友可以參考下2024-11-11
在本篇文章里小編給大家整理的是關(guān)于oracle處理鎖表基本操作以及相關(guān)代碼，需要的朋友們學(xué)習(xí)下。2019-11-11
Oracle數(shù)據(jù)庫設(shè)置任務(wù)計(jì)劃備份一周的備份記錄
這篇文章介紹了Oracle數(shù)據(jù)庫下通過任務(wù)計(jì)劃備份一周的記錄的批處理代碼，需要的朋友可以參考下2013-08-08