Where does HCIDBDUMP get its data??

[John Zalesak]

More specifically:

When I compare the output of the hcidbdump command with the contents of the .err and .log file, they do not match up and there is info missing in the files.

For example:

The .err and .log files have the same message id in them for particular error event.  The hcidbdump command does not out put this message id, but it outputs other message id’s that are not in our .err and .log files.  Also, the hcidbdump -L has the HL7 info in it but our .err and .log files do not have any HL7 in them.

Can anyone make sense of this for me?   What pc of the puzzle am I missing?  Thanks in advance.

Topic

[James Cobane]

John,

The .err and .log files will not contain the actual message data unless you have the EO turned up, or you have echoed out the message data from a proc.  Normally, you don’t want your EO turned up so high that you are displaying the message data in the .log files; depending on you volumes, they could get very large, very fast.

As for the message ID’s, the message ID changes as the message moves through the engine/recovery database in different states. So, depending on what event you are looking at in the log versus what event caused the message to error, the MID’s could be different.  Also, note that there are two fields in the message METADATA that contain MID’s:  msgMid & msgSrcMid, where msgMid is the current MID, and msgSrcMid is the MID of the message that the current message was derived from; i.e. the message MID that it had in its previous recovery DB state.

Hope this helps.

Jim Cobane

Henry Ford Health

[John Zalesak]

Thanks for your reply.  It did help.

You are correct, we do not have our EO turned up.  The HL7 Message is not in the ERR or LOG file but it is in the hcidbdump output.  Where did it get it?

We were looking for the with the data to save it for future reference.  We wanted to delete the errors but keep them incase we needed them later.  The best solution we had was to copy the output of hcidbdump to an output file.  Is this the best way??

Thanks again

[James Cobane]

John,

When the message error’s (for whatever reason), it writes the transaction to the error database.  If it is in the error database, you can simply use hcidbdump to write the transaction to a file for analysis.  To write all of the messages from the error database to a file, simply enter:

hcidbdump -e yourfilenamehere.txt

If you only want a specific transaction, you can dump it out by the message id (you can get this from the hcidbdump information):

hcidbdump -e -m 262152102 yourfilenamehere.txt

You can also dump the message from the error database on other criteria as well (i.e. message state, source connection, destination connection, etc.) If you use the DB Admin GUI, you can view the various options and also display the command line equivalent of the hcidbdump command to help can gain understanding of the syntax and options available.  Simply choose your desired options in the GUI, then click on the ‘Show command’ button – then you’ll see the command line equivalent.

Hope this helps.

Jim Cobane

Henry Ford Health

[John Zalesak]

Got it – Thanks

I just tried the GUI and it worked great.

Have a great weekend!

[Author]

Replies