6.5.1

6 Use the Oracle SERVICE_NAME instead of SID to verify that your Oracle database instance is
available.
n
Log in to the database server to read from the alert log:
$ORACLE_BASE/diag//rdbms/$instance_name/$INSTANCE_NAME/trace/alert_$
INSTANCE_NAME.log.
n
Log in to the database server to read from the Oracle Listener status output.
n
If you have the SQL*Plus client installed, you can use tnsping for the vCenter Database
instance. If the tnsping command does not work the first time, retry it after waiting a few
minutes. If retrying does not work, restart the vCenter Database instance on the Oracle server
and then retry tnsping to ensure it is available.
7 Verify that the JDBC driver file is included in the CLASSPATH variable.
8 Verify that permissions are set correctly.
9 Either assign the DBA role or grant the required permissions to the user.
10 For vCenter Server 5.5, run the cleanup script.
a Locate the cleanup_orphaned_data_Oracle.sql script in the ISO image and copy it to the Oracle
server.
b Log in to a SQL*Plus session with the vCenter Server database account.
c Run the cleanup script.
@pathcleanup_orphaned_data_Oracle.sql
The cleanup process purges unnecessary and orphaned data that is not used by any vCenter Server
component.
11 Make a full backup of the vCenter Server database.
Your database is prepared for the vCenter Server upgrade.
What to do next
After the upgrade is complete, you can optionally remove the following permissions from the user profile:
create any sequence and create any table.
By default, the RESOURCE role has the CREATE PROCEDURE, CREATE TABLE, and CREATE
SEQUENCE privileges assigned. If the RESOURCE role lacks these privileges, grant them to the
vCenter Server database user.
vSphere Upgrade
VMware, Inc. 129