ITPub博客

首页 > 数据库 > Oracle > oracle bdump 下.trc文件过大问题处理

oracle bdump 下.trc文件过大问题处理

原创 Oracle 作者:ningzi82 时间:2010-08-20 10:12:44 0 删除 编辑

$ vi init*.ora

加入以下事件:

*.event='1349 trace name context forever, level 1048576'[@more@]

$ vi init*.ora

加入以下事件:

*.event='1349 trace name context forever, level 1048576'

Starting Captures produces trace: Cannot Resolve Kxidsqn For Lcr [ID 331558.1]

Modified 28-JUL-2009 Type PROBLEM Status PUBLISHED

In this Document
Symptoms
Cause
Solution


Applies to:

Oracle Server - Enterprise Edition
This problem can occur on any platform.

Symptoms

When starting a capture process, trace files are being generated. The contents looks like this:

Cannot resolve kxidsqn for lcr:
++ LCR Dump Begin: 0x700000108320d98
operation: 26, bobjn: 0 objn: 12986, objv: 0,
flags: 0xa10000, flags2: 0x00, MergeFlag: 0x3, Id : 0 numChgRec = 0
Thread#: 1 rba: 0x20852.000a653a.4c
scn: 0x0001.1f774ae2
xid: 0x012e.02c.ffffffff
newcount = 0, oldcount = 0
LUBA: 0x46.1180a19c.2c.50.32ba



Cause

This is an informational warning on capture restart from Unpublished Bug 8502190
The message can be ignored or suppressed by setting an event in the init.ora

Solution

To turn this particular warning trace off ,set the event 1349 in the init.ora file.

event="1349 trace name context forever, level 1048576"

Then bounce the instance.

来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/789833/viewspace-1037097/ ,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论

注册时间:2008-12-16

  • 博文量
    130
  • 访问量
    358889