bulkcopy operation failed

[Max Drown (Infor)]

What causes the “bulkcopy operation failed” error.

Note: we’re on Cloverleaf 5.6. Variant is HL7 2.3.

-- Max Drown (Infor)

Topic

[Max Drown (Infor)]

Code:

[msg :RecP:ERR /0:   bn12_xlate:05/19/2009 13:57:23] [0.0.1913675] unknown segment ‘ZOR’ — ignored.
[xlt :xlat:ERR /0:   bn12_xlate:05/19/2009 13:57:23] [0.0.1913675] Xlate ‘ms42sleep_adt.xlt’ failed: Bulkcopy failure: unknown segment ‘ZOR’ — ignored.
[msg :RecP:ERR /0:   bn12_xlate:05/19/2009 13:57:23] [0.0.1913687] The # 7 segment encountered ‘ZOR’ is not defined for message type ‘ADT_A08’.  Segment ignored.
[xlt :xlat:ERR /0:   bn12_xlate:05/19/2009 13:57:23] [0.0.1913687] Xlate ‘ms42sleep_adt.xlt’ failed: Bulkcopy failure: The # 7 segment encountered ‘ZOR’ is not defined for message type ‘ADT_A08’.  Segment ignored.
[pdl :PDL :ERR /0:  bn12hmm_out:05/19/2009 13:57:24] read failed: Connection reset by peer
[pdl :PDL :ERR /0:  bn12hmm_out:05/19/2009 13:57:24] read returned error 104 (Connection reset by peer)
[pdl :PDL :ERR /0:  bn12hmm_out:05/19/2009 13:57:24] PDL signaled exception: code 1, msg device error (remote side probably shut down)

-- Max Drown (Infor)

[Jim Kosloskey]

Max,

I think the content of the message when a variant mismatch occurs has changed in 5.6.

That is not necessarily related to only BULKCOPY – I think any variant definition that does not match the message will cause Cloverleaf(R) to notify in the Process Log.

You can also make the message error out now if you want.

Are any of the messages that had the log entries end up in your Error DB?

Hopefully we resolve those errors during testing by correcting the variant to match the message.

email: jim.kosloskey@jim-kosloskey.com

[Max Drown (Infor)]

Yes, the messages with the ZOR segments were dumped to the error database. I added a proc to remove unwanted segments, but I thought in the past you’d get a warning in the log and the message would still proceed through the xlate and on to the down streams.

-- Max Drown (Infor)

[Jim Kosloskey]

Hmmm I thought you had to set an option under ‘Site Options’ to get those messages to actuall error otherwise it was still a warning.

Have you checked to see if anyone turned on the option?

I could be wrong — it may be that the default is to error out.

email: jim.kosloskey@jim-kosloskey.com

[Max Drown (Infor)]

None of the error options are checked.

-- Max Drown (Infor)

[John Mercogliano]

Max,

 Did you also check the Xlate Route Details for that translation?  In 5.6 there is the same check box so you can elevate the warnings to errors on a per route basic.

John Mercogliano
Sentara Healthcare
Hampton Roads, VA

[Jim Kosloskey]

John,

Thanks — I thought I saw that option somewhere else.

email: jim.kosloskey@jim-kosloskey.com

[Max Drown (Infor)]

The elevate warnings check box was not checked, still get the error.

-- Max Drown (Infor)

[John Mercogliano]

Do you have a master site and if you do, look at that sites site error config options to see if anything is checked.

John Mercogliano
Sentara Healthcare
Hampton Roads, VA

[Max Drown (Infor)]

We do not use a master site.

If someone wants to test this out, try sending a message through an xlate with a segment that is not defined in the variant, like ZOR. In our case, it was an empty ZOR segment even (ex. “ZOR|”). We did not get the bulkcopy error in the xlt tester, just when we sent it through the process.

-- Max Drown (Infor)

[Jim Kosloskey]

Max,

OK I did the test.

First I get notification of the invalid segment in the Xlate Tester.

Second the engine gives me a WARN not ERR and of course nothing in the Error DB.

I did this on 5.6 and AIX.

email: jim.kosloskey@jim-kosloskey.com

[Max Drown (Infor)]

Did you run the message through the process?

-- Max Drown (Infor)

[Jim Kosloskey]

Max,

Yup.

email: jim.kosloskey@jim-kosloskey.com

[John Mercogliano]

Max,

John Mercogliano
Sentara Healthcare
Hampton Roads, VA

[Max Drown (Infor)]

Yes, I’ve bounced many times.

-- Max Drown (Infor)

[Author]

Replies