Updating the Initialization File

Before running the database creation script, you need to verify that the default information provided in the database initialization file is correct for your environment.

  1. Verify that you are logged in as the same user that installed the DB2 software. Contact your database or system administrator to determine database user information.

  2. Navigate to the following directory:

    <SEE_install_dir>/<os_dir>/reffiles/SMAFIPserver/db/db2/

    Where <os_dir> is one of the following:

    • /win_b64/ for Windows 64-bit
    • /linux_a64/ for Linux 64-bit

  3. Open one of the following files in the text editor of your choice:

    • Windows: initdb.bat

    • Linux: initdb

  4. Review the following settings and, if necessary, update them appropriately:

    FIP_DB. The name of the SIMULIA Execution Engine database. The default setting is fiper.

    FIP_USER. The user with DB2 administrative privileges. The default setting is fiperacs.

    FIP_SERVERSIZE. The size of the system running the database. One of the following options should be used:

    • small. Used for a computer with 1 GB of memory.

    • large. Used for a server with at least 1.5 GB of memory.

    FIP_TABLEDIR. The directory in which you want to create buffer pool storage. This setting should be changed if you installed DB2 in a location other than C:\DB2 (Windows) or /opt/IBM (Linux). The default settings are C:\DB2\NODE0000\FIPER (Windows) or /opt/IBM/db2 (Linux).

    FIP_Territory. The location that controls localization of the database. The default setting is us. This entry must be set to one of the following options:

    • us (United States)

    • ca (Canada)

    • cn (China)

    • fr (France)

    • de (Germany)

    • jp (Japan)

    • kr (South Korea)

    • tw (Taiwan)

    • gb (United Kingdom)

    For additional territory location codes, see your DB2 documentation.

    For example, to update this setting to use the Germany option, your entry would appear as follows:

    SET FIP_TERRITORY=de
    

  5. Continue by running the database initialization scripts; see Executing the Database Scripts.