Problem in loading repository

[Former Member]

Hi,

A few weeks ago a particular LPAR had crashed and all the systems running on it went down, and we had manually restarted all of them.

Post this incident, although the MDM console shows all the systems as running/active  we are unable to load the repositories. Also the log files show some error as " ConnectionAcceptor::AcceptConnection(): accept() failed with errno=0x0000002A 'Protocol driver not attached'".

Can you please help as to

• why we are unable to load the repositories though our systems are active, and
• what could this error message in the MDS_LOG file mean?

Thanks in advance

Parul

[Former Member]

Parul,

As you said that a particular LPAR had crashed and all the systems running on it went down then you should follow the following approach to load your repository:

1. Stop MDM Server
2. Stop DBMS Server
3. Start DBMS Server
4. Start MDM Server
5. Repair your repository (Must Perform this Step)
6. Start Repository with Update Indices

Thx/ -Tarun

[Former Member]

Hi Parul,

Can you please provide OS and DB details.Also is this error happening only on few systems or happening for all client system?

Thanks,

Ravi

[former_member204080]

Hi ,

As already suggested please follow the sequence.There are cmds at OS level to stop and start the MDM manually.stop mdm first and DB second and while starting reverse procedure.

After restarting it give cmd sapcontrol -nr <SID> function Getsysteminstancelist which will show u whether all three process are running or not.If all process are green then its fine

Now go to MDM console and  here select the host name exactly and load repository .

Once it is loaded completely u should see the repository in green color.

[Former Member]

Hi Parul,

This possibly means there has been system damage.

You can try reverting to previous saved settings or use utility repair software provided by OS support.

However,I would I also suggest what Abhishek has mentioned,taking a proper sequenced restart again.

If the problem persists then you can go ahead getting in touch with OS support.

Thanks,

Ravi

[Former Member]

hello,

What is the sequence that you followed, to restart the system. The normal sequence is to shut MDM Server first, then the Database server. To start the DB server first them MDM Server.

Also do a repository check and repair for the repository.

Regards,
Abhishek

[Former Member]

Hi Abhishek ,

We actually have gone into the MDM Console, mounted the repository ( by right clicking on the server , then entering the database details along with the userid and password) .  

Then we have loaded the repository by right clicking on the repository just mounted and choosing load repository --> immediate.

Even after this, the end users are facing problem and are unable to use the transactions.

Please guide as to what would be the correct procedure to get the systems working in sync.

Thanks

Parul

[Former Member]

Hello,

Please select while loading, update indices rather than, immediate.

Regards,
Abhishek

[Former Member]

hello,

Please specify the sequence that you followed during restart of the entire system,

If possible please  follow the above mentioned sequence and use update indices while loading the repositories.

Regards,

Abhishek

[Former Member]

Hi Abhishek,

If I need to manually restart a server, can you please guide what would be the step-by-step procedure to do so.

Thanks in advance.

Regards

Parul

[Former Member]

Hello,

The process to follow is,

Shut MDM server, then DB server, once done,

Start the DB server first then MDM Server.

Ask your basis guy to restart the server.

There are OS commands based on your server that you need to follow to restart the server

Regards,

Abhishek