Trace file d:\app\administrator\diag\rdbms\orcl\orcl\trace\cdmp_20250615060010\orcl_vktm_3644_bucket.trc Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options Windows NT Version V6.2 CPU : 32 - type 8664, 16 Physical Cores Process Affinity : 0x0x0000000000000000 Memory (Avail/Total): Ph:36659M/63366M, Ph+PgF:43119M/72582M Instance name: orcl Redo thread mounted by this instance: 1 Oracle process number: 3 Windows thread id: 3644, image: ORACLE.EXE (VKTM) *** 2025-06-15 06:00:10.687 *** SESSION ID:(25.1) 2025-06-15 06:00:10.687 *** 2025-06-15 06:00:10.687 Process diagnostic dump for ORACLE.EXE (VKTM), OS id=3644, pid: 3, proc_ser: 1, sid: 25, sess_ser: 1 ------------------------------------------------------------------------------- current sql: Current Wait Stack: 0: waiting for 'VKTM Logical Idle Wait' =0x0, =0x0, =0x0 wait_id=0 seq_num=1 snap_id=1 wait times: snap=120631 min 25 sec, exc=120631 min 25 sec, total=120631 min 25 sec wait times: max=infinite, heur=120631 min 25 sec wait counts: calls=0 os=0 in_wait=1 iflags=0x5a0 Wait State: fixed_waits=0 flags=0x22 boundary=0x0000000000000000/-1 Session Wait History: elapsed time of 0.000000 sec since current wait Sampled Session History of session 25 serial 1 --------------------------------------------------- The sampled session history is constructed by sampling the target session every 1 second. The sampling process captures at each sample if the session is in a non-idle wait, an idle wait, or not in a wait. If the session is in a non-idle wait then one interval is shown for all the samples the session was in the same non-idle wait. If the session is in an idle wait or not in a wait for consecutive samples then one interval is shown for all the consecutive samples. Though we display these consecutive samples in a single interval the session may NOT be continuously idle or not in a wait (the sampling process does not know). The history is displayed in reverse chronological order. sample interval: 1 sec, max history 120 sec --------------------------------------------------- [121 samples, 05:58:10 - 06:00:10] idle wait at each sample ------------------------------------------------------------------------------- Process diagnostic dump actual duration=0.000000 sec (max dump time=30.000000 sec) *** 2025-06-15 06:00:10.687 ------------------------------------------------------------------------------- Trace Bucket Dump Begin: default bucket for process 3 (osid: 3644, VKTM) TIME(*=approx):SEQ:COMPONENT:FILE@LINE:FUNCTION:SECT/DUMP: [EVENT#:PID:SID] DATA ------------------------------------------------------------------------------- 2025-03-23 11:26:15.374268 :8000000D:db_trace:kst.c@673:kstipg(): [10280:3:0] kst: process state object created on 03-23 11:26:15.373 2025-03-23 11:26:15.374269 :8000000E:db_trace:kst.c@679:kstipg(): [10280:3:0] kst: process info: ospid=3644 pso_num=3 pso_serial#=1 2025-03-23 11:26:15.374318 :8000000F:db_trace:kso.c@4093:ksonfy(): [10420:3:0] kso: new process: pid=3644 osp_idx=2 osp_ver=0 osp_pg=0 (spawn #1) 2025-03-23 11:26:15.374318 :80000010:db_trace:kso.c@4099:ksonfy(): [10420:3:0] kso: new process: first_req_pid=2688 spawner_pid=2688 sga_crt_ts=x8A8A 2025-03-23 11:26:15.374318 :80000011:db_trace:kso.c@4103:ksonfy(): [10420:3:0] kso: new process: pso_index=3 reservation=1 time=35406 2025-03-23 11:26:15.374319 :80000012:db_trace:kso.c@4109:ksonfy(): [10420:3:0] kso: spawn diagnostics: queue time=0 secs 2025-03-23 11:26:15.374319 :80000013:db_trace:kso.c@4111:ksonfy(): [10420:3:0] kso: spawn diagnostics: fork time=0 secs 2025-03-23 11:26:15.374319 :80000014:db_trace:kso.c@4113:ksonfy(): [10420:3:0] kso: spawn diagnostics: exec time=0 secs 2025-03-23 11:26:15.374319 :80000015:db_trace:kso.c@4115:ksonfy(): [10420:3:0] kso: spawn diagnostics: pre dbkc time=0 secs 2025-03-23 11:26:15.374319 :80000016:db_trace:kso.c@4117:ksonfy(): [10420:3:0] kso: spawn diagnostics: post dbkc time=0 secs 2025-03-23 11:26:15.374356 :80000017:db_trace:ksl2.c@14083:ksl_update_post_stats(): [10005:3:0] KSL POST SENT postee=149 loc='kso2.h LINE:416 ID:ksoreq_reply' id1=0 id2=0 name= type=0 2025-03-23 11:26:15.374358 :80000018:db_trace:kso.c@5554:kso_spawn_diag_end(): [10420:3:0] kso: spawn diagnostics: init time=0 secs ------------------------------------------------------------------------------- Trace Bucket Dump End: default bucket for process 3 (osid: 3644, VKTM)