When installing DB2 11.1 on Ubuntu Server 16.04.1 LTS, db2prereqcheck does not check to see whether the libaio1 package has been installed on the system.
This issue is present in both the GA code as well as the current beta code (build: s1607131900)
This results in a situation where DB2 installs properly, but when you try to start an instance, you get the error:
$ db2start
db2start: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory
The db2val command does not appear to properly validate the environment either - it reports that validation completed successfully, even though it produces the following output:
$ db2val
DBI1379I The db2val command is running. This can take several minutes.
DBI1335I Installation file validation for the DB2 copy installed at
/opt/ibm/db2/V11.1 was successful.
/home/db2inst1/sqllib/adm/db2start: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory
DBI1339I The instance validation for the instance db2inst1 was
successful.
/home/db2inst1/sqllib/adm/db2stop: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory
DBI1343I The db2val command completed successfully. For details, see
the log file /tmp/db2val-160812_162022.log.
Here is the output from the file mentioned in STDOUT:
$ cat /tmp/db2val-160812_162022.log
Installation file validation for the DB2 copy installed at "/opt/ibm/db2/V11.1" starts.
Task 1: Validating Installation file sets.
Status 1 : Success
Task 2: Validating embedded runtime path for DB2 executables and libraries.
Status 2 : Success
Task 3: Validating the accessibility to the installation path.
Status 3 : Success
Task 4: Validating the accessibility to the /etc/services file.
Status 4 : Success
DBI1335I Installation file validation for the DB2 copy installed at
/opt/ibm/db2/V11.1 was successful.
Installation file validation for the DB2 copy installed at "/opt/ibm/db2/V11.1" ends.
Instance validation for "db2inst1" starts.
Task 5: Validating symbolic links in the instance directory.
Status 5 : Success
Task 6: Validating instance file ownership and permission.
Status 6 : Success
Task 7: Validating the accessibility to the /etc/services file.
Status 7 : Success
Task 8: Starting DB2 instance "db2inst1".
Status 8 : Success
DBI1339I The instance validation for the instance db2inst1 was
successful.
Instance validation for "db2inst1" ends.
Task 9: Stopping DB2 instance "db2inst1".
Status 9 : Success
DBI1343I The db2val command completed successfully. For details, see
the log file /tmp/db2val-160812_162022.log.
#Db2