Skip to Content
Technical Articles
Author's profile photo Varun Chhibber

Remove unwanted xs engine (classic) service from HANA topology


This blog details out the procedure to remove unwanted xs engine service from HANA topology. We have faced a situation where two xs-engine services added in the HANA database and one for them is not getting started.

System Details

  • HANA 2.0 SPS03


  1. You are logged on to the system database and having a system privilege DATABASE ADMIN.
  2. Make sure to take data backup of SystemDB.
  3. The database is online.
  4. Get the volume id, port number, and check-in M_TOPOLOGY_TREE view.


2679277 – HANA backup fails with error on orphaned volume in Multitenant Database


Error details

  1. Two xs-engine services added and one of them is not getting started.
  2. Backup error–Backup is not possible because the service ‘xs-engine’ at <host: port> responsible for the volume ‘volume id’ has the wrong state ‘no’, Orphaned volume with the number ‘volume id’ found in the topology.

Backup Error Message



We removed the SAP HANA Extended Application Services (SAP HANA XS) from the topology of our SAP HANA database because we do not use any applications that require SAP HANA XS.

Please do not remove the SAP HANA XS if there is an application running which uses the xs engine.


To solve this issue, we removed unwanted xs-engine from the topology.

Execute command “SELECT * FROM M_TOPOLOGY_TREE” to check-in the view of the topology tree and take a complete download on your desktop for further reference.

In the topology tree, we can find the volume id and port number of the service.

Execute command “SELECT * FROM M_VOLUMES” to check-in the assigned volume to the xs engine service port.


Once the volume of the xs engine service is verified also check the M_SERVICES view to confirm that there are no services associated with this volume.

Also, verify the size of the volume ID at the os level.

Removal of the service:

With the help of the steps mentioned above, we are now able to identify the service, port, and volume ID which needs to be removed.

In my case, the port number is 33007 and the volume ID is 3:2.

So let’s remove the service and volume using the below commands.

Make sure to execute these commands from SYSTEM DB.

Remove Service:-

ALTER SYSTEM ALTER CONFIGURATION (‘topology.ini’, ‘system’) UNSET (‘/host/<Host Name>/xsengine’,’33007′) WITH RECONFIGURE

Remove Volume ID:-

ALTER SYSTEM ALTER CONFIGURATION (‘topology.ini’, ‘system’) UNSET (‘/volumes’, ‘<database_id>:X’) WITH RECONFIGURE

here X is the volume id

Once the above commands executed successfully, then check if the xs service with error is removed or not.


  • Unwanted XS engine service is removed.
  • One engine with port 33040 is up and running.
  • There is no error in the overall status of the HANA database.
  •  Now we are able to take complete DB backup of the tenant database.     


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Sumit Jaiswal
      Sumit Jaiswal

      Thanks for the post.

      I'd just like to add that SAP has released detailed KBA sets to add/remove services such as xsengine,script-server, statistics server  etc in 2222249 - How-To: Resolving SAP HANA Service Inconsistencies between Daemon and Topology

      Also, the steps specific to xsengine are detailed  in 1697613 - Removing the SAP HANA XS Classic Engine service from the topology


      Author's profile photo Varun Chhibber
      Varun Chhibber
      Blog Post Author

      Thanks Sumit for sharing additional information.

      Author's profile photo DEL BASIS

      It's such a helpful document Varun !!

      Thank you !!

      Author's profile photo Kemal Ertas
      Kemal Ertas


      it is very good doc.



      Author's profile photo Varun Chhibber
      Varun Chhibber
      Blog Post Author

      Thanks Kemal!

      Author's profile photo Joerg Aldinger
      Joerg Aldinger

      Thank you for these instructions. We had a corrupt log area for the xsengine, and recreating the log area was failing, and the ALTER DATABASE .. REMOVE 'xsengine' ... was also failing since the service was not responding.

      These steps helped us remove the failed xsengine service, remove the data and log directories and then add it back as a new one.

      Thanks again!