(Glue-2411) Upgrading a System with SNP Glue

Owned by SNP
yesterday at 10:36 am
2 min read

Table of contents:

General Information

SAP Upgrade means a scenario, when the SAP application (S/4, ECC, BW, CRM, DMIS, etc.) or major NW version is being upgraded, while Glue is installed as an add-on on the system.

Excluded from this are:

  • Technical upgrades like SAP kernel or NetWeaver SP upgrades (using SPAU). In this case, steps in Planned Maintenance are sufficient.

  • Transformation or migration projects (e.g. ECC > S4). In such scenarios, it is recommended to disable and delete all Glue objects and re-implement the solution after migration.

There are two important things to know before upgrading:

First, Glue uses database triggers to capture changes happening to SAP tables. Triggers can interfere with the upgrade and need to be disabled upfront.

Second, to keep the consistency of Glue replication, you should minimize the window when Glue triggers are inactive.

In an ideal scenario, Glue triggers are only inactive during periods in which no transactions are happening in the system. In scenarios when this is not possible, after the upgrade is finished replications that use trigger delta need to be fully reloaded (full load + delta init).

Before upgrade

  1. Stop any currently running Schedulers (and legacy watchdogs).

  2. Stop Java Connector in /DVD/JCO_MNG.

  3. Disable any active triggers in /DVD/GL_DBT. If possible, do this after any interaction with the system is forbidden.

SAP Software Update Manager (SUM) does not allow upgrade to proceed, while any database triggers outside SLT namespace exist on SAP tables. Therefore, Glue triggers need to be disabled before SUM upgrade. Please note, that this does not include SLT Add-on scenario, in which SLT triggers are used for delta capture.

After upgrade

  1. If the NetWeaver release or installation number changed during the upgrade, request and apply for a new Glue license.

  2. Activate Glue triggers in /DVD/GL_DBT, preferably before any interaction is resumed.

  3. Reload any tables on which you might have missed changes.

  4. Start Java Connector in /DVD/JCO_MNG.

  5. Start schedulers.