Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

After upgrading vCenter to 4.1, the transaction logs grow larger than normal (1026407)

Symptoms

After upgrading to vCenter Server 4.1, the transactions logs grow larger than normal.

Resolution

When you upgrade to vCenter Server 4.1, the Recovery Model for SQL Server 2005 is set to Bulk-Logged. This causes the transaction logs to grow to a large size.

To resolve this issue, consult your DBA and choose an appropriate Recovery Model for your SQL database.

To choose an appropriate Recovery Model, see the MSDN article Choosing the Recovery Model for a Database.

For more information, see SQL Server Recovery Model Affects Transaction Log Disk Space Requirements (1001046).

Note: When you upgrade a vCenter Server that is deployed with a Microsoft SQL Server 2005 database to vCenter Server 4.1 Update 1, the recovery model continues to be the same as what it was before the upgrade. However, during upgrade, the Recovery Model will be in the bulk mode and may cause the transaction log file to consume a large amount of disk storage space. For more information, see the VMware vCenter Server 4.1 Update 1 Release Notes.

Additional Information

Note: As a result of transaction log growth after the Upgrade to vCenter Server 4.1, the vCenter Service may fail with an error in the vpxd log file similar to:

[2011-02-23 08:43:41.685 03548 error 'App'] Error inserting events: "ODBC error: (42000) - [Microsoft][SQL Native Client][SQL Server]Could not allocate space for object 'dbo.VPX_EVENT_ARG'.'PK_VPX_EVENT_ARG' in database 'VIM_VCDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup." is returned when executing SQL statement "INSERT INTO VPX_EVENT_ARG WITH (ROWLOCK) (EVENT_ID, ARG_ID, ARG_TYPE, ARG_DATA, OBJ_TYPE, OBJ_NAME, VM_ID, HOST_ID, COMPUTERESOURCE_ID, DATASTORE_ID, NETWORK_ID, NETWORK_TYPE, DVS_ID, DATACENTER_ID, RESOURCEPOOL_ID, FOLDER_ID, ALARM_ID, SCHEDULEDTASK_ID) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)"

For further details on troubleshooting transaction log file growth, see Troubleshooting transaction logs on a Microsoft SQL database server (1003980).


See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 15 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 15 Ratings
Actions
KB: