opt/vmware/vpostgres/current/bin/psql -U postgres -d VCDB -c "ALTER SEQUENCE vpx_ansfile_seq OWNER TO vc" opt/vmware/vpostgres/current/bin/psql -U postgres -d VCDB -c "ALTER SEQUENCE vpx_alarm_seq OWNER TO vc" opt/vmware/vpostgres/current/bin/psql -U postgres -d VCDB -c "ALTER SEQUENCE vpx_access_seq OWNER TO vc" If this is not the case you can change the owner for the relevant tables using these commands: /opt/vmware/vpostgres/current/bin/psql -U postgres -d VCDB -c "ALTER SEQUENCE vpx_vdevice_backing_rel_seq OWNER TO vc" You can now check your tables with the command: \ds Log into your vCSA 6.0 appliance using ssh as root and start postgres sql manager with this command: /opt/vmware/vpostgres/current/bin/psql -U postgres -d VCDB Also make sure you have a working root account for that host. An important step to perform before upgrading is taking a backup/snapshot of your vCenter VM, and any related components, so that you will be able to recover from a failed upgrade.Ī wise step is to use DRS rules to keep your vCSA VM to a single host so you know where to find it without vCenter. Remember that anything you see here is executed at your own risk. Thanks to black88m圆 There is a way to check this, and also to fix it. For some reason the table owner is often wrong. Postgres table ownerįirst check you postgres database.
#ORCHESTRATOR PLUG VCENTER 6.5 ERROR 1009 UPGRADE#
Here is a list of things that you might want to do before you upgrade your vCenter from vCSA 6.0 to vCSA 6.5.
0 kommentar(er)
