Trace file: DEBUG: AUTONOMOUS PROCESS REDO POO

I have a trace file being generated at 00:01 usually daily. Any idea what this is?
$cat /u01/app/oracle/admin/A001/bdump/a001_j000_3562.trc
Oracle Database 10g Enterprise Edition Release 10.1.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /u01/app/oracle/product/10.1.0/Db_1
System name: Linux
Node name: mybox.mydomain.com
Release: 2.6.9-1.724_FC3
Version: #1 Sun Jan 2 15:43:49 EST 2005
Machine: i686
Instance name: A001
Redo thread mounted by this instance: 1
Oracle process number: 12
Unix process pid: 3562, image: [email protected] (J000)
*** 2005-01-06 00:01:26.780
*** SERVICE NAME:(SYS$USERS) 2005-01-06 00:01:26.701
*** SESSION ID:(153.270) 2005-01-06 00:01:26.701
DEBUG: AUTONOMOUS PROCESS REDO POOL ALLOCATED
*** 2005-01-06 00:01:39.222
DEBUG: AUTONOMOUS PROCESS REDO POOL FREED

You displayed your owsidev_reco_1273966.trc file. This is the trace file being generated by the recoverer process.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/process.htm#i21745
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/manproc.htm#sthref667
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/process.htm#i24691

