Unsolved
This post is more than 5 years old
4 Operator
•
2.1K Posts
0
706
March 12th, 2012 10:00
Help with SYMCLI_CTL_ACCESS
I ran across a reference to the SYMCLI_CTL_ACCESS environment variable this morning and I've been searching in vain for any references to the ramifications of setting this from the default "Exclusive" to "Parallel". It seems to me that Parallel would be a better setting but there must be some reason for Exclusive to be the default. None of the documentation I can find explains anything beyond the (somewhat obvious) basics of what each setting means.
Can anyone tell me why I shouldn't just make this change, or at least what factors I should consider BEFORE making the change? So far the only references I see outside the official description is a few times when someone suggests "maybe you want to try this..."
This is a bit frustrating...!!!
PedalHarder
3 Apprentice
•
465 Posts
0
March 12th, 2012 14:00
From what I have seen from troubleshooting with parallel enabled, during the execution of a symcli command, the symapi_db can still get an exclusive lock, but only when it needs it to perform an update to the file. So only a portion of the time it takes to run the symcli command will have an exclusive lock. Several customers I deal with have the SYMCLI_CTL_ACCESS set and it works just fine with multiple CLI on the same host (improved success in CLI command execution over the default). I'm with you, can't see why this is not default behavior.
sauravrohilla
859 Posts
0
March 13th, 2012 00:00
When SYMCLI_CTL_ACCESS=PARALLEL the control CLI opens the DB file for read no_write, so even after we sync data as part of the control we cannot save updated data to DB file. So next command will switch to full load. The only commands which can update DB file in such a mode are symcfg discover or symcfg sync