2751571 - Downtime of systems during the installation of a license key - SAP for Me

• Will there be system downtime when a new license key is installed?
• Swapping out license keys after reassigning systems (KBA 2380985 and SAP Note 198140)
• Installation number in SAP license key changed, so new license keys need to be installed
• Need to install a new license key in updated environment
• Hardware changed
• System migration
• Moving systems between installations

• ABAP system
• JAVA system
• BOBJ system
• HANA system
• DOES NOT APPLY TO Sybase Products
• DOES NOT APPLY TO Cloud Tenants

Each product area handles this differently. Check out the downtime details below for installing new license keys:

• ABAP system
  There will be no downtime when installing the new license key. Before installing the new key, delete all old keys. The license can be installed with the transaction: SLICENSE.
  If you encounter a problem during the installation of the key, open a case under BC-SEC-LIK.
  
  
• JAVA system
  There will be no downtime, if the old license is invalidated the new license should be installed within the next 30 min.
  If you encounter a problem during the installation of the key, open a case under BC-JAS-COR.
  
  
• BOBJ system
  There will be no downtime when installing the new license key. Install the new key(s), then delete all old license key(s)^*. The license can be installed in the CMC or the License Manager of the software.
  If you encounter a problem during the installation of the key, open a case under BI-BIP-ADM.
  ^*Note: If the old and new license keys are not compatible, you will receive an 'invalid' message. In this case, you will need to remove the old license key before you can install the new license key.
  
  
• HANA system
  You have to delete all existing license keys. Afterwards you are able to install the new key with the same SID and Hardware key with different installation/system number.
  There will be a short downtime when you are deleting the license key. HANA may refuse to execute SQLs, except license specific SQLs, the connections will be kept alive.
  If you encounter a problem during the installation of the key, open a case under HAN-DB.
  • Check out the HANA Administration Guide - License Management
  • SAP Note 1644792 - License key/installation of SAP HANA
  • SAP Note 1704499 - System Measurement for License Audit

SYBASE (Exception)
Reassigning systems for Sybase product is not allowed and leads to unexpected issues and confusion, such as references to different kinds of out-dated information, previous and/or current license materials, etc. If you reassigned Sybase Systems, you may want to consider the following options:

1. Keep everything as is after the Re-assignment as your existing and installed license key files or your servers running the Sybase product will not be affected in any way. However, the confusion and issues mentioned above may remain.
2. Check In the existing licenses keys under each re-assigned System ID by using the Check In button. In the next step, use the Edit system button to request a new license key.
3. Check In the existing licenses keys and delete the re-assigned System IDs and add new ones.

See KBA 2756805 - Why a SAP Sybase System should never be moved/reassigned

If encounter a problem during the installation of the key, create a case for the Sybase Product in question, e.g.:  BC-SYB-ASE for SAP Sybase ASE, BC-SYB-IQ for SAP Sybase IQ, BC-SYB-REP for SAP Sybase Replication Server.

Downtime, Umhängen von Systemen, System Stillstand, Lizenzschlüssel, License key, Produktiv Systeme, License installation, Emergency, key, Schlüssel, , KBA , BC-SEC-LIK , Licence Key Administration , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , HAN-DB , SAP HANA Database , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , XX-SER-FORME , SAP for Me , XX-SER-LIKEY , License keys for SAP systems , BC-CST-SL , SAP License , XX-SER-LIKEY-SYB , Sybase Products , XX-SER-LIKEY-BOJ , Business Objects Products , How To