Decommissioning

WARNING: Decommissioning operations result in non-reversible loss of data.

Decommissioning involves the removal of managed objects such as hosts, databases and technical systems. This includes removal of all related artefacts such as customer network, LMDB namespace, data from Monitoring and Alerting Infrastructure (MAI), reporting data, configuration data, logs, alerts and work-modes.

Removing a host or a technical system from the LMDB will remove all data related to the corresponding LMDB object (identified by its GUID); therefore, the LMDB cleanup is the last step of the decommissioning operation. Decommissioning requires permissions for the RSRSM_SSI_CLEANUP report and administrative access for the technical system.

If you plan to move a technical system from one customer network to another, you must first decommission this system from the old customer network.

The general approach for decommissioning is to:

  • First decommission the technical system (like AS ABAP, AS JAVA)
  • Then decommission the database used by the technical system, if it is not used by other technical systems
  • Then decommission the hosts
  • Databases and hosts can only be deleted if they are no longer used by other managed objects

WARNING:

  • The tools provided to cleanup customer networks or technical systems can be instructed to also cleanup unused hosts. The tool to cleanup hosts will only cleanup a host if it is not used. During the cleanup process a host may go to an unused state if the technical system using the host was cleaned up.
  • A host is considered to be unused, if it is no longer used/referenced by other LMDB entities. It is not checked if the host is still used by SAP Focused Run features like Open Component Monitoring or Stand-Alone Host Monitoring. Please pay attention to this.

Automatic Decommissioning

WARNING: Decommissioning operations result in non-reversible loss of data.

  • Follow this general procedure for automatic decommissioning of technical systems, including a HANA single DB:

1    If you want to remove the technical system from the data center

a.    Plan a downtime work-mode for the technical system

b.    Shut down the technical system and all its hosts (if hosts are later re-used, the SimpleDAs must be deleted prior to re-using the hosts)

2    If you want to keep the technical system in your data center, but you want to remove the technical system from your SAP Focused Run installation

a.    Disable all SLD data suppliers for the technical system

b.    Disable outside discovery for all hosts of the technical system

3    Trigger cleanup of the technical system via SA38 Report RSRSM_SSI_CLEANUP (or using the SSI Web Services) to:

a.    Cleanup all SAP Focused Run feature-specific data stores

b.    Delete the technical system from the LMDB

4    If the technical system is still used in other SAP Focused Run or SAP Solution Manager installations, in order to avoid sending landscape data to the current SAP Focused Run installation, from which you have just removed the technical system

a.    Reconfigure and enable all SLD data suppliers for the technical system, to no longer send data to the current SAP Focused Run installation

b.    Reconfigure and enable the outside discovery for all hosts of the technical system, to no longer send data to the current SAP Focused Run installation

c.     Remove users on the technical system, which were created for data collection (see section “Technical Users in Managed Systems” in the SAP Focused Run Security Guide)

1    SAP Note 2883329 must be implemented on your SAP Focused Run test and production systems

2    The HANA system DB can only be decommissioned after all HANA tenant DBs have been decommissioned

3    The HANA system DB and each HANA tenant DB must be decommissioned individually

  • Decommission a HANA tenant DB as follows:

1    If you want to remove the HANA tenant DB from the data center

a.    Plan a downtime work-mode for the HANA tenant DB

b.    Disable the data supplier for the HANA system DB where the HANA tenant DB is running

2    Trigger cleanup of the HANA tenant DB via SA38 Report RSRSM_SSI_CLEANUP (or using the SSI Web Services) to:

a.    Cleanup all SAP Focused Run feature-specific data stores

b.    Delete the HANA tenant DB from the LMDB

3    If you want to keep the HANA system DB (since it is still used by other HANA tenant DBs)

a.    Delete the HANA tenant DB from the HANA system DB (skipping this step will cause the HANA tenant DB to reappear in the SAP Focused Run system)

b.    Enable the data supplier for the HANA system DB where the HANA tenant DB was running

  • Decommission a HANA system DB using the above described general procedure.

Report RSRSM_SSI_CLEANUP

The cleanup report has been designed so, that it in case an error occurs during the deletion of a given object, you can simply retry to delete that object. Check the log messages, and remove the root cause of the error before retrying the delete.

The SLG1 messages logged during the cleanup operation, will be displayed in the Cleanup Report UI.

