what happens in the single-task message?
- From: "Martin Busik" <martin.busik@xxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 2 Dec 2008 11:20:51 +0100
Hello list,
I'm observing quite a lot of similiar entries in a 10046 (level 8) trace
file
created on a 8.1.7.4 running under AIX:
INSERT INTO verguetung ( verg_at, verg_basis, verg_basis2,
verg_eb, verg_eb2, verg_f_ksa, verg_f_wae, verg_kto,
verg_my, verg_oa, verg_s_, verg_sort, verg_splitting,
verg_vnr, verg_bem )
VALUES
( :1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11, :12, :13, :14, :15 )
call count cpu elapsed disk query current
rows
------- ------ -------- ---------- ---------- ---------- ----------
----------
Parse 1 0.02 0.19 0 7 0
0
Execute 1 0.09 5.85 1 4 9
1
Fetch 0 0.00 0.00 0 0 0
0
------- ------ -------- ---------- ---------- ---------- ----------
----------
total 2 0.11 6.04 1 11 9
1
Misses in library cache during parse: 1
Optimizer goal: RULE
Parsing user id: 41
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total
Waited
---------------------------------------- Waited ----------
------------
single-task message 2 5.19
6.05
SQL*Net message from client 3 0.01
0.01
SQL*Net message to client 1 0.00
0.00
****************************************************************************
****
There is one primary key index, two other indexes (not unique)
and a context index on the column verg_bem.
Are there any changes to find out what is causing the system to spend 6
seconds in
the single-task message?
Thx in advance,
Martin
--
//www.freelists.org/webpage/oracle-l
Other related posts:
