Error Synchronizing Slave SRM-MDM Catalog

[Former Member]

Hello,

i have installed and configured the SRM-MDM Catalog 3.0 on Sap Netweaver 7, on Linux OS, Oracle Database.

I have created a slave of my Repository.

While I try to synchronize the Slave with the Master I get the following Return Code

0xFFAA2017

Is there someone who can tell whats the matter with this return code? I found nothing in the internet regarding SRM MDM 3.0

Thanks for you advise.

[Former Member · Accepted solution]

Hi Rico,

the error is a duplicate attribute name error. You may want to check your taxonomy attributes for that. Also, try to verify and repair the repository.

Best regards

Christian

[Former Member · Accepted solution]

Hello,

thanks for the fast answer.

I have deleted all attributes. in the respository. then try to synchronize again. Same Return code...

When I verify the master repository it shows three "non fatal error" see the following error:

****************************************************************************************************************************

$$$ Non-fatal error(1104): Index 'I_1_CO_OId' should be not unique. STACK TRACE:: -

---

> Emergency Stack Back Trace <---- (0):0x237c5ad (1):0x237c7c6 (2):0x235cdf4 (3):0x17825d7 (4):0x1790633 (5):0x17d56df (6):0x17d6db3 (7):0x17d720d (8):0x1424471 (9):0x1ef5f89 (10):0x1ef6ee9 (11):0x1efb3ad (12):0x1efa143 (13):0x2252009 (14):0x224b9ae (15):0x235f90c (16):0x234c778 (17):0x234cd79 (18):0x2b7ee4959143 (19):0x2b7ee6af38cd -

---

> Module List <---- |.text Start |.text End | Module File Name |0x0000000000400000|0x0000000002e01000| /usr/sap/MD3/MDS10/exe/mds-r |0x00002aaaaaaba000|0x00002aaaaac18000| /usr/sap/MD3/MDS10/exe/ncs.so |0x00002aaaaad4c000|0x00002aaaaae2e000| /usr/sap/MD3/MDS10/exe/sapcpp47.so |0x00002aaaaaf49000|0x00002aaaaaf4c000| /lib64/libuuid.so.1.2 |0x00002aaaab099000|0x00002aaaac250000| /oracle/client/10x_64/instantclient_10202/libclntsh.so |0x00002aaaac405000|0x00002aaaac6f6000| /oracle/client/10x_64/instantclient_10202/libnnz10.so |0x00002aaaac8ca000|0x00002aaab0bad000| /oracle/client/10x_64/instantclient_10202/libociei.so |0x00002b7ee4837000|0x00002b7ee4852000| /lib64/ld-2.4.so |0x00002b7ee4953000|0x00002b7ee4967000| /lib64/libpthread-2.4.so |0x00002b7ee4a6c000|0x00002b7ee4a74000| /lib64/librt-2.4.so |0x00002b7ee4b75000|0x00002b7ee4b88000| /lib64/libnsl-2.4.so |0x00002b7ee4c8c000|0x00002b7ee4c8e000| /lib64/libdl-2.4.so |0x00002b7ee4d90000|0x00002b7ee50e2000| /usr/sap/MD3/MDS10/exe/libxerces-c.so.26 |0x00002b7ee5221000|0x00002b7ee5a5a000| /usr/sap/MD3/MDS10/exe/libicudata.so.30 |0x00002b7ee5b5d000|0x00002b7ee5c3b000| /usr/sap/MD3/MDS10/exe/libicuuc.so.30 |0x00002b7ee5d49000|0x00002b7ee5d97000| /usr/sap/MD3/MDS10/exe/libsapucum.so |0x00002b7ee5ed3000|0x00002b7ee63f1000| /usr/sap/MD3/MDS10/exe/libsapnwrfc.so |0x00002b7ee65d2000|0x00002b7ee66b5000| /usr/lib64/libstdc+.so.6.0.8 |0x00002b7ee67b5000|0x00002b7ee67bb000| /usr/lib64/libstdc+.so.6.0.8 |0x00002b7ee67d0000|0x00002b7ee6824000| /lib64/libm-2.4.so |0x00002b7ee6925000|0x00002b7ee6932000| /lib64/libgcc_s.so.1 |0x00002b7ee6a33000|0x00002b7ee6b69000| /lib64/libc-2.4.so |0x00002b7ee6c69000|0x00002b7ee6c6c000| /lib64/libc-2.4.so |0x00002b7ee6c75000|0x00002b7ee6c89000| /usr/sap/MD3/MDS10/exe/libicudecnumber.so -

---

