udump trace files
671943Apr 5 2009 — edited Apr 5 2009Hello experts,
recent few days I am seeing some kind of trace files are generating in my udump directory , its udump trace files are dangerous to database ?
one of the contents of trace files :
(Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /orcl/app/db_1
System name: SunOS
Node name: sf440
Release: 5.9
Version: Generic_118558-04
Machine: sun4u
Instance name: db1
Redo thread mounted by this instance: 1
Oracle process number: 28
Unix process pid: 16648, image: oracledb1@sf440
*** 2009-04-01 13:57:19.780
*** ACTION NAME:() 2009-04-01 13:57:19.779
*** MODULE NAME:(TOAD 9.0.1.8) 2009-04-01 13:57:19.779
*** SERVICE NAME:(umr) 2009-04-01 13:57:19.779
*** SESSION ID:(249.15523) 2009-04-01 13:57:19.779
----------------------------------------
SO: 66e401bb8, type: 2, owner: 0, flag: INIT/-/-/0x00
(process) Oracle pid=25, calls cur/top: 0/66016bcd8, flag: (0) -
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 0 0 112
last post received-location: kcbzww
last process to post me: 66e40c9a8 52 0
last post sent: 0 0 15
last post sent-location: ksupsc
last process posted by me: 66e3f65e0 1 14
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 66e472450
O/S info: user: oracle, term: UNKNOWN, ospid: 14908
OSD pid info: Unix process pid: 14908, image: oracle\db1r@sf440
Short stack dump:
ksdxfstk()+36<-ksdxcb()+2452<-sspuser()+176<-sigacthandler()+44<-read()+12<-nttrd()+124<-nsprecv()+336<-nsrdr()+124<-nsdo()+1476<-nsbrecv()+32<-nioqrc()+372<-opikndf2()+700<-opitsk()+804<-opiino()+1128<-opiodr()+1548<-opidrv()+896<-sou2o()+80<-opimaireal()+124<-main()+152<-_start()+380
Dump of memory from 0x000000066E3D8D08 to 0x000000066E3D8F10
66E3D8D00 00000004 00000000 [........]
66E3D8D10 00000006 64F12AD0 00000010 0003139D [....d.*.........]
66E3D8D20 00000006 6016BCD8 00000003 0003139D [....`...........]
66E3D8D30 00000006 6E7F5CD8 0000000B 0003139D [....n.\.........]
66E3D8D40 00000006 6E5303D8 00000004 00031291 [....nS..........]
66E3D8D50 00000000 00000000 00000000 00000000 [................]
Repeat 27 times )
THIS SEEMS TO BE SOME MEMEORY THINGS;;;
WHAT MEASURES WE HAVE TO TAKE TOWARDS THIS KIND OF TRACE MESSAGES ?