Filter
Top Products
• To meet the need for UNIX script files for DB2 that accomplish the same thing that the provided DB2 DOS
batch files do, ".sh" scripts have been provided. There is one script for each database. These files should be
read and edited before executing them.
• Both the DOS and UNIX scripts have comments in them to provide some instruction in running and editing
them. Depending on how a script was installed on the DB machine, you may need to make it executable (for
example, by using the UNIX command chmod +x *.sh) and then run it ( ./cr_db2db_lmm.sh).
• All databases can also be built by running one script. The following points present information on how this
can be done:
• DB2 users: Commands for creating schemas and populating seed data are added to the ".sh" and ".bat"
scripts, but are commented out. System administrators can uncomment the scripts and run the .sh or .bat
script to build the whole database. On the other hand, you can still run the commands as described
earlier in this chapter while using the remarked commands as documentation of what is needed to run
all of the scripts manually.
• Oracle users: Schema creating scripts are provided that call seed data scripts (this has already been
explained earlier in this chapter).
• SQLServer users: The run_mssql_*.bat scripts have been provided. These scripts run all commands to
create an SQLServer database, create schema, and run seed data scripts. These are written to run as "sa"
or sysadmin, but can be edited to work for their environment. The batch file assumes that it is running on
the database server and creates the directory that the database files will be put into. As with every other
script, you should edit the script if these assumptions are not correct for your environment.
Chapter 9: Installing and Configuring Database Servers and Schema 47