vCenter Server 5 - MSSQL missing jobs

Similar Questions

• VCenter Server 4.1 missing Standard Options

  You have a question for the group...

  I'm running a node two ESXi 4.1 Enterprise Plus with Vcenter Server 4.1 standard. All legal. My two knots ESXi show HA and DRS are available optionally licensed as well as all the rest for Enterprise Plus. I created my cluster and joined my two nodes to the new cluster. For the life of me, I can't find the options to enable DRS and HA. I know I should be able to right click on the cluster and go on changing the settings to enable HA and Drs The cluster settings option is not present. I can't see the DRS tab also when I click on my name to cluster. Does anyone have an idea?

  Same thing here!  Thanks for the reply, Troy!

• vCenter Server 5.5 installation, MSSQL problem

  Hello

  I'm installing vCenter Server 5.5. I have already created database users and roles MSSQL with permissions, using scripts to the installation directory.

  During Setup, after you enter the credentials database, the error message: "entries by the user DB has no required permissions to install and configure vCenter Server with DB selected.» Correct the following errors: the database user "vpxuser" doesn't have the following privileges on the database "VCDB ':... "(les détails sur les captures d'écran)."

  Ok

  then my best trick is to grant vpxuser on the msdb db_owner. He needs create stats rollup jobs. After installation, you can revoke permissions.

  Concerning

• vCenter Server 5.1 fresh install database MSSQL w/box

  Hi all

  Looking for advice on how best to manage a new installation of vCenter Server 5.1 using a MSSQL database out of area.  Have done some research and looked at some of the videos that are out there, but have not found quite what I'm looking for.  So, I thought I would post.  Be gentle - I'm a bit new to the vMware environment.

  Here's my scenario.  And if there is a link/doc/post/video that covers what I'm after - very well.  Looking for a little help on searching for it.  If this isn't the case, direct responses will be fantastic.

  -Need to build a 5.1 vCenter server and use a MSSQL off the coast of the MessageBox database.  Out the door, I started with 6 guests and 24 guests, which, as I understand it, is just a little bigger than SQL Express can handle.  And the footprint of the host/guest is likely to increase over time.

  -Have available to build the DB MSSQL 2008 R2 cluster on.

  -My company has vMWare/vCenter existing deployments, but my particular scenario is going to be a unique and independent facility.

  -ESXi hosts will be 5.0 update 1 (to stay in our internal model of best practices).

  -vCenter maybe 5.1 for purposes of property management.

  -Also need to run the Update Manager, as I understand it, kind of excludes the version 'device' vcenter, or at the very least, a little complicated.

  -Leaning towards the Simple installation of vCenter 5.1.  Know that this will launch the single sign on the server, the inventory Service and the vCenter Server installed.  And that the installation of the Update Manager will be a 4th installation (and hopefully last).

  Where I am a little confused:

  -Discrete databases how should I really?  A school of thought (and practical in our 'other' vMWare environment) is 1 DB for each app on Cree.  This seems a bit complicated, but if this is the way it must be, so be.

  -I think I can run only a database and each of the 4 required applications would build/use the necessary table space they need.  Is this correct or am I far from base?

  -1 single database, if feasible, should I use a master service flavoured AD account for everything, or should I watch different service AD for different functions accounts.

  Not quite sure I'm being quite clear on what I'm after, fire so far with follow-up if necessary issues.

  1 DB for SSO, 1DB for VC and 1 DB for MUV.

  SSO DB needs to execute scripts (in your search for ISO for scripts to prepare your SQL DB:(:\Single Sign On\DBScripts\SSOServer\schema\mssql))

  The inventory service has its own DB.

  Concerning

  Girish

• A suspended snapshot could not be created for the virtual machine (DC) ha-data center (DC) \vm\VMware vCenter Server Appliance.

  Hello gentlemen,

  I can not only save this virtual machine with Backup Exec 2014 for a long time.

  They are there was no snapshot in snapshot Manager.

  Could you help me?

  A suspended snapshot could not be created for the virtual machine (DC) ha-data center (DC) \vm\VMware vCenter Server Appliance.

  V-79-57344-38260 - failed to create a snapshot of the virtual machine. The virtual machine is no longer exist, or may be too busy to pause to take the snap.

  A suspended snapshot could not be created for the virtual machine (DC) ha-data center (DC) \vm\FRPA111PRIM01.

  V-79-57344-38299-\vm\FRPA111PRIM01 ha-data center (DC) VMVCB::\\192.168.204.42\VCGuestVm\ (DC). To try to take a snapshot of a virtual machine failed because it could not be suspended in a file system.

  Hello

  I found the solution.

  I disabled the JOB BE general relativity.

  and the host where the virtual machine belong was not the right time. No Ntp server has been configured.

  I did and now there works.

  I think that the problem can come from this.

