I know there is already very good blogs on this topic, The purpose of this blog is to explain the process of performing a simple homogeneous system copy of a HANA (MDC-multi tenant database container) based system using the recovery of the source backup on the target HANA DB using HANA Studio and Using SWPM , I don’t find More blogs and details regarding homogeneous system copy or backup/Restore on HANA 2.0 on multi tenant database container , This blog may add more value on existing blogs , This blog is based on my personal experience , and I will be sharing the details and issue which I faced , and Also all the 3 ways in a single blog ?
2.0.0.7 (new build - previous 2.0.0.7 setup file was corrupted) Fixed a bug which caused the software to copy only one episodes on some episode DVDs. This occurred only if the DVD had all of the episodes in a single Titleset. Added a new right click menu option called 'Save Copy Preset'. Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
My Environment was:-
SAP HANA 2.0 ( For Both Target and Source )
- 2.0 sps 05. 2.0 sps 04. 2.0 sps 03. 2.0 sps 02. 2.0 sps 01. 2.0 sps 00. 1.0 sps 12. This version is out of mainstream maintenance. For more information, see the Product Availability Matrix (PAM).
- Solve your math problems using our free math solver with step-by-step solutions. Our math solver supports basic math, pre-algebra, algebra, trigonometry, calculus and more.
- Find a place on your USB drive to store the copied files. You can copy files to any folder on the USB drive. Your system likely popped up a dialog box a few moments after the device was connected. One of the options should be “Open folder to view files.” Click that link to arrive at the root (main folder) of your USB drive.
SAP BW 7.50 ( For Both Target and Source )
Schema Name (SAPABAP1)( For Both Target and Source )
My SAP HANA 2.0 Database is on separate Box and PAS (BW) is on separate ,
There 3 way I found to perform the homogeneous System copy ,
1- If you want to install a full SAP system including the required application server instances. Standard System
2- If the target system already exists and you merely want to replace the content of the database.
Database Refresh or Move
3- DB Refresh of HANA Based systems using HANA Studio Backup/Recovery without Using SWPM
All the 3 Steps are very easy to do if we plan correctly and read system copy documents and Required SAP notes,
Here I will explain point 1 and 3 and later in Future I will explain point No 2,
So lets Start,
1- If you want to install a full SAP system including the required application server instances. Standard System
I assume that you have already required backup which need to be used , So I will not explain much about taking backup,
- Take a complete DB backup of the source Database
- Move the required database backup to the Target system on Database Host
- Check the permission of the backup fine and Note down the backup prefix
- Collect the Schema user password of the source System
- Collect the DDIC 000 Password of the source System
Cross check you HANA DB version , its must be same or higher that source ,
Source SID- PRD
Target SID- QAS
Start SWPM as a user with administrative rights (root, Administrator) on the application server host
Select an option on the start screen.
- If you want to install a full SAP system including the required application server instances, choose <your product> -> <your database> -> System Copy -> Target System -> <system variant> -> Based on <technical stack> -> Standard System.
Here put your HANA Database SID host name and instance No,
SWPM will automatically detect the SYSTEM DB and Tenant DB name, and create it, you can also create Tenant Database using HANA Cockpit or SQL command ,
given the SYSTEM user password ( be care Full in giving the password if its wrong it will lock the user)
Give the required software path on SWPM
give the schema user password of the source system
Put the database SIDADM user password ,
here SAPControl WSDL URL will come by default
Note:- Your backup should be present on Database host and location of the backup will be the database host location ,
Backup name should be the prefix name of the complete data backup. I have used the default backup name (COMPLETE_DATA_BACKUP)
I did SLD later
Put the DDIC 000 Source Password
move SWPM
I had the issue during the recovery and checked the logs, I stopped the Tenant database manually from HANA Studio using SQL command ALTER SYSTEM STOP DATABASE SID, because during the recovery process Database must be stopped ,
This is completed now,
- Additional adjustments after the installation
- Checking the secondary database connections
After you copy the database, the target system has the same database connections (for example, for the DBA Cockpit) as the source system; this may cause problems. Therefore, you must check the database connections in transaction DBCO and adjust them if required. - Checking the RFC connections
After you copy the database, the target system has the same RFC connections as the source system; this may cause problems. Therefore, you must check the RFC connections in transaction SM59 and adjust them if required. - Checking the spool configuration
After you copy the database, the target system has the same spool configuration as the source system. Therefore, you must check the spool configuration in transaction SPAD and adjust it if required. - Changing the logical system name
If the SID of the ABAP system has changed, use transaction BDLS to change the logical system name. - Adjusting the SAP HANA calculation views
If you copied a BW system, you must adjust the SAP HANA calculation to the new system names views after the migration. This is done when calling the report RS_BW_POST_MIGRATION with all options.
- This completes the system copy.
Reference SAP note:- 1844468 – Homogeneous system copy on SAP HANA
******************************************************************************
Homogeneous system copy on SAP HANA without SWPN
*******************************************************************************
Scenario
This SAP Note describes a scenario such as the following: You want to copy the BW system PRD connected to the database PR1 to the BW system DEV connected to the database DV1. The name of the ABAP schema in PR1 is SAPABAP1. Therefore, PRD is the source system (the system that is to be copied), PR1 is the source database (the database system that is to be copied), DEV is the target system (the copied system), and DV1 is the target database (the target database system). SAPABAP1 is the (database) schema (the schema name) or the database user of the system.
We will be doing this on SAP HANA 2.0 multi tenant database container ,
- Take the source system backup or finalize which backup need to be restored
- Collect the Schema user password of source database
- Move the backup to the target database ,
Login to the Target database HANA Studio,
Stop your tenant Database using SQL command -ALTER SYSTEM STOP DATABASE SID
Now right click on SYSTEMDB
and select the Recover Tenant database
Note:- Ensure that the target tenant database system is shut down. If you will not stop tenant database manually HANA studio will stop it automatically,
Select the tenant database you want to recover , there may few multiple tenant database
After the Restore your application will not start, You need to perform the steps as below
Changing the database information in the target system.
If the SID of the target system differs from that of the source system, the name of the database schema that the target system expects is also different. You must therefore adjust the database information.
If the application server of the target system does not on Windows (but instead on Linux, Unix, AIX, HP-UX, Solaris, and so on), open a command line on the computer of the target system as user<SID>adm, switch to the directory /usr/sap/<SID>/hdbclient and execute the following command:
hdbuserstore set default <dbhost>:<dbport> <dbuser> <dbpassword>
exp:-
hdbuserstore set default myhostname:30041 SAPABAP1 xyzxxxxx
Note:- For tenant database you must put the indexserver SQL port of the tenant database for which you want to do refresh
Replace the information in the angle brackets as follows:
<dbhost>: The host name of the target database server
<dbport>: The port of the target database Index server server
<dbuser>: The database user for the copied schema ( SAPABAP1)
<dbpassword>: The password of the database user (SAPABAP1 Password)
run
hdbuserstore list commad to check
Also Check R3trans , should now return code 0,
- You can now start the target system.
Now perform the post steps ,
1.Implement a new license
a) If the SID has changed, you must implement a new license that is valid for the new SID in the target system. You can use transaction SLICENSE to do this.
2. Execute ABAP reports
a) To update required information, you must execute the following reports, if available, as the user DDIC in client 000:
RSWBOINS
RUTCSADAPT (for table declustering, as of NW 7.40)
RADDBDIF
RUTTTYPSET
UMG_POOL_TABLE
RUTPOADAPT (for table depooling as of NW 7.40)
DBPROC_ACTIVATE_PROXIES (as of NW 7.40 Support Package 1)
b) In addition, execute the following function modules, if available:
SNHI_DELIVERY_UNIT_MIGRATION (activation of SAP HANA content, as of NW 7.40).
3. Additional adjustments
a) Check the secondary database connections
After you copy the database, the target system has the same database connections (for example, for the DBA Cockpit) as the source system; this may cause problems. Therefore, you must check the database connections in transaction DBCO and adjust them if required.
b) Check the RFC connections
After you copy the database, the target system has the same RFC connections as the source system; this may cause problems. Therefore, you must check the RFC connections in transaction SM59 and adjust them if required.
Mathematica 10 0 1 intelkeygen download free. c) Check the spool configuration
After you copy the database, the target system has the same spool configuration as the source system. Therefore, you must check the spool configuration in transaction SPAD and adjust it if required.
d) Changing the logical system name
If the SID of the ABAP system has changed, use transaction BDLS to change the logical system name.
e) Adjusting the SAP HANA calculation views
The SAP HANA calculation views must be adjusted after migration to the new system name. This is done by calling the report RS_BW_POST_MIGRATION with all options.
4. This completes the system copy.
Reference SAP note :- 1709838 – BW 7.3 on HANA: System copy using backup and recovery
Please let me know your comments to add more value and all the suggestion are welcome ,
Thanks
Sadiq Iqbal
Also known as | GT-P3100 (3G & Wifi) GT-P3110 (Wifi)/GT-P3113 (with Infrared port) SCH-i705 (Verizon model) |
---|---|
Developer | Samsung |
Product family | Galaxy Tab |
Type | phablet, media player, PC |
Release date | 22 April 2012 (US) |
Operating system | Android 4.0 Ice Cream Sandwich (upgradable to 4.2.2 Jelly Bean) upgradable To Android 6.0.1 Marshmallow via LineageOS 13 (Unofficial upgrade to Android Nougat 7.1.2 via Lineage OS 14.1) |
System on a chip | Qualcomm Snapdragon S4 Plus (Verizon model) |
CPU | 1.0 GHz dual-core TI OMAP4430 (Cortex A9) SoC processor[1] Qualcomm Krait clocked @ 1.2 GHz (Verizon model) |
Memory | 1 GB |
Storage | 8/16/32 GBflash memory, microSD slot (up to 32 GB) |
Display | 1024×600 px, 7.0 in (18 cm) diagonal, PLS TFT LCD display |
Graphics | PowerVR SGX540Adreno 225 (Verizon model) |
Input | Multi-touchscreen, digital compass, proximity and ambient light sensors, accelerometer,[2]GPS |
Camera | 3.0 MP rear facing, VGA (0.3 MP) front facing |
Connectivity | HSPA+ 21 Mbit/s 850/900/1900/2100 MHz (3G & WiFi model) EDGE/GPRS 850/900/1800/1900 MHz (3G & WiFi model) Wi-Fi 802.11b/g/n, Bluetooth 3.0[3][4] LTE (Verizon model) |
Power | 4000 mAh Li-Ion battery |
Dimensions | 122.4 mm (4.82 in) H 193.7 mm (7.63 in) W 10.5 mm (0.41 in) D |
Mass | 344 g (0.758 lb) |
Predecessor | Samsung Galaxy Tab 7.0 Plus |
Successor | Samsung Galaxy Tab 3 7.0 |
Website | Microsite |
The Samsung Galaxy Tab 2 7.0 is a 7-inch Androidtablet produced and marketed by Samsung Electronics. Samsung Galaxy Tab 2 is an Ice Cream Sandwich sequel. It belongs to the second generation of the Samsung Galaxy Tab series, which also includes a 10.1-inch model, the Galaxy Tab 2 10.1. It was announced on 13 February 2012, and launched in the US on 22 April 2012. It is the successor to the Samsung Galaxy Tab 7.0 Plus.
History[edit]
The Galaxy Tab 2 7.0 was announced on 13 February 2012.[5] It was shown along with the Galaxy Tab 2 10.1 at the 2012 Mobile World Conference. Although the two devices were originally scheduled to launch in March, they did not do so, with Samsung explaining that the delay was due to unspecified problems with Ice Cream Sandwich and that they would instead be released at the end of April.[6] Samsung later confirmed that the Galaxy Tab 2 7.0 would be released on 22 April, with a price of $250 for the 8GB model.[7]
Features[edit]
The Galaxy Tab 2 7.0 was originally released with Android 4.0 Ice Cream Sandwich. An upgrade to Android 4.2.2 Jelly Bean was later made available.[8] Samsung has customized the interface with its TouchWiz UX software. As well as apps from Google, including Google Play, Gmail and YouTube, it has access to Samsung apps such as ChatON, S Suggest and All Share Play.[2]
The Galaxy Tab 2 7.0 is available in WiFi-only, WiFi with an IR Blaster (only available in the US and Canada), and 3G & WiFi variants. Storage ranges from 8 GB to 32 GB depending on the model, with a microSD card slot for expansion. It has a 7-inch PLS LCD screen with a resolution of 1024x600 pixels, and both front- and rear-facing cameras.[3][4] It is listed with 1GB of RAM but only 0.77GB are usable.
An additional feature is the Samsung 'Find my mobile' functionality which allows one to track the location of their mobile device if it is lost or remotely wipe it. Total video player 3 0 2014.
The device utilizes the Samsung proprietary connector for connecting a USB charging/data cable. In addition an adapter can be used that adds a USB OTG port enabling the tablet to be a USB host device. USB Mass Storage devices can be attached without any need for drivers. Additionally support for USB HID keyboard and mice are possible with this port. Limitations of device options are based on the Linux kernel version installed.
Copied 2 0 7 0
Reception[edit]
Reception for the Galaxy Tab 2 7.0 has been generally positive. The Verge reviewer David Pierce commented, 'The Tab 2 is more powerful than either the Kindle Fire or the Nook Tablet, and because it runs a fuller version of Android it's a more capable device if you're interested in more than just reading.'[9] Both Pierce and TechRadar's James Stables praised the size and weight of the device, as well as the low price compared to other full-size tablets.[10] Some criticism was made of the screen quality, with Stables describing it as 'dull and unresponsive', and Expert Reviews' David Ludlow criticizing the low resolution compared to the 2012 Google Nexus 7, despite otherwise finding it impressive.[11]
Variants[edit]
Copies 20740
Verizon released the Galaxy Tab 2 (7.0) under the name 'Galaxy Tab 2 (7.0) 4G LTE'. This device was sold in Verizon Wireless stores.
References[edit]
- ^Kerr, Rob (27 July 2012). 'Google Nexus 7 vs. Samsung Galaxy Tab 2 7.0 – specs comparison'. ITProPortal. Retrieved 16 January 2013.
- ^ ab'Samsung GALAXY Tab 2'. Samsung Mobile. Retrieved 15 January 2013.
- ^ ab'Samsung Galaxy Tab 2 7.0-inch WiFi – Tech Specs'. Samsung UK. Retrieved 15 January 2013.
- ^ ab'Samsung Galaxy Tab 2 7.0-inch 3G & WiFi – Tech Specs'. Samsung UK. Retrieved 15 January 2013.
- ^Trenton, Rich (13 February 2012). 'Samsung Galaxy Tab 2 is Ice Cream Sandwich sequel'. CNET UK. Retrieved 15 January 2013.
- ^Chacksfield, Marc (4 April 2012). 'Samsung Galaxy Tab 2 suffering from Ice Cream headache'. TechRadar. Retrieved 18 January 2013.
- ^Rougeau, Michael (3 April 2012). 'Samsung Galaxy Tab 2 7.0 Will Debut on April 22'. TechRadar. Retrieved 15 January 2013.
- ^Yalburgi, Vinod (12 January 2013). 'Galaxy Tab 2 7.0 P3110 Gets Android 4.2.2 Jelly Bean Update via XXCLL3 Official Firmware'. International Business Times. Retrieved 15 January 2013.
- ^Pierce, David (11 April 2012). 'Samsung Galaxy Tab 2 7.0 review'. The Verge. Retrieved 16 January 2013.
- ^Stables, James (31 May 2012). 'Samsung Galaxy Tab 2 7.0 review'. TechRadar. Retrieved 16 January 2013.
- ^Ludlow, David (17 August 2012). 'Samsung Galaxy Tab 2 7.0 review'. Expert Reviews. Retrieved 16 January 2013.
External links[edit]
Copied 2 0 72
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Samsung_Galaxy_Tab_2_7.0&oldid=979263168'