I have little experience with WMQI and the consultant who developed our flow is long gone, hope you can help.
Here’s the description: We’re getting data in a MQInput node with a Message Domain of BLOB (no 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:
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”414d5120514d5f…22300000”, X”414d5120514d5f…22300000”, TIMESTAMP”2003-01-09 16:45:03.274”,
X”3c3f786d6c207 … edited for space… 4d54727573743e”)
Now, I understand that we are seeing the hex representation of the various data, but what
could have caused this to suddenly change? I’m looking for suggestions on what I should belooking 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? Do you need more information from me? Any help