The Parameters MAX_CONCURRENT And MAX_CONCURRENT_TIMEOUT Don't Not Have Any Effect (Doc ID 752381.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

Oracle Lite - Version 10.3.0.2.0 to 10.3.0.2.0 [Release 10.3]
Information in this document applies to any platform.
***Checked for relevance on 19-Oct-2012***


Symptoms

Currently you try to limit your new system environment regarding concurrent sync processes.

 But MAX_CONCURRENT and MAX_CONCURRENT_TIMEOUT have no effect. You have been tried to sync in parallel with 3 clients and set MAX_CONCURRENT=1 and MAX_CONCURRENT_TIMEOUT=30. It seems that the default timeout of 1200 is used because you do not get any timeout or server busy exceptions. 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms