Release notes - IBM i2 iBase 9.0.2

IBM® i2® iBase 9.0.2 is available.



IBM i2 iBase is a database for investigations. It provides capabilities to configure a data store, and capture and analyze data, all in a controlled environment. In addition, it integrates fully with IBM i2 Analyst's Notebook.

Important: IBM i2 software at version 9 is not compatible with earlier versions of i2 software. Upgrading directly is not supported. To install IBM i2 Intelligence Analysis software at version 8.9 or later, you must first uninstall all of your existing i2 software, then install the new versions. In addition, due to the changes in this release, any custom plug-ins that are present in your system might need recompiling, contact the provider of any custom plug-ins before you do the upgrade.

Release contents

The following chargeable components are compatible and available for use with iBase 9.
Program Feature Description
IBM i2 iBase Designer Design and administer iBase databases and security files.
IBM i2 iBase Database Replication Use SQL Server merge replication to enable distributed use of iBase.
IBM i2 iBase Geographic Information Systems Interfaces Interface with Geographic Information Systems products (excluding Google Earth, which is provided by a plug-in to Analyst's Notebook).
IBM i2 iBase Plate Analysis Manage and analyze ALPR (Automatic License Plate Recognition) data that is stored in an iBase database.
IBM i2 iBase Geographic Information System Interfaces comprises interfaces to the following Geographic Information System products.
GIS product Supported versions
Esri ArcGIS for Desktop 10.4.1, 10.5.1, 10.6.0
Pitney Bowes MapInfo Professional 15, 16, 17 and 2019 including 32-bit and 64-bit versions where applicable
Northgate Public Services XD 2.7.1*
* Interface component provided directly by Northgate Public Services

iBase includes the optional Coordinate Extensions feature. The feature uses GEOTRANS v2.4, a product of the National Geospatial Intelligence Agency and US Army Engineering Research and Development Center. Use of GEOTRANS with iBase does not indicate endorsement or approval of iBase by the Secretary of Defense or the National Geospatial Intelligence Agency.


iBase only supports the operating systems and supported software listed in the detailed system requirements. Ensure that existing deployments are upgraded to currently supported versions of all the software required. For more information about the software supported for the current release, see System Requirements.
Note: If your current iBase system contains custom iBase plug-ins that are written in Visual Basic 6, these plug-ins require porting to C# (or another .Net Language) to maintain compatibility.

Release highlights

The following enhancements have been included:
  • iBase in non-tabbed mode can now create records without a datasheet.
  • Selected from pick lists:
    • Now display in alphabetical order.
    • Child pick list values are now only available after a parent selection has been made.
The following APARS are fixed in this release:
  • Cannot log in if user is a member of multiple Active Directory groups. [APAR PO09071]
  • Using commas as decimal separators for numbers is not correctly handled. [APAR PO09079]
  • Parent Pick List is not automatically populated when selecting a child pick list value. [APAR PO09083]
  • Default tab for 'Expand with parameters' is 'general' not 'entity types'. [APAR PO09084]
  • Date attribute changes are only shown on Analyst's Notebook charts for entities but not links. [APAR PO09087]
  • Pick list values appear in grey when editing records from chart surfaces. [APAR PO09095]
  • Deleting an iBase record from an Analyst's Notebook chart doesn't remove the item from the chart surface. [APAR PO09096]
  • Chart items created from iBase records are added in the wrong position. [APAR PO09097]

Compatible companion products

IBM i2 Analyst's Notebook 9.2.2 or later can be used to work with this version of iBase.

System Requirements

For more information about hardware and software compatibility, see the System Requirements.

Installing iBase

For information about installing iBase, see the IBM Knowledge Center Installing IBM i2 iBase.
Note: To install iBase, you must have administrator privileges.

Upgrading iBase

To upgrade iBase:
  • You must be logged in with an account that has administrator privileges for the machine, and permissions to modify the database
  • You should back up any databases before starting your upgrade
  • You should ensure that your any prerequisites are still supported and if not, upgrade these prerequisites before starting your iBase upgrade
  • If your existing deployment is earlier than iBase version 8.9.13, upgrading is a two step process. You must first install iBase 8.9.13 and open all databases in iBase Designer, before you can proceed to the latest version.
    Note: Your database is upgraded when it is first opened in iBase Designer and not as a part of the software installation.

Configuring iBase Geographic Information System Interfaces

You might need to modify the configuration file that specifies the background maps and other mapping session features.
Note: You must have the iBase database role Database Administrator to modify the configuration file. The user "SYSADMIN" in each default security file has this role.
  1. To initialize, open the database in iBase (not in iBase Designer) and select Tools > Initialize Database for Mapping. The necessary extra entries are made to the database to store the mapping configuration information.
  2. To configure an interface, select Format > Mapping > Configurations > New.

iBase Geographic Information System Interfaces installs a default-mapping application configuration file as one of i2_default.mxd, or i2_default.wor, and then copies it to i2.mxd, or i2.wor. If you need to make any changes, then make them to live version of the file and not the default, for example, i2.wor not i2_default.wor.

The configuration files that are used by the application are stored in CSIDL_COMMON_APPDATA\i2\i2 iBase 9\<language>\Mapping.

For more information about CSIDL values, see Microsoft Developer Network CSIDL.

Existing users that are upgrading to ArcGIS 10 need to update the version 9 configuration files by using either i2_default_10.mxd or i2_meters_10.mxd as a template. The files must be updated with any changes that they made to the configuration files for earlier releases of iBase Geographic Information System Interfaces. Then, save the configuration file as i2.mxd.
Note: The default configuration file, i2_default_10.mxd handles data in any units. The configuration file i2_meters_10.mxd uses meters to handle data.

To allow MapInfo users who log on as ordinary users rather than as Administrators to plot data, you must give them write access to the file i2.wor.

The default workspace file, i2_default.wor, expects the data to be in degrees. The product also includes i2_meters.wor. You need to copy the file to i2.wor to use it with data in meters.

You must start MapInfo once for each user of the PC before you use iBase GIS Interfaces because MapInfo initializes only user-specific information. User-specific information includes the custom symbols location the first time a user uses the product.

If you do not follow these steps and then use the iBase GIS Interfaces, you see an error that the application is not responding. MapInfo will then initialize and future operation of the iBase GIS Interfaces work normally.

Configuring iBase Plate Analysis

Information about setting up your installation is available in the IBM Knowledge Center or the iBase Help that is installed with the product. For more information, see Configuring iBase Plate Analysis. If you are using Plate Analysis with iBase Database Replication, then you need to complete these additional steps:
  1. Configure Plate Analysis at the Publisher.
  2. At each Subscriber, configure Plate Analysis: On the Configure page of the Plate Analysis Task Manager, click Optimize.

Virtualization support

iBase is supported on hardware virtualization environments that run any of the operating systems that are listed in the detailed system requirements. When you run in a virtual environment, any issues that can be replicated by IBM in a supported operating system are addressed by using the standard IBM support policy.

Known problems

The most up-to-date source for known problems in iBase is the HTML version of these release notes.
iBase items on the chart surface that were added using iBase 9.0.0 must be re-charted following an upgrade
Items that have been added to an Analyst's Notebook chart using iBase 9.0.0 must be re-added to the chart surface for later versions of iBase to recognize them.

The way that iBase items on Analyst's Notebook charts are identified as originating from an iBase database was changed in iBase 9.0.0. This led to issues with chart items from previous versions of iBase not being identified as iBase items, and issues with items charted from iBase 9.0.0 in other programs that used this method. To prevent further compatibility issues, the identifying information has reverted to the original value in 9.0.1.

"Error occurred in UniToolbox 2" issue on upgraded systems
When iBase systems are upgraded, if the Visual Basic Service Pack 6 runtime package has not been applied, you might see the following error message when opening databases in iBase Designer:
Invalid procedure call or argument
 Error #5 occurred in:
To prevent these messages, apply the Visual Basic Service Pack 6 runtime package:
Spell checking may not work as expected in all languages
The spell checking feature uses Microsoft libraries to provide the dictionaries. For spell checking to detect incorrect spellings, you must install the appropriate language pack for each language you intend to check.
Note: Uppercase words and characters are not included in spelling evaluation, as these are assumed to be acronyms.
Unable to access system information from the iBase Designer about box
Depending on the system, the System information... option on the iBase Designer might not open the system information for your machine.
When the Analyst's Notebook Connector for Esri is installed, Analyst's Notebook can fail to open when IBM i2 iBase items are charted
If items are sent from iBase to Analyst's Notebook with the Analyst's Notebook Connector for Esri installed you might see the following error when Analyst's Notebook opens:
Automation error
The remote procedure call failed.
Error #-2147023170 occurred in:

To avoid this problem, ensure that Analyst's Notebook is open before sending items from iBase.
Updating the chart with merged and restored items
Updating the chart with merged and restored items has some limitations.
  • An item that is merged on the chart in Analyst's Notebook but is not merged in iBase, is not restored by a chart update.
  • The chart update cannot accurately restore items that are soft-deleted and also merged in iBase. For example, A has links to B and B has links to C. Then, A is merged into B and B is merged into C. When those items are restored in iBase, the chart update cannot accurately restore all the entities and links. So, the update might result in some entities or links that are hidden on the chart.
Database Explorer display might be affected by changing display scaling options
Changing the display options to something other than 100% might cause black lines to appear in the Database Explorer window. When you set the display scaling back to 100%, the display returns to normal.
SCC codes and Case Control
SCC control codes and Case Control cannot contain quotations.
Mixed language settings
Mixed language settings between Analyst's Notebook and iBase are not supported.
Extra languages that are supported by IBM i2 Analyst's Notebook are not supported when IBM i2 Analyst's Notebook is used with iBase.
Search 360
User permissions to run the Search 360 Indexer
To run the Search 360 Indexer, you must have permission to run the CmdExec subsystem. To be able to run the CmdExec subsystem, you must either be an administrator with permission, or you must use a proxy account that references a user (through a credential) with suitable permissions.
You can use the proxy account in SQL Management Studio. You need to be granted access to this Proxy for SQL Login.
You can set up access within the Principals tab of the Proxy window in SQL Management Studio, with the following database role:
  • SQLAgentOperatorRole database role on the msdb database.
When you set up access, you can specify the proxy within the Configure Database window.
The proxy can then be specified in the Run As field of the Configure Database window.
PDF documents cannot be indexed in the presence of Adobe PDF iFilters
iBase Search 360 uses Microsoft SQL server to index information. Microsoft SQL server requires a supported iFilter to extract the contents of different documents.

Microsoft provide a iFilter for PDF documents natively on the operating systems that we support, so in new systems, this iFilter can be used for PDF documents. However, if you have had Adobe 9 iFilters installed on the machine that you use to run the index service, you will need to ensure that the system is restored to use the Microsoft PDF iFilter before your PDF contents can be indexed.

Indexing unrecognized document types
If a document submitted for indexing is of a type that the indexer does not recognize, the index is completed but the unrecognized document is skipped.
Search 360 Indexing cannot complete if an embedded corrupted PDF is detected
When documents are attached to iBase items that contain embedded PDFs, the contents of those PDFs are not routinely indexed, however the iFilters do scan embedded documents. As a part of this scanning, if a corrupted PDF is detected, the indexing is stopped. To prevent this issue, and to add the contents of PDFs to the index, attach documents directly to the iBase item and do not embed them (PO07619).
Language region limitations
In language regions other than English, Search 360 has some limitations.
  • Western European Script - Exact and spelled-like matching produces successful results. Sounds-like matching returns less useful results; however, the degree of matching must be evaluated by the user to determine whether these results are usable.
  • Central and Eastern European Script - Exact and spelled-like matching produces successful results. Sounds-like matching is unsupported in these language groups.
  • Arabic Script - Exact matching produces successful results. Spelled-like matching returns less useful results; however, the degree of matching must be evaluated by the user to determine whether these results are usable. Sounds-like matching is unsupported for these language groups.
  • East Asian Scripts - Exact matching produces mixed results. The indexing process that is employed by Search 360 is heavily reliant on word boundaries (for example a space). As these scripts do not reflect the same word boundaries as western scripting, the exact matching gives weak or no results. However, exact matching works in whole character sequences, for example the equivalent to English sentences.
Full text search
After an iBase repository is converted to Unicode, iBase users might see the following error message when they try to rebuild the Full Text Search index.
File 'sysft_i2Catalog' cannot be reused until after the next 
BACKUP LOG operation.
To solve this problem, run an SQL Server Transaction log back up. After the backup, the Full Text Search index rebuilds.
Microsoft Office compatibility
Microsoft Office applications can be used in conjunction with your iBase deployment. However there are some restrictions to the way the following applications are installed:
  • 64-bit versions of Microsoft Office
  • Online versions of Microsoft Office 365 applications
  • Microsoft Access Database engine
For more information about hardware and software compatibility, see the System Requirements.
Citrix dialog captions (11665)
When you run iBase on Citrix, some dialog captions appear with white boxes or spurious characters between the characters in the title. If you are using tabbed mode in iBase, only the first character is displayed in the tab title.
To fix the problem, set the following registry setting to "1":
Note: The captions do not appear in bold as for other dialogs, and do not include the spurious characters.
Focus when you run iBase on Citrix in Seamless Mode (11218)
When you run iBase on Citrix in Seamless Mode, message boxes are displayed by some dialogs upset the focus. iBase cannot regain focus properly and does not respond to mouse clicks or the keyboard within dialogs until you click the main title bar.
To fix the problem, set the following registry setting to "1".
iBase responds to a mouse click within the dialog after the message box is closed.
Note: You can use the fix with only Citrix in Seamless mode. In other environment settings, the registry entry might result in iBase losing focus when the message box is closed, and another application comes to the front.
Custom Icon support
Custom icons are now supported only if they are placed in the Custom images location,
CSIDL_MYDOCUMENTS\i2\i2 Shared\Custom Images\.
CSIDL_MYDOCUMENTS is the file system directory that is used to physically store a user's common repository of documents. The following path is a typical example.
C:\Documents and Settings\username\My Documents
For more information about CSIDL values, see Microsoft Developer Network CSIDL.
To add a custom icon, complete the following steps.
  1. Copy your image file to the Custom images folder, adding copies to both:
    • CSIDL_MYDOCUMENTS\i2\i2 Shared\Custom Images\Screen\Icons
    • CSIDL_MYDOCUMENTS\i2\i2 Shared\Custom Images\Printer\Icons
  2. Update the configuration file in use, with a new line, that includes the icon name a tab-separator and the file name, as shown in the following example.
Title filename
For more information about custom icon support, see the IBM Knowledge Center or iBase Designer help.

When you run large imports, disable alerting jobs to improve performance. This recommendation applies to large automated imports; which include import specifications, batch import specifications, bulk imports, and use of iBase Scheduler. Alerting jobs must be stopped before the import starts, and started again when the import is completed.

Alerting must also be unavailable when you back up your database.

You can control the scheduling of alerting jobs in the Alerting Configuration window (in iBase Designer). More advanced scheduling options are available in SQL Server Management Studio. You can also manually disable alerting jobs in the Alerting Configuration window by clicking Schedule and turning off the Enable check box.

Note: Do not click Suspend Alerting, as this action removes your alerting jobs.
SQL Server Express®
SQL Server Express Edition does not have a default facility to manage the scheduling of alerting or Search 360. If you would like to use alerting or Search 360, contact your support representative for more information.
Unicode support
In the Report Wizard, the Standard Report format does not support Unicode characters. If you would like to view reports that contain Unicode characters, you can select the Rich Text Format option.
Bulk Import with blank records
The Bulk Import does not import data from files that contain blank rows. To import the data present in these files, delete the blank rows before you resubmit the file.
Plate Analysis limitations
  • Case Control

    Plate Analysis cannot be used with case-enabled iBase databases.

  • SQL Server Databases

    Plate Analysis works only with SQL Server databases.

All Geographic Information System applications
  • Density Grid and Spatial Query tools

    The Density Grid and Spatial Query tools are sensitive to the current map units. That is, if the data is sent to the map in decimal degrees but the map is in meters then both of these tools fail.

  • Plotting data from multiple databases
    When you plot to the same mapping application, you might get unexpected results in the following situations.
    • The following results can occur when you plot data from different databases and then use iBase menu commands.
      • For Show and Add to Set, the wrong database might be presented and consequently no data is displayed or saved in a set.
      • For Add to Chart and Expand, only data from one database can be displayed on the chart.
    • The following results can occur when you plot data from databases with the same name.
      • When the databases have the same structures but different data, incorrect information is retrieved for records mapped from a database that is not currently open. Alternatively, the user might be informed that the record is deleted from the database.
      • When the databases have different structures and data, if an entity or link type with the same three letter identifier does not exist in the open Dataset, the user sees a permissions error message. If the three letter record identifier does exist, then a record for the incorrect entity or link type may be displayed. Alternatively, if there is no record with that record number, the user is informed that the record is deleted.
      • Running a query to find all entities or links in the vicinity of an entity or link on the map might return records on an unrelated area of the map.
      • Deleting an entity or link by using the Show window deletes it from the currently open database, which may not be the same database from which it was mapped.
      • To prevent this unexpected behavior only map from iBase databases with unique names.
ArcGIS Interface Blank menu
Following an upgrade from iBase 5, users of the iBase ArcGIS Interfaces might find a blank menu that is labeled iBase 5. The options that were available under this menu are now found within the file menu, and the menu can be removed by updating the i2.mxd file.
ArcGIS 10.4 to 10.6
If the ArcGIS application is not already open when you send items to be plotted on a map from iBase, the items might not be visible. Therefore, ensure ArcGIS is already open before you send items from iBase.
  • The main toolbar must be set up as a floating toolbar.
  • To ensure that all the extensions load correctly, start MapInfo before sending data from iBase.

More information

For more information, see the following resources:
IBM i2 iBase