Print this page.  If your browser doesn't allow JavaScript, right-click this page and choose Print from the popup-menu.        
Installing Mimer SQL on Linux
Category: System Management

This article describes the installation procedure for Mimer SQL on Linux. In general, the information herein is valid for Linux and Unix distributions of Mimer SQL from version 9.1, but its focus is Linux and Mimer SQL 10.

The Mimer SQL software installation is expected to be completed in less than a minute, and creating the initial data dictionary and starting the database server will only take just a little longer.

For Linux platforms the software package is available both as a tar archive file and an RPM file. The TAR installation is the most common one, and also the one that is used for all UNIX platforms.

To provide for a complete and proper easy-to-use installation, the procedure when installing Mimer SQL is doing all needed installation parts automatically. This includes updates to operating system locations, such as /usr/bin, /usr/lib and /etc. For example, the following tasks are handled:
  • TCP/IP settings for Mimer SQL client/server access (/etc/xinetd.d),

  • autostart settings for Mimer SQL databases (/etc/init.d),

  • desktop menu items (/etc/xdg),

  • system wide Mimer SQL database catalog (/etc/sqlhosts),

  • system wide ODBC data source catalog (typically /etc/odbc.ini and /etc/odbcinst.ini),

  • system wide Mimer SQL man-page setup (/usr/man or /usr/share/man, and

  • easy access for Mimer SQL programs and libraries (/usr/bin and /usr/lib).

Note! To achieve this, the installation requires sudo access, or it has to be executed as root. This includes execution of the rpm command, or the miminstall command of the tar package, and also when using the dbinstall command that creates an initial database.


When using the RPM package, the installation is predefined to a default setup.

The tar installation procedure allows for a more flexible installation, but other other hand, it requires some answers to questions. The questions are given with explanations to each installation step and with default options.

The Mimer SQL distribution contains the following:

  • Tools, libraries, examples, man-pages, etc.

  • A complete documentation set in PDF format. Online documentation, in PDF or HTML can be obtained here at the Documentation page.

  • An ODBC Driver, available in the libmimodbc shared library. This driver can be used for direct access to a Mimer SQL database, or it can be used with a third party ODBC Driver Manager. See the article unixODBC – An open source ODBC Driver Manager for an example).

  • A JDBC Driver, type-4, written in 100% Java – see JDBC Interface.

  • Various other database APIs like DBI/Embedded SQL and Micro API.

The default installation location is /opt, where a sub directory named according to the package is created. For example, if Mimer SQL 10.1.1A is installed, an installation path like /opt/MimerSQL-10.1.1A is used. This Mimer SQL main directory then contains the following sub directories:
  • bin – contains Mimer SQL tools, and other executable files.

  • DbVisualizer – contains all resources for the DbVisualizer tool that is bundled with Mimer SQL. Please note that an even more powerful version, DbVisualizer Pro, that can be purchased from The DbVisualizer Pro features are enabled by installing a license key file.

  • doc – contains Mimer SQL documentation.

  • examples – contains example files.

  • include – contains various header files that may be needed when developing with Mimer SQL.

  • lib – contains library files.

  • lib32 – contains 32-bit libraries for execution of 32-bit applications. (Only available in installation packages for 64-bit platforms).

  • man – contains Mimer SQL man pages.

  • misc – contains various additional files, like SQL scripts for deprecated schemas and desktop menu system resources.

Unpacking and installing the software

As mentioned above, you can choose to install Mimer SQL from a tar archive file or an RPM file. See below for the details.

Unpacking and installing the TAR distribution

This is the procedure to follow when using a tar format distribution of Mimer SQL.

Unpack the distributed tar archive by using a standard tar extract command, for example:

# tar xvf MimerSqlX64Linux1010d.tar

Flags used:
'x' means extract

'v' means verbose

'f' means that the file name that follows is the one that should be used.

A subdirectory named according to the distribution has now been created in the current directory, holding the tar archive contents. There, the miminstall command is available, which should be executed to install the Mimer SQL software. Simply execute the command as follows:

# ./miminstall

During the miminstall session the license agreement should be accepted, a temporary location for unpacking should be chosen, and then the location for the Mimer SQL software in the file system should be specified.

The tar installation can also be executed in silent mode, mainly aimed for embedded installations.

Note! The miminstall command can be executed in a non-operational mode by using the '-n' option, meaning it only prints information about the installation steps without performing them.

Unpacking and installing an RPM distribution

This is the procedure to follow when using an RPM distribution of Mimer SQL.

When using RPM, installed files are fully maintained by the RPM package manager. RPM will keep track of all files installed by RPM, and it will also check that all dependencies to system libraries are available and up-to-date.

To get a short description of an RPM file before installing it, you can use the following command:

# rpm -qpid MimerSQL-10.1.0D-10837.x86_64.rpm

An example installation using RPM could be as follows:

# rpm -i MimerSQL-10.1.0D-10837.x86_64.rpm

From the Mimer SQL point of view, the RPM installation is a silent install. RPM can be instructed to be "very verbose" by using the '-ivv' switch instead of '-i', which will display the information known by, and performed by, RPM for the installed package.

