用oracle的ADRCI功能檢視日誌
oracle11g中提供了一個檢視日誌檔案的命令列工具：Automatic Diagnostic Repository Command-Interpreter,包含在oracle database 11g中引入的故障可診斷性基礎結構中，主要用於管理trace檔案，alert檔案，dump檔案，健康監視報告等。在oracle10g中 這些檔案時存放在ORACLE_BASE/admin/INSTANCE_NAME目錄下的，到了oracle11g這些檔案存放在ORACLE_BASE/diag/rdbms/DBNAME/INSTANCE_NAME目錄下，oracle之所以修改這個跨越多個版本都沒有修改過的引數，是由於oracle11g退出了ADRCI工具，這個工具可以統一管理ASM例項和多個資料庫例項的alert檔案，使用者trace檔案，後臺trace檔案，dump檔案等。使用ADRCI，可以：
(1)檢視自動診斷資料檔案庫ADR中的診斷資料。
(2)將意外事件和問題資訊打包成zip檔案，以傳輸到oracle技術支援，此操作是使用稱為意外事件打包服務Incident Packaging Service ,IPS的服務完成的。
在資料庫中查詢v$diag_info檢視：
SYS@orcl 06-SEP-14>select name,value from v$diag_info;
NAME VALUE
------------------------- ----------------------------------------
Diag Enabled TRUE
ADR Base /u01/app/oracle
ADR Home /u01/app/oracle/diag/rdbms/orcl/orcl
Diag Trace /u01/app/oracle/diag/rdbms/orcl/orcl/tra
ce
Diag Alert /u01/app/oracle/diag/rdbms/orcl/orcl/ale
rt
Diag Incident /u01/app/oracle/diag/rdbms/orcl/orcl/inc
ident
NAME VALUE
------------------------- ----------------------------------------
Diag Cdump /u01/app/oracle/diag/rdbms/orcl/orcl/cdu
mp
Health Monitor /u01/app/oracle/diag/rdbms/orcl/orcl/hm
Default Trace File /u01/app/oracle/diag/rdbms/orcl/orcl/tra
ce/orcl_ora_27646.trc
Active Problem Count 0
Active Incident Count 0
11 rows selected.
開啟終端，執行adrci即可及進入ADRCI工具：
[oracle@localhost ~]$ adrci
ADRCI: Release 11.2.0.1.0 - Production on Sat Sep 6 02:58:47 2014
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ADR base = "/u01/app/oracle"
(1)檢視自動診斷資料檔案庫ADR中的診斷資料。
(2)將意外事件和問題資訊打包成zip檔案，以傳輸到oracle技術支援，此操作是使用稱為意外事件打包服務Incident Packaging Service ,IPS的服務完成的。
在資料庫中查詢v$diag_info檢視：
SYS@orcl 06-SEP-14>select name,value from v$diag_info;
NAME VALUE
------------------------- ----------------------------------------
Diag Enabled TRUE
ADR Base /u01/app/oracle
ADR Home /u01/app/oracle/diag/rdbms/orcl/orcl
Diag Trace /u01/app/oracle/diag/rdbms/orcl/orcl/tra
ce
Diag Alert /u01/app/oracle/diag/rdbms/orcl/orcl/ale
rt
Diag Incident /u01/app/oracle/diag/rdbms/orcl/orcl/inc
ident
NAME VALUE
------------------------- ----------------------------------------
Diag Cdump /u01/app/oracle/diag/rdbms/orcl/orcl/cdu
mp
Health Monitor /u01/app/oracle/diag/rdbms/orcl/orcl/hm
Default Trace File /u01/app/oracle/diag/rdbms/orcl/orcl/tra
ce/orcl_ora_27646.trc
Active Problem Count 0
Active Incident Count 0
11 rows selected.
[oracle@localhost ~]$ adrci
ADRCI: Release 11.2.0.1.0 - Production on Sat Sep 6 02:58:47 2014
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ADR base = "/u01/app/oracle"
adrci> help
HELP [topic]
Available Topics:
CREATE REPORT
ECHO
EXIT
HELP
HOST
IPS
PURGE
RUN
SET BASE
SET BROWSER
SET CONTROL
SET ECHO
SET EDITOR
SET HOMES | HOME | HOMEPATH
SET TERMOUT
SHOW ALERT
SHOW BASE
SHOW CONTROL
SHOW HM_RUN
SHOW HOMES | HOME | HOMEPATH
SHOW INCDIR
SHOW INCIDENT
SHOW PROBLEM
SHOW REPORT
SHOW TRACEFILE
SPOOL
There are other commands intended to be used directly by Oracle, type
"HELP EXTENDED" to see the list
可以透過show alert命令檢視警報日誌檔案，預設使用vi編輯器模式：
2014-08-21 18:50:52.038000 -07:00
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Shared memory segment for instance monitoring created
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
2014-08-21 18:50:56.360000 -07:00
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in client-side pfile /u01/app/oracle/admin/orcl/pfile/init.ora on machine localhost.localdomain
System parameters with non-default values:
processes = 150
memory_target = 812M
control_files = "/u01/app/oracle/oradata/orcl/control01.ctl"
HELP [topic]
Available Topics:
CREATE REPORT
ECHO
EXIT
HELP
HOST
IPS
PURGE
RUN
SET BASE
SET BROWSER
SET CONTROL
SET ECHO
SET EDITOR
SET HOMES | HOME | HOMEPATH
SET TERMOUT
SHOW ALERT
SHOW BASE
SHOW CONTROL
SHOW HM_RUN
SHOW HOMES | HOME | HOMEPATH
SHOW INCDIR
SHOW INCIDENT
SHOW PROBLEM
SHOW REPORT
SHOW TRACEFILE
SPOOL
There are other commands intended to be used directly by Oracle, type
"HELP EXTENDED" to see the list
可以透過show alert命令檢視警報日誌檔案，預設使用vi編輯器模式：
2014-08-21 18:50:52.038000 -07:00
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Shared memory segment for instance monitoring created
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
2014-08-21 18:50:56.360000 -07:00
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in client-side pfile /u01/app/oracle/admin/orcl/pfile/init.ora on machine localhost.localdomain
System parameters with non-default values:
processes = 150
memory_target = 812M
control_files = "/u01/app/oracle/oradata/orcl/control01.ctl"
顯示最近5條alert log(不是5行，預設是10條)：
使用這個命令首先要set home,否則會報錯DIA-48449:
adrci> show alert -tail 5
DIA-48449: Tail alert can only apply to single ADR home
使用這個命令首先要set home,否則會報錯DIA-48449:
adrci> show alert -tail 5
DIA-48449: Tail alert can only apply to single ADR home
這是因為在多個例項存在的情況下易造成混亂。
adrci> set home diag/rdbms/orcl/orcl
adrci> show alert -tail 5
2014-09-06 05:09:26.725000 -07:00
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Completed: ALTER DATABASE OPEN
Starting background process CJQ0
CJQ0 started with pid=28, OS id=8235
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
2014-09-06 05:14:26.719000 -07:00
Starting background process SMCO
SMCO started with pid=36, OS id=8861
透過show tracefile可以檢視ADR下的所有trace files:
adrci>show tracefile
diag/rdbms/orcl/orcl/trace/orcl_ora_14542.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_13410.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_26142.trc
diag/rdbms/orcl/orcl/trace/orcl_dbrm_12336.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_22490.trc
diag/rdbms/orcl/orcl/trace/orcl_arc0_19981.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_23694.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_9319.trc
diag/rdbms/orcl/orcl/trace/orcl_m000_21885.trc
diag/rdbms/orcl/orcl/trace/orcl_m000_29429.trc
diag/rdbms/orcl/orcl/trace/orcl_mman_2679.trc
diag/rdbms/orcl/orcl/trace/orcl_m001_19671.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_3424.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_17550.trc
diag/rdbms/orcl/orcl/trace/orcl_m002_27131.trc
diag/rdbms/orcl/orcl/trace/orcl_m000_21350.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_13162.trc
diag/rdbms/orcl/orcl/trace/orcl_ckpt_4808.trc
也可以對這些trace files檔案進行過濾，只看你所關注的資訊：
adrci> show tracefile %mmon%
diag/rdbms/orcl/orcl/trace/orcl_mmon_27960.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_20946.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_15962.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_28628.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_11531.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_16814.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_10029.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_16492.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_30359.trc
透過show incident命令檢視incident:
adrci> show incident
ADR Home = /u01/app/oracle/diag/tnslsnr/localhost/listener:
*************************************************************************
0 rows fetched
ADR Home = /u01/app/oracle/diag/rdbms/dummy/orcl:
*************************************************************************
0 rows fetched
ADR Home = /u01/app/oracle/diag/rdbms/orcl/orcl:
*************************************************************************
0 rows fetched
透過show problem檢視problem：
adrci> show problem
ADR Home = /u01/app/oracle/diag/tnslsnr/localhost/listener:
*************************************************************************
0 rows fetched
ADR Home = /u01/app/oracle/diag/rdbms/dummy/orcl:
*************************************************************************
0 rows fetched
ADR Home = /u01/app/oracle/diag/rdbms/orcl/orcl:
*************************************************************************
0 rows fetched
ADRCI的purge命令會清空alert log的內容，注意這裡的內容僅僅是XML的alert log(XML型別的警報日誌在diag/rdbms/orcl/alert
目錄下，名稱為log.xml)
對於trace目錄下的text格式的alert log不會進行清空，我們在使用purge時，可以指定
alert log中的entries保留的時間。
如清除10分鐘前的alert log，可用如下命令：
adrci> purge -age 10 -type alert
adrci> show alert
ADR Home = /u01/app/oracle/diag/rdbms/orcl/orcl:
*************************************************************************
但是diag/rdbms/orcl/orcl/trace目錄下，alert_orcl.log警報日誌檔案內容還是存在的。
可用如下命令檢視ADR中日誌的保留時間：
adrci> show control
adrci> set home diag/rdbms/orcl/orcl
adrci> show alert -tail 5
2014-09-06 05:09:26.725000 -07:00
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Completed: ALTER DATABASE OPEN
Starting background process CJQ0
CJQ0 started with pid=28, OS id=8235
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
2014-09-06 05:14:26.719000 -07:00
Starting background process SMCO
SMCO started with pid=36, OS id=8861
透過show tracefile可以檢視ADR下的所有trace files:
adrci>show tracefile
diag/rdbms/orcl/orcl/trace/orcl_ora_14542.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_13410.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_26142.trc
diag/rdbms/orcl/orcl/trace/orcl_dbrm_12336.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_22490.trc
diag/rdbms/orcl/orcl/trace/orcl_arc0_19981.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_23694.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_9319.trc
diag/rdbms/orcl/orcl/trace/orcl_m000_21885.trc
diag/rdbms/orcl/orcl/trace/orcl_m000_29429.trc
diag/rdbms/orcl/orcl/trace/orcl_mman_2679.trc
diag/rdbms/orcl/orcl/trace/orcl_m001_19671.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_3424.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_17550.trc
diag/rdbms/orcl/orcl/trace/orcl_m002_27131.trc
diag/rdbms/orcl/orcl/trace/orcl_m000_21350.trc
diag/rdbms/orcl/orcl/trace/orcl_ora_13162.trc
diag/rdbms/orcl/orcl/trace/orcl_ckpt_4808.trc
adrci> show tracefile %mmon%
diag/rdbms/orcl/orcl/trace/orcl_mmon_27960.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_20946.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_15962.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_28628.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_11531.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_16814.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_10029.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_16492.trc
diag/rdbms/orcl/orcl/trace/orcl_mmon_30359.trc
adrci> show incident
ADR Home = /u01/app/oracle/diag/tnslsnr/localhost/listener:
*************************************************************************
0 rows fetched
ADR Home = /u01/app/oracle/diag/rdbms/dummy/orcl:
*************************************************************************
0 rows fetched
ADR Home = /u01/app/oracle/diag/rdbms/orcl/orcl:
*************************************************************************
0 rows fetched
adrci> show problem
ADR Home = /u01/app/oracle/diag/tnslsnr/localhost/listener:
*************************************************************************
0 rows fetched
ADR Home = /u01/app/oracle/diag/rdbms/dummy/orcl:
*************************************************************************
0 rows fetched
ADR Home = /u01/app/oracle/diag/rdbms/orcl/orcl:
*************************************************************************
0 rows fetched
目錄下，名稱為log.xml)
對於trace目錄下的text格式的alert log不會進行清空，我們在使用purge時，可以指定
alert log中的entries保留的時間。
如清除10分鐘前的alert log，可用如下命令：
adrci> purge -age 10 -type alert
adrci> show alert
ADR Home = /u01/app/oracle/diag/rdbms/orcl/orcl:
*************************************************************************
可用如下命令檢視ADR中日誌的保留時間：
adrci> show control
ADR Home = /u01/app/oracle/diag/rdbms/orcl/orcl:
*************************************************************************
ADRID SHORTP_POLICY LONGP_POLICY LAST_MOD_TIME LAST_AUTOPRG_TIME LAST_MANUPRG_TIME ADRDIR_VERSION ADRSCHM_VERSION ADRSCHMV_SUMMARY ADRALERT_VERSION CREATE_TIME
-------------------- -------------------- -------------------- ---------------------------------------- ---------------------------------------- ---------------------------------------- -------------------- -------------------- -------------------- -------------------- ----------------------------------------
1335663986 720 8760 2014-08-21 18:50:50.266259 -07:00 2014-09-06 05:56:58.068378 -07:00 1 2 76 1 2014-08-21 18:50:50.266259 -07:00
1 rows fetched
ADR中有兩個策略，SHORTP_POLICY和LONGP_POLICY。
SHORT_POLICY:number of hours after which to purge ADR contents that have a short life.Default
is 720(30 days).A setting of 0 means that all contents that have a short lift can be purged.The
maxnimum setting is 35791394.If a value greater than 35791394 is specified , then this attribute is
set to 0.
The ADR contents that have a short life include the following:
trace files
core dump files
packaging information
LONG_POLICY:Number of hours after which to purge ADR contents that have a log life.Default
is 8760(365 days).A setting of 0 means that all contents that have a long life can be purged.The
maxnimum setting is 35791394.If a value greater than 35791394 is specified ,then this attribute
is set to 0.
The ADR contents that have a long life include the following:
incident information
incident dumps
alert logs
SHORTP_POLICY預設是720小時(30天)，其控制如下三種檔案的保留時間：
trace file
core dump files
packaging information
LONGP_POLICY預設是8760小時(365天)，其控制如下三種檔案的保留時間：
incident information
incident information
alert logs
可以用如下命令修改ADR的保留時間
adrci> set control (SHORTP_POLICY=360)
adrci> set control (LONGP_POLICY=2160)
*************************************************************************
ADRID SHORTP_POLICY LONGP_POLICY LAST_MOD_TIME LAST_AUTOPRG_TIME LAST_MANUPRG_TIME ADRDIR_VERSION ADRSCHM_VERSION ADRSCHMV_SUMMARY ADRALERT_VERSION CREATE_TIME
-------------------- -------------------- -------------------- ---------------------------------------- ---------------------------------------- ---------------------------------------- -------------------- -------------------- -------------------- -------------------- ----------------------------------------
1335663986 720 8760 2014-08-21 18:50:50.266259 -07:00 2014-09-06 05:56:58.068378 -07:00 1 2 76 1 2014-08-21 18:50:50.266259 -07:00
1 rows fetched
ADR中有兩個策略，SHORTP_POLICY和LONGP_POLICY。
SHORT_POLICY:number of hours after which to purge ADR contents that have a short life.Default
is 720(30 days).A setting of 0 means that all contents that have a short lift can be purged.The
maxnimum setting is 35791394.If a value greater than 35791394 is specified , then this attribute is
set to 0.
The ADR contents that have a short life include the following:
trace files
core dump files
packaging information
is 8760(365 days).A setting of 0 means that all contents that have a long life can be purged.The
maxnimum setting is 35791394.If a value greater than 35791394 is specified ,then this attribute
is set to 0.
The ADR contents that have a long life include the following:
incident information
incident dumps
alert logs
SHORTP_POLICY預設是720小時(30天)，其控制如下三種檔案的保留時間：
trace file
core dump files
packaging information
LONGP_POLICY預設是8760小時(365天)，其控制如下三種檔案的保留時間：
incident information
incident information
alert logs
可以用如下命令修改ADR的保留時間
adrci> set control (SHORTP_POLICY=360)
adrci> set control (LONGP_POLICY=2160)
adrci> show control
ADR Home = /u01/app/oracle/diag/rdbms/orcl/orcl:
*************************************************************************
ADRID SHORTP_POLICY LONGP_POLICY LAST_MOD_TIME LAST_AUTOPRG_TIME LAST_MANUPRG_TIME ADRDIR_VERSION ADRSCHM_VERSION ADRSCHMV_SUMMARY ADRALERT_VERSION CREATE_TIME
-------------------- -------------------- -------------------- ---------------------------------------- ---------------------------------------- ---------------------------------------- -------------------- -------------------- -------------------- -------------------- ----------------------------------------
1335663986 360 2160 2014-09-06 06:24:21.877124 -07:00 2014-09-06 05:56:58.068378 -07:00 1 2 76 1 2014-08-21 18:50:50.266259 -07:00
1 rows fetched
透過ADR生成診斷包：
adrci> ips create package
Created package 1 without any contents, correlation level typical
adrci> ips generate package 1 in /home/oracle
Generated package 1 in file /home/oracle/IPSPKG_20140906062831_COM_1.zip, mode complete
[oracle@localhost alert]$ cd /home/oracle
[oracle@localhost ~]$ ls
Desktop help.sql IPSPKG_20140906062831_COM_1.zip oradiag_oracle
[oracle@localhost ~]$ unzip -l IPSPKG_20140906062831_COM_1.zip
Archive: IPSPKG_20140906062831_COM_1.zip
Length Date Time Name
-------- ---- ---- ----
2818 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/IPS_CONFIGURATION.dmp
460 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/IPS_PACKAGE.dmp
151 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/IPS_PACKAGE_INCIDENT.dmp
870 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/IPS_PACKAGE_FILE.dmp
280 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/IPS_PACKAGE_HISTORY.dmp
2254 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/IPS_FILE_METADATA.dmp
214 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/IPS_FILE_COPY_LOG.dmp
908 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/DDE_USER_ACTION_DEF.dmp
708 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/DDE_USER_ACTION_PARAMETER_DEF.dmp
204 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/DDE_USER_ACTION.dmp
198 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/DDE_USER_ACTION_PARAMETER.dmp
353 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/DDE_USER_INCIDENT_TYPE.dmp
166 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/DDE_USER_INCIDENT_ACTION_MAP.dmp
576 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/INCIDENT.dmp
148 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/INCCKEY.dmp
119 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/INCIDENT_FILE.dmp
292 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/PROBLEM.dmp
536 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/HM_RUN.dmp
207 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/EM_USER_ACTIVITY.dmp
3900 09-06-14 06:00 diag/rdbms/orcl/orcl/alert/log.xml
604428 09-06-14 06:00 diag/rdbms/orcl/orcl/trace/alert_orcl.log
1453 09-06-14 06:29 diag/rdbms/orcl/orcl/hm/HMREPORT_HM_RUN_3301.hm
184 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/crs/crsdiag.log
527 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/metadata.xml
8059 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/manifest_1_1.xml
9092 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/manifest_1_1.html
10506 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/manifest_1_1.txt
527 09-06-14 06:29 metadata.xml
-------- -------
650138 28 files
ADR Home = /u01/app/oracle/diag/rdbms/orcl/orcl:
*************************************************************************
ADRID SHORTP_POLICY LONGP_POLICY LAST_MOD_TIME LAST_AUTOPRG_TIME LAST_MANUPRG_TIME ADRDIR_VERSION ADRSCHM_VERSION ADRSCHMV_SUMMARY ADRALERT_VERSION CREATE_TIME
-------------------- -------------------- -------------------- ---------------------------------------- ---------------------------------------- ---------------------------------------- -------------------- -------------------- -------------------- -------------------- ----------------------------------------
1335663986 360 2160 2014-09-06 06:24:21.877124 -07:00 2014-09-06 05:56:58.068378 -07:00 1 2 76 1 2014-08-21 18:50:50.266259 -07:00
1 rows fetched
adrci> ips create package
Created package 1 without any contents, correlation level typical
adrci> ips generate package 1 in /home/oracle
Generated package 1 in file /home/oracle/IPSPKG_20140906062831_COM_1.zip, mode complete
[oracle@localhost ~]$ ls
Desktop help.sql IPSPKG_20140906062831_COM_1.zip oradiag_oracle
Archive: IPSPKG_20140906062831_COM_1.zip
Length Date Time Name
-------- ---- ---- ----
2818 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/IPS_CONFIGURATION.dmp
460 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/IPS_PACKAGE.dmp
151 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/IPS_PACKAGE_INCIDENT.dmp
870 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/IPS_PACKAGE_FILE.dmp
280 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/IPS_PACKAGE_HISTORY.dmp
2254 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/IPS_FILE_METADATA.dmp
214 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/IPS_FILE_COPY_LOG.dmp
908 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/DDE_USER_ACTION_DEF.dmp
708 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/DDE_USER_ACTION_PARAMETER_DEF.dmp
204 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/DDE_USER_ACTION.dmp
198 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/DDE_USER_ACTION_PARAMETER.dmp
353 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/DDE_USER_INCIDENT_TYPE.dmp
166 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/DDE_USER_INCIDENT_ACTION_MAP.dmp
576 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/INCIDENT.dmp
148 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/INCCKEY.dmp
119 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/INCIDENT_FILE.dmp
292 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/PROBLEM.dmp
536 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/HM_RUN.dmp
207 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/export/EM_USER_ACTIVITY.dmp
3900 09-06-14 06:00 diag/rdbms/orcl/orcl/alert/log.xml
604428 09-06-14 06:00 diag/rdbms/orcl/orcl/trace/alert_orcl.log
1453 09-06-14 06:29 diag/rdbms/orcl/orcl/hm/HMREPORT_HM_RUN_3301.hm
184 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/crs/crsdiag.log
527 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/metadata.xml
8059 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/manifest_1_1.xml
9092 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/manifest_1_1.html
10506 09-06-14 06:29 diag/rdbms/orcl/orcl/incpkg/pkg_1/seq_1/manifest_1_1.txt
527 09-06-14 06:29 metadata.xml
-------- -------
650138 28 files
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/29618264/viewspace-2124004/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- 【ADRCI】使用ADRCI (ADR Command Interpreter) 工具檢視Oracle alert警告日誌Oracle
- oracle 日誌檢視方法Oracle
- MYSQL啟用日誌和檢視日誌MySql
- Oracle 使用logmnr檢視日誌Oracle
- oracle物化檢視日誌系列(一)Oracle
- oracle物化檢視日誌系列(二)Oracle
- oracle物化檢視日誌系列(三)Oracle
- 檢視日誌
- 檢視Oracle的redo日誌切換頻率Oracle
- Oracle 11g RAC檢視ASM日誌、grid日誌和DB日誌OracleASM
- alertmanager: 檢視日誌
- 用外部表實現Alert日誌的檢視
- oracle 11g檢視alert日誌方法Oracle
- Oracle 11g 檢視監聽日誌Oracle
- oracle cluster叢集相關日誌檢視Oracle
- 檢視docker映象的日誌Docker
- 檢視系統的日誌
- 檢視oracle的redo日誌組切換頻率Oracle
- Linux 檢視日誌Linux
- Hyperf日誌檢視元件元件
- 錯誤日誌檢視
- sql 日誌檢視工具SQL
- 使用外部表檢視ORACLE報警日誌薦Oracle
- Oracle如何根據物化檢視日誌快速重新整理物化檢視Oracle
- 檢視日誌的幾種形式
- 物化檢視日誌的維護
- Oracle的告警日誌之v$diag_alert_ext檢視Oracle
- 【物化檢視】幾種物化檢視日誌分析
- docker檢視容器日誌命令Docker
- Logminer如何檢視日誌
- 檢視mysql日誌及日誌編碼問題MySql
- 如何在iOS手機上檢視應用日誌iOS應用日誌
- 用exp、imp遷移包含物化檢視日誌的資料
- Oracle檢視每小時日誌切換量指令碼Oracle指令碼
- windows_weblogic日誌檢視WindowsWeb
- 實時檢視tomcat日誌Tomcat
- 檢視歸檔日誌空間
- LINUX檢視系統日誌Linux