Ensure that you have the necessary credentials, and that you complete any necessary cleanup or other preparation before migrating your Oracle database from Windows to an embedded PostgreSQL database in the appliance.
Verify that you have confirmed basic interoperability before preparing your Oracle database for migration.
Verify that you have backed up your database. For information about backing up the vCenter Server database, see the Oracle documentation.
- Verify that passwords are current and not set to expire soon.
- Ensure that you have login credentials, the database name, and the database server name that the vCenter Server database is to use.
Look in the ODBC system for the connection name of the database source name for the vCenter Server database.
- Use the Oracle SERVICE_NAME instead of SID to verify that your Oracle database instance is available.
- 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.
- Log in to the database server to read from the Oracle Listener status output.
- 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.
- Verify that the JDBC driver file is included in the CLASSPATH variable.
- Verify that permissions are set correctly.
- Either assign the DBA role or grant the required permissions to the user.
- Make a full backup of the vCenter Server database.
Your database is prepared for the vCenter Server migration to vCenter Server Appliance.