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

Master-Slave Problem: Please Help

I am having a problem getting master/slave repositories set up for synchronization.

My MDM server environment is Solaris with Oracle 10.2 database.

MDM version is 5.5.41.58 (5.5 SP05).

I create a repository. I unarchive my data into it. I create a slave repository from it. I go into Data Manager and change the description of one product in the master repository. In the Console, the server log has the following message:

Master Server failed to log change because of error: The new transaction id is less than the last transaction id. (code 4289454080).

Has anybody had the same issue? Any clues as to what the problem and/or fix is?

Thanks in advance.

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Sep 21, 2007 at 02:55 AM

    Hello Bruce,

    That error implies a specific and unusual problem with the master change log. Did you get any errors in either Server or Assertion logs when creating the slave?

    Secondly, you mentioned that you created a repository and unarchived data into it. Can you elaborate on that process?

    Finally, would it be possible for you to run the CLIX command repGetChangeCounter for the master and slave repositories?

    Regards,

    Simon

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      There is a bug in MDM releases 3.0 through 5.5 SP5 patch 2 where changes to master repositories are not logged properly for further synchronization if the MDS server server mounting them is mounted by a Console using either an IP address, "localhost" or a fully qualified hostname. When operating on master repositories with affected MDM releases, only the hostname should be used for mounting MDS servers in the Console.

      More detail is available in SAP note 1098610.

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.