If you want to inspect the SLG1 messages logged for a cleanup operation, after you have closed the Cleanup Report UI, you can do so via transaction SLG1. You must specify:

  • Object: AI_SSI
  • Subobject: CLEANUP

To remove a technical system from the SAP Focused Run system and the LMDB:

  1. Manually execute SA38 report RSRSM_SSI_CLEANUP
  2. Select a Customer Network
  3. Go to the Cleanup Technical System tab
  4. Select a Technical System
  5. Make your choice from the offered options
  6. Press Delete Selected Objects
  7. This will trigger the cleanup

To remove a host from the SAP Focused Run system and the LMDB:

  1. Manually execute SA38 report RSRSM_SSI_CLEANUP
  2. Select a Customer Network
  3. Go to the Cleanup Host tab
  4. Select a Host
  5. Press Delete Selected Objects
  6. This will trigger the cleanup

To remove a customer network from the SAP Focused Run system and the LMDB:

  1. Manually execute SA38 report RSRSM_SSI_CLEANUP
  2. Select a Customer Network
  3. Go to the Cleanup Customer Network tab
  4. Make your choice from the offered options
  5. Press Delete Selected Objects
  6. This will trigger the cleanup

WARNING:

  • A customer network can ONLY be deleted if no technical systems and hosts are assigned to it.
  • The associated namespace will be also deleted.

Known Issues

Decommissioning of Introscope Enterprise Manager Limitation

After the decommissioning of an Introscope EM system you may receive a warning like:

Could not delete Introscope EM properties with SAP Focused Run connection details from the Simple Diagnostics Agent. The Introscope EM may continue to send data to the SAP Focused Run system.

If this occurs, the decommissioning program has not been able to confirm that the relevant properties have been deleted from the Simple Diagnostics Agent. It is likely that the Introscope EM system still has the details for SAP Focused Run communication stored. As a consequence, the Introscope EM system may continue to send data to the SAP Focused Run system, although the technical system was successfully removed from the SAP Focused Run system and from the LMDB. In order to resolve this, you must:

  • Logon the OS of the Introscope EM system
  • Remove or rename the file <EM-HOME>/sap/<FRUN-SID>_srsm.e2emai.properties
  • In case of problems with this specific instruction you may open an incident at SV-SMG-DIA-WLY

Error NIEHOST_UNKNOWN

Per SAP Focused Run 3.0 SP00, the Simple System Integration cleanup mechanism will continue with a requested cleanup if a host cannot be found (error code: NIEHOST_UNKNOWN). In earlier service packs the cleanup was aborted on error NIEHOST_UNKNOWN. This applies both to report RSRSM_SSI_CLEANUP and the Web Service implementation. Error NIEHOST_UNKNOWN indicates that the respective hostname cannot be found in the system landscape.

In case the host still exists in the customer landscape (maybe under a new name), it can still have a running and configured Simple Diagnostics Agent on it. It must be ensured, that the configuration for the SAP Focused Run system on which the cleanup was performed, gets completely deleted from this Simple Diagnostics Agent. Failing to do so, will have following consequences:

  • The agent will continue to collect data, consuming considerable computing resources on the managed system
  • Due to outdated (wrong) username/password for the managed system, the SDAGENT user will get locked, and block data collection also for other still valid SAP Focused Run systems
  • The agent will continue sending data back to the “old” SAP Focused Run system (from which it was deleted), since a configuration is still available
  • The agent may try to connect to the “old” SAP Focused Run system, with outdated (wrong) username/password, possibly blocking back-users

The suggested cleanup procedure is:

  • After running a cleanup, check the logs for NIEHOST_UNKNOWN errors
  • For each host with an NIEHOST_UNKNOWN error:
    • If the host is no longer connected to another SAP Focused Run system:
      • Stop all SDA processes and delete the complete SDA directory on the respective host: <sha-directory>/SMDAgent
    • If the host is still used with other SAP Focused Run systems
      • Recursively delete all the left-over agent configuration directories for the respective FRUN system below: <sha-directory>/SMDAgent/default/configuration
        • An FRUN configuration directory is named by the <FRUN-SID> of the SAP Focused Run system
        • Following cURL command can be used to perform such recursive delete:
          • curl -X POST --noproxy '*' -u sapadm 'http://<host-name>:<sha-port>/lmsl/sda/default/?service=configuration&solution-manager=<FRUN-SID>&operation=reset'
          • Respective <place-holders> must be substituted