MaxDB Database Studio - Internal DB no more coming up

[Former Member]

After a reboot of the system where DBStudio is running the integrated database doesn´t come up again.

Trying to start the instance manually just leads to a "Database could not be started, this happend already 5 times" entry in the windows event log. Since I couldn´t find a knldiag (or knldiag.err) I wonder, how to recover from that situation and find out, what the problem with the database is.

Database Studio

Version: 7.7.03.18

Build: 018-123-160-639

Any ideas how this can be drilled down?

Regards,

Markus

[Former Member]

Hello Markus

with xinstinfo you can figure out where your IndeData is.

Database Studio is a JDBC based application and needs the x_server for the localhost communication, too.

The log file shows that Database Studio has a problem to start the x_server. Would you mind trying to start the x_server or a x_show via console?

Kind Regards

Markus Özgen

[markus_doehr2]

Hi Markus,

the x_server is running (and was at the time of starting, I don't know why this message is in the log):

C:ProgrammeSDBprogramsbin>x_show

SERVERDBs:
  - .M770318            [Stopped]
  - .UMDB               [Stopped]

Services:
  XSERVER               [Running]

I think I have a weird problem on that box:

C:ProgrammeSDBprogramsbin>xinstinfo
OS_ERROR  2: Das System kann die angegebene Datei nicht finden.
RTE_ERROR 1: Error during registry access to key IndepData
OS_ERROR  2: Das System kann die angegebene Datei nicht finden.
RTE_ERROR 1: Error during registry access to key IndepPrograms

The database studio was working fine (Installed it on a WTS 2K3) - but after reboot there seems to be some files missing although I didn't change (and nobody else) anything.

So much for indeterministic operating systems...

--

Markus

[Melanie]

Hi Markus,

this really sounds weird.

Do the dbmcli commands "dbm_getpath indepdatapath" and "dbm_getpath indepprogpath" work?

Could you please open a message for this issue to allow us to access your system?

Thanks,

Melanie

[markus_doehr2]

Hi Melanie,

those commands don't work:

C:ProgrammeSDBprogramsbin>dbmcli dbm_getpath indepdatapath
Error! Connection failed to node (local) for database (no dbname):
database instance not found

C:ProgrammeSDBprogramsbin>dbmcli -d .UMDB dbm_getpath indepdatapath
Error! Connection failed to node (local) for database .UMDB:
database instance not found

An OSS call (945376 2007) has been created to access the system.

Thank you!

Regards,

--

Markus

[Former Member]

Hello Markus

would you mind providing us the DB Studio log file dbstudio.log, too? You can find the log file in your /sdb/DatabaseStudio/.metadata/.plugins/com.sap.sdb.tools.core directory.

Thanks in advance

Markus Özgen

[markus_doehr2]

Hi Markus,

the dblog contains

Database Studio

Version : 1.0

Eclipse Version : 3.2.0

-

---

[D:2007-11-09 13:10:52.921][ERROR ][T:10][G:1][S:none][M:none][C:UI] Database connectivity not available

[P:com.sap.sdb.tools.core.ui][L:com.sap.sdb.tools.core.ui.CoreUIPlugin.connectUser(CoreUIPlugin.java:191)]

com.sap.sdb.tools.usermanagement.UM_Exception: Start XServer failed

at com.sap.sdb.tools.usermanagement.UM_DBManagement.umdbStartXServer(UM_DBManagement.java:206)

at com.sap.sdb.tools.core.ui.CoreUIPlugin.connectUser(CoreUIPlugin.java:189)

at com.sap.sdb.tools.ui.application.ToolsUIWorkbenchWindowAdvisor.postWindowOpen(ToolsUIWorkbenchWindowAdvisor.java:113)

at org.eclipse.ui.internal.WorkbenchWindow.fireWindowOpened(WorkbenchWindow.java:1128)

at org.eclipse.ui.internal.WorkbenchWindow.open(WorkbenchWindow.java:685)

at org.eclipse.ui.internal.Workbench.openWindowsAfterRestore(Workbench.java:2886)

at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1686)

at org.eclipse.ui.internal.Workbench.access$12(Workbench.java:1650)

