Search the VMware Knowledge Base (KB)
View by Article ID

VMware vCenter Server Appliance 5.0 GA with embedded DB2 database fails (2006812)

  • 27 Ratings

Symptoms

  • VMware vCenter Server Appliance (VCSA) 5.0 GA with embedded DB2 database fails with a backtrace
  • The VMware VirtualCenter Server service stops and then starts automatically on the Web client
  • The vSphere Client reports that the vCenter Server is not responding
  • The default transaction log size of DB2 is not sufficient to support an inventory of 5 hosts/50 virtual machines
  • Running VirtualCenter Management Service results in an error stating that the transaction log is full
  • In /var/log/vmware/vpx/vpxd logs, you see entries similar to:

    time [7FFFDE995710 error 'Default' opID=hostname@4979-bf58171f] [VdbStatement] SQL execution failed: UPDATE VPX_VM SET TOOLS_STATUS = ? , TOOLS_VERSION_STATUS = ? , TOOLS_RUNNING_STATUS = ? , TOOLS_VERSION = ? , GUEST_OS = ? , GUEST_FAMILY = ? , GUEST_STATE = ? , DNS_NAME = ? , IP_ADDRESS = ? , GUEST_OPS_READY = ? , INT_GUEST_OPS_READY = ? , SCREEN_HEIGHT = ? , SCREEN_WIDTH = ? , GUEST_IP_STACK = ? WHERE ID = ?

    time [7FFFDF133710 error 'Default' opID=SWI-95c6189a] Error inserting events: "ODBC error: (57011) -[IBM][CLI Driver][DB2/LINUXX8664] SQL0964C The transaction log for the database is full. SQLSTATE=57011 time [7FFFDF133710 error 'Default'] Alert:false@ /build/mts/release/bora-455964/bora/vim/lib/vdb/vdb.cpp:3253

    Backtrace:[00] rip 00007fffeed9ed14
    [01] rip 00007fffeecf59e2
    [02] rip 00007fffeec9b38b
    [03] rip 00007ffff555ab3d
    [04] rip 00007ffff5dc9ba3
    [05] rip 00007ffff533de5b
    [06] rip 00007ffff533dfe0
    [07] rip 00007ffff533eafb
    [08] rip 00007ffff533fd4e
    [09] rip 00007ffff52c56be
    [10] rip 00007ffff52d00fa
    [11] rip 00007ffff52d11c8
    [12] rip 00007ffff52d1805
    [13] rip 00007ffff60efb13
    [14] rip 00007ffff60ec962
    [15] rip 00007ffff60fa370
    [16] rip 00007fffeed920f2
    [17] rip 00007ffff4f97b65
    [18] rip 00007fffeed8d856
    [19] rip 00007fffed9f25f0
    [20] rip 00007fffed0f087d


  • After you start the VirtualCenter Management Service, you see this error in the vpxd.log file:

    [7FFFD9B8D710 error 'Default' opID=hostname@5545-c64328d3] An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Error: Error[VdbODBCError] (-1) "ODBC error: (57011) - [IBM][CLI Driver][DB2/LINUXX8664] SQL0964C The transaction log for the database is full. SQLSTATE=57011
    --> " is returned when executing SQL statement "insert into VPX_INT_ARRAY (ARRAY_ID, TYPE_ID, VALUE, ARRAY_INDEX, MO_TYPE, MO_ID) values (?, ?, ?, ?, ?, ?)"

Cause

This issue occurs when the transaction log of the embedded DB2 database is full.

Resolution

To resolve this issue, increase the transaction log size to the recommended size, 16*112*8192.

Note: In some instances, the transaction logs may fill as a result of the rollup jobs not executing which results in a large amount of rows in the vpx_hist_stat[1-4] tables. For more information, see Determining if vCenter Server rollup jobs are processing performance data (2007388).

To increase the transaction log size:
  1. Run this command to stop vCenter Server:

    service vmware-vpxd stop

  2. Run these commands:

    su db2inst1
    db2 connect to vcdb


  3. Run this command to retrieve the current database configuration:

    db2 get database config for vcdb | grep LOG

    You see output similar to:

    Catalog cache size (4KB) (CATALOGCACHE_SZ) = 300
    Log buffer size (4KB) (LOGBUFSZ) = 256
    Log file size (4KB) (LOGFILSIZ) = 1024
    Number of primary log files (LOGPRIMARY) = 13
    Number of secondary log files (LOGSECOND) = 4


  4. Run this command to update the database configuration:

    db2 update db CFG FOR VCDB USING logprimary 16 logsecond 112 logfilsiz 8192

    You see output similar to:

    DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
    SQL1363W One or more of the parameters submitted for immediate modification were not changed dynamically. For these configuration parameters, all applications must disconnect from this database before the changes become effective.


  5. Run this command to verify whether the update command has executed successfully:

    db2 get database config for vcdb | grep LOG

    You see output similar to:

    Catalog cache size (4KB) (CATALOGCACHE_SZ) = 300
    Log buffer size (4KB) (LOGBUFSZ) = 256
    Log file size (4KB) (LOGFILSIZ) = 8192
    Number of primary log files (LOGPRIMARY) = 16
    Number of secondary log files (LOGSECOND) = 112


    Note: Additionally, you can run this command to view output before the modification is made as per step 4.

    db2 get db config|egrep "LOG(FI|PR|SE)"

  6. Type exit to exit from the db2 session.
  7. Start the vCenter Server service and check the status with these commands:

    service vmware-vpxd start
    service vmware-vpxd status
Note: As a final step, you may also want to clear the core dumps generated by the vCenter Server Appliance (VCSA) crashes from /storage/core; depending on how long the issue has been occurring, the number and size of the core dumps could be quite large.

Additional Information

Note: To view the supported databases and to identify the services that are included/not included in vCenter Server Appliance (VCSA) 5.0.x, see Services bundled with vCenter Server Appliance (2002531).

Tags

vcenter-server-appliance-fails

See Also

This Article Replaces

2003668

Update History

12/19/2011 - Added steps 6 and 7 to resolution 07/19/2012 - Added link to article 2002531

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

  • 27 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)




Please enter the Captcha code before clicking Submit.
  • 27 Ratings
Actions
KB: