cancel
Showing results for 
Search instead for 
Did you mean: 

Error after unarchive process - Error: The MDM respository is invalid

Former Member
0 Kudos

Hi Experts:

We are on the process to unarchive a repository, but we are getting this error when trying to logon to load it.

Repository connect failed

Error: The MDM repository is invalid

p.s. We are trying to copy our Production environment to our Test Environment.

Thanks,

Claudia Hardeman

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi all,

I am working with Claudia and we are trying ur suggestion. However No success as of now.

Also, wanted to know that how we can repair a repository without actually logging on or without connecting to the repository?

Former Member
0 Kudos

Hi Claudia

Before archiving the repository we should always verify the repository. In the report generated see if any fatal errors are coming. If needed repair and compact the repository and then archive again.

You can use CLIX command for doing all these jobs without logging into MDM console and connecting to the repository.

Regards

Ravi

Former Member
0 Kudos

We did ran the verification and said it was ok, no errors.

How do you use CLIX to repair? I mean any string? What command strings to run?

Thanks a lot for your help,

Claudia Hardeman

Former Member
0 Kudos

Ravi:

We found some documentation with step by step instructions, we are going to try that.

Thanks,

Claudia Hardeman

Former Member
0 Kudos

We had a similar problem with the "invalid repostory" message. Check the logs. Somehow the database user password and the one stored in the mds.ini file was out of sync. We reset the repository user's password and then modified the mds.ini file to set the new password. You'll have to remove the "Password+" setting and add "Password" with the clear text password. After restarting MDM server it will encrypt the password. After that we were able to load the repository successfully.

Good luck,

John

Former Member
0 Kudos

Hi Claudia,

I have been across this scene many times the easiest and fastest way to get rid of this problem is -

1) Delete the repository from Database

Step 1 u2013 Connect to the Database using the Database Management tool

Step 2 u2013 Delete the databases - RepositoryName_z000 and RepositoryName_m000

Step 3 u2013 Delete repository specific entry from the table A2i_Catalogs in A2i_xCat_DBs database

2) Unarchive the repository from old archive

3) Load the repository

This will solve the issue.

Regards.

Former Member
0 Kudos

HI Claudia,

Is that problem solved?

Or Still facing the issue?

Former Member
0 Kudos

Thank you everybody for your help, deleting the repository was our only option.

Thanks again!

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Claudia,

Please let us know the symbol on the repository.

If the symbol is freezed without any color, the reason might be that the version in which the repository was archived & in the environment which you are trying to unarchive are different.

This problem will be slved if you update the repository.

Regards,

Pramod

Edited by: Pramod Govindan on Jun 4, 2009 6:25 AM

Former Member
0 Kudos

HI Claudia,

Please perform an update on repository

Former Member
0 Kudos

did the unarchive process go okay?

check the unarchive log if any.

try updating the repository. is ur test & production on same patch level or different? ideally it should not matter. But i guess an update repository action should fix any inconsistencies.

-Sudhir

Former Member
0 Kudos

Hi Claudia,

Follow the below steps

1. Stop MDM Server

2. Restart Database server

3. Start MDM Server

Try the same for your Mount repository issue.

Regards,

Jitesh Talreja

Edited by: Jitesh Talreja on Jun 4, 2009 2:17 AM

Former Member
0 Kudos

Hi Claudia,

Try restarting the database and MDM server. Also check whether the user (this is the Database user you give DBMS login and PWD) must be system user abd has rights to create database.

Best Regards,

Silpa Chillakuru