Release notes - IBM i2 iBase 9.0.2

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.

Invalid procedure call or argument
 Error #5 occurred in:
UniToolbox2

Automation error
The remote procedure call failed.
Error #-2147023170 occurred in:
id5Error 

CANDBPlugIn:Commands(Get)
FMain:ANDBPlugInCommands

• 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.

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.

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.

• Case Control

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

• SQL Server Databases

  Plate Analysis works only with SQL Server databases.

• 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.

• 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.