Hi,
Yes, exactly, Next-ID-Commit:T is the default on 7.6.04, but on earlier
version the default is Next-ID-Commit:F.
As for the "hardcoded" Next-ID-Commit:F setting. It is NOT hardcoded in an
unpatched 7.6.04 at least.
I know this because my log shows a FAILED transaction, where things are
rolled back, but the arschema.nextId++ part is NOT rolled back.
When I changed to Next-ID-Commit:F, it worked like earlier versions and
rolled back the arschema.nextId++.
Best Regards - Misi, RRR AB, http://rrr.se
> Misi,
> Looking at the log provided below, on line 30 I see a begin transaction,
> and then a commit on 36. Is that not committing the nextID on submit?
>
> So, this morning I did some re-config of my 7.5 server for testing
> purposes, setting Next-ID-Commit to F and Block-Size to 1 and ran a test
> submit in a test form. My outcome was something along the lines of
>
> Begin Transaction
> Update arschema
> Select from arschema
> Insert into T
> Insert into H
> Commit transaction
>
> This is the expected output with the value set to false. Changing the
> Next-ID-Commit to T gave me
>
> Begin Transaction
> Begin Transaction
> Update arschema
> Select from arschema
> Commit transaction
> Insert into T
> Insert into H
> Commit transaction
>
> This indicates to me that the Next-ID is committing during the create in a
> separate transaction, which is what you would expect with the server
> setting.
>
> Last night when I was doing testing on my 7.6.4 SP3 server, I experienced
> that regardless of what the Next-ID-Commit setting was set to, I got the
> same results as I'm getting today at work in my 7.5 server with the value
> set to T. This tells me that on 7.6.4 SP3, the Next-ID-Commit setting is
> being ignored, and is hard coded to T in the Remedy system
>
> Can anyone else confirm, on other 7.6.4 versions, initial release, or
> other patches, that they are getting the same results with the
> Next-ID-Commit set to F?
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:[email protected]] On Behalf Of Misi Mladoniczky
> Sent: Tuesday, September 11, 2012 6:51 AM
> To: [email protected]
> Subject: Re: Next-ID-Commit
>
> Hi,
>
> Here is an analysis on a default 7.6.04:
> http://rrr.se/tmp/rrrLog764nextId.html
>
> I use Next-ID-Commit:F on my 7.6.04 system, and it indeed uses the old
> behavior.
>
> Now what happens if you reserve chunks? That means that you can still
> loose ids, or get them created in non linear order. Especially on server
> group systems.
>
> But you can set the Chunk-Size to 1 on the forms where you need continuity
> and an unbroken series.
>
> But unfortunately the Next-ID-Commit can not be set on a form by form
> basis...
>
> Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
>
> Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11):
> * RRR|License - Not enough Remedy licenses? Save money by optimizing.
> * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
> Find these products, and many free tools and utilities, at http://rrr.se.
>
>> Misi,
>> I'm keenly interested in this specific topic. I believe I have
>> experienced that you CANNOT turn this feature off (set it to F) in
>> 7.6.04 SP3. I have a test app that I have built up and despite
>> setting the values properly in the config file, I still get next ID
>> generation in a separate transaction (evident via SQL logging).
>> Investigating the docs, I read this on page 379 of the config guide
>>
>> Note: Next-ID-Block-Size replaced Next-ID-Commit, but Next-ID-Commit
>> is available for backward compatibility
>>
>> The problem I have with this statement is that the Next-ID-Block-Size
>> doesn't offer the same capability as Next-ID-Commit, and I believe
>> that they have permanently set Next-ID-Commit to T, and just added a
>> capability to choose your block size. Are you able to verify this for
>> me with your own testing?
>>
>> -----Original Message-----
>> From: Action Request System discussion list(ARSList)
>> [mailto:[email protected]] On Behalf Of Misi Mladoniczky
>> Sent: Tuesday, September 11, 2012 12:00 AM
>> To: [email protected]
>> Subject: Re: EXTERNAL: Reasons for Entry ID increasing
>>
>> Hi,
>>
>> I have posted this many times ;-)
>>
>> The default settings in 7.6.04 has changed:
>>
>> New 7.6.04 default behavior (if lines are not present in ar.cfg):
>> Next-ID-Commit:T
>> Next-ID-Block-Size:25
>>
>> Old 7.6.03 and earlier default behavior:
>> Next-ID-Commit:F
>> Next-ID-Block-Size:1
>>
>> So to get the old behavior just put F/1 in the ar.cfg/conf file.
>>
>> Note that you can set the Next-ID-Block-Size on a per form basis as
>> well, so you could have the 25-blocks as default but 1 for a specific
>> form.
>>
>> Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP
>> 2011)
>>
>> Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11):
>> * RRR|License - Not enough Remedy licenses? Save money by optimizing.
>> * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy
>> logs.
>> Find these products, and many free tools and utilities, at
>> http://rrr.se.
>>
>>
>> ______________________________________________________________________
>> _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
>>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12
> www.wwrug12.com ARSList: "Where the Answers Are"
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
