After reading through a recent trace file I noticed entried with timestamps from last year.
The version of the database is 7.3.4 on NT
Could anyone explain this to me ????
I have included a section of the trace file.
Process global information:
process: 44c42920, call: 0, xact: 0, curses: 0, usrses: 44d68468
SO: 44c42920, type: 1, owner: 0, flag: INIT/-/-/0x00
(process) Oracle pid=19, calls cur/top: 0/2fc03230, flag: (0) -
int error: 0, call error: 0, sess error: 0
(latch info) wait_event=0 bits=0
O/S info: user: SYSTEM, term: SPDCDMS03, ospid: 0028B
OSD pid info: pid: 28b
SO: 44d68468, type: 3, owner: 44c42920, flag: INIT/-/-/0x00
(session) trans: 0, creator: 44c42920, flag: (41) USR/- -/-/-/-/-/-
oct: 0, prv: 0, user: 10/MLSAPROD
O/S info: user: OSPIERS, term: OSPIERS, ospid: 1084:1224, machine: MLUACCOUNT\OSPIERS
application name: SQL*Plus, hash value=3375793674
last wait for 'SQL*Net break/reset to client' seq=504 wait_time=-1
driver id=54435053, break?=1, =0
SO: 388a1a24, type: 19, owner: 44d68468, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=388a1a24 handle=3bea6664 mode=N
call pin=4428e004 session pin=0
user=44d68468 session=44d68468 count=1 flags=[00] savepoint=249
LIBRARY OBJECT HANDLE: handle=3bea6664

hash=bb06586c timestamp=11-14-2001 18:38:27
namespace=CRSR flags=RON/TIM/PN0/SML/[12010000]
kk-dd-aa-ll=00-01-00-01 lock=N pin=0 latch=2
lwt=3bea667c[3bea667c,3bea667c] ltm=3bea6684[3bea6684,3bea6684]
pwt=3bea6694[3bea6694,3bea6694] ptm=3bea66e8[3bea66e8,3bea66e8]