Submit Date out of Sequence
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 #INC00017563, entry id INC00015438 Submit Date 6/17/2013 1:30PM - Submitted via web service Incident #INC00017771, entry id INC00015557 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 mbritt...@navisite.commailto:mbritt...@navisite.com Office: 315-453-2912 x5335 Mobile: 315-882.5360 [cid:image001.gif@01CE77E4.4CD04710] 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. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years inline: image001.gif
Re: Submit Date out of Sequence
Mark, Are you in a Server Group? If so, you will find that each server has its own cache of next ID's. On Wed, Jul 3, 2013 at 10:11 AM, Brittain, Mark mbritt...@navisite.comwrote: ** 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 #INC00017563, entry id INC00015438 Submit Date 6/17/2013 1:30PM – Submitted via web service Incident #INC00017771, entry id INC00015557 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*** mbritt...@navisite.com Office: 315-453-2912 x5335 Mobile: 315-882.5360 [image: email-Logo-031813] ** ** -- 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
Re: Submit Date out of Sequence
Mark, The Submit Date is not entered until the Incident is saved; the Incident ID is assigned whether or not the Incident is ever saved to the server. You may also find that the Submit Date is later than the Last Resolved Date if the Incident is submitted as Resolved Thank you, Sandra Hennigan Remedy Developer From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Brittain, Mark Sent: Wednesday, July 03, 2013 12:12 PM To: arslist@ARSLIST.ORG Subject: Submit Date out of Sequence ** 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 #INC00017563, entry id INC00015438 Submit Date 6/17/2013 1:30PM - Submitted via web service Incident #INC00017771, entry id INC00015557 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 mbritt...@navisite.commailto:mbritt...@navisite.com Office: 315-453-2912 x5335 Mobile: 315-882.5360 [email-Logo-031813] 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 inline: image001.gif
Re: Submit Date out of Sequence
Hi Mark, There is a configuration for Next Request ID Block Size on the Server Information form / Configuration tab. Basically, what happens is each thread gets its own block of IDs to use. There's also the Next-ID-Commit setting, which is a T/F value in ar.conf/ar.cfg which will make sure that a number isn't used until the record hits the database. The default value shifted from True to False between 7.6 and 8. Under Form-Properties, you can change the Next-ID-Block-Size per form. These settings are to reduce contention in the database which would otherwise be a bit of a performance problem. Setting the block size to 1 would likely push your ID's to be sequential along with the create date but it would come at a performance cost. Thanks, Steve On Wed, Jul 3, 2013 at 9:11 AM, Brittain, Mark mbritt...@navisite.comwrote: ** 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 #INC00017563, entry id INC00015438 Submit Date 6/17/2013 1:30PM – Submitted via web service Incident #INC00017771, entry id INC00015557 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*** mbritt...@navisite.com Office: 315-453-2912 x5335 Mobile: 315-882.5360 [image: email-Logo-031813] ** ** -- 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
Re: Submit Date out of Sequence
And if your system is set to pre-fetch more than one Entry Id at a time, this will happen. Which is one of the reasons that most Remedy systems shouldn't have it set above 1. Rick On Jul 3, 2013 9:36 AM, Longwing, Lj llongw...@usgs.gov wrote: ** Mark, Are you in a Server Group? If so, you will find that each server has its own cache of next ID's. On Wed, Jul 3, 2013 at 10:11 AM, Brittain, Mark mbritt...@navisite.comwrote: ** 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 #INC00017563, entry id INC00015438 Submit Date 6/17/2013 1:30PM – Submitted via web service Incident #INC00017771, entry id INC00015557 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*** mbritt...@navisite.com Office: 315-453-2912 x5335 Mobile: 315-882.5360 [image: email-Logo-031813] ** ** -- 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_ _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
Re: Submit Date out of Sequence
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 mbritt...@navisite.com 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 #INC00017563, entry id INC00015438 Submit Date 6/17/2013 1:30PM – Submitted via web service Incident #INC00017771, entry id INC00015557 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 mbritt...@navisite.com 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
