Home » RDBMS Server » Server Administration » Logwr Blocking Other session (10.2.0.5 Enterprice edition Microsoft windows 2003)
Logwr Blocking Other session [message #585381] Fri, 24 May 2013 09:21 Go to next message
AnilKampiri
Messages: 69
Registered: September 2012
Location: Chennai
Member

Dear All,

I needed help Regarding one issue happens frequently in My database,Logwr process blocking other session,when i checked blocked session in v$session wait_class was commit and event was logfile sync,


EVENT# WAIT_CLASS
------ ----------------------------------------------------------------
   116 Commit
   116 Commit
   116 Commit
   116 Commit
   116 Commit
   116 Commit
   115 Configuration
   116 Commit
   116 Commit
   116 Commit
   116 Commit

EVENT# WAIT_CLASS
------ ----------------------------------------------------------------
   116 Commit
   116 Commit
   116 Commit
   116 Commit
   116 Commit
   116 Commit
   116 Commit
   116 Commit
   116 Commit
   116 Commit
   116 Commit

EVENT# WAIT_CLASS
------ ----------------------------------------------------------------



As per this we predicate Logbuffer Might be full so i just to reboot server,Note server was 32 Bit i can allocate only 1GB of SGA SYStem not allows me to increase SGA further.Please advice server reboot is proper solution?

Regards,
Anil

Re: Logwr Blocking Other session [message #585383 is a reply to message #585381] Fri, 24 May 2013 09:36 Go to previous messageGo to next message
BlackSwan
Messages: 22484
Registered: January 2009
Senior Member
>Please advice server reboot is proper solution?
NO, not any solution.

Which system resource (CPU, DISK, or RAM) primary bottleneck.
post COPY & PASTE proof which resource is primary system bottleneck.
Re: Logwr Blocking Other session [message #585384 is a reply to message #585381] Fri, 24 May 2013 09:51 Go to previous messageGo to next message
John Watson
Messages: 4370
Registered: January 2010
Location: Global Village
Senior Member
Is your user community happy with you solving their problems like that???
However, to have that many sessions waiting on log file sync is bad. It typically means that your log writer cannot write redo records to disc sufficiently fast, so check your I/O rates. Ask your sysadmin what is happening.
There are two possible solutions: reduce the size of the log buffer if it larger than default: probably best to remove the parameter completely, and let Uncle Oracle size it. Second, set COMMIT_WRITE=BATCH,NOWAIT. I wouldn't normally advise the latter, but if your users are happy with reboots, I don't think they'll object.
Re: Logwr Blocking Other session [message #585397 is a reply to message #585384] Fri, 24 May 2013 10:42 Go to previous message
Michel Cadot
Messages: 58499
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
... But the best solution is to commit less often that is remove any commit which is inside a (cursor) loop and put it outside.

Regards
Michel
Previous Topic: how to kill killed session
Next Topic: where does the pfile go?
Goto Forum:
  


Current Time: Wed Jul 23 09:06:47 CDT 2014

Total time taken to generate the page: 0.10007 seconds