Results 1 to 3 of 3
  1. #1
    Join Date
    Jul 2003
    Location
    Dublin, Republic of Ireland
    Posts
    2

    Unanswered: Memory dumps in Oracle 8i trace file

    Hi All

    Hoping one of you can help me out here.

    We are getting a "Dump of memory from <x> to <y>" message in trace files on a customer's Oracle 8.1.7.4 database. There are no corresponding messages in the alert log.

    A transcript of part of the trace file is given below: the memory dump message is recurring constantly throughout the file.

    Since 8.1.7.4 went out of support as from the end of last year, we can't get any assistance from Oracle Support/MetaLink - so if anyone can give me some pointers, I'd be most obliged.

    Transcript
    ========
    Dump file D:\oracle\ora81\RDBMS\TRACE\ORA02204.TRC
    Tue Jun 20 16:29:45 2006
    ORACLE V8.1.7.4.1 - Production vsnsta=0
    vsnsql=f vsnxtr=3
    Windows 2000 Version 5.0 Service Pack 4, CPU type 586
    Oracle8i Enterprise Edition Release 8.1.7.4.1 - Production
    JServer Release 8.1.7.4.1 - Production
    Windows 2000 Version 5.0 Service Pack 4, CPU type 586
    Instance name: idb

    Redo thread mounted by this instance: 1

    Oracle process number: 31

    Windows thread id: 2204, image: ORACLE.EXE


    *** 2006-06-20 16:29:45.203
    *** SESSION ID28.236) 2006-06-20 16:29:45.187
    =====================
    PARSING IN CURSOR #1 len=492 dep=0 uid=18 oct=3 lid=18 tim=0 hv=313033313 ad='57c5404'
    SELECT F_WorkObjectBlob, F_WobNum, F_WorkSpaceId, F_Locked, F_LockMachine, F_LockUser, F_LockTime, F_LastUser, F_BitFlags, F_BindPending, F_BoundUser, F_BoundMachine, F_NextQueue, F_Tag, F_UniqueId, F_OperationId, F_WorkClassId, F_QueueWPClassId, F_EnqueueTime, F_CreateTime, F_InstrSheetId, F_WorkOrderId, F_SortOrder, F_StepProcId, WorkItemID, QueueName, Priority, Step, IndexingArea, DiaryDate, MyBox, QARequired, ChildID, VWServer, Moved, Reactivated FROM VWQueue1_359 where F_WobNum = :W
    END OF STMT
    PARSE #1:c=0,e=0,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=0,tim= 0
    WAIT #1: nam='SQL*Net message to client' ela= 0 p1=1111838976 p2=1 p3=0
    WAIT #1: nam='SQL*Net message from client' ela= 0 p1=1111838976 p2=1 p3=0
    BINDS #1:
    bind 0: dty=23 mxl=32(16) mal=00 scl=00 pre=00 oacflg=00 oacfl2=0 size=32 offset=0
    bfp=0c0521dc bln=32 avl=16 flg=05
    value=
    Dump of memory from 0xC0521DC to 0xC0521EC
    C0521D0 9E2362B1 [.b#.]
    C0521E0 479F3EB7 8B3F2BA9 A1441E4C [.>.G.+?.L.D.]
    EXEC #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=4,tim= 0
    WAIT #1: nam='SQL*Net message to client' ela= 0 p1=1111838976 p2=1 p3=0
    WAIT #1: nam='SQL*Net message from client' ela= 0 p1=1111838976 p2=1 p3=0
    WAIT #1: nam='SQL*Net message to client' ela= 0 p1=1111838976 p2=1 p3=0
    FETCH #1:c=0,e=0,p=0,cr=4,cu=0,mis=0,r=1,dep=0,og=4,tim= 0
    WAIT #1: nam='SQL*Net message from client' ela= 0 p1=1111838976 p2=1 p3=0
    WAIT #1: nam='SQL*Net message to client' ela= 0 p1=1111838976 p2=1 p3=0
    WAIT #1: nam='SQL*Net message from client' ela= 0 p1=1111838976 p2=1 p3=0
    XCTEND rlbk=0, rd_only=1
    WAIT #0: nam='SQL*Net message to client' ela= 0 p1=1111838976 p2=1 p3=0
    WAIT #0: nam='SQL*Net message from client' ela= 0 p1=1111838976 p2=1 p3=0
    STAT #1 id=1 cnt=1 pid=0 pos=0 obj=3696 op='TABLE ACCESS BY INDEX ROWID VWQUEUE1_359 '
    STAT #1 id=2 cnt=1 pid=1 pos=1 obj=3697 op='INDEX UNIQUE SCAN '

  2. #2
    Join Date
    Nov 2002
    Posts
    833
    you have enabled an extended trace

    have executed somestring like


    execute dbms_system.set_ev(sid,serial#,10046,12,'');

  3. #3
    Join Date
    Jul 2003
    Location
    Dublin, Republic of Ireland
    Posts
    2
    Thanx for that.

    I was more after what had caused the message to appear, though........

    We have a third-party application using this database, and it has ben failing with a "Segmentation Violation Error" message in the APPLICATION's own logs - not the Oracle logs, which are showing nothing.

    Any ideas? Anyone?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •