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

Upgrading to vCenter Server 5.x fails with the error: Failed to execute dbuHelper.exe (2010529)

  • 10 Ratings

Symptoms

  • Upgrading to vCenter Server 5.x fails.
  • In the %TEMP%/VCDatabaseUpgrade.log, you see entries similar to:

    Info: Upgrading database from version x.x to version x.x successfully done
    Preparing to launch dbuHelper.exe
    Adding arguments for dbuHelper.exe
    Launching D:\vCenter-Server\dbupgrade\bin\dbuHelper.exe
    D:\vCenter-Server\dbupgrade\bin\dbuHelper.exeLaunched. Waiting for it to return
    Error: Failed to execute dbuHelper.exe: An error occurred
    Error while upgrading: An error occurred
    Info: Exiting Upgrade Wizard
    Successfully run: alter database [VirtualCenter] set recovery SIMPLE
    Failed to execute dbuHelper.exe

  • In the vpxd logs (C:\ProgramData\VMware\VMware VirtualCenter\Logs) contains entries similar to:

    [20732 info 'Default'] [DbuHelper] [UrlUpgrade] Upgrading URLs in table VPX_VM_FLE_FILE_INFO column NAME
    [20732 info 'Default'] [DbuHelper] [UrlUpgrade] Done upgrading URLs in table VPX_VM_FLE_FILE_INFO column NAME
    [20732 verbose 'Default'] [VdbSchemaLoader::LookupSchema] Found schema/index information for: VPX_EVENT_ARG
    [20732 info 'Default'] [DbuHelper] [UrlUpgrade] Upgrading URLs in table VPX_EVENT_ARG column ARG_DATA
    [20732 error 'Default'] [DbuHelper] [UrlUpgrade] NotConverted: url [[vmfs_data_01] ISO/EN_WINDOWS_SERVER_2003_R2_ENTERPRISE_DISC1_VLP.iso] was not converted to a valid url
    [20732 error 'Default'] [DbuHelper] [UrlUpgrade] NotConverted: url [[vmfs_boot_01]] was not converted to a valid url
    [20732 error 'Default'] [DbuHelper] [UrlUpgrade] NotConverted: url [[vmfs_data_01] ISO/Citrix presentation Server.iso] was not converted to a valid url
    [20732 error 'Default'] [DbuHelper] [UrlUpgrade] NotConverted: url [[vmfs_data_01] ISO/Citrix XenApp.iso] was not converted to a valid url
    [20732 error 'Default'] Unable to allocate memory: 18446744073648076376 bytes
    [20732 info 'Default'] CoreDump: Writing minidump
    [20732 panic 'Default']
    -->
    --> Panic: Unable to allocate memory
    --> Backtrace:
    --> backtrace[00] rip 000000018013d40a (no symbol)
    --> backtrace[01] rip 00000001800ffa38 (no symbol)
    --> backtrace[02] rip 00000001800fffee (no symbol)
    --> backtrace[03] rip 000000018015e668 (no symbol)
    --> backtrace[04] rip 000000018015e771 (no symbol)
    --> backtrace[05] rip 000000018014ea70 (no symbol)
    --> backtrace[06] rip 00000000725b10af (no symbol)
    --> backtrace[07] rip 00000000725fcb9f (no symbol)
    --> backtrace[08] rip 0000000140075904 (no symbol)
    --> backtrace[09] rip 0000000140077670 (no symbol)
    --> backtrace[10] rip 000000014006051e (no symbol)
    --> backtrace[11] rip 000000014000deeb (no symbol)
    --> backtrace[12] rip 0000000140010294 (no symbol)
    --> backtrace[13] rip 00000001400086ff (no symbol)
    --> backtrace[14] rip 0000000140001182 (no symbol)
    --> backtrace[15] rip 00000000773d466d (no symbol)
    --> backtrace[16] rip 0000000077508791 (no symbol)
    -->
    [20732 panic 'Default'] (Log recursion level 2) Unable to allocate memory

Cause

This issue occurs if the URLs in the ARG_DATA column of the VPX_EVENT_ARG table fails due to memory constraint.

Resolution

This is a known issue in vCenter Server 5.x.

