|
Home > Archive > BizTalk Server General > May 2004 > TrackedMessages_Copy_BizTalkMsgBoxDb problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
TrackedMessages_Copy_BizTalkMsgBoxDb problem
|
|
| Chris Holliday 2004-05-24, 4:37 pm |
| I am suffering what seems like a not so uncommon issue. Maybe its a bug,
maybe not.
Has anyone resolved the problem with the above JOB failing with the
following message:
SQL Server Scheduled Job 'TrackedMessages_Copy_BizTalkMsgBoxDb'
(0x82D644988B7BB64DA11A65F063234294) - Status: Failed - Invoked on:
2004-05-24 09:44:03 - Message: The job failed. The Job was invoked by
Schedule 17 (Schedule). The last step to run was step 1 (Purge).
I am confused as to why the SPOOL table allows NULL values on the
uidBodyPartID column at all? For what its worth, wholesale deletion of rows
with null BodyPartID column values is a BAD idea.
Any help would be greatly appreciated.
C.
| |
| Christof 2004-05-24, 4:37 pm |
| Any other logs/messages/events ??
Can you trace the job in SQL analyser?
Kind regards,
Christof
"Chris Holliday" <chris@-nospam-adventureology.com> wrote in message
news:eB6iQMaQEHA.3380@TK2MSFTNGP11.phx.gbl...
> I am suffering what seems like a not so uncommon issue. Maybe its a bug,
> maybe not.
>
> Has anyone resolved the problem with the above JOB failing with the
> following message:
>
> SQL Server Scheduled Job 'TrackedMessages_Copy_BizTalkMsgBoxDb'
> (0x82D644988B7BB64DA11A65F063234294) - Status: Failed - Invoked on:
> 2004-05-24 09:44:03 - Message: The job failed. The Job was invoked by
> Schedule 17 (Schedule). The last step to run was step 1 (Purge).
>
>
> I am confused as to why the SPOOL table allows NULL values on the
> uidBodyPartID column at all? For what its worth, wholesale deletion of
rows
> with null BodyPartID column values is a BAD idea.
>
> Any help would be greatly appreciated.
>
> C.
>
>
| |
| Chris Holliday 2004-05-24, 4:37 pm |
| Christof,
The job is very simple, it calls the procedure 'bts_CopyTrackedMessages'
which does what it says. In the process some items are deleted from the
TrackingMessageReferences table which causes its DELETE trigger to fire
which inserts the deleted rows into the Tracking_Spool1 table. Some of the
rows that are handled have NULL values for the uidBodyPartID (in the Spool
table). Null values are not allowed in the cooresponding column in the
Tracking_Spool1 table. The simple solution is to simply allow NULLS on the
column in the Tracking_Spool1 table, but this is a hack and doesnt solve the
underlying cause - why are NULL values going into this column?
Thanks,
C.
"Christof" <bts2004communityfeedback (at) hotmail (dot) com> wrote in
message news:ulmvHBbQEHA.1340@TK2MSFTNGP12.phx.gbl...
> Any other logs/messages/events ??
> Can you trace the job in SQL analyser?
>
> Kind regards,
> Christof
>
> "Chris Holliday" <chris@-nospam-adventureology.com> wrote in message
> news:eB6iQMaQEHA.3380@TK2MSFTNGP11.phx.gbl...
> rows
>
>
|
|
|
|
|