Exchange 2003 log generation number exhausted

All replies

• 

  

  0

  Sign in to vote

  When it finishes, you'll know.

  ---

  Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  Thursday, April 7, 2011 12:00 AM
• 

  

  0

  Sign in to vote

  if you want quick resolution

  dismount the database

  check the health of the database

  if it is in clean shutdown, move the log files  (E00.log, E00xxxxxxx.log,res1.log and res2.log) and check point file (E00.chk) to another location

  mount the database and u will see the log file generation from e0000001.log.

  ---

  Thanks Joseph Pradeep

  • Proposed as answer by Alan.Gim Tuesday, April 12, 2011 8:35 AM
  • Marked as answer by Alan.Gim Wednesday, April 13, 2011 8:38 AM

  Thursday, April 7, 2011 12:44 AM
• 

  

  0

  Sign in to vote

  Just starting to wonder its around hour 4 but the processor is still doing work.  Must be doing something.
  

  Thursday, April 7, 2011 12:58 AM
• 

  

  0

  Sign in to vote

  How's the progress right now? Any further update?

  ---

  Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  Monday, April 11, 2011 9:01 AM
• 

  

  0

  Sign in to vote

  the easiest way doing this task is

  dismounting all the databaes in the storage group

  then navigate to log folder directory

  rename the old logs folder to  something like   "SG4logs.old" then mount all databases. you can moved the old logs later

  this way you will avoid downtime while logs are beeing moved.

   

  NOw as you have already started the process with the assistant i would recomend you to wait. unless the process is not responding

  open the corrosponding process in taskmgr and see I/O if the bytes are constant.

  ---

  Dhruv

  Monday, April 11, 2011 2:10 PM