at org.eclipse.ui.internal.Workbench$17.run(Workbench.java:1529)

at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)

at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1473)

at org.eclipse.ui.internal.WorkbenchConfigurer.restoreState(WorkbenchConfigurer.java:183)

at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:702)

at org.eclipse.ui.internal.Workbench.init(Workbench.java:1085)

at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1847)

at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)

at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)

at com.sap.sdb.tools.ui.application.ToolsUIApplication.run(ToolsUIApplication.java:78)

at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)

at org.eclipse.core.launcher.Main.basicRun(Main.java:280)

at org.eclipse.core.launcher.Main.run(Main.java:977)

at org.eclipse.core.launcher.Main.main(Main.java:952)

Caused by: com.sap.sdb.tools.dbmprocess.LaunchException: DbmProcessUtility: Could not start x server.

at com.sap.sdb.tools.dbmprocess.DbmProcessUtility.startXServer_aux(DbmProcessUtility.java:246)

at com.sap.sdb.tools.dbmprocess.DbmProcessUtility.startXServer(DbmProcessUtility.java:181)

at com.sap.sdb.tools.usermanagement.UM_DBManagement.umdbStartXServer(UM_DBManagement.java:203)

... 30 more

[D:2007-11-09 13:10:52.921][ERROR ][T:10][G:1][S:none][M:none][C:UI] DbmProcessUtility: Could not start x server. [P:com.sap.sdb.tools.core.ui][L:com.sap.sdb.tools.core.ui.CoreUIPlugin.connectUser(CoreUIPlugin.java:191)]

com.sap.sdb.tools.dbmprocess.LaunchException: DbmProcessUtility: Could not start x server.

at com.sap.sdb.tools.dbmprocess.DbmProcessUtility.startXServer_aux(DbmProcessUtility.java:246)

at com.sap.sdb.tools.dbmprocess.DbmProcessUtility.startXServer(DbmProcessUtility.java:181)

at com.sap.sdb.tools.usermanagement.UM_DBManagement.umdbStartXServer(UM_DBManagement.java:203)

at com.sap.sdb.tools.core.ui.CoreUIPlugin.connectUser(CoreUIPlugin.java:189)

at com.sap.sdb.tools.ui.application.ToolsUIWorkbenchWindowAdvisor.postWindowOpen(ToolsUIWorkbenchWindowAdvisor.java:113)

at org.eclipse.ui.internal.WorkbenchWindow.fireWindowOpened(WorkbenchWindow.java:1128)

at org.eclipse.ui.internal.WorkbenchWindow.open(WorkbenchWindow.java:685)

at org.eclipse.ui.internal.Workbench.openWindowsAfterRestore(Workbench.java:2886)

at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1686)

at org.eclipse.ui.internal.Workbench.access$12(Workbench.java:1650)

at org.eclipse.ui.internal.Workbench$17.run(Workbench.java:1529)

at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)

at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1473)

at org.eclipse.ui.internal.WorkbenchConfigurer.restoreState(WorkbenchConfigurer.java:183)

at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:702)

at org.eclipse.ui.internal.Workbench.init(Workbench.java:1085)

at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1847)

at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)

at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)

at com.sap.sdb.tools.ui.application.ToolsUIApplication.run(ToolsUIApplication.java:78)

at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)

at org.eclipse.core.launcher.Main.basicRun(Main.java:280)

at org.eclipse.core.launcher.Main.run(Main.java:977)

at org.eclipse.core.launcher.Main.main(Main.java:952)

====================> current write pos <====================

which is clear since the database kernel is not runnign and I can't start it.

Regards,

Markus

[Melanie]

Hello Markus,

the name of the UserManagementDataBase should be <b>.UMDB</b>. The rundirectory should be located in <indep_data>/wrk/.UMDB

Can you find this directory and send me the logfiles?

Is this DatabaseStudio running on Windows or on Linux?

Thanks,

Melanie

[markus_doehr2]

Hi Melanie,

there is no "indep_directory" on those installation, that's why I'm wondering where the data is stored.

The directory structure looks like:

c:\programme\sdb\programs

bin

cluster

DatabaseStudio

env

etc

install

pgm

No "wrk" directory in the full path.

--

Markus