on 08-01-2012 12:02 PM
Hi
After we shut down some of our systems I cannot delete (right click -> delete) the related servers nor the databases from Database Studio 7.9.08.02: Cannot connect to host (obviously).
Has anybody a workaround for this which does not involve restarting the systems?
Regards
Michael
Hi Michael,
What error message do you see while you try to delete ? A screenshot would be helpful to answer your question.
Regards,
Yashwanth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Yashwanth,
to be honest I don't really get a error message while trying to delete - it simply does not do anything after I click OK.
But before deletion, in DB Studio -> my Landscape, if I expand the server node hosting the database, I get following error (which will not help very much since the server is shut down):
As I said, if I now try to delete either the server or the database below the server I don't get any error except the one above. It only asks if I'm sure I want to delete and on "OK" nothing really happens.
Hi Michael,
I tried doing this myself. I have the same version of DB Studio in my machine 7.9.08.02. I had my linux machine with MaxDB in the server list. After I shutdown my linux machine, and tried refreshing the servers in the DB studio, I saw a red X saying (x_server inactive). I tried deleting the server and it was deleted without any problems. Your situation seems starage to me - DB studio doing nothing.
Try opening the Database Studio using "Run as administrator" option and try deleting the server from the list.
Your Database Studio will save your landscape information into a metadata file. If the above doesnt help, the other alternative would be to delete the configuration files of the Database Studio as follows:
If you do NOT have multiple servers being monitored in the DB studio, this is a good solution, else you have to add the other servers manually all over again. If this is the case, then try restoring the file you backup in the 1st step and recover it as follows and then try deleting the inactive server from the list.
3. Recover the file <HOME>/<user>/sdb/DatabaseStudio/.metadata that you have saved before.
Let me know if this helps resolve your issue.
Regards,
Yashwanth
Okay, I didn't tell you a thing that may be relevant:
Recently I configured Central User Management in MaxDB Database Studio. I installed MaxDB-Software on a dedicated Win7 machine, set up a database called MAXDB, activated Central User Management (CUM) with an Identity called "it" and started adding Servers/Databases to this Identity.
Now all our admins - and also on this dedicated host - use their local DBStudio Installation with CUM and identity "it".
I do not know if your solution with metadata-file is also valid for CUM?!
I cannot delete the offline servers on that dedicated host, too - same behaviour.
The servers are not getting "inactive" after refresh of the Servers-node.
Maybe - due to lack of documentation - I did something wrong while setting up CUM?
Hello Michael,
Ok, now its clear for me that you are using User Management & created Identity specifying global logins for the landscape & using this to login to different databases - correct ?
Do the following steps:
Try removing the offline server one more time. Close the database studio & collect the following information.
Database Studio log file:
The system overwrites this log file each time Database Studio is started and saves the old log file as dbstudio.log.bak.
Please give me the database studio current log "dbstudio.log" & previous DB Studio log file "dbstudio.log.bak" located in
<user_home>\sdb\DatabaseStudio\.metadata\.plugins\com.sap.sdb.tools.core
Regards,
Yashwanth
Hi Yashwanth
both logs contain more or less the same information; because this would be about 1000 lines I will only post one of the repeated error messages:
[D:2012-08-07 09:48:14.109][ERROR ][T:10][G:1344325694108:947][S:none][M:none][C:Usermanagement] Delete childs [P:com.sap.sdb.resources.usermanagement][L:com.sap.sdb.tools.resources.usermanagement.impl.Server.delete(Server.java:273)][N:1344325694108:947][DB:null][U:null]
com.sap.sdb.tools.usermanagement.UM_Exception: Delete childs
at com.sap.sdb.tools.usermanagement.UM_Storage.ExceptionHandler(UM_Storage.java:8627)
at com.sap.sdb.tools.usermanagement.UM_Storage.deleteChilds(UM_Storage.java:8176)
at com.sap.sdb.tools.usermanagement.UM_Storage.delete3(UM_Storage.java:8411)
at com.sap.sdb.tools.usermanagement.UM_Storage.deleteObject(UM_Storage.java:8184)
at com.sap.sdb.tools.usermanagement.UM_Storage.delete(UM_Storage.java:5495)
at com.sap.sdb.tools.usermanagement.UM_Object.delete(UM_Object.java:413)
at com.sap.sdb.tools.resources.usermanagement.impl.Server.delete(Server.java:271)
at com.sap.sdb.tools.ui.actions.DeleteResourceAction$1.run(DeleteResourceAction.java:73)
at com.sap.sdb.tools.resources.base.internal.Workspace.run(Workspace.java:184)
at com.sap.sdb.tools.resources.base.internal.Workspace.run(Workspace.java:169)
at com.sap.sdb.tools.ui.actions.DeleteResourceAction.run(DeleteResourceAction.java:78)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Invalid column index 4.
at com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:300)
at com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB.generateSQLException(SQLExceptionSapDB.java:112)
at com.sap.dbtech.jdbc.ResultSetSapDB.findColumnInfo(ResultSetSapDB.java:2814)
at com.sap.dbtech.jdbc.ResultSetSapDB.getString(ResultSetSapDB.java:1290)
at com.sap.dbtech.jdbc.trace.ResultSet.getString(ResultSet.java:318)
at com.sap.sdb.tools.usermanagement.UM_Storage.deleteChilds(UM_Storage.java:8151)
... 38 more
[D:2012-08-07 09:48:14.109][ERROR ][T:10][G:1344325694108:947][S:none][M:none][C:Usermanagement] SAP DBTech JDBC: Invalid column index 4. [P:com.sap.sdb.resources.usermanagement][L:com.sap.sdb.tools.resources.usermanagement.impl.Server.delete(Server.java:273)][N:1344325694108:947][DB:null][U:null]
com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Invalid column index 4.
at com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:300)
at com.sap.dbtech.jdbc.exceptions.SQLExceptionSapDB.generateSQLException(SQLExceptionSapDB.java:112)
at com.sap.dbtech.jdbc.ResultSetSapDB.findColumnInfo(ResultSetSapDB.java:2814)
at com.sap.dbtech.jdbc.ResultSetSapDB.getString(ResultSetSapDB.java:1290)
at com.sap.dbtech.jdbc.trace.ResultSet.getString(ResultSet.java:318)
at com.sap.sdb.tools.usermanagement.UM_Storage.deleteChilds(UM_Storage.java:8151)
at com.sap.sdb.tools.usermanagement.UM_Storage.delete3(UM_Storage.java:8411)
at com.sap.sdb.tools.usermanagement.UM_Storage.deleteObject(UM_Storage.java:8184)
at com.sap.sdb.tools.usermanagement.UM_Storage.delete(UM_Storage.java:5495)
at com.sap.sdb.tools.usermanagement.UM_Object.delete(UM_Object.java:413)
at com.sap.sdb.tools.resources.usermanagement.impl.Server.delete(Server.java:271)
at com.sap.sdb.tools.ui.actions.DeleteResourceAction$1.run(DeleteResourceAction.java:73)
at com.sap.sdb.tools.resources.base.internal.Workspace.run(Workspace.java:184)
at com.sap.sdb.tools.resources.base.internal.Workspace.run(Workspace.java:169)
at com.sap.sdb.tools.ui.actions.DeleteResourceAction.run(DeleteResourceAction.java:78)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Else see here (dbstudio.log): http://pastebin.com/gPUsRFqt
and here (dbstudio.log.bak): http://pastebin.com/weq23gyJ
Thanks so far for your commitment!
Regards
Michael
I just opened a message with SAP and looking forward to an official response.
Did you succeed with recreation of the problem?
by the way, is there any documentation for Central User Management functionality within MaxDB Studio? Because - to be honest - I don't know what I did or what consequences this has
Hi Michael,
What is the message number ?
Unfortunately, we were not able to reproduce the problem. I contacted the developers in germany - the reason why there is no documentation for this is, this functionality is not officially supported and we do not recommend sharing of landscapes and logins.
I am sorry I could not provide any solution to this at this time. You do not have to worry about any consequnces. As I suggested you before, move your old user profile (copy or rename - DO NOT DELETE) to another location and you can recreate your landscape. Heres the documentation on how to create landscapes and managing users & creating login template in the Database Studio.
http://help.sap.com/saphelp_nw72/helpdata/en/f6/0884d8b4ee491cab96e2d046c257f0/frameset.htm
Hope this helps.
Regards,
Yashwanth
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.