Hello All
Just thought of checking with you all on the trace file generated by LMS Process (Lock Manager Server)
I have a trace file @ background_dump_dest of 15Gb (apx) By any chance can some one put some light on it and let me know what could be the potential cause to increase in the size of that file drastically which apparently blew the file system off .
| -rw-r----- | 1 oracle asmadmin 15308800000 Jan 22 23:44 GPP_lms0_19268006.trc |
here is some info from this trace file ..
lock: C rls: 0x0 acq: 0x1 latch: 13 lms: 1
flags: 0x31 fair: 0 recovery: 0
bscn: 0x0.35285570 bctx: 0x0 scan: 0x0
lcp: 0x0 lnk: [NULL] lch: [NULL]
seq: 21 hist: 407 197 48 121 225 60 65 67 143:0 208 352 197 48 121 225 60
65
GLOBAL CACHE ELEMENT DUMP (address: 0x70001022825b6e0):
id1: 0x248ccd id2: 0x2 pkey: OBJ#0,6,177993 block: (2/2395341)
lock: C rls: 0x0 acq: 0x1 latch: 14 lms: 1
flags: 0x31 fair: 0 recovery: 0
bscn: 0x0.ea6f92a bctx: 0x0 scan: 0x0
lcp: 0x0 lnk: [NULL] lch: [NULL]
seq: 9 hist: 407 197 48 121 239 144:0 192 352 32 121 45 4 33 225 60 424
GLOBAL CACHE ELEMENT DUMP (address: 0x70001022825b7f8):
id1: 0x13eb3 id2: 0x1 pkey: OBJ#0,0,18 block: (1/81587)
lock: C rls: 0x0 acq: 0x1 latch: 15 lms: 1
flags: 0x31 fair: 0 recovery: 0
bscn: 0x0.2eb83e0e bctx: 0x0 scan: 0x0
lcp: 0x0 lnk: [NULL] lch: [NULL]
seq: 181 hist: 407 197 48 121 334 144:0 213 7 352 197 48 121 334
GLOBAL CACHE ELEMENT DUMP (address: 0x70001022825b910):
id1: 0x1b075 id2: 0xb pkey: OBJ#0,6,193902 block: (11/110709)
lock: C rls: 0x0 acq: 0x1 latch: 0 lms: 0
flags: 0x31 fair: 0 recovery: 0
bscn: 0x0.c7af6f7 bctx: 0x0 scan: 0x0
lcp: 0x0 lnk: [NULL] lch: [NULL]
seq: 9 hist: 407 197 48 121 239 144:0 7 352 32 121 67 144:0 98 197 48
GLOBAL CACHE ELEMENT DUMP (address: 0x70001022825ba28):
Thanks in advance
Regards
Message was edited by: User347578