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

Mimer SQL Engine 9 is available for several Unix and Linux flavors. This document describes the installation procedure for these platforms, and shows how simple and clear the procedure is.

You can usually complete the software installation in less than a minute, and creating the initial data dictionary and starting the database server will only take a little longer.

For Linux platforms the software package is available both as a tar archive file and an RPM file. For more information on RPM, go to

For all other Unix platforms, the Mimer SQL Engine software is distributed in a tar archive file.


The installation procedure for Mimer SQL Engine 9 on Unix/Linux is performing all needed installation parts automatically. This includes automatic database server restart at reboot, networking management, license key management, etc.

The installation asks you to specify a few parameters and also provides you with default parameters if you wish to use them. It describes all the steps that are taken during the procedure and tells you about tools and examples to make it easy for you to continue. You can also run the installation in silent mode if you wish.


The Mimer SQL Engine 9 distribution contains the following:

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

  • A complete documentation set in PDF format (use Adobe Acrobat Reader, it can be downloaded for free from Adobe).

  • ODBC Driver, available in the libmimer shared library (it requires a third party ODBC Driver Manager. See the article unixODBC – An open source ODBC Driver Manager for an example).

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

During a default installation, tools, libraries and man pages are linked to dedicated system locations under the /usr directory. This gives everyone automatic access to distributed files.

The default installation location is /opt where a sub directory named according to the package is created. For example, if you install Mimer SQL Engine 9.1.3A, you get the installation path: /opt/MimerSQL-9.1.3A.

In turn, the Mimer SQL Engine directory, contains the following sub directories:
bin – contains Mimer SQL tools, exe files, etc.

doc – contains Mimer SQL Engine documentation

examples – contains example files

lib – contains library files

man – contains Mimer SQL Engine man pages

Unpacking and Installing the Software

As mentioned above, you can choose to install Mimer SQL Engine 9 from a tar archive file or an RPM file.

Unpacking and Installing the tar Distribution

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

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

# tar xvf MimerEngineAix913a.tar

Flags used:
'x' means extract

'v' means verbose

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

You can now use the miminstall command, available in the current directory, to install the Mimer SQL Engine software.

Note: you must execute the command as root since it will suggest recommended updates to operating system locations, such as /usr/bin, usr/man, /usr/lib and /etc (where TCP/IP settings for Mimer SQL Engine will be added).

Tip: the miminstall command can be executed in non-operational mode by using the '-n' option. When using this option, miminstall only prints information about the installation steps without performing them.

Simply execute the miminstall command as follows:

# ./miminstall

During the miminstall session you accept the license agreement and specify the location for the software in the file system.

Unpacking and Installing an RPM Distribution

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

Note: when using RPM, installed files are fully maintained by the RPM package manager. RPM will control all files installed by RPM. Because of this, it is possible that parallel installations of Mimer SQL, e.g. earlier versions installed with tar, may be slightly disrupted with regard to host global files. That is, when installing with RPM, so called configuration files will be renamed to contain the file name extension '.rpmsave'. Such configuration files are /etc/sqlhosts for database registration and /etc/mimerkey for the license keys, both of which are crucial for a proper operation of a Mimer system. Instead, default versions of these files will be installed. This is only a problem if using several versions of Mimer SQL in parallel.

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

# rpm -qpid MimerEngineLinux913a.rpm

An example installation using RPM could be as follows:

# rpm -i MimerEngineLinux913a.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 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 MimerEngineLinux913a.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 MimerEngineLinux913a.rpm

To get a listing of all installed rpm packages, use the following command:

# rpm -qa

To get details of the package and to get instructions on how to continue (i.e. execute the dbinstall command), use the following command:

# rpm -qid MimerSQL-9.1.3A-1

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

Creating an Initial Database

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

You must execute the dbinstall command as root, as follows:

# dbinstall

During the dbinstall session you specify the database name, database location, password for the database administrator (i.e. SYSADM), installation of example environments, etc.

When you have successfully completed the dbinstall session the database is in a fully operational state, enabled for client/server access over TCP and automatic start at reboot.

If you are upgrading an existing database from an earlier version of Mimer SQL, please see the How To Upgrade to Mimer SQL 9.1 for detailed information.

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 System Management Handbook found in the Mimer SQL Documentation Set.

Uninstalling the Software

The commands described below 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 possible using any single key operations.

If you want to remove databank files, use the mimdbfiles command to locate the databank files before you manually remove them.

Removing a tar Installation

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

# mimuninstall /opt/MimerSQL-9.1.3A

Removing an RPM Installation

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

# rpm -e MimerSQL-9.1.3A-1


We recommend that you use RPM for Linux installations. RPM will check and verify all dependencies for the package it is installing. That is, Mimer SQL Engine 9 may, for example, need a specific lowest version of a system library or depend on a Unix system command; RPM will verify that these parameters are fulfilled.

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

Last updated: 2005-12-05


Powered by Mimer SQL

Powered by Mimer SQL