DB2 Data Links Manager Quick Beginnings

Common Installation Considerations

Please read this information carefully before installing DB2 Data Links Manager. The information in this section is common to installations in both JFS and DCE-DFS environments. Specific JFS and DCE-DFS information follows this section.

Should I use the db2setup utility or SMIT?
We strongly recommend that you use the db2setup utility if you are installing DB2 Data Links Manager in JFS or DCE-DFS environments. The db2setup utility performs almost all Data Links Manager setup and configuration tasks for you. If you want to install DB2 Data Links Manager using SMIT, you will have to set up and configure your Data Links Manager system manually.

Disk space requirements
Ensure that there is at least 85 MB of free disk space in the /usr/lpp directory. To check available free disk space, enter the df -k /usr/lpp command.

Memory requirements
Ensure that there is at least 256 MB of memory available to your system. To check available memory, enter the lsattr -l sys0 -E -a realmem command.

Migrating from previous versions
Different levels of DB2 Data Links Manager instances cannot exist on the same machine. If you have a pre-Version 7.1 Data Links instance on your system, you must migrate the instance to the Version 7.1 format using the db2imigr command. For more information, refer to the DB2 for UNIX Quick Beginnings.

Registry variables offer more function and flexibility than environment variables. However, because of this, it is possible that migration will not be performed exactly as expected. The registry variables should be checked using the db2set command after migration. You do not need to check these variables if you are migrating from Version 6.1 to Version 7.1.

Migrating from DB2 File Manager Version 5.2 to DB2 Data Links Manager Version 7

If you are migrating from DB2 File Manager Version 5.2 to DB2 Data Links Manager Version 7.1, you should perform the following steps:

  1. Prepare your DB2 and DLFM databases for migration. For more information see "Migrating from Previous Versions of DB2" in Chapter 1 of the Quick Beginnings for UNIX manual.
  2. Install DB2 Version 7 on your DB2 server and DLFM server machines. These tasks are detailed below.
  3. As a user with root authority on the DLFM server machine, run the /usr/lpp/db2_07_01/adm/db2dlmmg command.

When you migrate from DB2 File Manager to DB2 Data Links Manager, the following environment variables will be converted to DB2 registry variables: 

   DLFM_INSTALL_PATH
   DLFM_PORT
   DLFM_LOG_LEVEL
   DB2_RR_TO_RS
   DLFM_BACKUP_DIR_NAME (1)
   DLFM_BACKUP_TARGET (2)
   DLFM_BACKUP_TARGET_LIBRARY (3)

Notes:

  1. This variable is used if a local file system is the backup target.

  2. Used to indicate the type backup target used. Possible values for this variable are LOCAL, TSM, or XBSA.

  3. Used to indicate the XBSA support code library if the DLFM_BACKUP_TARGET is set to XBSA. The support code library must be fully qualified and must include the shared object name, for example /u/dmcinnis/Legato/libxdb2.a(bsashr10.o). The name of the shared object, in this case bsashr10.o, is available from the vendor suppling the XBSA compliant shared library.

TCP/IP port number
You must have a TCP/IP port available for use by the Data Links File Manager. By default, the db2setup utility will generate a value for you. You can use this value or provide your own. You will need to know this port number to verify the installation.

If you want to specify your own port number, review the TCP/IP ports that are already in use on a machine by opening the /etc/services file. You will need to specify this port during the installation.

Once you have selected a TCP/IP port number for use by the DLFM, the value should not be changed.

New registry variable
A new registry variable, DLFM_FS_ENVIRONMENT, will be set up during install. This variable will be set to DFS or NATIVE (for JFS), depending on the file system you select when you install DB2 Data Links Manager.

Synchronize system clocks
Ensure that the system clocks on the Data Links server and the remote DB2 server are synchronized and remain synchronized. Synchronization of clocks is essential for the Data Links token expiry interval to work correctly. The token expiry interval is a database configuration parameter. To check the system time and date, enter the date command. For more information on synchronizing system clocks, refer to your AIX Administration Guide.

Depending on the file system (JFS or DCE-DFS) you plan to use with your DB2 Data Links solution, there are additional installation considerations you should take into account before you begin installing DB2 Data Links Manager on your AIX system.

[ Top of Page | Previous Page | Next Page ]