• vCenter Server Recovery of Cluster has failed (Site A to Site B)

  Hello community VMWare,

  I was wondering if someone could help understand me the following scenario.

  I have two Sites, and each one has its own VMWare Cluster.

  Site A Cluster goes down, which hosts our vCenter Server.

  The vCenter Server contains all of its components, for example database.

  I want restore vCenter Site b, so as the SAN and the networks are online I could just connect to an ESXi host, browse the data store, import the vCenter Server and turn it on?

  The only thing I could think of who could stop me is a possible file lock.

  All guests will perform in ESXi 5.5.

  I tried searching google but couldn't really find this type of scenario.

  May I use the wrong search words so my apologies to advanced if I missed something obvious.

  Thank you.

  Power on this virtual machine to the other site won't be a problem.

  Since you will be reproducing original VM of the Site A to Site B, they're just files residing on the data store, no locks on them.

  But of the things to think about is, network setting the guest OS etc. If you use a different subnet to the recovery of the site (Site B in your case).

• VCSA 6 - could not connect to one or more systems vCenter Server - but I already deleted it...

  I have a recording of question in my server vcenter (VCSA) after adding a few VCSAs to a single SSO. All VCSAs are displayed correctly, but I removed an old... will be... No... die. It causes the initial connection to last 2 to 5 minutes. It shows immediately and the error on the top of the page indicating the "vcenter server in not available.

  

  As you can see, the VCSA referenced in the error message is not even in the list of 'the vCenter inventory'-> 'resources"->"Server vCenter:

  

  But it's somehow in the section 'License' from the same server vcenter:

  

  I think that screwing with the other parts of my installation vcenter because that stuff will be reached a limit of 120 and stop working. Here is a SS just try to look at the Configuration of the system:

  

  It expires essentially like some other windows. Originally vcenter be largely unusable.

  I think that the main problem is that I can't remove a stale VCSA Mode related SSO. It causes hanging on login and many never completed processes. I could increase the time-out period, but this will not solve the bland entry which is the culprit.

  Here is the error that occurred within the VCSA. It is every time I have to refer to something to check with other vcenter servers. Given one is more accessible, it is not able to speak, causing a timeout. The data service has expired because a main task took more than 120 seconds. See the vsphere client - virgo.log for more details.

  Okay it looks like you can run the command cmsso-util. Time consuming but gets the job done.

  VMware KB: Dismantling of the vCenter Server or a Services Platform controller

  hqvcenter1: / # cmsso - unsubscribe util - node-pnid balvcenter3 [email protected] name

  2015 04-20 T 15: 21:17.810Z order: [' / usr/lib/vmware-vmafd/bin/dir-cli ', 'service', 'list', '-login', '[email protected]']

  2015 04-20 T 15: 21:17.952Z done by running the command

  2015 04-20 T 15: 21:18.145Z order: [' / usr/lib/vmware-vmdir/bin/vdcleavefed ', '-h', 'balvcenter3', '-u', 'administrator']

  2015 04-20 T 15: 27:37.058Z done by running the command

  Success

• Sliding missing jobs after migration

  Today, I finished my migration from a Windows 2008 R2 Server to a 2012 R2 Windows Server vCenter vCenter Server

  
  General information on what I've done (this movement included a move of Server DB 2008 - 2012 dedicated DB server)

  Back up the database and restored to SQL, 2012

  Ran vCenter installed (which I think would be ' inject jobs!) on the new Server R2 2012 Windows

  Anyone know how I can create jobs, is it easy? What is the best way to tackle this problem now, migration as a whole apart from that went well!

  This article shows the steps: VMware KB: update rollup jobs after the error: the performance data are currently not available for this entity

• Local administrators on Windows of vCenter server is automatically granted 'Administrator' role in vSphere

  
  This still applies (5.0 and 5.5).  I might have missed in the 5 documentation site.  I see still ESX Admin workaround applies to 5.5 and wondered about the role of local administrators.

  VMware vSphere 4 - ESX and vCenter Server

  
  It's the 4.0 site doc.

  "Host records all selected Windows domain user, or a group through the process of assigning permissions." By default, all users who are members of the local windows Group istrators Adminthe vCenter Server have the same rights of access as any user assigned to the Adminsector role. Users who are members of the group Administrators can log on as individuals and have full access. »

  EDIT - I found this... VMware vSphere 5.1

  Seems to be the same... :))

  The main difference is that before 5.1 and 5.5, the local Administrators group on the server vCenter Server is the default vCenter Server Administrator. With vCenter 5.x with the addition of SSO, installing vCenter, you will be asked which user account or the group will be initially given and vCenter Server Administrator role. Here is the screenshot. This screenshot, after installing vCenter, only the [email protected] has the role of administrator on the vCenter server.

  

  If you upgrade your server vCenter to 5.x since a previous version using a Simple installation, if I remember correctly, you won't see the screen above as the installation will use the existing as the vCenter Administrator local Windows Administrators group.

  It will be useful.

