cancel
Showing results for 
Search instead for 
Did you mean: 

Recover UMDB database - Dbstudio 7.7.06.09 RedHat ES 5

Former Member
0 Kudos

Platform: dbstudio 7.7.06.09 on RedHat 5 ES 64bits IBM x3650 8GbRAM:

Since a power failure and abnormal shut down of the dbstudio server last week, everytime I run dbstudio, the system tries to recover the user managemente database. Apparently got corrupted. After dbstudio recovered, I have to setup the local user permissions so I can administer the synchronization folder. After that, I can connect ot message server, but I receive error messages when I try to update message server at the synchronization folder context menu.

How can I solve this issue without reinstalling dbstudio again or do I have to?

Best Regards

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

MaxDB and DBStudio were reinstalled to solve the problem

lbreddemann
Active Contributor
0 Kudos

Hi Daniel,

please check the content of the KNLMSG file of the .UMDB database.

What errors do you get there?

Are you a SAP customer?

If so you may open a support message and we'll see what we can do about the .UMDB instance of yours.

regards,

Lars

Former Member
0 Kudos

Thank you. I finally decided to reinstall dbstudio and maxdb. At this moment the KRNLMSG file doesn't show any errors, however, the replication service which was working fine before the problem is now showing errors.

When I start up the syncservice service at the master server the following is shown:

INFO: starting administration thread at port 7223

INFO: done.

javax.naming.NamingException: com.sap.sdb.msgServer.service.ServiceException: Service <JNDI>: Name <jms.queue.SYNC_QUEUE_DEST1269879645557000164> not found!

javax.naming.NamingException: com.sap.sdb.msgServer.service.ServiceException: Service <JNDI>: Name <jms.queue.SYNC_QUEUE_DEST1269879645557000164> not found!

-- Network Failover --

When I do the same at the client server the following is shown:

INFO: starting administration thread at port 7223

INFO: done.

javax.naming.NamingException: com.sap.sdb.msgServer.service.ServiceException: Service <JNDI>: Name <jms.topic.SYNC_TOPIC_DEST1269879645557000164> not found!

javax.naming.NamingException: com.sap.sdb.msgServer.service.ServiceException: Service <JNDI>: Name <jms.topic.SYNC_TOPIC_DEST1269879645557000164> not found!

-- Network Failover --

I recreated the master/client units but the same error appears. My network is ok and the servers can see each others.

Thank you Lars.