> Symbolic Stack Back Trace <---- 1: 0x000000000237bd07 eo670_UnixTraceStack +0x01c7 Frameinfo [0x0] 2: 0x000000000237c7c6 eo670_CTraceContextStackOCB +0x0046 Frameinfo [0x0] 3: 0x000000000235cdf4 _Z13getStackTracePcjPv +0x0144 Frameinfo [0x0] 4: 0x00000000017825d7 ZN3A2i24FormatVerifyErrorMessageEPNS8ReporterEjz +0x02c7 Frameinfo [0x0] 5: 0x0000000001790633 ZN3A2i7CXCatDB17CheckTableIndexesEPNS12DBConnection16A2i_DBConnectionENS_4Utf86StringERN S1_15TableDescriptorENS_17XCatDBVerifyLevelES8_bRNS_8A2iArrayIjEESB_PNS_8ReporterE +0x0b73 Frameinfo [0x0] 6: 0x00000000017d56df ZN3A2i7CXCatDB20VerifyDBSchemaInLockEPNS12DBConnection16A2i_DBConnectionERKNS_17XCatDBVe rifyLevelES6_bRNS_8A2iArrayIjEES9_RNS_4Utf86StringEPNS_12CheckInTimerE +0x437f Frameinfo [0x0] 7: 0x00000000017d6db3 ZN3A2i7CXCatDB14VerifyDBSchemaERKNS17XCatDBVerifyLevelES3_bRNS_8A2iArrayIjEES6_RNS_4Utf8 6StringEb +0x01e3 Frameinfo [0x0] 8: 0x00000000017d720d ZN3A2i7CXCatDB14VerifyDBSchemaERKNS17XCatDBVerifyLevelERNS_8A2iArrayIjEERNS_4Utf86String Eb +0x006d Frameinfo [0x0] 9: 0x0000000001424471 ZN3A2i8Protocol6Server31MDSAdminServerCommandVerifyRep11CallExecuteEv +0x0101 Frameinfo [0x0] 10: 0x0000000001ef5f89 _ZN3A2i8Protocol6Server18CommandAbstraction7ExecuteEv +0x0199 Frameinfo [0x0] 11: 0x0000000001ef6ee9 _ZN3A2i8Protocol6Server18CommandAbstraction17PrepareAndExecuteEv +0x0c99 Frameinfo [0x0] 12: 0x0000000001efb3ad ZNK3A2i8Protocol6Server17NormalBandHandler23ImplementHandleMessageERNS_3Net6Server15Conn ectionProxyE +0x036d Frameinfo [0x0] 13: 0x0000000001efa143 ZN3A2i8Protocol6Server24FromClientMessageHandler23ImplementHandleMessageERNS_3Net6Server 15ConnectionProxyE +0x03a3 Frameinfo [0x0] 14: 0x0000000002252009 _ZN3A2i3Net6Server10Connection21HandleIncomingMessageEv +0x0059 Frameinfo [0x0] 15: 0x000000000224b9ae ZN124GLOBAL__N__localhome_builder_Projects_7.1.00.xx.nightly_src_GenericLibs_Networking2 ConnectionManager.cpp00000000_6000905126Call_HandleIncomingMessageEPv +0x000e Frameinfo [0x0] 16: 0x000000000235f90c _ZN3A2i17ThreadedOperation15ExecuteFunctionEv +0x003c Frameinfo [0x0] 17: 0x000000000234c778 _ZN3A2i12PooledThread20PooledThreadFunctionEv +0x0158 Frameinfo [0x0] 18: 0x000000000234cd79 ZN3A2i12PooledThread26PooledThreadFunctionHelperEPv +0x0009 Frameinfo [0x0] 19: 0x00002b7ee4959143 startthread +0x0093 Frameinfo [0x0] 20: 0x00002b7ee6af38cd __clone +0x006d Frameinfo [0x0] -

---

> End of Stack Back Trace <----

Edited by: Rico S. on Jun 10, 2009 1:19 PM

[Former Member · Accepted solution]

Can you repair these errors? In your log the line "Non-fatal error(1104): Index 'I_1_CO_OId' should be not unique" shows something like that, i.e. that there's a problem with unique values. Try to repair the repository and then load it with "Update Indices".

If that does not work, check which field this Index could belong to and change it to non-unique. That might be a little tricky. I had a similar problem and used the matching functionality to find duplicate entries for actually non-unique fields.

Let us know.

Christian

[Former Member · Accepted solution]

Hello,

I did repository repair and the errors in veriyfing log are gone. Thanks for that.

Now when I start the synchronization I get a status bar before getting the return code.

Beside, should i unload or load the repositories (Master and Slave) when synchronizing?

Edit: I only have non-unique fields. I think there can be double entries is that right?

I use the standard respository from the installation disc.

Edited by: Rico S. on Jun 10, 2009 2:07 PM

[Former Member · Accepted solution]

Hm, strange.

Generally, the repositories do not have to be loaded for synchronization. If you commit structural changes to the master, the slave repository would be unloaded by MDM. If you synchronize only with data, then it does not really matter.

Here is a list of things you may want to try (in that order):

- Load the repository with Update Indices. This should rewrite the indices.

- Delete the Slave and recreate it.

- Delete the content and try synchronizing an empty repository.

- Delete the repository and unarchive it again.

These are my suggestions, but you might want to simply drop SAP a message in form of an OSS note. Let us know what happened.

Good luck!

Christian

[Former Member · Accepted solution]

Hello,

I have solved the problem. It seems that the slave I created was deffect. After creating a new Slave and changing the data with the Data Manager within the Master I could synchronize the new Slave.

Thanks for your Help.