cancel
Showing results for 
Search instead for 
Did you mean: 

MDM 5.5 SP05 - Failure to unarchive standard Repositories

Former Member
0 Kudos

Hi,

We have recently upgraded to 5.5 SP05, I now experience failures when trying to unarchive any of the 55510_ or 55520_ Repositories, although with the 55410_, 55420_ and 55430_ Repositories there are no problems.

These are the last few lines of one error log:

<Trace ts="2007/09/07 09:01:27.145 GMT" tid="3085" entry-no="13128"><LF/> Table 210 MaterialsV51_m000-A2i_Data_87:</Trace>

<Trace ts="2007/09/07 09:01:27.165 GMT" tid="3085" entry-no="13131"> creation failed (probably exists)</Trace>

<Trace ts="2007/09/07 09:01:27.183 GMT" tid="3085" entry-no="13132"> Processing A2i_Data_87 - </Trace>

<Trace ts="2007/09/07 09:01:27.184 GMT" tid="3085" entry-no="13133">saving 1 row of 1 in source</Trace>

<Trace ts="2007/09/07 09:01:27.205 GMT" tid="3085" entry-no="13135">Error inserting into A2i_Data_87 table</Trace>

<Trace ts="2007/09/07 09:01:27.215 GMT" tid="3085" entry-no="13136">$$$ Operation ended in ERROR : 84020000H : General error, contact customer support</Trace>

<Trace ts="2007/09/07 09:01:27.218 GMT" tid="3085" entry-no="13137">Dropping failed target Repository [07/09/07 09:01:27]</Trace>

Any help much appreciated.

Kind regards

Kevan

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Kevan,

This behavior occurs when Unarchiving to Oracle or DB2. The standard repository

was created on SQL Server and uses some very long Japanese and Korean strings.

These character sets expand greatly in Oracle and DB2 and exceed the storage

allotted. A work-around for this problem is available in 5.5 SP05 Patch02.

Please read the release notes for placing

Increase TextStart Storage=true

into the mds.ini file.

I think this will fix the problem, however, you may have found a new bug.

Hope this helps.

D Poy.

Former Member
0 Kudos

Thank you for your response Dave.

I have looked through the SP05 Patch02 release notes and cannot find any mention of the mds.ini file.

Do you remember the SAPnote number containing this fix?

Regards

Kevan