Unable to undeploy Component SAP/MI

[Former Member]

Hello hello experts,

As part of our 7.31 upgrade of BW we need to uninstall/undeploy sap component SAP/MI as per 1407471. The problem we are facing is that the component only partially undeployed.

We attempted to remove MI ADMINISTRATION, MI LAPTOP, MI DRIVERS and MI CLIENT. All the "online" undeployments seem to have completed successfully however the "offline" are not successful leaving MI ADMINISTRATION partially installed.

These are the portions that just wont undeploy:

- sap.com/tc/mobile/admin/mds/service

- sap.com/tc/mobile/admin/services

---- SDM LOG ----

Caught exception during undeployment from SAP J2EE Engine's offline deploy API:

com.sap.engine.tools.offlinedeploy.rdb.ODeploymentException: ERROR: Can't remove component tc~mobile~admin~services

com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: ,

          at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:342)

          at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.commitConfigurationHandler(ConfigurationCache.java:1184)

          at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.commit(ConfigurationHandlerImpl.java:914)

          at com.sap.engine.tools.offlinedeploy.rdb.OfflineComponentDeployImpl.undeployComponent(OfflineComponentDeployImpl.java:289)

          at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOfflineUndeployerImpl.performUndeployment(EngineOfflineUndeployerImpl.java:175)

          at com.sap.sdm.serverext.servertype.inqmy.extern.EngineUndeployerImpl.undeploy(EngineUndeployerImpl.java:72)

          at com.sap.sdm.serverext.servertype.inqmy.EngineUndeploymentActionProcessor.executeAction(EngineUndeploymentActionProcessor.java:116)

          at com.sap.sdm.app.proc.undeployment.impl.BeforeExecutingActionImpl.execute(BeforeExecutingActionImpl.java:78)

          at com.sap.sdm.app.view.proc.undeployment.impl.local.VBeforeExecutingActionImpl.execute(VBeforeExecutingActionImpl.java:57)

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

          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

          at java.lang.reflect.Method.invoke(Method.java:331)

          at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)

          at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)

          at com.sap.sdm.gui.server.GuiAdminRoleCmdProcessor.process(GuiAdminRoleCmdProcessor.java:72)

          at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)

          at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)

          at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)

          at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)

          at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)

          at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)

          at java.lang.Thread.run(Thread.java:676)

Caused by: java.sql.BatchUpdateException: Db4TbxPreparedStatement: Failed to do batch update.

          at com.sap.sql.jdbc.db4.Db4TbxPreparedStatement.tryExecuteBatch(Db4TbxPreparedStatement.java:168)

          at com.sap.sql.jdbc.db4.Db4TbxPreparedStatement.executeBatch(Db4TbxPreparedStatement.java:88)

          at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1129)

          at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1091)

          at com.sap.engine.core.configuration.impl.persistence.rdbms.DBAccessDefault.execDeleteEntriesBatch(DBAccessDefault.java:1132)

          at com.sap.engine.core.configuration.impl.persistence.rdbms.UpdateProcessor.flush(UpdateProcessor.java:286)

          ... 22 more

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineOfflineUndeployerImpl.performUndeployment().OFFL_DEPL_EXC)

Feb 15, 2013 10:43:19... Error: Result: error

Feb 15, 2013 10:43:19... Info: Finished undeploying selected development components

Feb 15, 2013 10:43:19... Info: Restoring the state of the instance (JC_sapsbw_SBW_38) process dispatcher from Stopped to Running

Feb 15, 2013 10:43:19... Info: Restoring the state of the instance (JC_sapsbw_SBW_38) process server0 from Stopped to Running

Feb 15, 2013 10:58:39... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

--- END SDM LOG ---

Based on this I found information found here: http://help.sap.com/saphelp_nw04/helpdata/en/5b/302c4142aef623e10000000a155106/frameset.htm

we figured that the problem would most likely be related to the 'SecStore.properties' files so we recreated it using the configTool. This ended up being a 'fail' and we got the same results.

Additional info: not sure if this is useful or not but we noticed that when we connect to the server0 via telnet and list the "STARTED" programs (list_app |

grep sap.com/tc~mobile | grep STARTED) the system returns a list of about 70 programs that are still in operation. I tried stopping then and trying the undeploy, however to no avail.

Honestly, I am totally out of ideas so any help, tips or cues would be greatly appreciated.

Highest regards,

YC

[dorothea_stein · Accepted solution]

Hi,

usually, that part of the exception stack points to a problem in the JDBC driver or the database:

Caused by: java.sql.BatchUpdateException: Db4TbxPreparedStatement: Failed to do batch update.

One reason could be that the driver is too old. To determine the version, please cd to the directory that contains the driver (/usr/sap/<sid>/sys/jdbc/jt400) and execute the following java call:

java -cp jt400.jar utilities.AboutToolbox

The newest available version is JTOpen 7.8. Please follow SAP note 654800 to update the driver.

If that does not help, I recommed to open a CSN ticket to have us look at potential database problems.

Best regards,

Dorothea Stein

[Former Member · Accepted solution]

Hello just a quick update on this issue for anyone else who might get this issue...

Dorothea, you were right our toolbox was pretty old so we updated it, and eventually we realized that the main issue was that the journalizing was not active for the SAP<SID>DB.

I'm guessing something went wrong during the previous refresh!

Anyhow thanks for the input and help...

Regards,

Yannick C.

[sunny_pahuja2]

Hi,

I am not sure if you can uninstall usage type in NW 7.3 but you can deactivate usage type. For more information, you can check Installation Guide to install Additional Usage type on SMP in SAP Netweaver 7.3 Installation guide area.

Thanks

Sunny