To work around this issue, truncate (delete) the data the Tasks and Events of the vCenter Server database.

Note: Truncating the table does not impact the vCenter Server data. Only the Tasks and Events are deleted and you can preserve the Tasks and Events data for a number of days, as required.

Caution: VMware recommends you take a backup of your current database before proceeding.

To truncate Tasks and Events in SQL:

  1. Use SQL Management Studio to connect to the vCenter Server database.
  2. Select New Query.
  3. Enter this query in the new window and Click Execute:

    update vpx_parameter set value = '15' where NAME = 'event.MaxAge';
    update vpx_parameter set value = 'true' where NAME = 'event.MaxAgeEnabled';
    update vpx_parameter set value = '15' where NAME = 'task.MaxAge';
    update vpx_parameter set value = 'true' where NAME = 'task.MaxAgeEnabled';


    Note: Where 15 is the number of days to retain data for in Tasks and Events. If the value 15 does not resolve the issue, set a lower value or manually truncate Tasks and Events using the steps below.
    Manually truncating the Tasks and Events will remove ALL data in the Tasks and Events tables, where setting a lower value only reduces the amount of data to the specified amount of days.

  4. Run the built-in stored procedure dbo.cleanup_events_tasks_proc.

    To run this stored procedure, navigate to VCDB > Programmability > Stored Procedures, right-click dbo.cleanup_events_tasks_proc, and Click Execute.

    For SQL 2005, right-click the stored procedure, point to script stored procedure as, select execute To and select New Query Editor Window. Once there, Click execute on the icon bar.

    Note: This purges the data from tables vpx_event, vpx_event_arg, and vpx_task, based on the date specified for maxAge.


    • To manually truncate Tasks and Events in the SQL database, use this syntax:

      alter table VPX_EVENT_ARG drop constraint FK_VPX_EVENT_ARG_REF_EVENT, FK_VPX_EVENT_ARG_REF_ENTITY
      alter table VPX_ENTITY_LAST_EVENT drop constraint FK_VPX_LAST_EVENT_EVENT
      truncate table VPX_TASK
      truncate table VPX_ENTITY_LAST_EVENT
      truncate table VPX_EVENT
      truncate table VPX_EVENT_ARG
      alter table VPX_EVENT_ARG add constraint FK_VPX_EVENT_ARG_REF_EVENT foreign key(EVENT_ID) references VPX_EVENT (EVENT_ID) on delete cascade,
      constraint FK_VPX_EVENT_ARG_REF_ENTITY foreign key (OBJ_TYPE) references VPX_OBJECT_TYPE (ID)
      alter table VPX_ENTITY_LAST_EVENT add constraint FK_VPX_LAST_EVENT_EVENT foreign key(LAST_EVENT_ID)
      references VPX_EVENT (EVENT_ID) on delete cascade

    • To truncate Tasks and Events in Oracle database, use this syntax

      alter table VPX_EVENT_ARG disable constraint FK_VPX_EVENT_ARG_REF_ENTITY;
      alter table VPX_EVENT_ARG disable constraint FK_VPX_EVENT_ARG_REF_EVENT;
      alter table VPX_ENTITY_LAST_EVENT disable constraint FK_VPX_LAST_EVENT_EVENT;
      truncate table VPX_TASK;
      truncate table VPX_ENTITY_LAST_EVENT;
      truncate table VPX_EVENT;
      truncate table VPX_EVENT_ARG;
      alter table VPX_EVENT_ARG enable constraint FK_VPX_EVENT_ARG_REF_ENTITY;
      alter table VPX_EVENT_ARG enable constraint FK_VPX_EVENT_ARG_REF_EVENT;
      alter table VPX_ENTITY_LAST_EVENT enable constraint FK_VPX_LAST_EVENT_EVENT;

  5. Stop the VMware VirtualCenter Server service and then upgrade to vCenter Server 5.x.

Update History

01/12/2012 - Added syntax to truncate Tasks and Events in the Oracle database 10/10/2012 - Added steps to manually truncate Tasks and Events in the SQL database 04/04/2014 - Update product VMware vCenter Server 5.5.x

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

  • 10 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.
  • 10 Ratings
Actions
KB: