Database Configuration

Server Management

OpenBase Manager provides options for managing server information. This includes Network access, License information, and Security. These settings are accessed by clicking File on the OpenBase Manager menu bar, selecting the Server option, and then Configure Local Host.

Figure 2: OpenBase Manager Server Configuration

Network Access

Network settings allow you to specify your local ipaddress and to which local network your database server belongs. Both are important to help people on your network find the databases that they are looking for.

For each local database network there is a process called infoserver which runs at a single central location. Please choose one computer on your network with OpenBase installed to be your database infoserver. Computers that share the same infoserver will appear on the same local network in the OpenBase Manager.

Computers which are used as production web servers should point to themselves. This minimizes dependencies between computers.

If you have several workgroups which manage independent databases, you can create several “virtual” local database networks on your local network by assigning a different infoserver to each group. This will ensure that each group will only see their own databases by default.

For DHCP customers it is important to use “localhost” for the hostname and “” as both the ipaddress and the infoserver address. This will enable the ipaddress of the computer to be dynamically assigned while allowing you to run local databases. Databases on computers that receive dynamic ipaddresses from DHCP can not be accessed from other computers. Network accessible database servers should always have static ipaddresses.

Select this option to allow access to the network by this host.

License Install Wizard

Click this button to run the License Install Wizard and enter your licensing information. You will be prompted to enter your serial number and authorization code. It is recommended that you copy this information directly from the email you received from OpenBase when you purchased your license.


When you select a host category, the OpenBase Manager checks the host security. It is recommended that you set a host password to make sure that only authorized users can copy, move, add and delete databases. If you are concerned about security you may also want to set the user passwords for each database.

To set a read password, click on the Read Password lock icon and enter the password. Enter the password a second time to verify.

To set a host password, click on the Host Password lock icon and enter the password. Enter the password a second time to verify.

To change the password, click on Read Password or Host Password and enter the new password and verification.

To remove the password, click on Read Password or Host Password and then click Continue without entering any password.

Safe SQL Mode

Safe SQL Mode makes the server run more defensively to protect users from misbehaving clients and wasted resources. This is especially valuable when some applications allow users to specify their own queries. Sometimes leaving out a join constraint can multiply a result and turn thousands of records into an unintended result of tens of millions of result rows. When Safe SQL Mode is checked on, it checks the SQL to make sure all joins exist and have indexed constraints before they are evaluated.

Configuring the Database

The OpenBase Manager provides controls for renaming databases and/or moving them between host computers, as well as configuring other database preferences.

Selecting a database and clicking the configure button will bring up the configure database window. From this window you can configure your database. Click on the desired tab and enter the preferences for the database.

Figure 3: Configuration: General Settings

Change the name of the database by clicking in the Database Name field and entering the new name.

Changing the Run-on-Host popup will physically move the database from one host to another (this is not supported in Windows).

To make your database automatically start when the specified computer boots up, click the Start Database at Boot check-box.

Enable the Encrypt Communications by checking the box.

Enabling Change Notification instructs the server that you want applications to be notified when changes to the database take place. This allows clients to automatically update screen displays when database information changes. OpenBase Manager Data Viewer and RADbrowser both support this feature.

To ensure that the database cannot be deleted accidentally, click the check-box next to Disable Delete.

Select the desired display color, if any, and add a short description of the database. On the OpenBase Manager window the database name will appear in a bubble of the selected color.

Figure 4: Configuration: Localization Settings

On the Localization tab, set the encoding that the database will use internally for representing data. Latin encoding is recommended and will work with most single-character languages. For two byte character sets we recommend that you try either Japanese or Unicode Extended encoding. We recommend that you use the default unless your language requires another encoding.

Note: Changing this setting will not convert existing data. Select the desired international sort order and date/time preferences.

Date, Time, and Money

Specifying preferences for date, time and money will change the default format for databases on the specified host. If you would like to display several different formats at the same time in your program, you will need to change these formats programmatically. The datetime type only uses the default NeXT calendar date format, so it is not listed on this panel.

Localized Sorting

Since different languages have different characters and sorting rules, the international sort order section provides a way to specify upper and lower case letters in the natural sort order. The top text field should contain the set of lower case letters in order of their importance and the bottom text field should contain capital letters in the same order. Letters that are not specified in this list will assume their ASCII value and in a sorted list will appear after the letters in the text fields.

Figure 5: Configuration:KeysSettings

The unique key generation system in OpenBase allows you to synchronize or mirror databases by ensuring that the same key is not used twice. The keys are used to identify the records that are inserted by clients and therefore must be unique. If they are not unique, a second insertion with the same key will violate the rules and fail.

When one server is involved, this is not such a big problem. When a client inserts a new record, OpenBase ensures that each new key is unique and not given out twice. Client applications do not need to use the keys immediately since the key generator will always continue with the next value in the sequence.

