|
操作系统:windos Server 2008 R2 Enterprise 64位
数据库版本:11.2.0.2
告警日志:
Wed Jan 03 20:55:53 2018
Dumping diagnostic data in directory=[cdmp_20180103205553], requested by (instance=1, osid=2396), summary=[incident=150343].
Errors in file D:\RUNTIME\ORACLE\diag\rdbms\orcl\orcl\trace\orcl_ora_2396.trc (incident=150344):
ORA-04030: 在尝试分配 1049112 字节 (pga heap,log read buffer) 时进程内存不足
ORA-03113: 通信通道的文件结尾
ORA-04030: 在尝试分配 4194328 字节 (QERHJ hash-joi,HT buckets) 时进程内存不足
Incident details in: D:\RUNTIME\ORACLE\diag\rdbms\orcl\orcl\incident\incdir_150344\orcl_ora_2396_i150344.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file D:\RUNTIME\ORACLE\diag\rdbms\orcl\orcl\trace\orcl_ora_2396.trc:
ORA-04030: 在尝试分配 1049112 字节 (pga heap,log read buffer) 时进程内存不足
ORA-03113: 通信通道的文件结尾
ORA-04030: 在尝试分配 4194328 字节 (QERHJ hash-joi,HT buckets) 时进程内存不足
Errors in file D:\RUNTIME\ORACLE\diag\rdbms\orcl\orcl\trace\orcl_ora_2396.trc:
ORA-03113: 通信通道的文件结尾
ORA-03113: 通信通道的文件结尾
ORA-04030: 在尝试分配 4194328 字节 (QERHJ hash-joi,HT buckets) 时进程内存不足
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x10] [PC:0xCD4D3E, dbgerEvalConditions()+358]
Dumping diagnostic data in directory=[cdmp_20180103205555], requested by (instance=1, osid=2396), summary=[incident=150344].
ERROR: Unable to normalize symbol name for the following short stack (at offset 213):
dbgexProcessError()+200<-dbgeExecuteForError()+65<-dbgePostErrorKGE()+2235<-dbkePostKGE_kgsf()+77<-kgeade()+563<-kgerelv()+151<-kgerev()+45<-kgerec5()+60<-sss_xcpt_EvalFilterEx()+1869<-sss_xcpt_EvalFilter()+174<-.1.6_8+59<-0000000077B985A8<-0000000077BA9D0D<-0000000077B991AF<-0000000077BD1278<-dbgerEvalConditions()+358<-dbgerEvaluateRules()+83<-dbgexPhaseII()+1594<-dbgexExplicitEndInc()+769<-dbgeEndDDEInvocationImpl()+760<-dbgeEndDDEInvocation()+47<-kghnospc()+5579<-kghalo()+1978<-qerhjAllocHashTable()+248<-qerhjBuildHashTable()+340<-PGOSF550_qerhjInnerProbeHashTable()+1244<-PGOSF672_qervwRowProcedure()+317<-PGOSF670_qeruaRowProcedure()+356<-PGOSF555_qerflRop()+102<-PGOSF672_qervwRowProcedure()+317<-PGOSF670_qeruaRowProcedure()+356<-qerfxFetch()+977<-rwsfcd()+136<-qeruaFetch()+773<-qervwFetch()+177<-qerflFetch()+178<-rwsfcd()+136<-qeruaFetch()+773<-qervwFetch()+177<-rwsfcd()+136<-qerhjFetch()+626<-qergsFetch()+9093<-opifch2()+3855<-kpoal8()+3225<-opiodr()+1607<-ttcpip()+1325<-opitsk()+2106<-opiino()+1246<-opiodr()+1607<-opidrv()+862
Errors in file D:\RUNTIME\ORACLE\diag\rdbms\orcl\orcl\trace\orcl_ora_2396.trc (incident=150345):
ORA-07445: 出现异常错误: 核心转储 [dbgerEvalConditions()+358] [ACCESS_VIOLATION] [ADDR:0x10] [PC:0xCD4D3E] [UNABLE_TO_READ] []
ORA-03113: 通信通道的文件结尾
ORA-04030: 在尝试分配 4194328 字节 (QERHJ hash-joi,HT buckets) 时进程内存不足
Incident details in: D:\RUNTIME\ORACLE\diag\rdbms\orcl\orcl\incident\incdir_150345\orcl_ora_2396_i150345.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Wed Jan 03 20:55:56 2018
Process m000 died, see its trace file
Dumping diagnostic data in directory=[cdmp_20180103205558], requested by (instance=1, osid=2396), summary=[incident=150343].
Wed Jan 03 20:56:57 2018
Sweep [inc][150345]: completed
Sweep [inc][150344]: completed
Sweep [inc][150343]: completed
Sweep [inc2][150345]: completed
Sweep [inc2][150344]: completed
Sweep [inc2][150343]: completed
Wed Jan 03 21:05:43 2018
Errors in file D:\RUNTIME\ORACLE\diag\rdbms\orcl\orcl\trace\orcl_ora_11520.trc (incident=150351):
ORA-04030: 在尝试分配 4186152 字节 (QERHJ hash-joi,QERHJ list array) 时进程内存不足
Incident details in: D:\RUNTIME\ORACLE\diag\rdbms\orcl\orcl\incident\incdir_150351\orcl_ora_11520_i150351.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Non critical error ORA-00001 caught while writing to trace file "D:\RUNTIME\ORACLE\diag\rdbms\orcl\orcl\incident\incdir_150351\orcl_ora_11520_i150351.trc"
Error message: OSD-00001: 附加错误信息
O/S-Error: (OS 8) 存储空间不足,无法处理此命令。
Writing to the above trace file is disabled for now on...
报错现象:OS空间不足,怀疑是某个进程占了大量的内存,具体什么进程需要进一步分析。
暂时解决办法:重启数据库。
|
|