• The upgrade to vCenter Server 5.5 U1 beat vCO AD Plugin

  Hey guys,.

  I've recently updated vCenter Server (under Windows) to 5.5 U1, and so vCO has been upgraded to the latest version as well. It seems that the AD plugin has been upgraded to 1.0.4 - 763 and now can not be configured correctly. The vCO newspapers give the following:

  2014-05-12 12:11:14.141 - 0400 [WorkflowExecutorPool-thread-1] ERROR {[email protected]: Configure Active Directory server: 8a6abc61-9f1e-4b75-84e3-5f7ed902af57:1d74889645f12cdf0145f133c1e20009} [MSPluginFactory] condition of credentials are corrupted.

  java.lang.RuntimeException: org.bouncycastle.crypto.InvalidCipherTextException: block corrupted buffer

  at ch.dunes.util.PasswordEncryptor.decrypt(PasswordEncryptor.java:76)

  at ch.dunes.util.EncryptHelper.newDecrypt(EncryptHelper.java:61)

  Furthermore, when I try to set up an advertising server by using the plug-in, I have the following problem, showing me one of the configuration objects is null - 'ConfigurationManager '.

  2014-05-12 12:11:14.251 - 0400 [WorkflowExecutorPool-thread-1] WARN {[email protected]: Configure Active Directory server: 8a6abc61-9f1e-4b75-84e3-5f7ed902af57:1d74889645f12cdf0145f133c1e20009} Script Runtime error [WorkflowItemTaskRunner] on the workflow: Server Configure Active Directory / 'Configuration' (item1) update: ReferenceError: 'ConfigurationManager' is not defined. (Workflow: Configure the Active Directory Server / update of Configuration (item1) #10)

  2014-05-12 12:11:14.351 - 0400 [WorkflowExecutorPool-thread-1] ERROR {[email protected]: configures Active Directory server: 8a6abc61-9f1e-4b75-84e3-5f7ed902af57:1d74889645f12cdf0145f133c1e20009} [SCRIPTING_LOG] [Server Configure Active Directory (12/05/14 12:11:12)] ReferenceError: 'ConfigurationManager' is not defined. (Workflow: Configure the Active Directory Server / update of Configuration (item1) #10)-null

  We do not use LDAPS, LDAP standard, so I don't see why we would receive an exception of encryption, and the 'ConfigurationManager' null configuration object is interesting.

  Is it possible to reset the configuration of the plugin, re-establish a connection, and try again? I prefer not to reinstall this vCO, as we have done a lot of configuration.

  Uninstalling and reinstalling the 1.0.4 plugin does not seem to solve the problem. I should come back 1.0.3 or can it?

  Thanks for all your help.

  Thank you, Christophe, who complained of being 'ConfigurationManager' being missing (according to the first message in this thread). That said...

  Rename/Delete the

  C:\Program Files\VMware\Infrastructure\Orchestrator\app-server\conf\plugins\AD.xml and

  C:\Program Files\VMware\Infrastructure\Orchestrator\app-server\server\vmo\conf\plugins\AD.xml

  and re - configure the plugin (1.0.3 in this case) AD, seems to have allowed the AD connection is restored. At that time, we were see errors in the vCO related to plugin configuration of the client (it seems that all the old cruft of 1.0.4 has not been completely cleaned), so I upgraded the plugin from 1.0.3 to 1.0.4.

  I can now browse through the structure of the AD in vCO as expected. A terrifying upgrade, plugin-breaking!

• vCenter Server 5.5 compatibility with vSphere 4 hypervisor

  I recently installed vCenter Server 5.5.0.5201 (with a Standard license valid vCenter) and I am trying to add the hosts to vCenter data center. I can connect successfully to the host but vSphere displays the following error:

  "The host is licensed with vSphere 4 hypervisor. The license of vCenter Server edition doesn't support vSphere 4 hypervisor. »

  Now I found the slot compatibility matrix and there clearly shows that vCenter 5.5 is compatible with all the way back to version 4 for ESXi. I must be missing something, can someone please clarify the question.

  

  I know that vSphere hypervisor and ESXi Server is essentially the same but vSphere hypervisor is the free version, so is there a difference that I know?

  This happens because you are using a free license on the ESXi 4.1 key.

  "The host is licensed with vSphere 4 hypervisor" means that it is a free ESXi. You will not be able to manage the free ESXi with vCenter.
  

• [HELP] SMV disappeared after restart of the host - 5.5 ESXI, Vcenter Server to the same host

  I restarted the ESXI using classic Vsphere Client. Now, all virtual machines have disappeared. I tried to connect with Vsphere Client and workstation and the list is empty. I can't access the Vcenter server since it is a virtual machine that resides in the home.

  The data store is a local disk. The data store is still there and the amount of disk space used is correct. I don't see the virtual machines in the inventory. I have re-installed ESXI 5.5, refreshed of store data and what not, there is nothing there. I am freaking out and don't know what to do.

  EDIT: I am able to navigate the data store manually by creating the new virtual machine and select the existing virtual machine following this guide but I'm not sure what is the reason for which the files would be missing or corrupt

  http://techhead.co/VMware-ESX-how-to-easily-recreate-a-missing-or-corrupt-vmx-file/

  When you browse the data store you see the virtual machine and their records?

  If you see the virtual computer files, you can open the folder, right click on the .vmx file and select Add to the inventory. who will get your VM in the inventory.

• vCenter Server 5.5 cannot connect

  Hi all

  I can't connect using vsphere client in my vcenter server. I installed the simple installation.

  I installed the related modules and VMware vCenter Server for Windows on a Windows Server 2008 R2.

  Installation completed successfully. I can not connect with the vsphere client. He says I don't have permissions.

  Only the connection that works, is to webbrowser https://server-IP:9443 , but I can't add hosts etc. just look a that its empty.

  I'm sure I missed something but don't know what.

  Could you please help me?

  Kind regards

  Roland

  

  Please log in the https://server-ip:9443 / with [email protected] user and password defined during installation. Your vcenter will then appear in the inventory. After that, you will be able to add guests.

• The upgrade to vCenter Server to vCenter Server 5.1 5.1 update 1 when the SQL database is remote and vCenter Server Heartbeat is installed

  Hi guys,.

  I'm in the middle of an upgrade to vSphere 5.1 5.1 vSphere update 1. I have vCenter protected by HB and SQL on a separate computer (also protected by HB) I also run Syslog, Update Manager and Proxy authentication on vCenter.

  I've successfully upgraded HB on all 4 nodes (2 x vCenter & 2 x SQL) and started the upgrade components on the secondary according to the •vCenter Server Heartbeat 6.5 server and vCenter Update 1 Installation on Windows Server 2008 when the secondary server is virtual (PDF) http://www.vmware.com/pdf/vcenter-server-heartbeat-65-u1-installation-windows-2008-virtual-guide.pdf

  I got to step 3.c

  3. change the primary/active server role:

  a launch of the vCenter Server Heartbeat wizard configure server and click the tab of the Machine to change the server role for the current server (primary) to the active State and click Finish.

  b using the Service Control Manager, start the Server Heartbeat of VMware vCenter service.

  c using the vCenter Server Heartbeat Console, check that all the status icons on the server: summary page are green indicating that the boot process is completed and protected from all the services are started.

  d using the Service Control Manager, stop the service Server Heartbeat of VMware vCenter.

  As the vCenter service does not start, I'm stuck at this point. As far as I'm concerned, the error is quite logical. I've updated vCenter using the secondary server, and then I'm trying to connect (according to the guide) with another version that breaks down.

  If I continue with the services stop and launch the installer SSO, it is trying to perform an uninstall!

  Did I miss something in this upgrade?

  Concerning

  
  Ciaran

  Hi guys, VMware have finally updated the documentation to reflect the right way forward: https://www.vmware.com/support/pubs/heartbeat_pubs.html U1 6.5 Select from the menu drop-down and you'll see the last date of update for each of the documentation is now 10/10/2013. The guide States now specifically to restore the vCenter database before proceeding with any other measure, this is copied below for convenience: "the upgrade of the main server of the upgrade process further guess upgrading the secondary server completed successfully. Procedure 1 before continuing the upgrade process, perform a restore of the database of vCenter Server, Single Sign-On database, VMware Update Manager database and SSL certificates that were backed up in step 4 on the secondary server. regards Ciaran

• Error connecting to vCenter Server

  After that a sudden loss of power I got the following error trying to connect to vcenter server:

  Internal server error

  2013-05-15 17:47:44, 772 | DEBUG | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). JobManager | Add the activity log: JOB_VC_START
  _CONNECTION > < cloudvcs0(com.vmware.vcloud.entity.vimserver:23b4fe43-1f29-4c6f-adc1-1048b2a8845c) > |
  2013-05-15 17:47:44, 773 | DEBUG | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). CJob                           | updateFailedJob (com.vmware.vcloud.ap
  i.presentation.service.InternalServerErrorException) with locale = null |
  com.vmware.vcloud.api.presentation.service.InternalServerErrorException: internal server error
  at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.onOuterLoopBreakWithException(VcUpdateListenerImpl.java:721)
  at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.outerWaitForUpdatesLoop(VcUpdateListenerImpl.java:633)
  at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.run(VcUpdateListenerImpl.java:343)
  Caused by: org.hibernate.exception.GenericJDBCException: could not execute the query
  at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126)
  at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:114)
  at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
  at org.hibernate.loader.Loader.doList(Loader.java:2231)
  at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125)
  at org.hibernate.loader.Loader.list(Loader.java:2120)
  at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:118)
  at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1596)
  at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:306)
  at com.vmware.vcloud.inventory.cache.PropertyMapDao.validateOrGet(PropertyMapDao.java:336)
  at com.vmware.vcloud.inventory.cache.PropertyMapDao.bulkValidateOrGet(PropertyMapDao.java:321)
  at com.vmware.vcloud.inventory.cache.PropertyMapDao.bulkValidateAndGetNewer(PropertyMapDao.java:267)
  at com.vmware.vcloud.inventory.cache.InventoryCacheManagerImpl.bulkGetInternal(InventoryCacheManagerImpl.java:418)
  at com.vmware.vcloud.inventory.cache.InventoryCacheManagerImpl.bulkGet(InventoryCacheManagerImpl.java:549)
  at com.vmware.vcloud.inventory.impl.InventoryServiceImpl.processUpdateSet(InventoryServiceImpl.java:931)
  to com.vmware.vcloud.inventory.impl.InventoryServiceImpl.access$ 300 (InventoryServiceImpl.java:145)
  to com.vmware.vcloud.inventory.impl.InventoryServiceImpl$ 5.run(InventoryServiceImpl.java:860)
  to com.vmware.vcloud.inventory.impl.InventoryServiceImpl$ 5.run(InventoryServiceImpl.java:826)
  at com.vmware.vcloud.common.persist.ConversationContextExecutor.execute(ConversationContextExecutor.java:46)
  at com.vmware.vcloud.inventory.impl.InventoryServiceImpl.processAndBatchUpdates(InventoryServiceImpl.java:826)
  at com.vmware.vcloud.inventory.impl.InventoryServiceImpl.handleUpdate(InventoryServiceImpl.java:799)
  at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke (unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke (unknown Source)
  at java.lang.reflect.Method.invoke (unknown Source)
  at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:309)
  at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
  at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
  at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
  to $Proxy187.handleUpdate (Unknown Source)
  at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.dispatchUpdates(VcUpdateListenerImpl.java:1080)
  at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.innerWaitForUpdatesLoop(VcUpdateListenerImpl.java:925)
  at com.vmware.vcloud.vimproxy.internal.impl.VcUpdateListenerImpl.outerWaitForUpdatesLoop(VcUpdateListenerImpl.java:594)
  ... 1 more
  Caused by: java.sql.SQLException: ORA-01555: snapshot too old: rollback segment number with the name "" too small
  ORA-22924: snapshot too old

  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:388)
  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:381)
  at oracle.jdbc.driver.T4C8TTILob.processError(T4C8TTILob.java:789)
  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)
  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
  at oracle.jdbc.driver.T4C8TTILob.read(T4C8TTILob.java:146)
  at oracle.jdbc.driver.T4CConnection.getBytes(T4CConnection.java:2313)
  at oracle.sql.BLOB.getBytes(BLOB.java:319)
  at oracle.sql.BLOB.getBytes(BLOB.java:209)
  at oracle.jdbc.driver.T4CBlobAccessor.getBytes(T4CBlobAccessor.java:464)
  at oracle.jdbc.driver.OracleResultSetImpl.getBytes(OracleResultSetImpl.java:676)
  at oracle.jdbc.driver.OracleResultSet.getBytes(OracleResultSet.java:398)
  at org.hibernate.type.AbstractBynaryType.get(AbstractBynaryType.java:101)
  at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:184)
  at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:173)
  at org.hibernate.type.AbstractType.hydrate(AbstractType.java:105)
  at org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2124)
  at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1404)
  at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1332)
  at org.hibernate.loader.Loader.getRow(Loader.java:1230)
  at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:603)
  at org.hibernate.loader.Loader.doQuery(Loader.java:724)
  at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259)
  at org.hibernate.loader.Loader.doList(Loader.java:2228)
  ... 32 more
  2013-05-15 17:47:44, 774. DEBUG | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). JobString | Object - object: cloudvcs0 (com.
  name of the VMware.vCloud.Entity.vimserver:23b4fe43-1f29-4c6f-adc1-1048b2a8845c operation): JOB_VC_START_CONNECTION |
  2013-05-15 17:47:44, 842. DEBUG | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). CJob                           | Not the last pending work: [cloudvcs0 (c
  OM. (VMware.vCloud.Entity.vimserver:23b4fe43-1f29-4c6f-adc1-1048b2a8845c)], status [3] = |
  2013-05-15 17:47:44, 846. DEBUG | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). CJob                           | Last jobs update: [cloudvcs0 (c
  OM. (VMware.vCloud.Entity.vimserver:23b4fe43-1f29-4c6f-adc1-1048b2a8845c)], status = [3], [15/05/13 17:47] |
  2013-05-15 17:47:44: 964 | DEBUG | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). ValidationServiceImpl | Jump queuing of the validator for co
  validator of m.vmware.ssdc.backend.valeventhandler.ProviderVdcVALStateValidator since it is a duplicate, current validation queue length: 1 |
  2013-05-15 17:47:44, 966 | INFO | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). InventoryServiceImpl | Reception earphone stopped for VC 23 b
  4fe43-1f29-4c6f-adc1-1048b2a8845c |
  2013-05-15 17:47:44, 966 | WARN | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). InventoryRecordPurger | Records of the inventory for 23b4fe4 trap
  3 1f29-4c6f-adc1-1048b2a8845c is not active.
  2013-05-15 17:47:44, 968 | INFO | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). VcUpdateListenerImpl | Releasing the proxy property of VC
  23b4fe43-1f29-4C6F-ADC1-1048b2a8845c |
  2013-05-15 17:47:44, 968 | INFO | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). VcUpdateListenerImpl | trying to clear the instance of cell id on
  VC 23b4fe43-1f29-4c6f-adc1-1048b2a8845c (current number of retries to 0). |
  2013-05-15 17:47:44, 969 | INFO | 23b4fe43-1f29-4c6f-adc1-1048b2a8845cListener (260). VcUpdateListenerImpl | 23b4fe43-1f29-4c6f-adc1-1048b2a88 VC
  45 c: attempt to set the instance id of cells from 70 to 0.

  Caused by: java.sql.SQLException: ORA-01555: snapshot too old: rollback segment number with the name "" too small

  ORA-22924: snapshot too old

  I found these two articles in the KB:

  VMware KB: The vCloud Director Web UI reports the error: ORA-01555: snapshot too old: rollback number with n segment...

  VMware KB: Make sure that you have adequate undo tablespace before upgrading a vCloud Director Oracle database

  I added more space for the undo tablespace, new redologs, also change the setting of retention for all LOB in the vCloud regime without a different result.

  Anyone have any idea on this?

  Best regards

  I finally had an answer for the Oracle error.

  I did a full export of the vcloud database and detect an error in this table:

  ORA-31693: Table object "VCLOUD" data "" PROPERTY_MAP "impossible to load/unload and being ignored because of the error:

  ORA-02354: Error exporting/importing data

  ORA-01555: snapshot too old: rollback segment number with the name "" too small

  ORA-22924: snapshot too old

  This OPINION score details this condition:

  Export fails with ORA-2354 ORA ORA-1555-22924 errors and how to confirm the Corruption of the LOB Segment using the export utility? [833635.1 ID]