The updmulti utility might fail with one of the following error messages:

Invalid TXN record (SeqNo='00000000000000000000000000000013')
ids_real_time_async_get failed

When you perform multiple searches simultaneously, the search results might contain garbled data.

When a search fails, you do not get detailed log messages.

The Table Loader utility might fail to run with one of the following error messages:

Error: NAME3V2 get_keys_encoded failed 'Error reported by core: SSA Rsp Code: (0203462000 0203462000) 0203462000E SSATSSA EMPTY STACK'
Load IDT 'escholar_idt' failed

In the SDF Wizard, when you create fields for the identity table, you get an error message.

A search with similar names returns an incorrect match score.

When you use the Lite search client, you might get the following error message:

An Error Has Occurred:
SsaAdminSearchEng.java> Error occurred while performing 'ids_search_start ('SRCH_ADDRESS' '0) 'ids_error_get_all failed

The Relate utility adds unmatched records to the output file that you configured for the matched records.

In an environment that uses Rulebase Server Group, when the connection to the database is lost, the Rulebase Servers fail to connect to the database even after the connection to the database is reestablished.

When a secondary Rulebase Server becomes primary after the primary Rulebase Server shuts down unexpectedly, the Search Server does not connect to the new primary Rulebase Server.

The Synchronization Server might start with the following error message:

Program terminated with signal 11

When you use a flat file to create a system definition file in the SDF Wizard, you get the following error message, and the SDF Wizard shuts down unexpectedly:

An unexpected error has occurred.

When you try to upgrade

Identity Resolution

, the upgrade fails if the

IDSInstallationInfo.xml

file does not exist in the

Identity Resolution

installation directory.

The Relate utility might stop with the following error message:

ORA-03113: end-of-file on communication channel

When a secondary Rulebase Server becomes primary after the primary Rulebase Server shuts down unexpectedly, the Console Client does not connect to the Rulebase.

The updsync utility does not stop even though the connection to the database is lost.

When you run the db_util utility, you might get the following error message:

'db_util' is not recognized as an internal or external command, operable program or batch file.

The Identity Table uses the

YYYY-MM-DD HH24:MI:SS

format to store dates even though the date format is different in the source system.

The Table Loader process uses the connection strings even though you configure alias names for the connection strings.

A SoapUI response does not properly display the Latin-1 characters.

When you edit a system, if you get the following message and you try to import the system template, the Console Client becomes unresponsive:

The System Editor requires a System template to be present in the Rulebase to be able to add definitions. Do you want to import it now?

When you perform a search, you might get the following error message:

Not enough memory allocated to receive string, need 2490369 > 65

The Population Override Manager does not display some category definitions and rules even though the population file contains them.

The updsync utility restarts even though you add a transaction to the IDS_UPD_SYNC_TXN table to stop the updsync utility.

When you use the Match Explain function, you might get the following error message:

Internal error -501130908*Request envelope:

When you use the System Editor to add a multi-search definition, you might get the following error message:

ssa.ssautil.SSAMalformedException: Unknown Persistent-ID-Method selected

In the SDF Wizard, when you try to add a join criteria, you might get the following error messages:

An unexpected error has occurred.
IIR System Definition Wizard will not exit.