Hi Drew,
Well that's just it...
Schemaid 1247 is the HPD:Help Desk form,,,, and the nextid field seems to
contain the next 'request id' number.. however as you can see from the log
below, it sets UPDATE arschema SET nextId = nextId + 1 WHERE schemaId = 1247
But that's the request id field...
But then it sets
*/INSERT INTO H1247 (entryId,T0,U0,T1,U1) VALUES
('INC000000018430',1196971076,'mtdollu',1196971076,'mtdollu')
One of the values is 'INC000000018430' which is really the incident id.
When I look at the db, the value in nextid is 371... not 18429.
So seemingly I'd set the nextid field.. but where in the world is the system
coming up with 18430?
Sorry if it's very simple and I'm making it overly complicated....:(
Thanks!!
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Drew Shuller
Sent: Thursday, December 06, 2007 2:36 PM
To: arslist@ARSLIST.ORG
Subject: Re: Resetting Incident Number to 1
Mary, forgive me if I'm giving an answer you already know...wouldn't you
reset whatever table schemaId=1247 is?
Drew
On Thu, 6 Dec 2007, Mary Dollus
wrote:
> Below is the log entry that sets the number.. it's using $LASTID$ to get
the
> Incident number... where can that be reset? Thanks again!!!
>
>
> <ACTL> Checking HPD:INC:GIN_010_SetINCNumber-P (10)
> <ACTL> -> Passed qualification -- perform if actions
> <ACTL> 0: Push Fields
> <ACTL> To Schema HPD:CFG Ticket Num Generator on Server @
> <ACTL> (2) = mtdollu
>
> <API > <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.1005 */+CE ARCreateEntry -- schema HPD:CFG Ticket
> Num Generator from Remedy User (protocol 12) at IP address 192.168.1.64
> <FLTR> <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.1010 */Start filter processing -- Operation - CREATE
> <FLTR> <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> HPD:CFG Ticket Num Generator - <NULL>
> <FLTR> <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.1186 */ End of filter processing (phase 1)
> <SQL > <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.1187 */UPDATE arschema SET nextId = nextId + 1 WHERE
> schemaId = 1247
> <SQL > <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.1212 */OK
> <SQL > <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.1212 */SELECT nextId FROM arschema WHERE schemaId =
> 1247
> <SQL > <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.1227 */OK
> <SQL > <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.1230 */INSERT INTO T1247 (C2,C179,C7,C8,C3,C5,C6,C1)
> VALUES
>
('mtdollu','AG216371749900R1hURAETcyMAnXMA',1,'.',1196971076,'mtdollu',11969
> 71076,'INC000000018430')
> <SQL > <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.1290 */OK
> <SQL > <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.1291 */INSERT INTO H1247 (entryId,T0,U0,T1,U1) VALUES
> ('INC000000018430',1196971076,'mtdollu',1196971076,'mtdollu')
> <SQL > <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.1352 */OK
> <SQL > <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.1353 */COMMIT WORK
> <FLTR> <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.3304 */ Restart of filter processing (phase 3)
> <FLTR> <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.3305 */Stop filter processing
> <API > <TID: 0000000031> <RPC ID: 0000009710> <Queue: Fast >
> <Client-RPC: 390620 > <USER: mtdollu
>> /* Thu
>
> Dec 06 2007 13:57:56.3305 */-CE OK -- New ID INC000000018430
>
> -----Original Message-----
> From: Mary Dollus [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 06, 2007 1:54 PM
> To: 'arslist@ARSLIST.ORG'
> Subject: Resetting Incident Number to 1
>
> Hello all,
>
> I looked thru the arslist to see how this was done. What I found is that
it
> says to set the "nextid" field to 1 in the arschema table where name =
> "HPD:Help Desk".
>
> However I don't want to reset the Request ID field, just the Incident ID
> field. I also want to do the same on Problem, Change and Tasks. We've
been
> testing on a new prod box and are ready to go live this weekend and we
want
> all app ID's set back to 1 before I start importing legacy records.
>
> Has this been done by anyone?
>
> Solaris
> Oracle 10.2g
> ARS 7.0.01 patch 4
>
> Thanks!!!!
>
> Mary Dollus
>
>
____________________________________________________________________________
___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
>
>
____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
