vCenter

 View Only
  • 1.  STILL getting 'transaction log for database 'VIM_VCDB' is full,' why??

    Posted Aug 09, 2012 02:47 PM

    Found and followed various Internet instructions:

    1) verified recovery model is set to simple

    2) set logs to upper limit 1 GB, 10 MB growth

    3) shrank the log files

    4) restarted vCenter Server service

    I *still* get error 9002 -- "The transaction log for database 'VIM_VCDB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases"

    This is vCenter Server 5.0 U1 with the embedded SQL Server 2008 R2 database.

    What can/should I do??

    Really can't have vCenter stopping all the time. :smileyhappy:

    Thank you, Tom



  • 2.  RE: STILL getting 'transaction log for database 'VIM_VCDB' is full,' why??

    Posted Aug 14, 2012 01:37 PM

    maybe you have simply outgrown SQL Express?  There is a 4GB limit.



  • 3.  RE: STILL getting 'transaction log for database 'VIM_VCDB' is full,' why??

    Posted Aug 14, 2012 01:44 PM

    The database is SQL Server 2008 R2 Express which has a 10 GB database limit.

    That’s for the database, not the logs.

    VMware set the database maxsize to 5 GB something.

    This is a LOG file issue – more a SQL server issue than anything else but it sucks that VMware did not configure/write the logging aspect well enough that this issue does not happen. Log files in simple recovery model are not usually supposed to do this issue. ☺

    For now I changed it to unrestricted growth and 100 MB increment and we’ll see what happens.

    Plus check every 5 minutes if the vCenter service is running or not.

    Thank you, Tom



  • 4.  RE: STILL getting 'transaction log for database 'VIM_VCDB' is full,' why??

    Posted Aug 14, 2012 01:50 PM

    you are correct on the 10GB size, my apologies