However, when two or more servers are involved, this becomes a much more complex problem. In the case of mirroring/clustering, servers are normally in contact with one another all the time and could coordinate the vending of unique keys. But in the real world, there are often breakdowns in communication, and so the unique key generation has to be able to operate independently to avoid downtime. This is especially true for synchronization, where communication is triggered by a synchronization event, and completely offline the rest of the time. The OpenBase unique key generation is designed to solve this problem by making sure that unique keys are generated in such a way that no client receives the same key.

How Unique Key Generation Works

OpenBase generates keys using a multiplier and a unique identifier assigned to each database. The identifier must be unique and less than the multiplier. Each server increments keys by the multiplier plus the database id. So a database with an ID of 1 and a multiplier of 10 would generate keys 11, 21, 31, 41. An ID of 2 would generate keys 12, 22, 32, 42. This allows servers to operate independently, while generating keys which do not conflict.

Configuring Unique Key Generation

Clicking the Activate Distributed Key Generation check-box tells the server that it needs to generate globally unique keys. This is necessary when you have several databases that need to be synchronized periodically. Each database will generate its own set of keys. Enter a unique number for this Database ID. You will need to do this for all databases in your synchronization group.

Figure 6: Configuration: Mirroring Settings

If mirroring of the database is desired, click the box next to the desired options and enter the settings.

OpenBase Database Clustering / Mirroring

The OpenBase clustering/mirroring mechanism can be setup to offer one-directional or bi-directional mirroring of database servers.

What we mean by this is that you can have two databases residing on separate servers that are exact duplicates. When transactions are executed on one, they are also executed on the other. It is also noteworthy that OpenBase's mirroring technology allows the databases to operate independently of one another when the connection between the databases goes down.

The OpenBase mirroring mechanism is also extremely flexible in that it also allows you to optionally exclude certain SQL statements, such as deletes, from traveling between servers. Database clustering/mirroring can happen across multiple platforms, so you can combine MacOS X, Solaris and Linux systems in your cluster. It is not yet available as an option on Windows systems.

It is recommended that you use the MacOS X tools for setting up a pair of mirrored servers. However, if you do not have access to the MacOS X tools or you need to mirror more than two servers, the instructions below will help.

See OpenBase Advanced Admin (8700) for additional information and examples of setting up mirroring.

Figure 7: Configuration: Backup Settings

OpenBase comes with an online backup mechanism which allows you to schedule compressed copy of the database and/or complete data dumps of the database to timestamped ASCII files. You specify when you would like the backup to take place and where the backup files should be placed.

Click the box next to the desired database backup options to select it. Enter the path for the backup. Set the schedule for the backup. Options are

Every Day or a specific day of the week. Select the time for the backup to run.
The backup schedule is read each day around midnight and backups are scheduled for the following day.

When setting the backup schedule for your databases it is very important that you specify a valid pathname (with no spaces). Without a valid path the backup will not work.

Figure 8: Configuration: Automatic Settings

You can set the schedule for stored procedures to automatically run. OpenBase Manager has several common stored procedures: BackupDatabaseFile, BackupDatabaseToASCII, CleanupDatabase, and RebuildDatabase. New procedures may be added by clicking the New button and selecting the procedure from the list of available procedures to add it to the list in the window. Click on the procedure in that list to enter its parameters.

Once a procedure is selected, you can enter the following specific parameters for that procedure:

Execute Schedule None, On Event, Every Minute, Every Hour, Every Day, Every Week, Every Month

Event None, Startup, Shutdown, Login, Logout

Minute of Hour If Every Hour or Every Day is chosen this field is active. Select the number of minutes after the hour that the procedure is to run.

Hour of Day If Every Day is chosen this field is active. Select the hour that the procedure is to run. Select the minutes in the Minute of Hour field.

Day of Week If Every Week is chosen this field is active. Select the day of the week for the procedure to run. Also select the time in the Minute and Hour fields.

Day of Month If Every Month is chosen this field is active. Select which day of the month (1 - 31) that the procedure is to run. Also select the time in the Minute and Hour fields.

For example, if you select the Cleanup Database procedure and set the Execute Schedule to On Event and select the Event Shutdown, this configures the server to go through a database cleanup process before stopping the database under normal conditions. This reduces your start-up time if the database needs to do recovery.

Figure 9: Configuration: Expert Settings

Connection Timeouts Enter the number of seconds for timeout on idle transactions and idle connections.

Specify Static TCP/IP Port Click in the field and enter the specific IP address for the Static TCP/IP Port if you do not want the IP address to by dynamically assigned.

External SQL Log Tells locally running servers to log SQL commands to a log file located in the directory specified in the Log File field. The generated log file, combined with a backup of the database, can be used to roll forward backup databases in case of hard disk failures.

Click the box to select it and enter the path of the log file.

Diagnostic Mode Click the box to turn on logging for debugging purposes.

When all the parameters have been set, close the window. You will be prompted to either Cancel, Close without Save, or Save Changes. Click Save Changes to save all the parameters entered.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License