SAP HANA Tenant Databases Operations Guide
You can perform a near-zero downtime update of a single-container system to SAP HANA 2.0 SPS 01 in a system replication landscape. A single-container system will be automatically converted to a tenant database system during the update. Converting an SAP HANA system to a tenant database system is permanent and cannot be reversed.
Prerequisites
- The statistics server is not running as a separate server process (statisticsserver), but instead as an embedded service in the master index server. If this is not the case, migrate the statistics server to the embedded statistics service as described in SAP Note 1917938.
- The SAP HANA system has been installed with its server software on a shared file system (export options rw, no_root_squash).
- The SAP HANA system has been installed with the SAP HANA database lifecycle manager (HDBLCM).
- You are logged on as the system administrator user <sid>adm.
Perform one of the following procedures to update your system replication landscape to SAP HANA 2.0 SPS01:
Near-Zero Downtime Update (NZDU)
1. Update the secondary system using the SAP HANA database lifecycle manager. The migration to a tenant database system is triggered automatically.
2. Wait until the update has finished and all systems are in sync again. The replication will be possible in this situation although the primary is still a single-container system.
3. Perform a takeover to the updated secondary system. Only now the migration to a tenant database system is finalized for the secondary.
4. Update the primary system using the SAP HANA database lifecycle manager. The migration to a tenant database system is done automatically.
5. Wait until the update has finished and the primary system is up and running again.
6. Register this former primary system as the new secondary to the new primary (former secondary).
1999880 - FAQ: SAP HANA System Replication
Can I set up system replication between systems with different topologies?
The topology of primary and secondary site of a system replication scenario must be identical. As a consequence it isn't possible to replicate from non-MDC to MDC (SAP Note 2101244) and vice versa, and it is also not possible to replicate from single-node to scale-out and vice versa.
2101244 - FAQ: SAP HANA Multitenant Database Containers (MDC)
Is it possible to convert SAP HANA 1.0 single container system to SAP HANA 1.0 MDC system with HANA System Replication?
No, conversion from single container to MDC with HANA System Replication is not supported. You would need to disable replication before starting the conversion else the conversion on secondary would fail with the below error.
SAP HANA Lifecycle Management - SAP HANA 1.00.122.17.1526900527
***************************************************************
10:03:43.088 - INFO: Start Date: 2018-10-26 - hdblcm
10:03:43.104 - INFO: Performing secondary system check
10:03:43.104 - ERR : The SAP HANA System cannot be converted to multitenant database containers, because it is a system replication site
10:03:43.105 - INFO: Summary of critical errors
10:03:43.104 - ERR : The SAP HANA System cannot be converted to multitenant database containers, because it is a system replication site
You would need to disable replication and need to perform the conversion on primary and all connected secondaries in case you have multitier replication.
./hdblcm --db_mode=single_container
./hdblcm --action=install --ignore=check_signature_file --db_mode=single_container
SAP HANA Lifecycle Management - SAP HANA Database 2.00.024.06.1538035880
************************************************************************
Scanning software locations...
Detected components:
SAP HANA Database (2.00.024.06.1538035880) in /int/software/sapcd/db/hana/hana_rev20_024_6/SAP_HANA_DATABASE/server
SAP HANA AFL (incl.PAL,BFL,OFL,HIE) (2.00.024.0600.1538046631) in /int/software/sapcd/db/hana/hana_rev20_024_6/SAP_HANA_AFL/packages
SAP HANA LCAPPS (2.00.024.0600.483443) in /int/software/sapcd/db/hana/hana_rev20_024_6/SAP_HANA_LCAPPS/packages
SAP HANA Database Client (2.2.74.1536258378) in /int/software/sapcd/db/hana/hana_rev20_024_6/SAP_HANA_CLIENT_LINUX/client
SAP HANA Smart Data Access (2.00.3.000.0) in /int/software/sapcd/db/hana/hana_rev20_024_6/SAP_HANA_SDA/packages
SAP HANA Database version '2.00.024.06.1538035880' will be installed.
./hdblcm --action=install --ignore=check_signature_file --db_mode=single_container
SAP HANA Lifecycle Management - SAP HANA Database 2.00.035.00.1545187853
************************************************************************
Scanning software locations...
Detected components:
SAP HANA Database (2.00.035.00.1545187853) in /int/software/sapcd/db/hana/hana_rev20_035_0/SAP_HANA_DATABASE/server
SAP HANA AFL (incl.PAL,BFL,OFL) (2.00.035.0000.1545200735) in /int/software/sapcd/db/hana/hana_rev20_035_0/SAP_HANA_AFL/packages
SAP HANA LCAPPS (2.00.035.0000.485538) in /int/software/sapcd/db/hana/hana_rev20_035_0/SAP_HANA_LCAPPS/packages
SAP HANA Database Client (2.3.130.1542919958) in /int/software/sapcd/db/hana/hana_rev20_035_0/SAP_HANA_CLIENT/client
SAP HANA Smart Data Access (2.00.3.000.0) in /int/software/sapcd/db/hana/hana_rev20_035_0/SAP_HANA_SDA/packages
Configuration error:
Checking command line parameter '--db_mode' failed.
Value 'single_container' is invalid. Please use one of: multiple_containers
Summary before execution:
=========================
SAP HANA Database
Update Parameters
SAP HANA System ID: AN1
Remote Execution: ssh
Update Execution Mode: optimized
Database User Name: SYSTEM
Software Components
SAP HANA AFL (incl.PAL,BFL,OFL)
Do not install
SAP HANA LCAPPS
Do not install
SAP HANA Database
Update from version 2.00.024.06.1538035880 to 2.00.035.00.1545187853
Location: /int/software/sapcd/db/hana/hana_rev20_035_0/SAP_HANA_DATABASE/server
SAP HANA Database Client
Update from version 2.2.74.1536258378 to 2.3.130.1542919958
Location: /int/software/sapcd/db/hana/hana_rev20_035_0/SAP_HANA_CLIENT/client
SAP HANA Smart Data Access
Do not install
Note: The upgrade of SAP HANA Database to this version will convert your system to multi-tenant database containers. This is a mandatory step. For more information, see SAP Note 2423367.
Do you want to continue? (y/n): y
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
8 | |
5 | |
5 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 |