Re: Strange create date behavior

2013-06-18 Thread patchsk
Not sure about IncidentID but for RequestID I think it is due to Next 
Request ID block size.
This is my understanding that 
the blocks are allocated at the server level or the thread level and stored 
in memory.
So depending upon which thread/server gets the api call to create entry, a 
requestID from the corresponding block will be used causing out of synch 
with db times.

On Monday, June 17, 2013 12:57:28 PM UTC-7, Remedy_Mark wrote:

 ** 
  
 HI All,

  

 I have two ARS server in a server group and one database server. I have 
 incidents being created from a web service and an email template. Both 
 types of requests are processed through the IncidentInterface_Create form. 
  The Incident Number and the Entry ID are sequences in the same order but 
 the Submit Date is not as shown below. There were about 120 incidents 
 created in a span of two minutes and I wouldn’t think it would matter. Only 
 thing I could think my be the cause is the time on the two AR Servers are 
 not in sync.  Has anyone seen this before?

  

 Incident #INC00017563, db record id INC00015438  Create Date 
 6/17/2013 1:30PM

 Incident #INC00017771, db record id INC00015557  Create Date 
 6/17/2013 1:28PMl

  

 ARS 7.6.04 SP3

 Oracle 11.

  

 Thanks

 Mark

  

 *Mark Brittain*

 Remedy Developer

 ITILv3 Foundation

 *NaviSite – **A Time Warner Cable Company***

 mbritt...@navisite.com javascript:

 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


Strange create date behavior

2013-06-17 Thread Brittain, Mark
HI All,

I have two ARS server in a server group and one database server. I have 
incidents being created from a web service and an email template. Both types of 
requests are processed through the IncidentInterface_Create form.  The Incident 
Number and the Entry ID are sequences in the same order but the Submit Date is 
not as shown below. There were about 120 incidents created in a span of two 
minutes and I wouldn't think it would matter. Only thing I could think my be 
the cause is the time on the two AR Servers are not in sync.  Has anyone seen 
this before?

Incident #INC00017563, db record id INC00015438  Create Date 6/17/2013 
1:30PM
Incident #INC00017771, db record id INC00015557  Create Date 6/17/2013 
1:28PMl

ARS 7.6.04 SP3
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@01CE6B72.89D00C00]



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