从11gR1开始,Oracle提供了一种处理错误和跟踪文件的新方法:现在有一个专用于此目的的特殊命令行实用程序称为adrci(自动诊断存储库命令解释器)。这篇文章旨在向您展示基本命令,DBA应该知道这些命令才能使用它。我们将看
- 查看alert.log
- 事件与问题之间的关系
- 创建软件包和ZIP文件以发送给Oracle支持
- 管理,特别是清除跟踪文件
首先,我会提出一个问题。不要对您的生产数据库执行此操作!特别是:切勿在字典表上进行DML!
oracle@uhesse ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.2.0 Production on Wed Jun 1 10:25:06 2011
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select * from v$version;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
PL/SQL Release 11.2.0.2.0 - Production
CORE 11.2.0.2.0 Production
TNS for Linux: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production
SQL> show parameter diagnostic
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
diagnostic_dest string /u01/app/oracle
SQL> grant dba to adam identified by adam;
Grant succeeded.
SQL> connect adam/adam
Connected.
SQL> create table t (n number);
Table created.
SQL> select object_id from user_objects;
OBJECT_ID
----------
75719
SQL> connect / as sysdba
Connected.
SQL> update tab$ set cols=2 where obj#=75719;
1 row updated.
SQL> commit;
Commit complete.
SQL> alter system flush shared_pool;
System altered.
SQL> connect adam/adam
Connected.
SQL> select * from t;
select * from t
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Process ID: 2236
Session ID: 29 Serial number: 9
我刷新了共享池,以使数据字典缓存为空。否则,选择可能不会使会话崩溃。假设用户现在通过电话给我打电话。作为经验丰富的DBA的第一个想法是:我们查看alert.log!是的 请注意,我们现在有两种不同的alert.log。
每个OFA都以常规文本格式显示一个,格式为$ORACLE_BASE/diag/rdbms//数据库名称/实例/跟踪的名称。此位置由新的初始化参数DIAGNOSTIC_DEST确定,而BACKGROUND_DUMP_DEST在11g中已弃用。
1.查看alert.log
另一个格式为XML格式,位于 $ORACLE_BASE/diag/rdbms//数据库名称/实例/警报名称中。adrci访问此版本的alert.log:
[oracle@uhesse ~]$ adrci
ADRCI: Release 11.2.0.2.0 - Production on Wed Jun 1 10:20:08 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ADR base = "/u01/app/oracle"
adrci> show home
ADR Homes:
diag/tnslsnr/uhesse/listener
diag/rdbms/orcl/orcl
请注意,我们有不同的ADR主目录。就我而言,只有两个,因为我没有在此演示系统上使用网格基础结构,否则将会有另一个。我首先指定我的数据库主页。然后,我看一下alert.log。如果您使用的是Windows,那么这是个好消息:最后,您还可以在alert.log -tail加上-f
adrci> set home diag/rdbms/orcl/orcl
adrci> show alert -tail -f
2011-06-01 10:16:35.337000 +02:00
db_recovery_file_dest_size of 4032 MB is 0.00% used. This is a
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.
Starting background process CJQ0
CJQ0 started with pid=21, OS id=2204
2011-06-01 10:18:42.668000 +02:00
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x0] [PC:0x90D891A, qcstda()+702] [flags: 0x0, count: 1]
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_2236.trc (incident=6153):
ORA-07445: exception encountered
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_6153/orcl_ora_2236_i6153.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
2011-06-01 10:18:47.518000 +02:00
Dumping diagnostic data in directory=[cdmp_20110601101847], requested by (instance=1, osid=2236), summary=[incident=6153].
2011-06-01 10:18:48.727000 +02:00
Sweep [inc][6153]: completed
Sweep [inc2][6153]: completed
2.事件与问题之间的关系
您会看到事件记录在alert.log中。它告诉您“使用ADRCI或支持工作台打包事件。” 我们将很快看到如何做到这一点。首先,我想解释事件和问题之间的关系:事件是问题的具体发生。换句话说:同一问题可能有多个事件。为了说明这一点,我将打开另一个终端,并再次对表t进行选择,同时仍然在第一个会话中添加警报日志。
第二终端:
[oracle@uhesse ~]$ sqlplus adam/adam
SQL*Plus: Release 11.2.0.2.0 Production on Wed Jun 1 10:21:52 2011
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select * from t where n=42;
select * from t where n=42
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Process ID: 2299
Session ID: 36 Serial number: 11
第一终端:
2011-06-01 10:21:31.367000 +02:00
Starting background process SMCO
SMCO started with pid=19, OS id=2268
2011-06-01 10:22:08.781000 +02:00
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x0] [PC:0x90D891A, qcstda()+702] [flags: 0x0, count: 1]
Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_2299.trc (incident=6201):
ORA-07445: exception encountered: core dump [qcstda()+702] [SIGSEGV] [ADDR:0x0] [PC:0x90D891A] [Address not mapped to object] []
Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_6201/orcl_ora_2299_i6201.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
2011-06-01 10:22:11.135000 +02:00
Dumping diagnostic data in directory=[cdmp_20110601102211], requested by (instance=1, osid=2299), summary=[incident=6201].
2011-06-01 10:22:13.370000 +02:00
Sweep [inc][6201]: completed
Sweep [inc2][6201]: completed
我已经看到了第二起事件。我用CTRL + C从-tail -f退出并继续:
adrci> show problem
ADR Home = /u01/app/oracle/diag/rdbms/orcl/orcl:
*************************************************************************
PROBLEM_ID PROBLEM_KEY LAST_INCIDENT LASTINC_TIME
-------------------- ----------------------------------------------------------- -------------------- ----------------------------------------
1 ORA 7445 [qcstda()+702] 6201 2011-06-01 10:22:08.924000 +02:00
1 rows fetched
所以有一个ID 1问题,最后一次事件发生在10:22。还有更多吗?
adrci> show incident
ADR Home = /u01/app/oracle/diag/rdbms/orcl/orcl:
*************************************************************************
INCIDENT_ID PROBLEM_KEY CREATE_TIME
-------------------- ----------------------------------------------------------- ----------------------------------------
6153 ORA 7445 [qcstda()+702] 2011-06-01 10:18:42.995000 +02:00
6201 ORA 7445 [qcstda()+702] 2011-06-01 10:22:08.924000 +02:00
2 rows fetched
我想查看有关事件的更多详细信息:
adrci> show incident -mode detail -p "incident_id=6201"
ADR Home = /u01/app/oracle/diag/rdbms/orcl/orcl:
*************************************************************************
**********************************************************
INCIDENT INFO RECORD 1
**********************************************************
INCIDENT_ID 6201
STATUS ready
CREATE_TIME 2011-06-01 10:22:08.924000 +02:00
PROBLEM_ID 1
CLOSE_TIME
FLOOD_CONTROLLED none
ERROR_FACILITY ORA
ERROR_NUMBER 7445
ERROR_ARG1 qcstda()+702
ERROR_ARG2 SIGSEGV
ERROR_ARG3 ADDR:0x0
ERROR_ARG4 PC:0x90D891A
ERROR_ARG5 Address not mapped to object
ERROR_ARG6
ERROR_ARG7
ERROR_ARG8
ERROR_ARG9
ERROR_ARG10
ERROR_ARG11
ERROR_ARG12
SIGNALLING_COMPONENT SQL_Parser
SIGNALLING_SUBCOMPONENT
SUSPECT_COMPONENT
SUSPECT_SUBCOMPONENT
ECID
IMPACTS 0
PROBLEM_KEY ORA 7445 [qcstda()+702]
FIRST_INCIDENT 6153
FIRSTINC_TIME 2011-06-01 10:18:42.995000 +02:00
LAST_INCIDENT 6201
LASTINC_TIME 2011-06-01 10:22:08.924000 +02:00
IMPACT1 0
IMPACT2 0
IMPACT3 0
IMPACT4 0
KEY_NAME ProcId
KEY_VALUE 25.3
KEY_NAME Client ProcId
KEY_VALUE oracle@uhesse (TNS V1-V3).2299_140262306875136
KEY_NAME PQ
KEY_VALUE (0, 1306916528)
KEY_NAME SID
KEY_VALUE 36.11
OWNER_ID 1
INCIDENT_FILE /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_2299.trc
OWNER_ID 1
INCIDENT_FILE /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_6201/orcl_ora_2299_i6201.trc
1 rows fetched
我想看看上面提到的事件跟踪文件:
adrci> show trace /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_6201/orcl_ora_2299_i6201.trc
/u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_6201/orcl_ora_2299_i6201.trc
----------------------------------------------------------
LEVEL PAYLOAD
----- ------------------------------------------------------------------------------------------------------------------------------------------------
Dump file /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_6201/orcl_ora_2299_i6201.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1
System name: Linux
Node name: uhesse
Release: 2.6.32-100.28.5.el6.x86_64
Version: #1 SMP Wed Feb 2 18:40:23 EST 2011
Machine: x86_64
Instance name: orcl
Redo thread mounted by this instance: 1
Oracle process number: 25
Unix process pid: 2299, image: oracle@uhesse (TNS V1-V3)
*** 2011-06-01 10:22:08.929
*** SESSION ID:(36.11) 2011-06-01 10:22:08.929
*** CLIENT ID:() 2011-06-01 10:22:08.929
*** SERVICE NAME:(SYS$USERS) 2011-06-01 10:22:08.929
*** MODULE NAME:(SQL*Plus) 2011-06-01 10:22:08.929
*** ACTION NAME:() 2011-06-01 10:22:08.929
Dump continued from file: /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_2299.trc
1> ***** Error Stack *****
ORA-07445: exception encountered: core dump [qcstda()+702] [SIGSEGV] [ADDR:0x0] [PC:0x90D891A] [Address not mapped to object] []
1< ***** Error Stack ***** 1> ***** Dump for incident 6201 (ORA 7445 [qcstda()+702]) *****
2> ***** Beginning of Customized Incident Dump(s) *****
2> ***** Beginning of Customized Incident Dump(s) *****
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x0] [PC:0x90D891A, qcstda()+702] [flags: 0x0, count: 1]
Registers:
%rax: 0x0000000000000000 %rbx: 0x00007f915c77f0e0 %rcx: 0x0000000000000007
%rdx: 0x0000000000000000 %rdi: 0x00007f915c77be98 %rsi: 0x0000000000000000
%rsp: 0x00007fffc65178e0 %rbp: 0x00007fffc6517960 %r8: 0x0000000000000028
%r9: 0x0000000000002000 %r10: 0x00000000093849c0 %r11: 0x0000000000000168
%r12: 0x00007f915c77ade8 %r13: 0x000000008edbb178 %r14: 0x00007f915c777da0
%r15: 0x00007f915c77ae28 %rip: 0x00000000090d891a %efl: 0x0000000000010246
qcstda()+686 (0x90d890a) mov -0x40(%rbp),%rdi
qcstda()+690 (0x90d890e) mov %rdx,0x18(%rbx)
qcstda()+694 (0x90d8912) mov 0x60(%r15),%rsi
qcstda()+698 (0x90d8916) mov %ecx,0x8(%r15)
> qcstda()+702 (0x90d891a) mov %ecx,(%rsi)
qcstda()+704 (0x90d891c) mov 0x78(%rdi),%rdx
qcstda()+708 (0x90d8920) test %rdx,%rdx
qcstda()+711 (0x90d8923) jnz 0x90d8d03
qcstda()+717 (0x90d8929) mov -0x70(%rbp),%rdi
*** 2011-06-01 10:22:08.963
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x3, level=3, mask=0x0)
3> ***** Current SQL Statement for this session (sql_id=8r222qucmawdt) *****
select * from t where n=42
3< ***** current_sql_statement ***** 3
3.创建软件包和ZIP文件以发送给Oracle支持
我自己可能无法解决问题。Oracle支持将帮助我完成这一任务。我使用称为“事件包装服务”(IPS)的方法收集所有必需的信息:
adrci> ips create package problem 1 correlate all
Created package 2 based on problem id 1, correlation level all
该文件尚未创建ZIP文件,因此被称为“逻辑包”。ZIP文件的产生从逻辑包,这是创建:
adrci> ips generate package 2 in "/home/oracle"
Generated package 2 in file /home/oracle/ORA7445qc_20110601112533_COM_1.zip, mode complete
4.管理,特别是清除跟踪文件
现在到跟踪文件的管理。您可能会注意到11g创建了许多不时需要清除的跟踪文件。实际上,这是自动完成的,但是您可能需要更改默认的清除策略:
adrci> show tracefile -rt
01-JUN-11 10:31:48 diag/rdbms/orcl/orcl/trace/orcl_mmon_2106.trc
01-JUN-11 09:43:43 diag/rdbms/orcl/orcl/trace/orcl_ckpt_2100.trc
01-JUN-11 09:22:13 diag/rdbms/orcl/orcl/trace/alert_orcl.log
01-JUN-11 09:22:11 diag/rdbms/orcl/orcl/trace/orcl_diag_2088.trc
01-JUN-11 09:22:10 diag/rdbms/orcl/orcl/trace/orcl_ora_2299.trc
01-JUN-11 09:22:10 diag/rdbms/orcl/orcl/incident/incdir_6201/orcl_ora_2299_i6201.trc
01-JUN-11 09:18:47 diag/rdbms/orcl/orcl/trace/orcl_ora_2236.trc
01-JUN-11 09:18:47 diag/rdbms/orcl/orcl/incident/incdir_6153/orcl_ora_2236_i6153.trc
01-JUN-11 09:17:19 diag/rdbms/orcl/orcl/trace/orcl_dbrm_2090.trc
01-JUN-11 09:16:44 diag/rdbms/orcl/orcl/trace/orcl_j002_2210.trc
01-JUN-11 09:16:30 diag/rdbms/orcl/orcl/trace/orcl_ora_2187.trc
01-JUN-11 09:16:19 diag/rdbms/orcl/orcl/trace/orcl_mman_2094.trc
01-JUN-11 09:16:16 diag/rdbms/orcl/orcl/trace/orcl_vktm_2082.trc
01-JUN-11 09:16:14 diag/rdbms/orcl/orcl/trace/orcl_ora_2016.trc
30-MAY-11 14:07:02 diag/rdbms/orcl/orcl/trace/orcl_mmon_2093.trc
30-MAY-11 11:15:30 diag/rdbms/orcl/orcl/trace/orcl_ora_3414.trc
30-MAY-11 11:00:01 diag/rdbms/orcl/orcl/trace/orcl_j000_2245.trc
30-MAY-11 10:56:58 diag/rdbms/orcl/orcl/trace/orcl_dbrm_2077.trc
30-MAY-11 10:56:20 diag/rdbms/orcl/orcl/trace/orcl_j002_2201.trc
30-MAY-11 10:56:06 diag/rdbms/orcl/orcl/trace/orcl_ora_2178.trc
30-MAY-11 10:55:58 diag/rdbms/orcl/orcl/trace/orcl_mman_2081.trc
30-MAY-11 10:55:55 diag/rdbms/orcl/orcl/trace/orcl_vktm_2069.trc
30-MAY-11 10:55:53 diag/rdbms/orcl/orcl/trace/orcl_ora_2006.trc
27-MAY-11 10:53:25 diag/rdbms/orcl/orcl/trace/orcl_mmon_8589.trc
27-MAY-11 10:17:05 diag/rdbms/orcl/orcl/trace/orcl_ora_11390.trc
27-MAY-11 09:26:41 diag/rdbms/orcl/orcl/trace/orcl_ora_10739.trc
27-MAY-11 09:23:53 diag/rdbms/orcl/orcl/trace/orcl_dbrm_8573.trc
27-MAY-11 09:22:58 diag/rdbms/orcl/orcl/trace/orcl_ora_8687.trc
27-MAY-11 09:22:54 diag/rdbms/orcl/orcl/trace/orcl_mman_8577.trc
27-MAY-11 09:22:50 diag/rdbms/orcl/orcl/trace/orcl_vktm_8565.trc
27-MAY-11 09:22:48 diag/rdbms/orcl/orcl/trace/orcl_ora_8516.trc
27-MAY-11 09:22:44 diag/rdbms/orcl/orcl/trace/orcl_ora_8515.trc
27-MAY-11 09:22:44 diag/rdbms/orcl/orcl/trace/orcl_vktm_8347.trc
27-MAY-11 09:21:24 diag/rdbms/orcl/orcl/trace/orcl_dbrm_8355.trc
27-MAY-11 09:20:29 diag/rdbms/orcl/orcl/trace/orcl_ora_8470.trc
27-MAY-11 09:20:28 diag/rdbms/orcl/orcl/trace/orcl_mmon_8371.trc
27-MAY-11 09:20:28 diag/rdbms/orcl/orcl/trace/orcl_ora_8381.trc
27-MAY-11 09:20:26 diag/rdbms/orcl/orcl/trace/orcl_mman_8359.trc
27-MAY-11 09:20:20 diag/rdbms/orcl/orcl/trace/orcl_ora_8299.trc
27-MAY-11 09:20:15 diag/rdbms/orcl/orcl/trace/orcl_ora_8297.trc
27-MAY-11 09:20:15 diag/rdbms/orcl/orcl/trace/orcl_vktm_8096.trc
27-MAY-11 09:20:07 diag/rdbms/orcl/orcl/trace/orcl_ora_8296.trc
27-MAY-11 09:19:42 diag/rdbms/orcl/orcl/trace/orcl_ora_8285.trc
27-MAY-11 09:19:33 diag/rdbms/orcl/orcl/trace/orcl_dm00_8271.trc
27-MAY-11 09:19:33 diag/rdbms/orcl/orcl/trace/orcl_dw00_8273.trc
27-MAY-11 09:19:11 diag/rdbms/orcl/orcl/trace/orcl_dbrm_8104.trc
27-MAY-11 09:18:53 diag/rdbms/orcl/orcl/trace/orcl_ora_8267.trc
27-MAY-11 09:18:33 diag/rdbms/orcl/orcl/trace/orcl_j001_8237.trc
27-MAY-11 09:18:26 diag/rdbms/orcl/orcl/trace/orcl_mmon_8219.trc
27-MAY-11 09:18:23 diag/rdbms/orcl/orcl/trace/orcl_ora_8231.trc
27-MAY-11 09:18:22 diag/rdbms/orcl/orcl/trace/orcl_cjq0_8229.trc
27-MAY-11 09:18:16 diag/rdbms/orcl/orcl/trace/orcl_ora_8131.trc
27-MAY-11 09:18:14 diag/rdbms/orcl/orcl/trace/orcl_m000_8223.trc
27-MAY-11 09:18:13 diag/rdbms/orcl/orcl/trace/orcl_mman_8108.trc
27-MAY-11 09:18:05 diag/rdbms/orcl/orcl/trace/orcl_ora_8048.trc
27-MAY-11 09:17:59 diag/rdbms/orcl/orcl/trace/orcl_vktm_7920.trc
27-MAY-11 09:17:59 diag/rdbms/orcl/orcl/trace/orcl_ora_8046.trc
27-MAY-11 09:17:00 diag/rdbms/orcl/orcl/trace/orcl_mman_7932.trc
27-MAY-11 09:16:56 diag/rdbms/orcl/orcl/trace/orcl_ora_7954.trc
27-MAY-11 09:16:51 diag/rdbms/orcl/orcl/trace/orcl_ora_7871.trc
我已经有一些跟踪文件。他们要待多久?
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
1 rows fetched
普通跟踪文件将保留30天(720小时),而事件文件之类的文件默认保留一年(8760小时)。我们可以通过以下方式更改该政策:
adrci> set control (SHORTP_POLICY = 360)
adrci> set control (LONGP_POLICY = 2190)
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 2190 2011-06-01 11:42:17.208064 +02:00 1 2 80 1 2011-05-27 10:16:46.997118 +02:00
1 rows fetched
另外,我们可能想手动清除跟踪文件。以下命令将手动清除所有早于2天(2880分钟)的跟踪文件:
adrci> purge -age 2880 -type trace
adrci> show tracefile -rt
01-JUN-11 10:46:54 diag/rdbms/orcl/orcl/trace/orcl_mmon_2106.trc
01-JUN-11 09:43:43 diag/rdbms/orcl/orcl/trace/orcl_ckpt_2100.trc
01-JUN-11 09:22:13 diag/rdbms/orcl/orcl/trace/alert_orcl.log
01-JUN-11 09:22:11 diag/rdbms/orcl/orcl/trace/orcl_diag_2088.trc
01-JUN-11 09:22:10 diag/rdbms/orcl/orcl/incident/incdir_6201/orcl_ora_2299_i6201.trc
01-JUN-11 09:22:10 diag/rdbms/orcl/orcl/trace/orcl_ora_2299.trc
01-JUN-11 09:18:47 diag/rdbms/orcl/orcl/incident/incdir_6153/orcl_ora_2236_i6153.trc
01-JUN-11 09:18:47 diag/rdbms/orcl/orcl/trace/orcl_ora_2236.trc
01-JUN-11 09:17:19 diag/rdbms/orcl/orcl/trace/orcl_dbrm_2090.trc
01-JUN-11 09:16:44 diag/rdbms/orcl/orcl/trace/orcl_j002_2210.trc
01-JUN-11 09:16:30 diag/rdbms/orcl/orcl/trace/orcl_ora_2187.trc
01-JUN-11 09:16:19 diag/rdbms/orcl/orcl/trace/orcl_mman_2094.trc
01-JUN-11 09:16:16 diag/rdbms/orcl/orcl/trace/orcl_vktm_2082.trc
01-JUN-11 09:16:14 diag/rdbms/orcl/orcl/trace/orcl_ora_2016.trc
30-MAY-11 14:07:02 diag/rdbms/orcl/orcl/trace/orcl_mmon_2093.trc
30-MAY-11 11:15:30 diag/rdbms/orcl/orcl/trace/orcl_ora_3414.trc
30-MAY-11 11:00:01 diag/rdbms/orcl/orcl/trace/orcl_j000_2245.trc
30-MAY-11 10:56:58 diag/rdbms/orcl/orcl/trace/orcl_dbrm_2077.trc
30-MAY-11 10:56:20 diag/rdbms/orcl/orcl/trace/orcl_j002_2201.trc
30-MAY-11 10:56:06 diag/rdbms/orcl/orcl/trace/orcl_ora_2178.trc
30-MAY-11 10:55:58 diag/rdbms/orcl/orcl/trace/orcl_mman_2081.trc
30-MAY-11 10:55:55 diag/rdbms/orcl/orcl/trace/orcl_vktm_2069.trc
30-MAY-11 10:55:53 diag/rdbms/orcl/orcl/trace/orcl_ora_2006.trc
结论:通过adrci,我们有了一个新的高效实用程序来处理Oracle错误-尤其是收集信息以将其发送给Oracle支持部门。此功能称为事件打包服务。11g正在生成大量跟踪文件。我们可以通过adrci控制它们的清除策略。最后,我们现在可以在任何操作系统上添加-f我们的alert.log。