Starting Captures produces trace: Cannot Resolve Kxidsqn For Lcr
(Doc ID 331558.1)
Last updated on AUGUST 04, 2018
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.8 to 10.2.0.4 [Release 9.2 to 10.2]Information in this document applies to 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
++ 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
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |