Hi Misi,

My remedy version is 7.1 version.


On Wed, Aug 21, 2013 at 6:36 PM, Misi Mladoniczky <m...@rrr.se> wrote:

> Hi,
>
> I presume your version is 7.6.04 or later.
>
> You MUST have the following in your ar.cfg if you want unbroken request id
> chains created in chronilogical order for all forms:
> Next-ID-Commit: F
> NextID-Block-Size: 1
>
> And it does work. I have tried it many times.
>
> If you are after something other than an unbroken chain of request ids,
> please
> explain.
>
>         Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)
>
> Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11/12):
> * 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.
>
> > Hi All,
> >
> > I tried many options whatever suggested so far. like given
> "*Next-ID-Commit:
> > T , **NextID-Block-Size: 100*" and even tried "*Next-ID-Commit: F ,
> > **NextID-Block-Size:
> > 1*, also chagened the form property "*Next Request ID Block - 1*".
> >
> > Today i can see huge difference in the request ID, it giving difference
> of
> > 700 and 600.
> >
> > Please find the below details.
> >
> >   Case ID Difference  2928816 -791  2929607 -5  2929612 -20  2929632 -14
> > 2929646 -71  2929717 -5  2929722 -8
> >
> >
> > On Wed, Aug 21, 2013 at 7:07 AM, Misi Mladoniczky <m...@rrr.se> wrote:
> >
> >> Hi,
> >>
> >> You must use the below values, which was default on systems prior to
> >> 7.6.04:
> >> Next-ID-Commit: F
> >> NextID-Block-Size: 1
> >>
> >> The new default is T and 25.
> >>
> >> You can still do the block-size of 25 to minimize bottlenecks in your
> >> system,
> >> and instead set the block-size to 1 on those forms that is important to
> >> keep
> >> in sequence. Yes, it is a form-property :-)
> >>
> >>         Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP
> 2011)
> >>
> >> Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11/12):
> >> * 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.
> >>
> >> > Hi Snehal,
> >> >
> >> > Thanks for the mail.
> >> >
> >> > I have one doubt, it works fine in Dev remedy server with the
> parameter
> >> > detail.
> >> > Please correct me if i am wrong.
> >> >
> >> > *Next-ID-Commit: F*
> >> >
> >> > *NextID-Block-Size: 1*
> >> >
> >> >
> >> > On Tue, Aug 20, 2013 at 3:20 PM, snehal mhaske
> >> > <snehal.mha...@vyomlabs.com>wrote:
> >> >
> >> >> **
> >> >>
> >> >> Hi Karthick,**
> >> >>
> >> >> ** **
> >> >>
> >> >> *Next-ID-Commit* : When the system generates the next ID number for a
> >> >> record in the****
> >> >>
> >> >> database, it performs a new commit transaction if this parameter is
> set
> >> to
> >> >> T****
> >> >>
> >> >> (true). If the parameter is set to F (false), the transaction to
> >> generate
> >> >> the next****
> >> >>
> >> >> ID is included as part of the create entry transaction. *Set the
> value
> >> to
> >> >> **T **to*
> >> >>
> >> >> *increase efficiency and for debugging*. The default is F.****
> >> >>
> >> >> ** **
> >> >>
> >> >> *NextID-Block-Size* : Allocates next IDs in blocks rather than one
> at a
> >> >> time. Allocating in blocks****
> >> >>
> >> >> increases performance during a create operation.****
> >> >>
> >> >> *Edit the **NextID-Block-Size **value to a positive number (up to
> 1000),
> >> >> for*
> >> >>
> >> >> *example: **NextID-Block-Size: 50***
> >> >>
> >> >> The default value is 1. If 0 or a negative number (for example, -1)
> is
> >> >> used,****
> >> >>
> >> >> the server will use the default value of 1.****
> >> >>
> >> >> You do not need to restart the server for the change to take effect.
> >> The**
> >> >> **
> >> >>
> >> >> option is started immediately.****
> >> >>
> >> >> To disable this option, set the value of NextID-Block-Size to 1, or
> >> remove
> >> >> ****
> >> >>
> >> >> the parameter from the configuration file. Note that this option does
> >> not*
> >> >> ***
> >> >>
> >> >> work with Informix databases.****
> >> >>
> >> >> ** **
> >> >>
> >> >> I would suggest, to add both the parameters in ar.cfg on Prod box.
> Set
> >> the
> >> >> values as follows:****
> >> >>
> >> >> *Next-ID-Commit: T*
> >> >>
> >> >> *NextID-Block-Size: 100*
> >> >>
> >> >> ** **
> >> >>
> >> >> Regards,****
> >> >>
> >> >> Snehal****
> >> >>
> >> >> *From:* Action Request System discussion list(ARSList) [mailto:
> >> >> arslist@ARSLIST.ORG] *On Behalf Of *Karthick S
> >> >> *Sent:* Tuesday, August 20, 2013 9:42 AM
> >> >> *To:* arslist@ARSLIST.ORG
> >> >> *Subject:* Sequence issue in Request ID while creating tickets****
> >> >>
> >> >> ** **
> >> >>
> >> >> ** ****
> >> >>
> >> >> Hi All,****
> >> >>
> >> >> ** **
> >> >>
> >> >> We have Sequence issue in Request ID while creating tickets in prod
> >> Remedy
> >> >> . Here are the few example numbers seem to be jumping and skipping
> the
> >> next
> >> >> in sequence.****
> >> >>
> >> >> ** **
> >> >>
> >> >> 000000002930522****
> >> >>
> >> >> 000000002930521****
> >> >>
> >> >> 000000002930518****
> >> >>
> >> >> 000000002930515****
> >> >>
> >> >> ** **
> >> >>
> >> >> I have replicated the issue in Dev box and it seems to be working
> fine
> >> >> with sequence order. I have noticed the ar.cfg file and it has
> >> >> Next-ID-Commit: F and Next Request ID Block Size 1. i couldn't find
> the
> >> >> same in Production ar.cfg file.****
> >> >>
> >> >> ** **
> >> >>
> >> >> I tried adding those details, but still nothing happens. do i really
> >> need
> >> >> to restart the services.****
> >> >>
> >> >> ** **
> >> >>
> >> >> Please provide your idea on this.****
> >> >>
> >> >> ** **
> >> >>
> >> >> Remedy Version is 7.1 Patch 006****
> >> >>
> >> >> Windows 2003****
> >> >>
> >> >> SQL 2005 DB****
> >> >>
> >> >>  ****
> >> >>
> >> >>  ****
> >> >>
> >> >> *Thanks and Regards,*****
> >> >>
> >> >> *Karthick S*****
> >> >>
> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ ****
> >> >>  _ARSlist: "Where the Answers Are" and have been for 20 years_
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > **
> >> > **
> >> > *Thanks and Regards,*
> >> > *Karthick S*
> >> >
> >> >
> >>
> _______________________________________________________________________________
> >> > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> >> > "Where the Answers Are, and have been for 20 years"
> >> >
> >>
> >>
> >>
> _______________________________________________________________________________
> >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> >> "Where the Answers Are, and have been for 20 years"
> >>
> >
> >
> >
> > --
> > **
> > **
> > *Thanks and Regards,*
> > *Karthick S*
> >
> >
> _______________________________________________________________________________
> > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> > "Where the Answers Are, and have been for 20 years"
> >
>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>



-- 
**
**
*Thanks and Regards,*
*Karthick S*

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to