Extracting the Db2 Big SQL installation files

Extract the Db2® Big SQL installation files that are needed to do an offline install of Db2 Big SQL.

Before you begin

  • You must acquire the Db2 Big SQL installation tarball file from IBM® Passport Advantage®. See Obtaining Db2 Big SQL for details.
  • If you are doing a fresh install and not a migration, ensure that Cloudera Data Platform (CDP) is installed.
  • Ensure that you followed the steps in Requirements for installing Db2 Big SQL.
  • If you install Db2 Big SQL as the non-root user, preface the instructions with sudo, where the instruction would normally require the root user. For more information about non-root access, see Configuring non-root access to Db2 Big SQL.

About this task

Transfer the tarball file to a local intranet repository server that is accessible from all candidate Db2 Big SQL nodes. The tarball contains the top-level Db2 Big SQL RPM that is named IBM-Big_SQL-<Db2 Big SQL version>-<OS><version>-<platform>.rpm (for example, IBM-Big_SQL-7_1_0_0.el7.x86_64.rpm), and the remaining Db2 Big SQL RPMs.


  1. Extract the contents of the tarball.
    For example:
    tar -xvf <tarball_name>.tar.gz
    The contents of the tarball are extracted to the directory <download directory path>/IBM-Big_SQL/packages/IBM-Big_SQL/<OS><version>/<platform>/<BigSQL_version>. For example, /tmp/IBM-Big_SQL/packages/IBM-Big_SQL/RHEL7/x86_64/
  2. Update the permissions on the Db2 Big SQL top-level RPM to enable read and write.
    For example:
    chmod 644 /tmp/IBM-Big_SQL/packages/IBM-Big_SQL-7_1_0_0.el7.x86_64.rpm
  3. Copy the Db2 Big SQL top-level RPM to the local repository server location <your.local.repository.server.document.root>/repos/bigsql.
    For example:
    cp /tmp/IBM-Big_SQL/packages/IBM-Big_SQL-7_1_0_0.el7.x86_64.rpm /var/www/html/repos/bigsql/
  4. Copy the remaining Db2 Big SQL RPMs from the extracted tarball to the local repository server location <your.local.repository.server.document.root>/repos/bigsql.
    For example:
    cp /tmp/IBM-Big_SQL/packages/IBM-Big_SQL/RHEL7/x86_64/*.rpm /var/www/html/repos/bigsql/
  5. On the repository server, run the createrepo command to initialize the repository:
    createrepo /var/www/html/repos/bigsql
  6. If the web server isn't already started, start it. If you use Apache HTTPd, start it by using either of the following commands:
    apachectl start
    service httpd start

    Ensure that any firewall settings allow inbound HTTP access from your cluster nodes to the local repository server.

  7. Test that your local repository is running Apache, can be accessed, and files browsed by typing the following in a web browser:

    If you see all of the files in the browser, Apache is running and the files are present on the repository server. If you do not see all of the files or there is another error, you must resolve the problem before you continue with the next step.

  8. On the target install node for the Db2 Big SQL Head, create the repo file IBM-Big_SQL-7_1_0_0.repo in the /etc/yum.repos.d/ directory, specifying your local repository in baseurl.
    vi /etc/yum.repos.d/IBM-Big_SQL-7_1_0_0.repo
    baseurl=http://<local repository server fully qualified domain name>/repos/bigsql
  9. Install the Db2 Big SQL top-level package:
    yum install IBM-Big_SQL-7_1_0_0
    Note: You must install by using the repo file and not directly by using the RPM.
  10. If you are installing Db2 Big SQL as a non-root user, change the ownership of all files and directories in the /usr/ibmpacks/IBM-Big_SQL/ directory to <non-root user name>:hadoop:
    chown -R <non-root user name>:hadoop /usr/ibmpacks/IBM-Big_SQL/

What to do next

If you are installing Db2 Big SQL on a cluster that does not have access to the internet, manually install the Cloudera Manager python client. Otherwise, install Db2 Big SQL.