Hi,
I am trying out the behavior of the Next-ID-Block-Size and Next-ID-Commit in
ar.conf/cfg.
In earlier versions where I tried it size:1 and commit:F never increased the
ARSCHEMA.NextID field unless a record was actually successfully created.
In 9.1 it seems that the T/F is ignored, and the ARSCHEMA.NextID is never
forwarded on an error in Phase 1 and always forwarded if you get an error in
later phases.
Next-ID-Block-Size:1 Next-ID-Commit:F
The default values now seem to be what would equal an earlier setting of:
Next-ID-Block-Size:100 Next-ID-Commit:T
As expected when changing to size:1 and then issuing an arsignal -c localhost,
the ARSCHEMA.NextID was used and incremented all the time.
This gave me the total records of:
000000000000001
000000000000002
000000000000101
000000000000102
When I changed the size:25, followed by arsignal -c localhost, an interesting
thing happened, and that was that the server started incerting records at 3.
When all records were filled up to 100, it then jumped to 103 and incremented
ARSCHEMA.NextID with 25.
I wondered if it was looking at the gaps in the database, but I think instead
it keeps a copy of the old Next-ID-Block it used somehow and starts there when
the Next-ID-Block-Size is changed from 1 to a higher number. I understood that
after deleting all records and still seeing it continue somewhere in the old
block when changing the size from 1 to 25 yet again.
So what is the purpose of all this on my behalf? Well I am trying to forward
the TicketNumGenerator forms ARSCHEMA.NextID to make sure that the counter is
reset to the correct number when synchronizing data between servers. In normal
forms this is no problem as the ARSCHEMA.NextID is increased when you import
data. In the TicketNumGenerator forms the data is always deleted, so there is
no actual data to synch, only the ARSCHEMA.NextID.
So my conclusion is that when you go in to the DB and change the
ARSCHEMA.NextID, all the servers in the server group needs a restart to make
sure only new numbers are used :-(
Any suggestions?
Best Regards - Misi, RRR AB, http://www.rrr.se (http://www.rrr.se) (ARSList MVP
2011)
Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13)
* 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
(http://rrr.se)
--
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist
