Database Error and Repository gets outdated after unarchiving in SAP MDM

[Former Member]

Hello All,

At present, we are working with SAP MDM 7.1 SP05 with Oracle as the database. Now that, we have upgraded the MDM system to SAP MDM 7.1.SP14 with MaxDB as the database, I want to archive my repository which was built in MDM 7.1 SP05 (Oracle) to MDM 7.1.SP14 (MaxDB).

I did the following to move my repository to the new upgraded version:

1. Archived the repository in MDM 7.1.SP05

2. Copied the archive .a2a file from Archives directory in MDM 7.1 SP05 (Oracle) and pasted it to archive directory in MDM 7.1.SP14 (MaxDB).

3. Mounted the MDM server.

4. Unarchived the .a2a file in MDM 7.1.SP14 (MaxDB).

After the Unarchive process, the repository gets displayed in the Console, but the status of the unarchived repository in console is displayed as "Outdated"

So, I tried updating the repository by clicking the Update Repository option from the context menu in Console. When I do so, it throws an error message " Database command execution error. A SQL statement could not execute. The actual error may have been written to a log file."

I am not getting any clue as to what is the issue here.

Request your advice to solve this issue.

Best Regards

Arshiya

[Former Member]

Hi Arshiya

please check the MDS log first, get the SQL statement error as Carlos mensioned above.

you can read this log from console ,and also you can get the source csv file from bellowing path in your MDM server:  <drive>:\usr\sap\<SAPSID>\MDS00\log, get  the right  time log file and  you can open this file with SAP MDM Logviewer, there find  the error  statement.then we can go  further.

best regards

Stephen

[Former Member]

Hi Arshiya,

Before you archive the MDM 71 SP05-repository, please verify and repair (if necessary). The error you are describing sometimes occurs when you for instance deleted fields or tables that are being referenced by Assignments or Validations.

Good luck!

Gerwin

[kulbhushan_madkar]

As we know, we cant start an outdated MDM repository,though you can see the repository,it cant be loaded.

Also, it is mentioned somewhere that MDM repository might not update successfully if underlying data bases have been modified by an application other than MDM.

Kindly share the Report file which is generated when this Update activity is completed. You can view this Report file in Admin tab-->Reports, and can sort using type = Update.

[cweissheimer]

Hello Arshiya!

Investigate the MDS logs for the specific SQL errors that are preventing the update operation.

You can paste them here so I can check them.

Best Regards,

Carlos Weissheimer