| # Appendix DB2 This Appendix provides some extra information about the ERP Enterprise installation and the DB2 database. To allocate disk space for DB2 To establish a stable DB2 environment, you must thoroughly consider your disk usage. During the installation of ERP Enterprise, you are asked whether you want to create the tablespaces for the system catalogs, ERP Enterprise tables (user tablespace), temporary data (temporary tablespace), and the index data. By default, DB2 places the catalog and temporary tablespaces into the same directory as the database. Database-managed space (DMS) During the installation of ERP Enterprise, you can create a tablespace for the user data. The user tablespace will be a database-managed space (DMS). The DMS tablespace containers are either Operating System (OS) files or raw devices. In a DMS tablespace, the database manager controls the storage space. To use the raw devices as tablespace containers for DMS tablespaces, use the following notes to fill in the path for the raw devices and their size. UNIX devices are classified into two categories: Character serial devices Block-structured devices All file-system devices usually have a corresponding character serial device, or raw device, for each block device, or cooked device. The block-structured devices are typically designated by names similar to hd0 or fd0. The character serial devices are typically designated by names similar to rhd0, rfd0, or rmt0. These character serial devices have faster access than block devices. The character serial device names must be used for the path of the raw devices and not block device names. If you want to use the device lv06 under the /dev directory, you must use the following character serial device name: /dev/rlv06. In addition, fill in the size of the DMS tablespace in megabytes in the size text box given for the tablespace size. System-managed space (SMS) The SMS tablespace containers are OS directories. The user in case of SMS decides on the location of the files (containers), DB2 controls their names and the UNIX file system manager controls the storage page. The Installation Wizard enables you to create both Database Managed Space (DMS) and System Managed Space (SMS) tablespaces. For best performance, place the ERP Enterprise tables, index data, and the DB2 system catalogs on separate tablespaces on various disks. Tables for each package can be stored in a different tablespace. Tables with high growth rates can be separated from other tables and placed in a tablespace with a larger extent size to avoid fragmentation and to allow tablespace backup and recovery. Note The following values are rough estimates. The true values depend on several installation considerations. Also the choice of character set is crucial. For Unicode for example you need twice as much diskspace. Sizing by Infor is highly recommended. Note At least one extent, by default, 32 pages of 8K each, is allocated for each table created in a DMS tablespace. Bear this fact in mind when you allocate files or devices to the tablespace. If the tables you will use are small and you have limited disk space, use system-managed space (SMS). Only the space that is required for each table is allocated. Note You can only create a limited number of objects (tables and indexes) in each database-managed space (DMS) tablespace. If you create multiple companies with all packages, plan to have at least one tablespace for every two companies. Change the DB2 profile For ERP Enterprise to work properly with DB2, you must change the DB2 profile. To change the profile, take the following steps: Step 1. Edit the db2profile file You can find this file in the sqllib directory in the home directory of the instance owner. Step 2. start your DB2 database manager Whenever you want to start your DB2 database manager, run db2profile before you start DB2 with the db2start command. For example, from the directory that contains sqllib, type the following:
    . ./db2profile
    db2start
Add UNIX group account You must create a UNIX group for all ERP Enterprise users. The group name must correspond with the DB2 database that will be created during the installation of ERP Enterprise. Any user who must have access to the database must be a member of this group. Add UNIX user accounts Before you can install ERP Enterprise, you must create the following UNIX user accounts: Create a UNIX user ( bsp), who will run the Installation Wizard to install ERP Enterprise. You must add this user to the ERP Enterprise application user group for example; erpln and to the database administration group for example db2iadm Create a UNIX user ( erpln) whose name corresponds to the DB2 database group that will be created during the installation of ERP Enterprise. You must add this user to the erpln user group and database administration group ( db2iadm). Create ERP Enterprise users and add them to the erpln user group. Add all ERP Enterprise users that require access to the database to the erpln group. All users that require database administration access must belong to the group db2iadm that was created during the installation of DB2. $BSE is a variable of the directory path in which the ERP Enterprise software will be installed Modify the UNIX user account root Modify the UNIX user account root and make the account a member of the ERP Enterprise user group, which is probably in the example infor. In addition, the user root must be a member of the DB2 related groups, which are DB2, the ADMIN group, and other groups created during installation. To connect to a remote database Step 1. Modify the db2profile Modify the db2profile file in the sqllib subdirectory of the instance’s home directory, on both the client and the server system, to add or change the following three environment variables:
    export DB2COMM=TCPIP
    export DB2INSTANCE=instance_name
Make sure that this file is carried out in the startup shell for user root and all other users who need to access or maintain the database from outside ERP Enterprise. Step 2. /etc/services files In the /etc/services files of the client, as well as of the server, look for two consecutive unused TCP/IP port numbers higher than 1024 to use these port numbers for DB2 client/server communication. Edit the /etc/services files on the client as well as the server, to include the following two lines:
    name1	port_number1/tcp
    name2	port_number2/tcp
The name of the first port number is referred to as the service name. |