If you look in the server information form, there's a setting for next ID block 
size. It's typically set to 100. When each server in your server group boots 
up, it caches 100 IDs and updates the nextId for each form in the arschema 
table. This is to prevent an update and select statement to the arschema table 
for every record created. It looks like the first record was created using the 
app server that was booted 2nd. Causing the record IDs to be larger for the 
earlier submitted ticket.


Jason Bess

On Jul 3, 2013, at 12:11 PM, "Brittain, Mark" <[email protected]> wrote:

> **
> HI All,
>  
> I have a situation that occasionally occurs during peak submit periods. On 
> two incidents the Incident ID and entry id are in sequence but the Submit 
> dates are not in sequence. I have a VIP to two mid-tiers which are load 
> balanced to 2 AR Servers in a server group. Both AR servers use the same 
> Oracle database. The submits use the Incident Interface Create form either 
> from a web service or an email. The web service passes through the VIP and 
> the email goes to a mailbox on the first server in the group. Any suggestions 
> on what might be the cause, what to check and maybe to change?
>  
> Incident #INC000000017563, entry id INC000000015438 Submit Date 6/17/2013 
> 1:30PM – Submitted via web service
> Incident #INC000000017771, entry id INC000000015557 Submit Date 6/17/2013 
> 1:28PM – Submitted via email
>  
> ARS 7.6.04 SP3
> ITSM 7.6.04 SP3
> LINUX 5
> Oracle 11
>  
> Thanks
> Mark
>  
> Mark Brittain
> Remedy Developer
> ITILv3 Foundation
> NaviSite – A Time Warner Cable Company
> [email protected]
> Office: 315-453-2912 x5335
> Mobile: 315-882.5360
> <image001.gif>
>  
> 
> This E-mail and any of its attachments may contain Time Warner Cable 
> proprietary information, which is privileged, confidential, or subject to 
> copyright belonging to Time Warner Cable. This E-mail is intended solely for 
> the use of the individual or entity to which it is addressed. If you are not 
> the intended recipient of this E-mail, you are hereby notified that any 
> dissemination, distribution, copying, or action taken in relation to the 
> contents of and attachments to this E-mail is strictly prohibited and may be 
> unlawful. If you have received this E-mail in error, please notify the sender 
> immediately and permanently delete the original and any copy of this E-mail 
> and any printout.
> _ARSlist: "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"

Reply via email to