The OECATALOG command-line utility's -build option does not create the physical database. That option only creates the tables and populates them with data. To create a new master catalog, you MUST run the New Catalog wizard on the physical database before using the OECATALOG command-line utility.
Building a master catalog on a server is a multi-stage process:
1. Create an empty database and database server on the server.
a. Start a PROENV session on the machine where you want the master catalog.
b. Create a directory to hold the master catalog.
c. Use the PRODB utility to create an Empty database in that directory.
d. Create a database server with the appropriate connection parameters for the master catalog using OpenEdge Management or OpenEdge Explorer. Remember that the database server has to support SQL.
e. Start the database server.
2. Run the New Catalog wizard
a. Start a Progress Developer Studio for OpenEdge session on your local machine in a workspace that has no catalogs defined.
b. Choose File > New > Other . The New dialog box appears.
c. Choose OpenEdge > Meta Catalog > Meta Catalog and click Next. The Create Meta Catalog wizard appears.
d. Enter the empty database's name for the Meta Catalog name and click Next.
e. Click Next on the this page. You have already created the database.
f. On the Meta Catalog Connection page, enter the connection information for the empty database and click Next.
g. Continue creating the catalog definition as usual.
h. When you have set all the options correctly for your master catalog, deselect the Load content from selected projects toggle and click Finish.
Your master catalog now has the Meta Catalog tables.
3. Transfer the catalog definition from your local machine to the server.
Before you can use the OECATALOG utility on your master catalog, you need a catalog definition file for it.
a. Choose Windows > Preferences. The Preferences dialog box appears.
b. Choose OpenEdge > Meta Catalog. The Meta Catalog browser appears.
c. Click Export All.
d. Save the catalog definition file with a unique name.
e. Copy the catalog definition file to the master catalog's directory on the server.
You now have a master catalog database and a catalog definition file for it.
4. Run the OECATALOG command-line utility to populate the master catalog using the catalog definition file. For example: oecatalog -build -catalog masterCatalog.xml -root c:\wrk
Note: The -root setting should match where the resources are stored on the master catalog's machine, not where your local copies are.
You can now use the OECATALOG utility to populate and rebuild the master catalog as needed. The master catalog does not contain any data yet, because the content builders have not run against the source files yet.
