MQSeries.net :: View topic

jasonlove · TIMESTAMP ''2003-01-09 16:45:03.274''

I desparately need your help! A consultant developed our WMQI message flows and now that he's long gone it's somehow fallen on my shoulders to fix a problem that has arisen and they need the solution yesterday. Unfortunately, I have little experience (that's actually being liberal) with it so I'm hoping you all may be able to help me...

WMQI v2.1 running on Win2K SP2

Here's the description: We're getting data in a MQInput node with a Message Domain of BLOB (not message set, type, or format defined). The message is sent immediately to a database node to be logged in a SQLServer 2K database (on Win2K SP2) with the following ESQL
(Transaction Mode=Commit):

insert into Database.XSP_MSG_AUDIT (
AUDIT_MSG_TYPE,
MESSAGE_ID,
CORRELATION_ID,
DW_TIMESTAMP,
DW_MESSAGE
)
values (
'XSP_SOURCE',
Root.MQMD.MsgId,
Root.MQMD.MsgId,
current_timestamp,
Root."BLOB"."BLOB"
);

return TRUE;

Here's the problem: Until a few weeks ago the data was being inserted with no problems. When we look at rows from when it was working this is what we get (relevant to above insert):

AUDIT_MSG_TYPE: XSP_SOURCE
MESSAGE_ID: AMQ QM_stcinohhqvÂ¸Â¾=R0
CORRELATION_ID: AMQ QM_stcinohhqvÂ¸Â¾=R0
DW_TIMESTAMP: 10/31/2002 8:51:43 AM
DW_MESSAGE: <?xml version="1.0" standalone="yes"?><XSP_AMTrust> ...Edited for length, but a valid XML message... </XSP_AMTrust>

However, now when the message is inserted, it errors out with several SQL errors relating to the insert statement. I put a trace on the SQL server and this is the insert that WMQI is attempting to perform:

INSERT INTO XSP_MSG_AUDIT(AUDIT_MSG_TYPE, MESSAGE_ID, CORRELATION_ID, DW_TIMESTAMP, DW_MESSAGE)
VALUES(''XSP_SOURCE'', X''414d5120514d5f737463696e6f6868712de01a3e22300000'',
X''414d5120514d5f737463696e6f6868712de01a3e22300000'', TIMESTAMP''2003-01-09 16:45:03.274'',
X''3c3f786d6c207 ... edited for space again ... 4d54727573743e'')

Now, I understand that we are seeing the hex representation of the various data, but what could have caused this to suddenly change (and where did the "TIMESTAMP" come from)? I'm told that no work was done on anything before this started happening. While I'm not convinced about that, I'm looking for suggestions on what I should be looking for to make the insert work as it once did. Is it even possible for the above situation to have inserted the data as it was (maybe that's changed?) Do you need more information from me? Any help at all would be appreciated!

Thanks!
--Jason