Prerequisite checks for stand-alone installations with DB2

The InfoSphere® MDM installer application runs tests to ensure that certain prerequisites are in place before each stand-alone installation with DB2® begins.

The prerequisite checking tool helps to prevent you from beginning an installation that will be unable to successfully complete due to any missing prerequisites.

Tip: Run the prerequisite checks from within Installation Manager from the Installation Configuration Review panel by clicking Verify Installation Requirements.

When running a stand-alone installation with DB2, the installation application runs the following prerequisite checks.

Table 1. System checks
Prerequisite check Description Resolution
Installation disk space verification This check validates that there is sufficient disk space to install InfoSphere MDM and all required software for a stand-alone with DB2 deployment, including the WebSphere® Application Server profile and the database. Ensure that there is at least 32 GB of disk space available on the installation target machine.
Memory verification for running the installation application This check validates that there is sufficient memory to run the installation. This message is a warning only. Ensure that the system that you are installing on has at least 8 GB of RAM.
Note: You can choose to ignore this warning, but the installation may fail.
Table 2. Database checks
Prerequisite check Description Resolution
Database instance verification The check validates that the database does not already exist. Stand-alone installations with DB2 require an environment without a preexisting database. If your installation environment has a preexisting database, remove it before attempting to complete the installation.
Database name verification The check validates that the database name is valid. The database name must consist of 12 or fewer alphanumeric characters. Underscore ( _ ) characters can be used in the name. Other characters are not supported.
Database user verification This check determines if the database user specified in the installation panels exists. This user should not already be present in the system. This message is a warning only. Delete the database user if it already exists. The stand-alone installation with DB2 will create the user during installation. Alternately, ensure that the db2admin database user has the same default password.
Note: You can choose to ignore this warning, but the installation may fail.
Global Security Kit v8 verification This check determines if the Global Security Kit library is present from a previous DB2 installation.

If the Global Security Kit library is present and the installed version is below the minimum requirement for InfoSphere MDM, then the check will fail. If the Global Security Kit library is the wrong version, then the DB2 database manager is unable to start.

 Delete the Global Security Kit library folder (GSK8\lib64), then continue with the installation.
Tip: On Microsoft Windows, You can locate the GSK8 folder by checking the Path in your System variables and looking for a directory path similar to C:\Program Files\IBM\GSK8\lib64
ODBC datasource verification This check determines whether an ODBC datasource exists in a Microsoft Windows registry. This check will fail with an error if an ODBC datasource already exists.
Note: For non-Windows systems, this check will always pass.
 If an ODBC datasource exists in your Windows registry, remove the datasource:
  1. Open the Windows Registry Editor by running the command regedit.
  2. Find the entry HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI.
  3. Expand ODBC.INI, locate the ODBC datasource entry, then right-click it and select Delete.
  4. Under ODBC.INI, select the ODBC Data Sources entry. In the display pane, all of the subentries are shown.
  5. Locate the ODBC datasource entry in the list of subentries. Right-click the entry and select Delete.
Table 3. Operational server checks
Prerequisite check Description Resolution
SOAP port verification This check determines if the required port numbers for SOAP are available. Both of the required port numbers, 8879 and 8880, must be available. Ensure that both ports 8879 and 8880 are available for use by SOAP.