Virtual circuit wait on XDB
Hello,
I'm facing a problem, I can't get behind...
I've created a PL/SQL Package that generates a HTML page with the package procedure "HTP.PRN" in a Ora11gR2 DB.
Everything works fine. A client with IE or Firefox can access the HTML page without any problem by calling url
http://<db-servername>:8080/<DAD>/<Package_Name>.<Procedure_Name>
But when a second client tries to call the same page, it has to wait for approx a minute until the page will be shown in the browser.
During this time, I can see in dbconsole, that there is a massive peak for "virtual circuit wait" events. After loading the page in IE
"virtual circuit waits" run against zero again.
I've tested this now on ORA 11GR2 on a Windows and a Linux box. On both machines, there is the same behavior.
The listener.ora looks like this (on Windows box):
# listener.ora Network Configuration File: D:\oracle\product\11.2.0\JAAP\network\admin\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = CLRExtProc)
(ORACLE_HOME = D:\oracle\product\11.2.0\JAAP)
(PROGRAM = extproc)
(ENVS = "EXTPROC_DLLS=ONLY:D:\oracle\product\11.2.0\JAAP\bin\oraclr11.dll")
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = rrottlaender02.seepex.local)(PORT = 1521))
ADR_BASE_LISTENER = D:\oracle
Any hint, showing me the rigth direction, would be great!
Thank you in advance...
Ciao,
Roland
Increase the amount of SHARED SERVERS via an ALTER SYSTEM statement
SQL> show user
SYS
SQL> alter system set shared_servers=5 scope=both;
Similar Messages
-
High virtual circuit wait event
Hi,
in my 11g Enterprise Edition Database I have a problem with some sessions that are almost always in virtual circuit wait event. What is this wait event and how can I troubleshoot it?
IMPORTANT: I'm not using XDB or APEX
Edited by: Insaponata on Jan 9, 2011 8:00 AMFrom awr report based on the last our of work I see:
Top 5 Timed Foreground Events
Event Waits Time(s) Avg wait (ms) % DB time Wait Class
virtual circuit wait 95,038 16,056 169 263.91 Network
DB CPU 305 5.02
SQL*Net message from dblink 42,432 48 1 0.79 Network
db file sequential read 21,990 48 2 0.78 User I/O
db file scattered read 26,021 36 1 0.59 User I/O
Do you think that this situation is normal? If no, how can I troubleshoot? -
Wait event "virtual circuit wait" in wait class "Network" was consuming sig
Hello,
We are facing this problem when there are 2 queries try to run at the same time.
The first query takes longer to finish so 2nd has to wait for 1st to be finished and then only 2nd starts. It seems the jam is at netowork instead of server.
I want to make sure before I start testing on network.
I get following :
Wait event "virtual circuit wait" in wait class "Network" was consuming significant database time. 98.4
Wait class "Network" was consuming significant database time.
and recommendations is stated as :
Investigate the cause for high "virtual circuit wait" waits with P1 ("circuit#") value "21" and P2 ("type") value "2".
I am checking OEM.
Thanks,
Shashi.Hello Sybrand,
Can you suggest some changes to be done to test ?
Here is my shared server config :
SQL> show parameter SHARED
NAME TYPE VALUE
hi_shared_memory_address integer 0
max_shared_servers integer
shared_memory_address integer 0
shared_pool_reserved_size big integer 135895449
shared_pool_size big integer 0
shared_server_sessions integer
shared_servers integer 1
Thanks,
Shashi. -
Hii All..
I am seeing the following wait in the result of the query.Have you any idea what is the reason of the wait ?
SELECT event, total_waits, time_waited_micro
FROM v$system_event
WHERE wait_class <> 'Idle' order by 3 desc
result is
EVENT TOTAL_WAITS TIME_WAITED_MICRO
1 virtual circuit wait 588966 241791462220
2 SQL*Net more data from client 433132 78999049842
3 direct path read 7570504 22167783009
4 db file sequential read 10187059 18516379084
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production on AIX 5.3 ML 10Hii..
In the metalink note ID 6653834.8
This is a performance monitoring enhancement to split the
'virtual circuit status' wait event into two new
wait events:
"shared server idle wait" - for when the shared server is
idle waiting for something to do
"virtual circuit wait" - for when the shared server is
blocked waiting on a specific
circuit / message
The wait "virtual circuit status" no longer exist with this fix. -
What does the event "virtual circuit wait" mean?
Hi all !
Can anyone tell me about this event? Yesterday I checked my ASH table and found that most of the time database spends on are 2 "non-idle" events: "db file sequential read" and "virtual circuit wait". I did not find any information about the second event on Metalink or in Documentation. Do i need to pay my attention to this event? DB is 11g on HP-UX.
Thanks in advance!The Oracle Reference has descriptions of wait events:
[Virtual Circuit Wait|http://download.oracle.com/docs/cd/E11882_01/server.112/e10820/waitevents003.htm#BABBCJEF]
The session waits for a virtual circuit operation to complete.Wait Time: 30 seconds
Parameter Description
circuit# Indicates the virtual circuit# being waited on
type Indicates the type of operation the session is waiting for -
"EMPTY" Virtual Circuits causes the dispatcher proces D000 use 100% CPU
(29th April)
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Apr 29 14:59:56 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Data Mining and Real Application Testing options
Could someone please indicates why the D000 process uses 100% cpu while no XDB action seems to be running? Whe are not using shared server (besides the XML DB usage) and the only value for the dispatcher parameter in the init<SID>.ora = (PROTOCOL=TCP) (SERVICE=<SID>XDB).
update (30th april)
When I lookup the virtual circuits I notice 2 VC without server and waiter address and without session info.
GERE@ARG_DV8>
# SELECT RAWTOHEX(C.CIRCUIT), RAWTOHEX(C.SERVER) SRV, RAWTOHEX(C.WAITER)WTR,
2 D.NAME,
3 S1.NAME,
4 S.SID,
5 S.SERIAL#,
6 C.STATUS,
7 C.QUEUE,
8 C.MESSAGES,
9 C.BYTES
10 FROM V$CIRCUIT C, V$DISPATCHER D, V$SHARED_SERVER S1, V$SESSION S
11 WHERE C.DISPATCHER = D.PADDR(+) AND C.SERVER = S1.PADDR(+) AND
12 C.SADDR = S.SADDR(+)
13 /
CIRCUIT SRV WTR NAME NAME SID SERIAL# STATUS QUEUE MESSAGES BYTES
C0000002398456C0 00 00 D000 NORMAL NONE 6 261
C000000239840DC0 00 00 D000 NORMAL NONE 7 280
2 rows selected.
The SADDR is empty also.
GERE@ARG_DV8>
# SELECT SADDR, CIRCUIT, DISPATCHER, SERVER, SUBSTR(QUEUE,1,8) "QUEUE", WAITER
2 FROM V$CIRCUIT;
SADDR CIRCUIT DISPATCHER SERVER QUEUE WAITER
00 C000000239840DC0 C000000214C05FB8 00 NONE 00
00 C0000002398456C0 C000000214C05FB8 00 NONE 00
2 rows selected.
A lsnrctl services shows 2 current
Service "ARG_DV8XDB" has 1 instance(s).
Instance "ARG_DV8", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:58903 refused:0 current:2 max:2046 state:ready
DISPATCHER <machine: leo, pid: 5672>
(ADDRESS=(PROTOCOL=tcp)(HOST=leo.argenta.be)(PORT=53044))
Stop and start of the listener doesn't solve this problem but killing the unix process will do. When I killed the D000 proces a new dispatcher is started (does pmon do this?) and the current shows 0. This workaround is fine on the DVL machine but no sollution on a production DB :-)
Kind regards,
Rene
Edited by: Rene Geilings on Apr 30, 2009 2:28 AMBy the way... you just could be unlucky hitting a very rare situation that caused the phenomenon decribed by you. Deamon processes also could arise due too standard JDBC, ODBC or other connection methods. As long as you don't provide Oracle Support with a SR, you will not know if it is actually XDB related or not.
If I would implement XDB functionality in a production system than at least I would:
a) disable automatic memory management by setting SGA parameters manually
b) set the large_pool_size to a appropriate value to support the shared server processes
c) tweak dispatcher and shared server processes to match at least values that represent
the minimum++ needed processes (= a higher value then needed maximum)
d) set java_pool size to a decent size (250 Mb or higher)
e) set an appropriate PGA setting to support XML fragment handling
f) DISABLE autoregistering database functionality with the listener
(see amongs others "Registering non-default XMLDB HTTP/WebDAV and FTP ports
on a non-default Oracle Listener port" - http://www.liberidu.com/blog/?p=116)
g) alter the xdbconfig.xml file with more appropiate timeouts, locking and cache handling.
h) dedicate a specific listener (aka a a listener not called "LISTENER") for shared server
connection handling (this for management reasons and specific debugging).
i) use version 10.2.0.4.0 or 11.1.0.7.0 for production environments (I know that this
matches your environment)
j) always enforce that client software matches the database version
(as in your case 10.2.0.4.0)
k) keep NLS settings on client and database equal and support a AL32UTF characterset
(IMHO a minimum requirement on the database side) -
Error 18 creating virtual circuit
I am get the "error 18 creating virtual circuit" it is happening about 10 or 12 times then goes a way. I assume that I am running out of a resource, but which one?
This is on a 9i 9.2.0.4 with the security patches.
-
. " number of virtual circuits" what it means ?
Hi,
Here is the excert from the manual.
"The CIRCUITS parameter sets a maximum limit on the number of virtual circuits that can be created in shared memory."
. " number of virtual circuits" what it means ?
thanks
sivavirtual circuitsConnections (sessions) to database through dispatchers and server processes.
-
SNMP monitoring for EoMPLS virtual circuit
I am looking to implement SNMP-based monitoring of an MPLS layer-2 tunnel. The desired result would be the same as the output from the following command:
"sh mpls l2transport vc"
I have configured the router to generate SNMP traps based on LDP changes, but this is not specific to the status of the EoMPLS tunnel.
Thanks in advance.Polling to these MIB values would have your task accomplished.
1) VC status <--> cpwVcOperStatus
2) If you need outbound staus <--> pwVcInboundOperStatus
3) Inbound status <--> cpwVcOutboundOperStatus
And here is the link for list of MIB objects for L2VPN.
http://www.cisco.com/en/US/products/ps6441/products_configuration_guide_chapter09186a00808194e1.html
HTH-Cheers,
Swaroop -
Too much time on network wait!
At peak time my apex pages are very very slow. I open Home>Utilities>Database Monitor>Sessions>Waits, and see all wait classes are network. I have already changed shared_servers to 100. But all waiting sessions are still waiting for network. How to improve it? Thank you!
John,
it was in the context of a cross-platform 9.2 to 11.1 migration that
we decided to opt for EPG using the APEX bundle integral to the db
packages (thus, we are still running 3.0.1). I think some documents
mentioned certain advantages of this architecture, but meanwhile I
have my doubts ...
To install APEX, we simply followed Note:457621.1 (How to Configure
Oracle Application Express (APEX) & the Embedded PL/SQL Gateway (EPG)
in an 11G DB).
We currently have a SR open for weeks, were it is tried to track down
the reason for those numerous virtual circuit waits, and found that
all sessions emenate from APEX sessions (with various users and
various apps). Thus, it is quite difficult to track down the reason
for those waits.
Is there an easy procedure to switch to Apache instead of EPG?
Regards, Thomas -
Serious heating after Bootcamp installation
Hi,
After I installed Windows using BootCamp, my MBP is getting too heated even when running on Mac. I had the similar issue before on my another MBP laptop. But I could not get it that time that after Windows installation my Mac got corrupted.
Now most of my application is taking too much time to load, and also the CPU and enclosure temperature is unbelievable. Please help me.Fact #1 All Apex forms are stored in a database.
Fact #2 Apex connects as user ANONYMOUS
Fact #3 Apex is essentially a development environment, though the development part can be switched off
Question #1: Did you realize you were installing a development product in a production environment? If so, as your production environment doesn't seem to be able to cope with the load, why did you install it
Fact #4: 'Virtual circuit waits' signify the use of shared server. Do you use the mod_plsql installation of Apex or did you install the Apex listener? Or is the TCP protocol configured for shared server (Mod_plsql uses XDB which runs on shared server)
My suggestion would be either of two choices
1 redirect this question to the Apex forum
2 de-install Apex from your production environment
Personally I would choose option 2.
Sybrand Bakker
Senior Oracle DBA -
We have Oracle 11g (11.1.0.6) on HP-UX environment with CC&B application. It was working fine and after we upgrade the database to 11.1.0.7 last week, since then the database performance is really slow. After we upgrade the database we notice that xdb component became invalid.
We are not sure how to investigate this issue, any help would be appreciated.WORKLOAD REPOSITORY report for
DB Name DB Id Instance Inst Num Startup Time Release RAC
CCBPROD 3218377102 ccbprod 1 10-Jan-12 20:26 11.1.0.7.0 NO
Host Name Platform CPUs Cores Sockets Memory(GB)
huccbhp5 HP-UX IA (64-bit) 4 4 2 23.97
Snap Id Snap Time Sessions Curs/Sess
Begin Snap: 43912 11-Jan-12 10:00:31 157 96.1
End Snap: 43913 11-Jan-12 11:00:35 186 101.3
Elapsed: 60.08 (mins)
DB Time: 653.40 (mins)
Cache Sizes Begin End
~~~~~~~~~~~ ---------- ----------
Buffer Cache: 12,160M 12,096M Std Block Size: 8K
Shared Pool Size: 704M 704M Log Buffer: 58,764K
Load Profile Per Second Per Transaction Per Exec Per Call
~~~~~~~~~~~~ --------------- --------------- ---------- ----------
DB Time(s): 10.9 0.5 0.02 0.02
DB CPU(s): 3.6 0.2 0.01 0.01
Redo size: 529,539.6 24,544.1
Logical reads: 155,545.5 7,209.5
Block changes: 2,047.0 94.9
Physical reads: 204.6 9.5
Physical writes: 96.0 4.5
User calls: 698.7 32.4
Parses: 77.8 3.6
Hard parses: 0.1 0.0
W/A MB processed: 406,873.3 18,858.5
Logons: 0.4 0.0
Executes: 456.1 21.1
Rollbacks: 19.6 0.9
Transactions: 21.6
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 100.00 Redo NoWait %: 99.97
Buffer Hit %: 99.87 In-memory Sort %: 100.00
Library Hit %: 99.93 Soft Parse %: 99.89
Execute to Parse %: 82.95 Latch Hit %: 99.99
Parse CPU to Parse Elapsd %: 0.01 % Non-Parse CPU: 99.93
Shared Pool Statistics Begin End
Memory Usage %: 89.78 90.02
% SQL with executions>1: 86.04 84.87
% Memory for SQL w/exec>1: 86.22 86.03
Top 5 Timed Foreground Events
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Avg
wait % DB
Event Waits Time(s) (ms) time Wait Class
virtual circuit wait 2,170,696 15,761 7 40.2 Network
DB CPU 13,115 33.5
db file sequential read 362,802 6,304 17 16.1 User I/O
enq: TX - row lock contention 115 1,118 9721 2.9 Applicatio
log file sync 8,183 818 100 2.1 Commit
Host CPU (CPUs: 4 Cores: 4 Sockets: 2)
~~~~~~~~ Load Average
Begin End %User %System %WIO %Idle
3.28 3.93 93.1 2.3 2.8 4.6
Instance CPU
~~~~~~~~~~~~
% of total CPU for Instance: 91.1
% of busy CPU for Instance: 95.4
%DB time waiting for CPU - Resource Mgr: 0.0
Memory Statistics
~~~~~~~~~~~~~~~~~ Begin End
Host Mem (MB): 24,545.7 24,545.7
SGA use (MB): 13,312.0 13,312.0
PGA use (MB): 935.9 949.3
% Host Mem used for SGA+PGA: 58.05 58.05 -
How unhealthy is this RAC?
Here's is the contents of v$system_event..
Is this
EVENT TOTAL_WAITS TIME_WAITED AVERAGE_WAIT
enq: TX - index contention 40564851 214701526 5.29
enq: TX - row lock contention 188846 12454614 65.95
enq: SQ - contention 141971 70568 0.5
cause for concern?
EVENT TOTAL_WAITS TIME_WAITED AVERAGE_WAIT
SQL*Net message to client 6015051449 607254 0
SQL*Net message from client 6015048542 178177969892 29.62
gcs remote message 2948555287 2633481757 0.89
CGS wait for IPC msg 1517805027 634397 0
db file sequential read 1500615188 816364485 0.54
ges remote message 1247679701 1407300224 1.13
gc cr multi block request 778432813 9913464 0.01
gc current block 2-way 747852637 38030616 0.05
db file scattered read 709428365 460939295 0.65
rdbms ipc message 708473316 37650068633 53.14
gc buffer busy acquire 671285134 1033621285 1.54
PX Deq: reap credit 667784615 484449 0
gcs log flush sync 592376026 171712257 0.29
gc cr block 2-way 530861847 19607062 0.04
library cache pin 437937120 15126237 0.03
log file sync 379523272 797193932 2.1
DIAG idle wait 359607166 2822108755 7.85
log file parallel write 351225436 259263769 0.74
LNS ASYNC end of log 350170653 1398410516 3.99
LNS wait on SENDREQ 321652621 3209301 0.01
PX qref latch 297396661 94308 0
read by other session 289140108 148440270 0.51
buffer deadlock 163505781 983055 0.01
gc current block busy 119223825 467716658 3.92
PX Deq: Table Q Normal 117332841 23574867 0.2
ksxr poll remote instances 110480324 90333 0
buffer busy waits 106938153 19933900 0.19
direct path read 93429599 108427028 1.16
SQL*Net more data from client 86471785 23026529 0.27
gc current grant busy 84978157 28215346 0.33
control file sequential read 82646297 23694583 0.29
PX Deq Credit: send blkd 78641669 9569299 0.12
latch: cache buffers chains 74218671 690277 0.01
gc current grant 2-way 72557796 1920419 0.03
library cache: mutex X 71106697 75993 0
DFS lock handle 70722498 2716407 0.04
gc cr grant 2-way 64558237 1633004 0.03
PX Deq: Execution Msg 61706261 314222076 5.09
gc cr block busy 61469863 119850802 1.95
library cache lock 52428649 3773354 0.07
PX Deq: Slave Session Stats 48040224 1886805 0.04
db file parallel read 46415188 118467902 2.55
IPC send completion sync 46250594 965101 0.02
enq: TX - index contention 40564851 214701526 5.29
PX Deq: Execute Reply 39689685 17243721 0.43
gc buffer busy release 36976909 242714774 6.56
SQL*Net more data to client 36627952 44167 0
PX Deq: Msg Fragment 30501244 343397 0.01
rdbms ipc reply 29725302 1352370 0.05
RMAN backup & recovery I/O 28824547 37722662 1.31
reliable message 27892263 3082134 0.11
PX Idle Wait 27356097 4651277341 170.03
ASM file metadata operation 25098749 8850323 0.35
gc object scan 22705857 7485 0
db file parallel write 19896252 52152606 2.62
latch: ges resource hash list 19336183 427451 0.02
enq: PS - contention 19143961 707455 0.04
PX Deq: Parse Reply 19093356 895799 0.05
gc cr disk read 17816846 448909 0.03
ASM background timer 16101806 1383957874 85.95
PX Deq: Slave Join Frag 16044789 233149 0.01
wait for unread message on broadcast channel 15056320 1413552546 93.88
cursor: mutex X 13435193 24140 0
KJC: Wait for msg sends to complete 13268497 11397 0
PX Deq: Signal ACK RSG 13214824 101941 0.01
KSV master wait 13206286 4235645 0.32
direct path read temp 12617694 5487608 0.43
PX Deq Credit: need buffer 11675868 879967 0.08
row cache lock 11536185 398216 0.03
PX Deq Credit: Session Stats 9480862 78910 0.01
SQL*Net message to dblink 9312894 1538 0
SQL*Net message from dblink 9312894 6279631 0.67
control file parallel write 7760982 11854435 1.53
pmon timer 7558889 1412576090 186.88
PX Deq: Join ACK 7548816 498931 0.07
gc current multi block request 6035173 155898 0.03
PING 5706961 1413230267 247.63
enq: XR - database force logging 4662671 198813 0.04
class slave wait 4561877 7097429006 1555.81
Streams AQ: waiting for messages in the queue 4495828 1543411682 343.3
SQL*Net more data from dblink 3696582 444575 0.12
LGWR wait for redo copy 3655353 17840 0
log file sequential read 3387305 6610414 1.95
Log archive I/O 2990486 276772 0.09
SQL*Net break/reset to client 2971976 2385935 0.8
direct path write temp 2839390 2522114 0.89
Space Manager: slave idle wait 2827526 1412987186 499.73
latch: shared pool 2808517 298150 0.11
latch: gc element 2421717 24688 0.01
SGA: MMAN sleep for component shrink 2336447 2458094 1.05
latch: enqueue hash chains 2279645 15435 0.01
latch free 2089418 78732 0.04
gc current split 2044784 1864009 0.91
PX Deq: Signal ACK EXT 1976164 19263 0.01
enq: FB - contention 1473469 61036 0.04
cursor: pin S wait on X 1313129 1464789 1.12
SQL*Net more data to dblink 1232891 986 0
Streams AQ: RAC qmn coordinator idle wait 1211300 788 0
enq: HW - contention 1175390 2077008 1.77
latch: session allocation 1167768 21883 0.02
Streams AQ: qmn coordinator idle wait 1144699 1412546634 1233.99
Streams AQ: qmn slave idle wait 1031585 2227183681 2158.99
lock deadlock retry 962937 4698 0
enq: CF - contention 956154 609647 0.64
latch: cache buffers lru chain 902764 37552 0.04
latch: object queue header operation 817911 27717 0.03
global enqueue expand wait 768633 654105 0.85
Data file init write 756191 329758 0.44
latch: gcs resource hash 647021 4147 0.01
local write wait 603007 286191 0.47
latch: row cache objects 599358 6453 0.01
ges lmd/lmses to freeze in rcfg - mrcvr 481759 156345 0.32
shared server idle wait 471190 1413238589 2999.3
enq: RF - DG Broker Current File ID 469833 23209 0.05
smon timer 432383 1411851085 3265.28
SGA: allocation forcing component growth 363333 379008 1.04
gc current retry 341104 1121252 3.29
enq: RF - synch: DG Broker metadata 319143 588290 1.84
enq: PG - contention 313659 14830 0.05
enq: TT - contention 260134 11207172 43.08
enq: KO - fast object checkpoint 236745 820808 3.47
dispatcher timer 236637 1413242481 5972.2
direct path write 231382 191008 0.83
cursor: pin S 229011 394 0
Streams AQ: waiting for time management or cleanup tasks 199981 1413148548 7066.41
enq: TX - row lock contention 188846 12454614 65.95
enq: TX - allocate ITL entry 153703 54252 0.35
enq: SQ - contention 141971 70568 0.5
ksdxexeother 141885 56 0
latch: redo allocation 138912 1858 0.01
recovery area: computing applied logs 126415 45925 0.36
gc current block congested 126318 21768 0.17
resmgr:cpu quantum 123074 151384 1.23
jobq slave wait 120678 35574221 294.79
Datapump dump file I/O 90431 9127 0.1
ges inquiry response 89402 4041 0.05
os thread startup 83809 222586 2.66
cr request retry 80062 71896 0.9
PX Deq: Table Q Sample 79665 133402 1.67
gc cr block congested 79026 14792 0.19
gc cr failure 77521 25019 0.32
enq: WF - contention 73983 825388 11.16
enq: TQ - TM contention 72871 3319 0.05
lock escalate retry 65714 1574 0.02
buffer exterminate 59775 64919 1.09
fbar timer 47136 1413183353 29980.98
log file switch completion 46911 452097 9.64
recovery area: computing obsolete files 45699 8547 0.19
enq: US - contention 40401 8805 0.22
enq: TM - contention 39149 5435032 138.83
library cache load lock 36311 382575 10.54
kjbdrmcvtq lmon drm quiesce: ping completion 31668 47443 1.5
enq: TD - KTF dump entries 31468 1424 0.05
enq: RO - fast object reuse 28422 31772 1.12
parallel recovery slave wait for change 27558 3163 0.11
name-service call wait 23694 181533 7.66
control file single write 22375 1624 0.07
kksfbc child completion 21239 106926 5.03
PX Deq: Table Q qref 19325 245 0.01
enq: TX - contention 18805 113253 6.02
latch: messages 17203 181 0.01
enq: RS - prevent file delete 16913 1013 0.06
enq: RS - prevent aging list update 15682 642 0.04
PX Deq: Table Q Get Keys 14322 42935 3
gc current grant congested 14292 2192 0.15
cursor: mutex S 13285 8 0
log file single write 13164 5371 0.41
latch: undo global data 12649 178 0.01
kksfbc research 11894 12680 1.07
parallel recovery slave idle wait 11193 5872 0.52
wait list latch free 11026 11794 1.07
enq: CT - state 11001 417 0.04
latch: checkpoint queue latch 10526 132 0.01
enq: PE - contention 10506 1139 0.11
ARCH wait on SENDREQ 9957 216480 21.74
gc cr grant congested 9465 1584 0.17
wait for scn ack 9377 3155 0.34
enq: TA - contention 8856 324 0.04
log buffer space 8777 89323 10.18
enq: TK - Auto Task Serialization 8542 343 0.04
enq: DR - contention 7842 323 0.04
process diagnostic dump 7707 2072 0.27
JOX Jit Process Sleep 7612 11286431 1482.72
enq: TC - contention 7357 340817 46.33
ges global resource directory to be frozen 7140 12299 1.72
enq: CO - master slave det 6850 312 0.05
enq: JS - job run lock - synchronize 6704 397 0.06
gcs drm freeze in enter server mode 6542 40742 6.23
enq: TS - contention 5959 89332 14.99
ARCH wait for archivelog lock 5600 36 0.01
PX Nsq: PQ load info query 5377 104798 19.49
db file single write 5373 3452 0.64
gc remaster 5315 50625 9.52
latch: parallel query alloc buffer 4939 1906 0.39
enq: TO - contention 4799 143 0.03
enq: AF - task serialization 4395 161 0.04
enq: PI - contention 4251 163 0.04
ges2 LMON to wake up LMD - mrcvr 4210 28 0.01
enq: DL - contention 3889 239 0.06
kjctssqmg: quick message send wait 3408 22 0.01
LNS wait on DETACH 3275 741 0.23
ksfd: async disk IO 3274 1 0
LNS wait on ATTACH 3273 51940 15.87
ARCH wait on DETACH 3231 714 0.22
ARCH wait on ATTACH 3226 43238 13.4
enq: BR - file shrink 2787 116 0.04
write complete waits 2631 1070 0.41
enq: MD - contention 2596 67 0.03
enq: WL - contention 2198 266518 121.25
single-task message 2098 25896 12.34
enq: OD - Serializing DDLs 2054 66 0.03
resmgr:internal state change 2001 14735 7.36
ARCH wait on c/f tx acquire 2 1751 175230 100.07
enq: WR - contention 1636 69 0.04
latch: cache buffer handles 1610 29 0.02
statement suspended, wait error to be cleared 1497 22626 15.11
Streams AQ: qmn coordinator waiting for slave to start 1214 678966 559.28
enq: PD - contention 1182 33 0.03
JS kgl get object wait 1096 4922 4.49
undo segment extension 1070 10065 9.41
PL/SQL lock timer 949 8739819 9209.5
enq: AE - lock 937 28 0.03
LGWR-LNS wait on channel 832 913 1.1
ges DFS hang analysis phase 2 acks 816 495 0.61
latch: redo writing 729 9 0.01
gc quiesce 665 564 0.85
enq: JS - queue lock 482 2111 4.38
PX Deq: Test for credit 442 13 0.03
enq: SS - contention 386 274 0.71
recovery area: computing dropped files 328 1400 4.27
recovery area: computing backed up files 328 496 1.51
ksdxexeotherwait 279 10592 37.97
log switch/archive 250 137570 550.28
gc domain validation 223 39964 179.21
auto-sqltune: wait graph update 195 96514 494.95
wait for a undo record 170 1214 7.14
parallel recovery coord send blocked 168 4 0.02
enq: JS - wdw op 168 3741 22.27
enq: KT - contention 165 5 0.03
switch logfile command 156 6290 40.32
gcs resource directory to be unfrozen 149 12839 86.17
Data Guard Broker Wait 139 10906 78.46
enq: SK - contention 129 4 0.03
enq: JS - job recov lock 128 4 0.03
gc cr block lost 125 6772 54.17
virtual circuit wait 122 3 0.03
ges LMON to get to FTDONE 100 187 1.87
enq: CU - contention 80 242 3.02
enq: JQ - contention 78 7 0.09
cursor: pin X 73 83 1.14
parallel recovery coord wait for reply 70 510 7.29
PX Deq: Txn Recovery Start 67 3436 51.29
SQL*Net break/reset to dblink 60 0 0
gc current block lost 57 2869 50.33
ges LMD suspend for testing event 51 709 13.89
inactive session 46 4550 98.91
recovery read 45 5 0.11
JS kill job wait 41 3548 86.53
enq: AS - service activation 40 1 0.03
enq: TL - contention 35 2 0.05
enq: UL - contention 34 524 15.42
gcs enter server mode 33 1559 47.24
wait for stopper event to be increased 30 218 7.27
enq: TQ - DDL contention 24 300 12.52
enq: MR - contention 21 1 0.03
ges reconfiguration to start 20 54 2.72
ges enter server mode 20 502 25.08
buffer latch 18 1337 74.26
enq: SR - contention 18 1 0.05
Streams: RAC waiting for inter instance ack 18 3748 208.21
enq: PR - contention 17 46 2.72
kupp process wait 16 166 10.39
checkpoint completed 15 3678 245.19
PX Deque wait 14 68 4.87
enq: BF - allocation contention 14 1 0.08
enq: XL - fault extent map 14 51 3.66
enq: FU - contention 14 17 1.18
enq: TH - metric threshold evaluation 13 114 8.78
enq: MW - contention 12 0 0.04
enq: DD - contention 10 0 0.04
process terminate 8 41 5.08
ges cgs registration 8 151 18.9
buffer resize 7 0 0
ktm: instance recovery 7 698 99.66
LNS wait on LGWR 6 0 0
ASM background starting 6 381 63.43
gc cr block 3-way 5 0 0.08
enq: PV - syncstart 5 9 1.74
Global transaction acquire instance locks 4 4 1.09
enq: RS - read alert level 4 0 0.04
LGWR wait on LNS 3 0 0
gc recovery 3 540 179.85
Streams AQ: enqueue blocked on low memory 3 544 181.2
DBWR range invalidation sync 3 17 5.83
enq: DM - contention 3 0 0.03
enq: RF - FSFO Observer Heartbeat 3 0 0.03
enq: JS - q mem clnup lck 3 0 0
DG Broker configuration file I/O 2 0 0
enq: RC - Result Cache: Contention 2 493 246.6
enq: KM - contention 2 0 0.03
enq: RT - contention 2 0 0.04
instance state change 2 0 0.12
kkdlgon 2 10 5.11
enq: TQ - INI contention 2 292 146.07
enq: JS - contention 2 0 0
ARCH wait for netserver start 1 400 400.02
log file switch (checkpoint incomplete) 1 3 3.44
JS coord start wait 1 50 50.09
ges lmd and pmon to attach 1 1 1.26
wait for tmc2 to complete 1 3 3.03
control file heartbeat 1 400 400.02
enq: SW - contention 1 0 0.04
enq: PW - perwarm status in dbw0 1 0 0.09
enq: FS - contention 1 0 0.04
enq: XR - quiesce database 1 0 0.04
enq: RS - write alert level 1 0 0.02
enq: CN - race with init 1 0 0.03
enq: FE - contention 1 4 3.77
Wait for shrink lock2 1 10 10.03
enq: IA - contention 1 0 0.02
enq: RF - atomicity 1 0 0.05
enq: RF - synchronization: aifo master 1 0 0.02
enq: RF - RF - Database Automatic Disable 1 0 0.06
enq: WP - contention 1 0 0.02
enq: TB - SQL Tuning Base Cache Load 1 0 0.05
enq: JS - evt notify 1 0 0.02Edited by: steffi on Mar 20, 2011 12:21 AM
Edited by: steffi on Mar 20, 2011 8:18 AM
Edited by: steffi on Mar 20, 2011 8:19 AMText can be formatted by tagging the beginning and end of the block of text with the code ta
\Formatted text goes here.
\Example:
This is formatted.When cutting and pasting text such as execution plans, excerpts from AWR reports, etc, it will maintain spacing and formatting, and make for much easier reading.
As to the content, well, dumping the contents of v$system_event is pretty close to useless.
As to the first three events you listed, 'enq: TX - index contention', 'enq: TX - row lock contention', 'enq: SQ - contention', well, all of those are easily tunable.
First, for 'enq: SQ - contention', check your sequences. Do you have any NOCACHE sequences? Or sequences with small caches?
As for 'enq: TX - row lock contention', well that's fairly self-explanatory. You have multiple sessions trying to lock the same row in the same table at the same time.
Last, 'enq: TX - index contention', that's non-row level contention on an index. For example, if you have a unique index, insert a row w/ column value 1, but don't commit, then try to insert that same value from another session.
But, before you do any of that, I think you need to clearly understand where the bottlenecks are. Try taking some AWR snapshots, about 5 minutes apart, when you're having performance problems. Look at the AWR report for that 5 minute period. In particular, look at your Top 5 timed events.
Hope that helps,
-Mark -
APEX 4.1 Applicaton Performance issue!
Problem:
Virtual Circuit wait is running high.
Apex application pages loads much slower comparing to our old environment APEX 3.0 on 10g, apache server.
Issues after installing apex with embedded PL/SQL ... OEM showing Virtual Circuit wait is running high ... APEX application pages loads with significant delays specially when first loaded.
Environment:
New 11g server with New apex 4.0 and updated to 4.1 with embedded pl/sql, windows server 2008 64 bit.
Migrated old application from 3.0 to 4.0 ---- No problems other than performance issue, slow pages load.
The reason why I went with the embeded pl/sql and not the apache because Windows server 2008 R2 and the apache HTTP server (conpanion cd) could not be installed on this version.
We did not have this issue with 10g apex 3.0 running with an apache server?
Where can I find HTTP server for windows server 2008 R2 64 bit?
Is this an embedded PL/SQL issue install on windows server 2008 x64?
Others ...
There is no Companion Disk for the Oracle Database 11g Release 1 (11.1.0.7.0) for Microsoft Windows Server 2008 x64 therefore the Http server is not included in the install or packaged software (companion or examples). The Oracle database 10g had the HTTP server in the companion disks. The 11 g examples download does not include the APACHE HTTP Server !!!!! Did anyone find a solution for this problem, or is the prior version of Oracle database 10 R 2 -HTTP SERVER (Companion Disk) windows server 2008 x64 compatable with 11g Release 1 installed. Can I install the companion disk included in the 10g R2 (Http server) with Oracle 11 g Release 1. Again for windows server 2008 x64.
Thanks,
MhndDimitri,
Thanks for taking the time to answer my question. So you are saying the listener which is my third choice should eliminate this issue. I know oracle have three choices for the web server but I'm only familiar with the two mentioned above, the APEX installation document provide information about the listener but haven't gone that path yet. The apache 2 only comes packaged for 32 bit systems (last I checked 2.16), and they don't have the 64bit version. I'm going to try the listener approach and see how it goes. Hopefully this will solve the issue with page loading slow. Should I uninstall the embedded PL/SQL or just continue with the listener install?
Mobra,
Thanks for your suggestions but I'm going to stick with the Oracle suggested methods for now. Hopefully some will work out for our environment.
Thanks,
Muhannad. -
Hello!
A have noticed some bad performance on database, Enterprise manager says the next query is top query.
SELECT ID ,
MIME_TYPE ,
BLOB_CONTENT,
FILENAME ,
FILE_CHARSET,
FILE_TYPE ,
FLOW_ID ,
CREATED_ON ,
LAST_UPDATED
FROM WWV_FLOW_FILE_OBJECTS$
WHERE FILENAME = :B2
AND SECURITY_GROUP_ID = :B1
I know its apex schema, but where is this code?
also it says about virtual circuit wait.
can you help me understand what is happening?Christian
Thank you very much,
I switched to Apex Listener over Weblogic Server that was already working, just added a new managed server and deployed apex.war and i.war on it.
the server resources are very good now.
Maybe you are looking for
-
how can I convert or print a html to a tiff format? since i would like to fax out the html by using some fax program!
-
SPRY accordion widget IE8 ONLY issue
hello everybody, i noticed a strange "jumpy" behavior while using the spry accordion widget -- this affects IE8 only (currently using 8.0.6001.18882 on vista), other browsers (including IE7 and IE8 forced into IE7 mode) work as expected. this issue s
-
[PERSISTENCE CLASS] SELECT OPTION in WHERE statement
Hi Gurus, I would like to know how could I code the WHERE statement with a SELECT OPTION, in Persistence Class ? Currenlty, I would like to code this kind of request : DELETE FROM ziTab WHERE zdate IN so_date
-
E72 input problem since upgrade
I updated my E72 to the lastest firmware a couple of days ago, it appeared to go ok although it was really slow for the first few reboot, but since the update it would not accept the password in the facebook app. It would either close the app when i
-
How to provide link in OIM 11g requestor screen
Could you please anyone suggest how we can put a link in OIM 11g request screen ? When we click the link it should open a diffrent window. Thanks in advance for your help.