VMware vCenter 5.0 Update 1b & VMware View 5.1.1发布 (DL)

housefull

本帖最后由 housefull 于 8-17-2012 16:26 编辑
vmware vCenter 5.0 Update 1b发布
主要修复Upgrading vCenter Server 5.0 Update 1a fails on an Oracle database的bug
以及vCenter tomcat的内存溢出的bug
https://www.vmware.com/support/v ... _u1b_rel_notes.html
http://kuai.xunlei.com/d/KPZOXAVTYBVN
华丽的分割线。。。。。。。。。。。。。。。。。。。华丽的分割线
VMware View 5.1.1发布
没有任何的新功能，只是修复一些已知的bug,增加稳定性。。。
http://kuai.xunlei.com/d/KRJXXWBBXSCG

jaimy

坑爹，刚升级完VMware vCenter 5.0 Update 1a
坐等 5.1

housefull

1b主要是为使用oracle作为vCenter数据库的用户准备的。。。

天擎

那么我不用升级了。

TiGi

本帖最后由 TiGi 于 8-17-2012 18:39 编辑
热闹！！！
————————
明显注意力放到v5.1上了。
————————
主要修复的问题：
Upgrade and Installation
    Upgrading vCenter Server 4.0.x and 4.1.x to vCenter Server 5.0 Update 1a fails on an Oracle database for Windows with the error: PLS-00905 STATS_ROLLUP2_PROC is invalid
    Upgrading vCenter Server 4.0.x and 4.1.x to vCenter Server 5.0 Update 1a might fail on an Oracle database. If you install through the media VMware-VIMSetup-all-5.0.0-757163, the VCDatabaseUpgrade.log reports an error similar to:
    PLS-00905: object STATS_ROLLUP2_PROC is invalid
    ORA-06550: line 1, column 99:
    PL/SQL: Statement ignored
    ORA-06512: at "SYS.DBMS_JOB", line 82
    ORA-06512: at "SYS.DBMS_JOB", line 140
    ORA-06512: at line 39
    Note: This issue does not exist when upgrading from vCenter Server 5.0 or vCenter Server 5.0 Update 1 to vCenter Server 5.0 Update 1a
    This issue is resolved in this release.
    Changing the inventory size setting for vCenter Server Appliance through the Web Console causes the vServiceManager and EAM services to stop running
    In the vCenter Server Appliance, changing the inventory size through the Web Console to any setting other than small, results in the vServiceManager and EAM services to stop running.
    This issue is resolved in this release.
    After ESXi host reboot HA configuration fails or host does not reconnect to vCenter
    If the vCenter Agent (vpxa) and HA agent get installed in ESXi ramdisk instead of vmkramdisk, these bundles do not get persisted in the bootbank image. Therefore, after the host reboot, they do not get automatically redeployed.
    This problem occurs in the following situations:
        If the build number of the ESXi 4.0 host falls between 219381 and 392992.
        If ESXi build number does not fall within the range mentioned above, this problem occurs on the ESXi host, the latest vpxa/fdm installation log entries in /var/log/vpxa-installer.log or /var/log/fdm-installer.log reports, Now try installing on ramdisk and installation completed saying "All done! Status: 0".
    This issue is resolved in this release.

ganyuansi

，先现在收集了，继续等5.1哦

masinfo

坐等5.1哦   

xingyun1031

强帖留名