Populate the Database

This assumes that the environment has been set up as explained in Set Up the Environment, that the database has been created in the proper subdirectory as explained in Set Up the Database, and that the appropriate variables have been set for accessing the databases and their facilities. This last step is shown at the end of Set Up the Database, and in the pds_root README file.

However, the database still has not been populated with data at this point. This is the next step, and can be accomplished in one of two ways:

Populate with standard values only from the load files.
Populate with the haddock data from the database export file.

This is the first decision to be made. The following two sections cover each of these choices.

Populate from Load Files

The objective of this part is to create the tables in the database and to populate them with the reference data and standard instance data. This is explained in the pds_root README file, and is also outlined below.

The first steps as given in the other sections is to install the system, set up the environment script, and source the script. (Note: You should source the appropriate script whenever you logon to your account.) See Set Up the Environment for details on these steps.

If you have not already done so, source the appropriate script in the env_scripts subdirectory.

Next, execute the script (assuming c shell) $POSC_PDS_BIN/Builder as follows:

  $POSC_PDS_BIN/Builder <input_file >&! output_log_file &

where the < input_file may be omitted. The >&! output_log_file directs the output to some log file so that the results of the build can be saved. The final "&" causes the job to run in the background since it may take several hours to build.

The optional input_file is either a single character "Y" or "N" (followed by a carriage return). If a file is not specified, the script will prompt for the Y or N as input. (Of course, if the program is running in the background, you cannot use this option.) A "Y" will drop all the tables, build new ones, and load the reference and standard instances. A "N" will assume that the tables are already built, but not populated, and will only load the reference and standard instances.

The Builder README file that explains Builder is located in /rootdirectory/pds_root/bin.

Populate from Database Export File

The relational implementations of Epicentre in the three vendor databases all allow export files to be generated. POSC has created some of these export files, which can be used to load a database.

In order to load the export file, it is required that a database already be set up. Note: The database should be EMPTY. Do NOT create any tables. Do NOT load any data before importing the database files. However, it should be noted that, once the files are imported, additional data can be loaded into the now-created-and-populated database. See the section on Setting up a Database for details on this step.

The data is stored in a gnuzipped file in the /Haddock/<database> directory on the second CD where database is one of informix, oracle, or sybase. See the README file for information on this step.

[Return to Getting Started Introduction]