You can run the installation procedure without actually installing anything by using the "--test" option as in the following example:

# rpm -i --test MimerSQL-10.1.0D-10837.x86_64.rpm

If an older version of an RPM-package is already installed when a new RPM-package is available, the upgrade switch can be used. See the following example:

# rpm -U MimerSQL-10.1.0D-10841.x86_64.rpm

Note! An upgrade can only be done if the only difference in the package name is the package revision number, in this case "10841". Otherwise the new product is installed using the '-i' option, and then the old package is removed (see below).

To get a listing of all installed rpm packages the "-qa" switch is used. Combined with grep the following command will display all Mimer SQL packages installed with the rpm command:

# rpm -qa | grep -i mimer

To get details of the package and to get instructions on how to continue, including how to create a database using the dbinstall, use the following command:

# rpm -qid MimerSQL-10.1.0D-10837

For further details about RPM, see the corresponding man-page, or visit the RPM Documentation page.

Installing RPM file on Ubuntu/Debian

For platforms that use the Debian installation format, the alien tool can be used to install the RPM distribution, or to convert it to a Debian installation package.

For example, on an Ubuntu system the following steps can be used:
  • Use the following command to install the alien command (if it does not already exist on your system):

    sudo apt-get install alien

  • Use the following command to install the RPM distribution file:

    sudo alien -i MimerSQL-10.1.0D-10837.x86_64.rpm

  • Use the following command to convert the RPM distribution file, and then install the created Debian package:

    sudo alien MimerSQL-10.1.0D-10837.x86_64.rpm
    sudo dpkg -i package_file.deb

Running several Mimer SQL versions in parallel

If it is desirable to run two or more Mimer SQL versions in parallel on a host computer, this is fully feasible, but the following must be regarded:
  • If installing an RPM version while a tar installation is already made, it may be the case that host global configuration files such as /etc/sqlhosts for database registration and /etc/mimerkey for the license keys are reinstalled. In this case the original files are renamed to have the file name extension '.rpmsave'.

  • If two packages of exactly the same version is installed, only one can be installed using RPM, and the tar installation cannot use the default /opt location.

  • If installing using RPM, the installation will always put itself as the preferred installation, located via /usr/bin and /usr/lib, for example. This is an installation option if installing with tar. The commands mimlink and mimunlink can be used to adjust this after installations are done, but please note that it is essential that there is an installation linked to these locations since various default settings are pointing there.

Creating an initial database

Once you have installed the software you can build a Mimer SQL database by using the dbinstall command.

As mentioned before, the dbinstall command requires sudo access, or must be executed by root. If not started from a privileged shell sudo password will be asked for:

# dbinstall
This operation needs root access. Using sudo...
root's password:
Mimer SQL Version 10.1.0, Database Server Installation Procedure...

During the dbinstall session, database name, database location, and password for the database administrator (i.e. SYSADM) should be specified. There will also be options for installing example environments, etc. When the session is completed, a fully operational database is available - enabled for client/server access over TCP and automatic start at reboot.

Note! dbinstall creates all system databanks in the given database server home directory. In a production system it is recommended that the SYSDB, TRANSDB and LOGDB files are located on separate disks due to performance and reliability reasons. You can read more about this in the Mimer SQL System Management Handbook found in the Mimer SQL Documentation Set.

Upgrading an existing database

If you are upgrading an existing database from an earlier version of Mimer SQL, please see the Mimer SQL Release Notes for detailed information. This document is provided within each Mimer SQL distribution package. In short the steps are as follows:
  1. Install the new Mimer SQL version in parallel with your existing Mimer SQL.

  2. Stop the database.

  3. Make sure the new Mimer SQL version is the one accessed, and run the sdbgen -u database command.

  4. Start the database with the database server program from the new Mimer SQL version.

Uninstalling the software

The commands described below, mimuninstall and rpm -e, will remove the given software installation, but any databases using the installation will remain intact. Since databases may contain valuable data, the removal of databank files is not made under cover.

If a database, and its databank files, is going to be removed, use the dbuninstall command. When executed, a question will be raised asking if specified database should be removed, i.e. permanently deleted.

# dbuninstall database_name

Removing a TAR installation

To remove an installation that was installed using the miminstall command, use the mimuninstall command as follows:

# mimuninstall /opt/MimerSQL-10.1.0D

Removing an RPM installation

To remove an installation installed using RPM, use the following RPM command:

# rpm -e MimerSQL-10.1.0D-10837

For more detailed information printout when uninstalling, the -ev or -evv options can be used.


We recommend that you use RPM for Linux installations. RPM will check and verify all dependencies for the package it is installing.

However, by using a tar installation, which is the method available for all Unix platforms, you can manage the layout of the Unix system more flexibly according to your requirements.

For more information on RPM, see

It should also be mentioned that there are some Linux/Unix specific appendixes in the System Management Handbook part of the Mimer SQL Documentation Set, that may be worth reading.
Last updated: 2013-05-21


Powered by Mimer SQL

Powered by Mimer SQL