The vCenter Server installer creates the schema during installation. Experienced database administrators who need more control over schema creation because of environmental constraints can use a script to create their database schema.

To have the vCenter Server installer create your schema for you, see Configure a Connection to a Local DB2 Database on Microsoft Windows or Configure a Connection to a Remote DB2 Database on Linux, UNIX, or Microsoft Windows, depending on your environment.

Create the DB2 database and user. You can create the DB2 database manually or by using scripts.

1

Open a DB2 Command Editor window and log in as the user that you created on the vCenter Server database.

a

Open DB2 Control Center.

b

Select the database.

c

Right-click the database and select Menu > Query.

2

In the directory of the vCenter Server installation package /installation directory/vpx/dbschema, locate the dbschema scripts.

3

In the DB2 Command Editor window, open the SQL files one at a time and press Ctrl+Enter to run each SQL file query in the order shown here.

VCDB_db2.sql
TopN_DB_db2.sql

For the following files, change the statement termination character from ; to @.

load_stats_proc_db2.sql
purge_stat1_proc_db2.sql
purge_stat2_proc_db2.sql
purge_stat3_proc_db2.sql
purge_usage_stats_proc_db2.sql
stats_rollup1_proc_db2.sql
stats_rollup2_proc_db2.sql
stats_rollup3_proc_db2.sql
cleanup_events_db2.sql
delete_stats_proc_db2.sql
upsert_last_event_proc_db2.sql
load_usage_stats_proc_db2.sql
calc_topn1_proc_db2.sql
calc_topn2_proc_db2.sql
calc_topn3_proc_db2.sql
calc_topn4_proc_db2.sql
clear_topn1_proc_db2.sql
clear_topn2_proc_db2.sql
clear_topn3_proc_db2.sql
clear_topn4_proc_db2.sql
rule_topn1_proc_db2.sql
rule_topn2_proc_db2.sql
rule_topn3_proc_db2.sql
rule_topn4_proc_db2.sql
process_license_snapshot_db2.sql
process_temptable0_proc_db2.sql
process_temptable1_proc_db2.sql
process_temptable2_proc_db2.sql
job_schedule1_db2.sql
job_schedule2_db2.sql
job_schedule3_db2.sql
job_cleanup_events_db2.sql
job_topn_past_day_db2.sql
job_topn_past_week_db2.sql
job_topn_past_month_db2.sql
job_topn_past_year_db2.sql
job_property_bulletin_db2

You now have a database schema that is compatible with vCenter Server.

4

(Optional) you can also run the following scripts to enable database health monitoring. Use @ for the statement termination character.

job_dbm_performance_data_db2.sql
process_performance_data_db2.sql
5

On the machine that you intend to install vCenter Server on, create a data source name (DSN) that points to the database server that has the schema.

6

Run the vCenter Server installer.

When prompted, provide the database user login.

7

If a database reinitialization warning message appears in the vCenter Server installer, select Do not overwrite, leave my existing database in place and continue the installation.

This message appears if you are using a database that has vCenter Server tables that were created by a previous installation. The message does not appear if the database is clean.

If you leave your existing database in place, you cannot join the vCenter Server to a Linked Mode group during the installation. You can join after the installation is complete. (See Join a Linked Mode Group After Installation.)