Installing Mimer SQL on Mac OS X
Tools and Interfaces
This article will describe the simple procedure of getting started with Mimer SQL on Mac OS X.
Installation of the Mimer SQL software
The installation starts by downloading the Mimer SQL product for Mac OS X from the Mimer SQL Download page.
Usually the zip package is wrapped up automatically when downloaded to Mac OS X and also the Installer application recognizes the pkg file and executes it. So, just by downloading the package we get to the following welcome screen:
As you can see to the left in the screen shot you will get into a series of steps to complete the software installation. Mainly, you take part of the information that will be provided on the screen and carries on to the next step by clicking the Continue button. If suitable, when selecting destination, use the default value
/Applications for the folder to install into.
If the installation doesn't start automatically, just click on the zip file to wrap it up, and then click on the pkg file to launch the Installer application.
Note! If you re-install the same version of Mimer SQL as installed earlier it will overwrite the current one. If you install a newer version, i.e. with a higher version, they will be installed in parallel, and the most recent installation will be the one used by default. To continue using the old version the PATH and DYLD_LIBRARY_PATH environment variables must be set to point out the installation in question. See the man pages for the
mimuninstall commands for information on how to deal with parallel installations.
Create a Mimer SQL database
When the software is installed you will find the Mimer SQL installation folder as
/Application/MimerSQL-9.2.4D, or corresponding.
In this directory you can find three applications, Mimer SQL Database Install, Mimer SQL Database Admin and DbVisualizer.
To create a Mimer SQL database, launch the Mimer SQL Database Install application.
You should choose a database name and a password for the SYSADM user - these fields are required. The SYSADM user is the System Administrator for the database you are going to create, i.e. the user that can do administrative tasks, create other users and delegate access rights and privileges. This means that this password is important - it should be kept secret and it should be remembered!
In the screenshot above, the database name "mimdb" has been chosen. The rest of the fields and options have the default values. In this state you are ready to click the Create button to continue with the installation.
Note!If the computer has several disks, and if you are creating a production system, it is advisable to spread the databanks on those disks. The LOGDB databank file should be given highest priority to get a separate disk. This is due to database recovery reasons in case of a disk failure. If there are three disks or more available, the TRANSDB databank file should be placed on the fastest disk for performance reasons. For details, see the Mimer SQL Documentation for details on databanks and their placement. Look for The Database Environment section in the System Management Handbook part.
When the database is created, the database server is started for the database automatically, which means that the database is opened for multi-user access.
When the database is created successfully the other application in the installation folder, Mimer SQL Database Admin, can be launched. This application can be used to administer the database servers that you have.
In this session the state for the database server named
mimdb has been asked for.
Connecting to the database
One of the easiest ways to get a connection to the created database is to open up a Terminal application window and launch the Mimer BSQL program. The Terminal application is found in
/Applications/utilities. Launch it from the Finder application.
At the command line prompter, write
bsql followed by the database name for the database that you just created, and login using the SYSADM user and the corresponding password.
# bsql mimdb
SQL>select cast(object_name as char(25)), object_type from system.objects
SQL&where object_type = 'BASE TABLE';
OBJECTS BASE TABLE
SYNONYMS BASE TABLE
SCHEMATA BASE TABLE
USERS BASE TABLE
DATABANKS BASE TABLE
TABLES BASE TABLE
VIEWS BASE TABLE
TABLE_CONSTRAINTS BASE TABLE
REFER_CONSTRAINTS BASE TABLE
KEY_COLUMN_USAGE BASE TABLE
CHECK_CONSTRAINTS BASE TABLE
COLUMNS BASE TABLE
DOMAINS BASE TABLE
DOMAIN_CONSTRAINTS BASE TABLE
TABLE_PRIVILEGES BASE TABLE
COLUMN_PRIVILEGES BASE TABLE
USAGE_PRIVILEGES BASE TABLE
MODULES BASE TABLE
ROUTINES BASE TABLE
SPECIFIC_NAMES BASE TABLE
PARAMETERS BASE TABLE
SEQUENCES BASE TABLE
TRIGGERS BASE TABLE
TRIGGERED_COLUMNS BASE TABLE
CHAR_SETS BASE TABLE
COLLATIONS BASE TABLE
TRANSLATIONS BASE TABLE
OBJECT_OBJECT_USE BASE TABLE
OBJECT_COLUMN_USE BASE TABLE
COLUMN_OBJECT_USE BASE TABLE
SOURCE_DEFINITION BASE TABLE
AST_CODES BASE TABLE
AST_SOURCES BASE TABLE
SERVER_INFO BASE TABLE
SQL_LANGUAGES BASE TABLE
FIPS_FEATURES BASE TABLE
FIPS_SIZING BASE TABLE
API_FUNCTION BASE TABLE
MESSAGE BASE TABLE
SEVERITY BASE TABLE
SQL_CONFORMANCE BASE TABLE
TYPE_INFO BASE TABLE
TABLE_TYPES BASE TABLE
LEVEL2_RESTRICT BASE TABLE
LEVEL2_VIEWCOL BASE TABLE
LEVEL2_VIEWRES BASE TABLE
ONEROW BASE TABLE
MANYROWS BASE TABLE
EXEC_STATEMENTS BASE TABLE
STATEMENT_DESCRIPTORS BASE TABLE
STATEMENT_ROUTINE_USE BASE TABLE
USER_DEF_TYPES BASE TABLE
COLLATE_DEFS BASE TABLE
53 rows found
A more sophisticated access to the database can be achieved by using the DbVisualizer application. See the article Mimer SQL and DbVisualizer using JDBC on Mac OS X on how to use this powerful database tool.
To connect to the database using ODBC, please see the articles Using Mimer SQL with iODBC on Mac OS X and Apache – PHP &ndash Mimer SQL on Mac OS X.
To be able to connect to remote database servers, you need to add an entry for each remote database in the
/etc/sqlhosts database registration file. See the man page for the
mimhosts command for details on how to do this.
Note! You may have to consider the article Firewall issue on Mac OS X when your database server is going to be acessed by remote database clients.
Last updated: 2005-09-30