Restore SingleDB on 122.08 to Multi Tenant DB on HANA 2.0 SPS01 by Nicholas Chang 

Just tested recover a single Database to Multi Tenant Database without the need to convert them to MDC beforehand with below scenario and thought it is a good idea to share.
This enhancement only work on target >= HANA 2.0 SPS01 and is particularly useful where it keeps your source/ productive database intact and allows you to to perform a series of testing before converting them to MDC, especially if you plan to upgrade to HANA 2.0 SPS01 since MDC would be the standard and only operation mode.
Source
HANA revision: 122.08 (HANA Platform Ed 1.0)
SID: NC2
Mode: SingleDB

Target
HANA Revision: 2.00.010 (HANA 2.0 SPS01)
SID: NC1
Mode: MultiDB (MDC)

Scenario:
Restore the backup taken from NC2 (singleDB) to tenant NC2_MULTIDB@NC1
i. Backup source singleDB NC2 on HANA platform Ed 1 – SPS122.08
3 HANA services were backup.
ii. Once backup completed, in HANA 2.0 SPS01, you can either restore the backup taken directly to the available tenant or to a newly created tenant.
In below, the singleDB will restore to tenant NC2_MULTIDB on NC1 on HANA 2.0 SPS01
Restore using the backup taken on SingleDB on SPS122.08
If you noticed, only 2 services – indexserver and xsengine were restored. 
iii. Once recovery completed, you’ll need to re-enter the NC2 SYSTEM user password into tenant NC2_MULTIDB@NC1 in HANA Studio as source password was overwritten from restore.
And now your singleDB is restored to a tenant in MDC without the need to convert them to MDC beforehand.

I’ve tested and it works perfectly on source revision 122.07 and 122.08 and assume it should work on SPS12. For revision <=SPS11, further testing will be needed.

Comments

Post a Comment

Popular posts from this blog

Image
How to switch on/off HANA alerts  To check HANA alert status for alert ID "33" select * from _SYS_STATISTICS.STATISTICS_SCHEDULE where id = '33' To deactivate HANA alert for alert id "33" UPDATE _SYS_STATISTICS.STATISTICS_SCHEDULE SET "STATUS" = 'Inactive' where id = '33' To activate HANA alert for alert id "33" UPDATE _SYS_STATISTICS.STATISTICS_SCHEDULE SET "STATUS" = 'Idle' where id = '33' Note: You have to run this both place SYSTEMDB and Tenant DB and also ensure your alert ID which you are going to disable to enable  KBA 2481438 - How-To: Switch HANA alerts off/on
Read more

SPOOL_INTERNAL_ERROR

System can no longer create spool requests & creating spool requests takes a long time. Finally, the system cannot create any more requests and the short dump  SPOOL_INTERNAL_ERROR  occurs. In the dump itself and in the syslog, the system issues the message  "Spool full"  or  "Spool overflow" . In the standard  SAP  system, the number of spool requests that can be created is limited to 32000. If you reach this limit, there are no more free numbers and the errors described above occur. You can raise the upper limit for spool requests. As of Release 4.0, you can set the upper limit to anywhere between 2 and 31 numbers (previously 99,000). However, we recommend that you do not set the interval higher than 999,999 because the human user finds higher numbers difficult to process. (This is not a technical restriction; it concerns the handling only.) Proceed as follows: 1.  Log on to the system in client 000 and call transaction  SNRO . 2.  Select
Read more
How to run multiple SAP commands in a single line on a linux terminal If you want to stop and start SAP. You can use below commands sidadm$ stopsap ; cleanipc 00 remove ; cleanipc 01 remove ; startsap If you want do any other just add semicolon ";" after your commands.   
Read more