Skip to Content
author's profile photo Former Member
Former Member

MDM Workflow - Database binary Object Error

Hi all,

I developed several MDM worklows without problems. All of a sudden I am getting "Database binary object error" when launching my workflows. Any ideas why this may be happening and how to fix it?

I am using MDM 5.5 SP3 [5.5.28.00] with an oracle dbms.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 21, 2006 at 07:36 PM

    Hi,

    I got the similar error couple of days ago. I am also using MDM SP3 amd Oracle database. But, when I unloaded my repository, stopped and started the MDM Server and loaded the repository again, the problem was resolved. I am not at sure, whay this happened.

    Regards,

    Rajani

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Mar 15, 2006 at 12:16 PM

    Hi, Owen!

    Yestaday I was start developed MDM workflow, and I am getting "Database binary object error" when launching my workflows. I am also using MDM 5.5 SP3 [5.5.28.17] with an Oracle dbms. Unloaded my repository, stopped and started the MDM Server and loaded the repository again, the problem was NOT resolved.

    Ask me, please, how you was resolved this problem?

    Any ideas why this may be happening and how to fix it?

    Regards,

    Alexsey

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Richard,

      We're trying to upgrade from MDM 4.0.73.02 to 5.5 through subsequent upgrades to SP0, SP1, SP2, SP3 and SP4 (5.5.33.25) but receiving 'Database binary Object Error' while trying to unarchive the repository in Oracle 9.0 set with Unicode character set. In order to get around this problem we created two Oracle 9.0 database containers: one with mixed character set(CHARACTER SET WE8MSWIN1252 and NATIONAL CHARACTER SET UTF8) and another with unicode only (UTF8).

      We don't have any issues running the upgrade in the mixed character set environment, however when we archive the repository in the first container and try to anarchive it in the second container(Unicode), we still receive the same Database binary Object Error. Since our business requires multilingual support, we have to be able to use Unicode. Any sunggestions?

      Thank you,

      Lena.

      Message was edited by:

      Yelena Zeltser

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.