Similar Messages

  • Trace / debug Cobol process

    How to trace or debug cobol process . For example : Records and enrollment - Enroll Students - Block enrollment - enrollment request i am getting the error :
    Remote program SRPCERC failed with reason : SELECT-CAR(FETCH)NO ROW RETURNED(2,-1) ENRL_RE_HDR_WRK.ENRL_REQ_RC_PB.FieldChange PCPC:479 Statement: 10
    Select returned no rows. From which table . Please help , how to debug this process .

    It seems there is a similar bug, described in the solution id #200970506.
    Anyway, you could set the trace by setting SQLTrace (e.g. to 3) in your ProcessScheduler config file.
    You could read the following discussion :
    http://peoplesoft.ittoolbox.com/groups/technical-functional/peopletools-l/tracing-cobol-programs-1499824
    Nicolas.

  • How to use trace file information?

    Hello.
    I got trace files in $O_H/network/trace/ listener.trc and in
    $O_H/rdbms/log/ora_orcl_22846.trc and others in the same dir. SO
    how can I get any understandable form? ( All this numbers and
    letters say nothing to me :((. Maybe I should read some manual?)
    Thank You.
    null

    ANdrey (guest) wrote:
    : Hello.
    : I got trace files in $O_H/network/trace/ listener.trc and in
    : $O_H/rdbms/log/ora_orcl_22846.trc and others in the same dir.
    SO
    : how can I get any understandable form? ( All this numbers and
    : letters say nothing to me :((. Maybe I should read some
    manual?)
    : Thank You.
    Listener trace should be humanly readable by itself and
    oracle trace files should be processed by using tkprof.
    null

  • Trace files being truncated after 18mb

    I have enabled trace file debugging for my application and after the trace file has reached approx 18mb, it stops writing to the file. Im also doing logging and the log file is usually around 80mb. Is there some sort of maximum file size restriction? How do I fix this?

    You gave almost no details but as a general statement there are no limits on file sizes, at least with the size of files you're dealing with. Some O/S's and file systems might have an issue after 2GB.
    What is your application? What kind of logging does it use (i.e. log4j, jdk logging, etc). What O/S are you on? How much free disk space do you have?

  • Regarding trace files

    Dear all,
    I have multiple trace files in the path specified in parameter background_dump_dest i.e /u01/DEV/db/tech_st/11.1.0/admin/DEV_crod/diag/rdbms/dev/DEV/trace
    Different patterns of the trace files in that directory are as below
    DEV_m001_20989.trm
    DEV_m001_20989.trc
    DEV_ora_16836.trm
    DEV_ora_16836.trc
    DEV_dbrm_16264.trm
    DEV_dbrm_16264.trc
    DEV_vktm_16258.trm
    DEV_vktm_16258.trc
    DEV_lgwr_16856.trm
    DEV_lgwr_16856.trc
    DEV_arc2_16878.trm
    DEV_arc2_16878.trc
    DEV_pmon_17878.trm
    DEV_pmon_17878.trc
    DEV_cjq0_17949.trm
    DEV_cjq0_17949.trc
    alert_DEV.log
    Kindly, let me know what are all the files needed to be present in this directory so that I can remove the unnecessary. one's
    Regards,
    Charan

    Hi,
    Can you elaborate what does "something wrong in your system mean", I mean for what kind of errors those trace files will be generated.Need not be something wrong (al though some times it could be, you will not know until you open and see it).
    For example: Please see
    No problem for the following message in trace file
    J00 Trace Files Generated After 11g Upgrade With Bind Mismatch Messages [ID 1229793.1]
    The Database Server Is Creating A Lot Of Trace Files From the VKTM Process [ID 837105.1]
    Some sort of problem in the following trace file.
    Ksvcreate: Process(M001) Creation Failed , Database hang [ID 1233079.1]
    Thanks

  • Generation of MMON process trace files in large file size (GB Size)

    Hi,
    I have created a database using the dbca in windows platform. Few days I found that, in the BDUMP directory the MMON process trace files are getting generated. The files starts to generate in MB size and will increase upto GB size. I know that the back ground process trace files cannot be disabled. So now iam force to manually delete these files from the bdump directory.plz help me to resolve this issue.
    I have checked and verified the SGA size, Shared Pool size and other memory areas.
    The statistics level in Typical also.
    But still the files are generated.
    PLease Helppp.....
    Shiyas

    hi
    As per your instruction i have checked the Alert log file. I have pasted a part of errors that found in the alert log file.
    Mon Jun 07 09:30:58 2010
    Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_652.trc:
    ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []
    Mon Jun 07 09:31:02 2010
    Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_652.trc:
    ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []
    Mon Jun 07 09:36:00 2010
    Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_652.trc:
    ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []
    Mon Jun 07 09:36:08 2010
    Restarting dead background process MMON
    MMON started with pid=11, OS id=656
    Mon Jun 07 09:36:11 2010
    Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_656.trc:
    ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []
    Mon Jun 07 09:36:15 2010
    Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_656.trc:
    ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []
    Mon Jun 07 09:41:12 2010
    Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_656.trc:
    ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []
    Mon Jun 07 09:41:16 2010
    Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_656.trc:
    ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []
    Mon Jun 07 09:46:13 2010
    Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_656.trc:
    ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []
    Mon Jun 07 09:46:17 2010
    Errors in file d:\oracle\product\10.2.0\admin\mir\bdump\mir_mmon_656.trc:
    ORA-00600: internal error code, arguments: [kjhn_post_ha_alert0-862], [], [], [], [], [], [], []
    Mon Jun 07 09:50:18 2010
    Shutting down instance: further logons disabled
    Mon Jun 07 09:50:19 2010
    Stopping background process QMNC
    Mon Jun 07 09:50:19 2010
    Stopping background process CJQ0
    Mon Jun 07 09:50:20 2010
    Stopping background process MMNL
    Mon Jun 07 09:50:21 2010
    Stopping background process MMON
    Mon Jun 07 09:50:22 2010
    Shutting down instance (immediate)
    License high water mark = 4
    Mon Jun 07 09:50:22 2010
    Stopping Job queue slave processes, flags = 7
    Mon Jun 07 09:50:22 2010
    Job queue slave processes stopped
    Waiting for dispatcher 'D000' to shutdown
    All dispatchers and shared servers shutdown
    Mon Jun 07 09:50:23 2010
    alter database close normal
    Mon Jun 07 09:50:23 2010
    SMON: disabling tx recovery
    SMON: disabling cache recovery
    Mon Jun 07 09:50:23 2010
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Thread 1 closed at log sequence 71
    Successful close of redo thread 1
    Mon Jun 07 09:50:23 2010
    Completed: alter database close normal
    Mon Jun 07 09:50:23 2010
    alter database dismount
    Completed: alter database dismount
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    But I am not able to understand anything above of this.
    And I am sorry we dont have the metalink support or srs support.
    Is there any other way to resolve this issue.
    Shiyas

  • Process m001 died, see its trace file

    Hi
    Kindly tell why process died & look at the trace file
    Process m001 died, see its trace file
    Thu Dec 28 14:30:53 2006
    ksvcreate: Process(m001) creation failed
    ORACLE V10.2.0.1.0 - Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    Windows 2000 Version V5.0 Service Pack 3
    CPU : 4 - type 586
    Process Affinity : 0x00000000
    Memory (Avail/Total): Ph:443M/2047M, Ph+PgF:3071M/4967M, VA:1572M/2047M
    Instance name: xxxx
    Redo thread mounted by this instance: 1
    Oracle process number: 11
    Windows thread id: 4712, image: ORACLE.EXE (MMON)
    *** SERVICE NAME:(SYS$BACKGROUND) 2006-12-26 18:31:12.750
    *** SESSION ID:(29.1) 2006-12-26 18:31:12.750
    *** 2006-12-26 18:31:12.750
    Process m001 is dead (pid=5516, state=3):
    *** 2006-12-27 15:30:13.421
    Process m001 is dead (pid=6128, state=3):
    *** 2006-12-27 16:31:07.359
    Process m001 is dead (pid=5572, state=3):
    *** 2006-12-28 14:30:53.312
    Process m001 is dead (pid=5792, state=3):

    According to
    KSVCREATE: PROCESS(M000) CREATION FAILED' MESSAGES IN ALERT LOG
         Doc ID:      Note:352388.1      Type:      PROBLEM
         Last Revision Date:      14-SEP-2006      Status:      PUBLISHED
    you should increase the PROCESSES parameter of your database instance.

  • Enabling trace file in Debug mode

    Hi all
    how to enable the trace file in debug mode,...
    can any one help me in this,...

    Hi,
    answered in your second thread on this. *g
    Regards,
    Heike

  • Unable to start the database(Process m000 died, see its trace file)

    Hi,
    Oracle Version:10.2.0.1
    Operating System:Linux
    Hi suddenly the database went down and in alert logfile it is showing error like this.
    Fri Feb 18 01:40:51 2011
    Process m000 died, see its trace file
    Fri Feb 18 01:40:51 2011
    ksvcreate: Process(m000) creation failed
    Fri Feb 18 01:41:18 2011
    Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_ora_15998.trc:
    ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
    Fri Feb 18 01:41:19 2011
    Process m000 died, see its trace file
    Fri Feb 18 01:41:19 2011
    ksvcreate: Process(m000) creation failed
    Fri Feb 18 01:42:19 2011
    Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_ora_16032.trc:
    ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
    Fri Feb 18 01:42:20 2011
    Process m000 died, see its trace file
    Fri Feb 18 01:42:20 2011
    ksvcreate: Process(m000) creation failed
    Fri Feb 18 01:43:20 2011
    Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_ora_16036.trc:
    ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
    Fri Feb 18 01:43:21 2011
    Process m000 died, see its trace file
    Fri Feb 18 01:43:21 2011
    ksvcreate: Process(m000) creation failed
    Fri Feb 18 01:44:21 2011
    Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_ora_16042.trc:
    ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
    Fri Feb 18 01:44:22 2011
    Process m000 died, see its trace file
    Fri Feb 18 01:44:22 2011
    ksvcreate: Process(m000) creation failedand generating lot of trace files.
    Please help me how to solve this .
    Thanks & Regards,
    Poorna Prasad.

    In my alert log file I also find this error.
    ed Feb 16 06:11:13 2011
    Process J000 died, see its trace file
    Wed Feb 16 06:11:13 2011
    kkjcre1p: unable to spawn jobq slave process
    Wed Feb 16 06:11:13 2011
    Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_cjq0_26196.trc:
    Wed Feb 16 06:11:13 2011
    Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_j000_4172.trc:
    ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
    Wed Feb 16 06:11:14 2011
    Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_j000_4172.trc:
    ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
    Process J000 died, see its trace file
    Wed Feb 16 06:11:14 2011
    kkjcre1p: unable to spawn jobq slave process
    Wed Feb 16 06:11:14 2011
    Errors in file /u01/app/oracle/admin/apdtest/bdump/apdtest_cjq0_26196.trc:Thanks & Regards,
    Poorna Prasad.S

  • Process m000 died, see its trace file

    Oracle keeps crashing. When i look at the log, i'm seeing Process m000 died, see its trace file. In the trace file, i see the following error message.
    Process m000 is dead (pid=20243, state=3):
    Unable to schedule a MMON slave at: Auto Flush Main 1
    Attempt to create slave process failed.
    Can happen for several reasons:
    - No process state objects
    - Reached OS set limits
    - A shutdown was going on
    Check alert log for more details.
    Does anyone know what is causing this? We are currently running Oracle 10.2.0.4 on solaris 10.

    Metalink note : 458981.1
    Unable to Schedule a MMON Slave Message in Trace File After Enable/Disable Restricted Session
    Bug 3599698 - ENABLE RESTRICTED SESSION/IMPORT/DISABLE RESTRICTED SESSION GENERATES TRACE
    -Anantha

  • Process J000 died, see its trace file

    os：centos5.4 64
    db：oracle 11.2.0.3
    alert日志中经常出现以下告警（有时候1分钟报好几次）：
    Process m000 died, see its trace file
    Process J000 died, see its trace file :
    kkjcre1p: unable to spawn jobq slave process
    Errors in file 。。。。
    SQL> show parameter job
    NAME TYPE VALUE
    job_queue_processes integer 1000
    SQL> show parameter parallel_max_servers
    NAME TYPE VALUE
    parallel_max_servers integer 320

    谢谢您的回复。
    数据库异常时间是 11月1号早上9点10分左右。
    alert发您邮箱了[email protected]。
    trace里面没看到内容。
    tmpfs 21G 13G 8.1G 62% /dev/shm
    物理内存 24G
    swap 4G
    memory_max_target 20G
    memory_target 20G
    sga_max_size 20G
    不知道我这样的内存分配，会不会合理呢？
    帖子经 961972编辑过

  • Claim lock for dead process  in a trace file

    Has anyone seen messages like this in a trace file?
    Any clues on whats causing it?
    claim lock for dead process][lp 0x39dc41d50][p 0x39e626f70.7242][hist x49514951]
    [claim lock for dead process][lp 0x39de15308][p 0x39e626aa0.7179][hist
    x49514951]
    [claim lock for dead process][lp 0x39de15068][p 0x39e626aa0.7179][hist
    x49514951]
    [claim lock for dead process][lp 0x39dc41c00][p 0x39e626f70.7242][hist
    x49514951]
    [claim lock for dead process][lp 0x39de0f908][p 0x39e626aa0.7179][hist
    x49514951]
    *

    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    PL/SQL Release 10.2.0.4.0 - Production
    CORE 10.2.0.4.0 Production
    TNS for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Productio
    NLSRTL Version 10.2.0.4.0 - Production

  • Get blocker from the (self) deadlock trace file

    Hi,
    Recently I had an issue on a 10.2.0.4 single instance database where deadlocks were occurring. The following test case reproduces the problem (I create three parent tables, one child table with indexed foreign keys to all three parent tables and a procedure which performs an insert into the child table in an autonomous transaction):
    create table parent_1(id number primary key);
    create table parent_2(id number primary key);
    create table parent_3(id number primary key);
    create table child( id_c number primary key,
                       id_p1 number,
                       id_p2 number,
                       id_p3 number,
                       constraint fk_id_p1 foreign key (id_p1) references parent_1(id),
                       constraint fk_id_p2 foreign key (id_p2) references parent_2(id),
                       constraint fk_id_p3 foreign key (id_p3) references parent_3(id)
    create index i_id_p1 on child(id_p1);
    create index i_id_p2 on child(id_p2);
    create index i_id_p3 on child(id_p3);
    create or replace procedure insert_into_child as
    pragma autonomous_transaction;
    begin
      insert into child(id_c, id_p1, id_p2, id_p3) values(1,1,1,1);
      commit;
    end;
    insert into parent_1 values(1);
    insert into parent_2 values(1);
    commit;And now the action that causes the deadlock:
    SQL> insert into parent_3 values(1);
    1 row created.
    SQL> exec insert_into_child;
    BEGIN insert_into_child; END;
    ERROR at line 1:
    ORA-00060: deadlock detected while waiting for resource
    ORA-06512: at "SCOTT.INSERT_INTO_CHILD", line 4
    ORA-06512: at line 1My question is: how can I determine which table the insert into CHILD was waiting on? It could be waiting on PARENT_1, PARENT_2, PARENT_3, a combination of them or even on CHILD if I tried to insert a duplicate primary key in CHILD. Since we have the full testcase we know that it was waiting on PARENT_3 (or better said, it was waiting for the "parent" transaction to perform a commit/rollback), but is it possible to determine that solely from the deadlock trace file? I'm asking that because to pinpoint the problem I had to perform redo log mining, pl/sql tracing with DBMS_TRACE and manual debugging on a clone of the production database which was restored to a SCN just before the deadlock occurred. So, I had to do quite a lot of work to get to the blocker table and if this information is already in the deadlock trace file, it would have saved me a lot of time.
    Below is the deadlock trace file. From the "DML LOCK" part I guess that the child table (tab=227042) holds a mode 3 lock (SX), all the other three parent tables have mode 2 locks (SS), but from this extract I can't see that parent_3 (tab=227040) is blocking the insert into child:
    Deadlock graph:
                           ---------Blocker(s)--------  ---------Waiter(s)---------
    Resource Name          process session holds waits  process session holds waits
    TX-00070029-00749150        23     476     X             23     476           S
    session 476: DID 0001-0017-00000003     session 476: DID 0001-0017-00000003
    Rows waited on:
    Session 476: obj - rowid = 000376E2 - AAA3biAAEAAA4BwAAA
      (dictionary objn - 227042, file - 4, block - 229488, slot - 0)
    Information on the OTHER waiting sessions:
    End of information on OTHER waiting sessions.
    Current SQL statement for this session:
    INSERT INTO CHILD(ID_C, ID_P1, ID_P2, ID_P3) VALUES(1,1,1,1)
    ----- PL/SQL Call Stack -----
      object      line  object
      handle    number  name
    3989eef50         4  procedure SCOTT.INSERT_INTO_CHILD
    391f3d870         1  anonymous block
            SO: 397691978, type: 36, owner: 39686af98, flag: INIT/-/-/0x00
            DML LOCK: tab=227042 flg=11 chi=0
                      his[0]: mod=3 spn=35288
            (enqueue) TM-000376E2-00000000  DID: 0001-0017-00000003
            lv: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  res_flag: 0x6
            res: 0x398341fe8, mode: SX, lock_flag: 0x0
            own: 0x3980df420, sess: 0x3980df420, proc: 0x39859c660, prv: 0x398341ff8
            SO: 397691878, type: 36, owner: 39686af98, flag: INIT/-/-/0x00
            DML LOCK: tab=227040 flg=11 chi=0
                      his[0]: mod=2 spn=35288
            (enqueue) TM-000376E0-00000000  DID: 0001-0017-00000003
            lv: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  res_flag: 0x6
            res: 0x3983386e8, mode: SS, lock_flag: 0x0
            own: 0x3980df420, sess: 0x3980df420, proc: 0x39859c660, prv: 0x3983386f8
            SO: 397691778, type: 36, owner: 39686af98, flag: INIT/-/-/0x00
            DML LOCK: tab=227038 flg=11 chi=0
                      his[0]: mod=2 spn=35288
            (enqueue) TM-000376DE-00000000  DID: 0001-0017-00000003
            lv: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  res_flag: 0x6
            res: 0x398340f58, mode: SS, lock_flag: 0x0
            own: 0x3980df420, sess: 0x3980df420, proc: 0x39859c660, prv: 0x398340f68
            SO: 397691678, type: 36, owner: 39686af98, flag: INIT/-/-/0x00
            DML LOCK: tab=227036 flg=11 chi=0
                      his[0]: mod=2 spn=35288
            (enqueue) TM-000376DC-00000000  DID: 0001-0017-00000003
            lv: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  res_flag: 0x6
            res: 0x39833f358, mode: SS, lock_flag: 0x0
            own: 0x3980df420, sess: 0x3980df420, proc: 0x39859c660, prv: 0x39833f368
          ----------------------------------------Thank you in advance for any comments,
    Jure

    Hi Jonathan,
    thank you very much for your reply which more than answers my question. I think it actually clears a lot of doubts I had about TX locks, since your mentioning of "undo segment header transaction table" pointed me in the right direction for further research on this topic (honestly, I didn't know what's "behind" TX locks). So if I understood correctly, to determine which table is the blocker (in the testcase presented above), you have to have some kind of history of executed SQL statements (e.g. by mining redo logs)?
    The statement you wrote:
    At this point, and with your example, the waiting session is waiting on a TX (transaction) lock - this means it has not idea (and no interest) in the actual data involved, it is merely waiting for an undo segment header transaction table slot to clear. and the example with the savepoint you gave, made me think of some of the consequences of that behaviour. That is probably the reason why it is not possible to get the "blocker" table from v$lock (although sometimes it's possible to get it from v$session.row_wait_obj#) when a session tries to change a row another session holds in exclusive mode, e.g.:
    create table t1 (id number);
    insert into t1 values (1);
    commit;
    Session 126:
    SID = 126> update t1 set id=2 where id=1;
    1 row updated.
    Session 146:
    SID = 146> update t1 set id=2 where id=1;
    {session hangs}
    In a separate session:
    SQL> SELECT   CASE
      2                  WHEN TYPE = 'TM'
      3                     THEN (SELECT object_name
      4                             FROM user_objects
      5                            WHERE object_id = l.id1)
      6               END object_name,
      7                  SID, TYPE, id1, id2, lmode, request, BLOCK
      8          FROM v$lock l
      9         WHERE SID IN (126, 146)
    10     ORDER BY SID, TYPE, 1
    11  /
    OBJECT_NAME    SID TY        ID1        ID2      LMODE    REQUEST      BLOCK
    T1             126 TM      68447          0          3          0          0
                   126 TX     262153       4669          6          0          1
    T1             146 TM      68447          0          3          0          0
                   146 TX     262153       4669          0          6          0The only thing I can tell from this output is that session 146 is trying to get a TX lock in exclusive mode, and session 126 is blocking it, the reason of the blocking being unknown from this view alone.
    Since I'd like to get a better understanding on the mechanics behind this (e.g. why the blocked session can't know the segment that is waiting for, since it has to go to the same segment's data block to find the address of the undo segment header transaction table slot? ; can we get the content/structure of the transaction table in the data block - probably by making a block dump?), do you have any source where a more in depth explanation what happens "behind the scenes" is available (perhaps in Oracle Core?)? Some time ago I found a link on your blog http://jonathanlewis.wordpress.com/2010/06/21/locks/ which points to Franck Pachot's article where he nicely explains the various locking modes: http://knol.google.com/k/oracle-table-lock-modes#. There I also found Kyle Hailey's presentation about locks http://www.perfvision.com/papers/09_enqueues.ppt where slide 23 nicely depicts what's going on when acquiring TX locks. Of course I'll try to search on my own, but any other source (especially from an authority like you) is more than welcome.
    Thank you again and regards,
    Jure

  • Error in trace file

    Following is getting created in D:\Oracle\Ora81\DATABASE folder once or twice a month. I do not see any error entries in db1alrt.log. Please help to find out the problem.
    Thanks,
    Anil
    Dump file .\ORA05244.TRC
    Sun May 01 21:30:07 2005
    ORACLE V8.1.5.0.0 - Production vsnsta=0
    vsnsql=d vsnxtr=3
    Windows NT V5.2, OS V14.206, CPU type 586
    Oracle8i Release 8.1.5.0.0 - Production
    With the Java option
    PL/SQL Release 8.1.5.0.0 - Production
    Windows NT V5.2, OS V14.206, CPU type 586
    Instance name: db1
    Redo thread mounted by this instance: 0 <none>
    Oracle process number: 0
    5244
    *** 2005.05.01.21.30.07.127
    ksedmp: internal or fatal error
    ORA-00600: internal error code, arguments: [508], [163], [0], [1413697536], [1], [0], [], []
    Current SQL information unavailable - no session.
    ----- Call Stack Trace -----
    calling call entry argument values in hex
    location type point (? means dubious value)
    ksedmp+a5                       CALLrel  ksedst+0
    75BE3F8
    ksfdmp+e                        CALLrel  ksedmp+0 3
    _kgeriv+95                       CALLreg  00000000                        
    ED16A08
    3
    kgeasi+67                       CALLrel  kgeriv+0
    1E440
    0 1FC
    5
    675BE570
    kslwte+11a                      CALLrel  kgeasi+0
    ED16A08
    0 1FC
    2 5 0
    A3 0
    0 0
    54435000
    0 1 0
    0
    opikndf2+537                    CALLrel  kslwte+0 A3
    54435000
    1 0
    _opitsk+3da                      CALLreg  00000000                        
    ED193E4
    2
    675BF544
    1 0
    opiino+50c                      CALLrel  opitsk+0 0
    _opiodr+4ce                      CALLreg  00000000                         3C 4
    675BFBF8
    opidrv+380                      CALLrel  opiodr+0 3C 4
    675BFBF8
    0
    sou2o+19                        CALLrel  opidrv+0
    opimai+110                      CALLrel  sou2o+0
    OracleThreadStart@4+48c         CALLrel  opimai+0 2
    675BFE78
    77E4A98D CALLreg 00000000
    ----- Argument/Register Address Dump -----
    Argument/Register addr=675be3f8. Dump of memory from 0x675BE3B8 to 0x675BE4F8
    675BE3A0 00000000 00000003
    675BE3C0 E8D60800 6552211C 00000033 00000000 FFFFFFFD 00000048 00000000 00000000
    675BE3E0 00000000 00000000 0000001D 2ED16888 675BE408 00418404 00C936B4 00C936B4
    675BE400 00C936D4 00C936B4 00C936B4 00C936B4 00C936BC 00C936B4 00C936BC 00C936B4
    675BE420 00C936B4 00C936B4 00C936B4 00C936BC 675BE4E0 004191E0 675BE444 0000001C
    675BE440 00000000 2A2A2A0A 30303220 35302E35 2E31302E 332E3132 37302E30 32332D25
    675BE460 2D252073 25207338 7332332D 675F0020 00000000 00000001 000007D5 35373620
    675BE480 37454642 25200038 7332332D 342D2520 00000A73 00000003 65522178 00000033
    675BE4A0 00000000 2ED16888 01218A97 00000000 00000000 00000000 675BFFEC 00000000
    675BE4C0 675BFE78 00000000 00000001 00000001 00000000 675BDDD0 00000009 675BE504
    *** Trace file full ***

    you have what one session wants the other session has what you want; neither will give it up and so Oracle detects this and kicks one out. If you trace your SQL and COMMIT logic you will find the problem

  • Ubormal trace file generation in 11.1.0.7

    oracle version
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
    PL/SQL Release 11.1.0.7.0 - Production
    CORE 11.1.0.7.0 Production
    TNS for 64-bit Windows: Version 11.1.0.7.0 - Production
    NLSRTL Version 11.1.0.7.0 - Production
    OS
    Windows 2008 EE R1 SP2
    Problem
    My trace files generated every 30 second and its drive me crazy i have to delete to maintain space of the server
    i check the alert logfile and it does not show anything suspecious here are a couple of lines from the alert.log file
    Sat Jan 22 00:16:52 2011
    Thread 1 advanced to log sequence 117 (LGWR switch)
    Current log# 1 seq# 117 mem# 0: E:\DATA\ORACLE\PMDB\REDO01A.LOG
    Current log# 1 seq# 117 mem# 1: E:\DATA\ORACLE\PMDB\REDO01B.LOG
    Sat Jan 22 02:00:00 2011
    Clearing Resource Manager plan via parameter
    Sat Jan 22 06:00:00 2011
    Setting Resource Manager plan SCHEDULER[0x2C49]:DEFAULT_MAINTENANCE_PLAN via scheduler window
    Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
    Sat Jan 22 06:00:03 2011
    Begin automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
    End automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
    Sat Jan 22 06:00:36 2011
    Thread 1 advanced to log sequence 118 (LGWR switch)
    Current log# 2 seq# 118 mem# 0: E:\DATA\ORACLE\name\REDO02A.LOG
    Current log# 2 seq# 118 mem# 1: E:\DATA\ORACLE\nameREDO02B.LOG
    Sat Jan 22 11:09:15 2011
    Thread 1 advanced to log sequence 119 (LGWR switch)
    Current log# 1 seq# 119 mem# 0: E:\DATA\ORACLE\name\REDO01A.LOG
    Current log# 1 seq# 119 mem# 1: E:\DATA\ORACLE/name\REDO01B.LOG
    Sat Jan 22 11:37:19 2011
    Thread 1 advanced to log sequence 120 (LGWR switch)
    Current log# 2 seq# 120 mem# 0: E:\DATA\ORACLE\nam\REDO02A.LOG
    Current log# 2 seq# 120 mem# 1: E:\DATA\ORACLE\name\REDO02B.LOG
    And i have cheched the trace files and here are a couple of lines
    *** 2011-01-19 15:23:54.265
    *** SESSION ID:(43.21827) 2011-01-19 15:23:54.265
    *** CLIENT ID:() 2011-01-19 15:23:54.265
    *** SERVICE NAME:(name) 2011-01-19 15:23:54.265
    *** MODULE NAME:(OMS) 2011-01-19 15:23:54.265
    *** ACTION NAME:() 2011-01-19 15:23:54.265
    XS Users and Roles -- OCI Info
    kzxupnamread error -- 942: ORA-00942: table or view does not exist
    XS Users and Roles -- OCI Info
    kzxupnamread error -- 942: ORA-00942: table or view does not exist
    Trace file e:\app\oracle\diag\rdbms\pmdb\pmdb\trace\pmdb_ora_7688.trc
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Windows NT Version V6.0 Service Pack 2
    CPU : 16 - type 8664, 8 Physical Cores
    Process Affinity : 0x0000000000000000
    Memory (Avail/Total): Ph:8575M/16372M, Ph+PgF:24932M/32827M
    Instance name: name
    Redo thread mounted by this instance: 1
    Oracle process number: 18
    Windows thread id: 7688, image: ORACLE.EXE (SHAD)
    Would you please help me in identifying a solution to this problem

    Thanks everybody ,
    I have communciated to Oracle Support below is their reply :-
    << Based on the Developer comment in the bug, "This belongs to EXTENDED SECURITY and don't have conditions to run, it is addressed in patch 7019661 and solved in 11.2", >>
    i have to test the patch in the test environment and than i will do it in Live
    Thank you again

Maybe you are looking for

  • Strange SaveAs dialog in Leopard Mail 3.6

    This is the craziest thing, I've never seen this before. Normally when I save a message or attachment in Mail, the Save As dialog rolls down and when I look at it in list view, I see two columns headings, Name and Date Modified. Starting this morning

  • Mac Book Pro Shuts down on Battery Power

    First, I apologize to everyone for asking this question yet again. I have gone through the previous posts and I am still at a loss. So thank you for your patience and help. When I run my MacBook pro on battery power it will run for around 15 - 20 min

  • How to Install Solaris for Intel so that it boots off from a boot floppy?

    Hi all, Sorry to bother you with this one (I went through all documentations/manuals and could not find straight answers to following specific questions): I have one hard drive with 1st partition used by Windows XP and a second partition that's a bla

  • VAR report for switzerland

    Hello All, We need to configure the VAR report for switzerland to satify the legal reporting on foreign trade.( SAP provides this through VE21 and VE22). Can anyone help us with the basic configuration requirements? In the standard report, there are

  • Navbar disappears from welcome page

    when I publish to an external server I lose the navbar with the links at the top of the page. So my multi page site become just a one page welcome page. I'm not a coder and am something of a complete idiot, but if you go to eddysbistro.com you will s