Search

Release Notes

Release Notes

10.1
- 10.5 HotFix 3
- 10.5 HotFix 2
- 10.5 HotFix 1
- 10.5
- 10.2 HotFix 1
- 10.2
- 10.1 HotFix 1
- 10.0 HotFix 1
- 10.0

Back Next

Fixed Limitations

Fixed Limitations

The following table describes fixed limitations:

Reference Number	Description
IR-727	When the XML Search Server remains inactive for some time, a search request fails with an internal error.
IR-721 IR-639	In an environment that uses Rulebase Server Group, when the primary Rulebase Server shuts down unexpectedly, the Search Server might not respond or you might get the following message: Exception in thread "main" java.lang.StackOverflowError at java.lang.ThreadLocal$ThreadLocalMap.getEntry(Unknown Source) at java.lang.ThreadLocal$ThreadLocalMap.access$000(Unknown Source)
IR-709	The updsync utility might shut down unexpectedly.
IR-678	When the XML Synchronization Server automatically restarts, you get the following message: 2016-07-18 13:43:17.141826 ssasrsv 102] ssaxsrt.c(2514) ssaxsrt_real_time_async_get: Warning: [2016-07-18 13:43:17.128640 11] Flush and Commit Processing Failed
IR-675	When a Rulebase Server shuts down unexpectedly or loses connection with the database, you get the following messages: 2016-07-12 07:15:49.820878 ssasrsv -1/ 4] errmsg_put 'ssa_odbc_connect: [02] Reason: [SSAOCI,1] OCILogon ssaoci.c 3408 failed 'ORA-12545: Connect failed because target host or object does not exist'' [2016-07-12 07:15:49.820929 ssasrsv -1/ 4] errmsg_put 'cannot connect to Data Source' [2016-07-12 07:15:49.821117 ssasrsv -1/ 4] errmsg_put 'ssaodbc.c 4800 rc 9 108*100 db_connect_user' [2016-07-12 07:15:49.821152 ssasrsv -1/ 4] errmsg_put 'connect user failed'
IR-672	When you run the Relate client, you might get the following error: Unable to initialize thread structures -1
IR-660	On AIX, the ssacssv.err and ssacssv.log files have entries with incorrect time stamps.
IR-653	When you use the ids_match_explain function in your environment, the response time is unexpectedly long.
IR-643	When you start the updsync utility with the -g parameter, you get the following error: -g parm is invalid
IR-584	When you use a flat file as the source, the synchronizer does not shut down automatically after the synchronizer reaches the end of the file.

Identity Resolution 10.0 HotFix 1

Watch

Comments

0 COMMENTS

We’d like to hear from you! Log in to comment.