Dear SAP Community Member, In order to fully benefit from what the SAP Community has to offer, please register at: Thank you, The SAP Community team. How can upgrade sap SAP_BASIS patch. Tech Sign In Page Forgot Password? Don't have an account? Decompress the files with the following commands sapcar -xvf *.CAR, sapcar. Installed SAP Download Manager.
Use always the newest available SAPCAR release compatible to your operating system. You can download a patched version of SAPCAR from the SAP Service Marketplace: - Support Packages and Patches - Browse Our Download Catalog - Additional Components - SAPCAR. Then add the SAPCAR version for your OS to the Download Basket. Note that the downloadable file is tagged with the.exe extension for all OS platforms because of software center naming conventions.
On UNIX platforms you have to delete the extension and to rename the file to SAPCAR because this is the official tool name which is known by other SAP tools on UNIX platforms. The downloadable file is not compressed so you may run it without extracting it before.
As of R/3 Release 4.6C, the new archiving tool SAPCAR replaces the previous archiving tool CAR. This results in some special considerations listed below.
According to the replacement of CAR, the extension of the archive files delivered by SAP changes from '.CAR' to '.SAR' for files concerning R/3 Release 4.6C or higher. The command line interface of SAPCAR is downward compatible with the command line interface of CAR. The only two exceptions to this are: During extraction, SAPCAR checks the file name extensions of the archives you want to extract from. The extensions '.CAR' and '.SAR' are both valid.
The option '-s' for checking the free space on the target filesystem is only valid for displaying the contents of an archive. The option is no longer valid for extracting files. For example, the command 'SAPCAR -tsf ARCIVE.SAR' is valid, but the command 'SAPCAR -xsf ARCHIVE.SAR' is invalid.
Pay attention to the fact that the archive format changed for SAPCAR. You can not use CAR with archives created by SAPCAR. On the other hand, you can use SAPCAR to extract, check, or list the content of archives created by CAR. But it is not possible to create CAR archives with SAPCAR. On some platforms, SAPCAR requires certain dynamic C program libraries. These libraries are possibly not part of the standard installation of your operating system.
In this case, you need to install them before using SAPCAR. Possible platforms where manual installation of these C runtime libraries may be required, are: SunOS 5.6 (Solaris 2.6): You possibly need to install the latest patch that includes the package SUNWlibC. All other SunOS releases contain the required runtime libraries. Use the command 'pkginfo fgrep -i SUNWlibC' to check if C runtime libraries are installed. HP-UX: You possibly need a patch containing the HP C runtime libraries.
Since March 1997 HP delivers these patches worldwide every two months on an Extension Software CD to CD-ROM customers of HP with support (see Use the command '/usr/sbin/swlist -l product fgrep -i PHSS fgrep -i aC fgrep -i runtime' to check which C runtime environment is installed. Sinix/ReliantUNIX: You possibly need to install the C runtime environment. The package CDSRTS version 2.0C is required. Use the command 'pkginfo -l CDSRTS' to check which C runtime system version is installed. In case you want to run the unicode version of SAPCAR the shared library libsapu16.
Is needed (where 'lib ext' is one of 'dll', 'so', 'sl' or 'o'). Make sure that this library resides in the search path of the program loader of your operating system. Normally this library can be found on the kernel CD.
For more information regarding the handling of SAPCAR, type 'SAPCAR' at the command prompt.
This series of publication intends to provide an overview and explanation of major steps and considerations for BW on HANA migrations from anyDB (any database). The complex procedure involves: 1) Preparatory work in the BW system 2) SUM DMO Upgrade and Actual migration 3) Post processing on the migrated systems This first part focuses on the SUM DMO tool used for the migration, pre-requisites, optimization and the actual migration steps By OZSoft Consulting for ITConductor.com Author: Terry Kempis Editor: Linh Nguyen. BW Migration to HANA Part 2 - SUM DMO Tool for SAP Upgrade & Migration. 1. BW Migration to HANA Part 2 of 3 SUM DMO Tool for SAP Upgrade & Migration By OZSoft Consulting for ITConductor.com Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 1 Any DB Migrate Upgrade. Introduction.
This is Part 2 of the series of publication which provides an overview and explanation of major steps and considerations for BW on HANA migrations. Migrating a BW system from anyDB (any database) to HANA involves 1. Preparatory work in the BW system 2. SUM DMO Tool for SAP Upgrade and Migration 3. Post processing on the migrated systems. This part focuses on the tool used for the migration, pre- requisites, optimization and the actual migration steps.
Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 2. DMO, Guides. SUM’s DMO (Database Migration Option) is the tool to update and migrate anyDB (any Database) to HANA. HINT: It cannot be used for pure migration purposes only! If your current release/level already meet the HANA requirement and does not want to do go the latest release/level, then at least update other package (e.g.
ST-PI) so that you will have stack xml which is needed by DMO. Before embarking on doing migration using DMO, first go through the following. ‘SAP First Guidance - Using the DMO Option to Migrate BW on HANA,. ‘Database Migration Option (DMO) of SUM - Introduction’ - it provides a very good introduction of DMO and contains links to other related blog (e.g. Optimization, technical background). All notes in this document and the steps followed in this migration exercise were based on the cookbook, blogs and the references below.
The central note 2257362 for DMO with SUM 1.0 SP 17. Update of SAP Systems using SUM 17:1128/lmsl/sumabap//doc/sluiguiext/ Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 9. SLUIGUI – LOGS, BREAKPOINTS Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 10 V Logs can be viewed without going to the OS Breakpoints can be set from here.
Observer Mode Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 11 This feature allows monitoring for the update process from a mobile device or desktop. Prepare the observer mode (create new user obs, add a password, then add group SAPSYS to obs. Start the observer monitor with the following URL, login with the obs user:1128/lmsl/sumobserver/ABA/mo nitor/index.html. Resetting DMO, source DB instance after migration Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 12 RESETing the DMO After migration, the source database remains intact. It’s on the state before the shutdown. If for whatever reason, it can be used again after a reset which is provided by DMO. Note that the reset will delete data from the target HANA DB.
Reference: DMO technical background Source database after migration After the migration testing, we installed another PAS pointing to the source database – so we ended up with two running systems: 1. A migrated system in HANA 2. The original source ASE system The normal steps in installing a Distributed system are: 1. ASCS instance 2. Database Instance 3. Primary Application System (PAS) But only step 1 and 3 are needed.
Note that by skipping step 2, the profile parameter, environment (env.csh) and DB (dbenc.csh) variables may have some missing items. Fortunately, that DMO backup the source system versions, including the kernel for reference/re-use. This is handy for production copy sandbox – for comparison purposes, but not on production. Ensure that this is totally isolated from normal use. DMO - Optimization During the days of Combined Upgrade and Unicode Conversion (CUUC) – downtime optimization was a challenge. You need to manually specify table split, which tables to do first, etc. With DMO, tools and features are available to reduce the downtime, including optimized table splitting.
![Sap Download Sapcar Exercise Sap Download Sapcar Exercise](https://itsiti.com/wp-content/uploads/2016/06/SUM%20-%20New%20Version.jpg)
Benchmark Tool. Migration repetition Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 13. Benchmarking tool Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 14 DMO’s ’benchmarking’ (migration) tool is available to simulate the export and import process to check the migration rate/speed. It has repetition option to enable optimization by adjusting the process parameters (SQL uptime, SQL downtime, R3load uptime, R3load downtime). This should be done before the DMO and against a production copy which mirrors the production setting, (i.e.
Capacity, network, target HANA) HINT: benchmark both export and import to simulate production run For more details, refer to the following Optimizing DMO Performance. Migration Repetition/Optimizing downtime Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 15 DMO provides ‘migration repetition’ to help reduce the system downtime. For each DMO run, the following files are created. ‘MIGRATEUT/DTDUR.XML’ - contains statistics for each migrated table.
UPGANA.XML These files can be use for subsequent DMO run to optimize and reduce the downtime. See DMO Guide Cookbook DMO UPGANA.XML MIGRATE.DUR.XML. Preparations/Checks - 1 Migration Key - Generate the system migration key License - Generate the license for the target migrated system (i.e. Based on HANA DB).
Time zone. Make sure both source system and the HANA severs have the same time zone settings and within SAP (transaction STZAC). DB Free space. As a shadow system is created, there should be at least 50Gb database free space, or more, depending on the existing components. SAPLOCALHOST/Hostname Make sure that the profile parameter SAPLOCALHOST matches the hostname in SM51.
WARNING: Hostname 'XXXXXXXX' is different from hostname 'YYYYYYYY' system runs with! If you encounter the issue in the shadow instance, stop SAPup, stop the shadow instance, edit the parameter in the SHADOW profile directory, restart the shadow instance. Resume the process. Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 16. Preparations/Checks - 2 SAP Host agent – install/update to the latest version SPAM Update to the latest SPAM, or download and extract it into /trans/EPS/in SAPCAR download the latest SAPCAR for extraction HANA Client. Download and extract the HANA client. For LINUX PAS, the DMO will install it as part of the migration.
For Windows PAS, install it manually before starting the DMO. DOWNLOAD/Stack.xml. The Maintenance Planner is now used to generate the stack.xml and download the target components, including the latest SUM, ACPs, and kernel (for all platforms) Target HANA DB log mode. Set the logmode parameter to ‘overwrite’ Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 17. Preparations/Checks - 3 Deletion of some BW objects Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 18 In one of the dialog, you will enter values as per below.
Discuss with your BW team. Delete temporary BW query bookmarks older than. Days:: 99 Delete sent BW query bookmarks older than. Days:: 9 Delete BW traces older than.
Days:: 99 Delete BW statistics older than. Days:: 9 After extracting the SUM package, change owner to adm and the group to sapsys As root, register to host agent - cd /SUM./STARTUP confighostagent Normal upgrade preparations are not included in this document, e.g. Pre-downtime tasks like queue processing, stopping jobs, locking users, etc. SUM. Migration Steps/Screenshots - 1 Start DMO Extracts from SAPupConsole.log – note that only DMO-related phases are included here Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 19 This is SAPup release lmt008 V53.000 - all engines are running Welcome to Software Update Manager Important information for this program is included in. SAP Note 2223738. and further SAP Notes mentioned therein.
The keyword is included in the relevant product-specific SAP Note. Read the current version before you start preparing the procedure and check the SAP Note again for changes before you start the procedure. Migration Steps/Screenshots - 2 Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 20 2016/08/05 13:14:32 START OF PHASE PREPINPUT/MIG2NDDBINI Database Migration Option Enter the target database type: 01) - No migration 02). SAP HANA DATABASE TYPE: SAP HANA Migration Parameters Select tables for table comparison checks. 01). Do not compare table contents 02) - Operate on all tables 3) - Operate on selected tables only Provide a valid migration key for installation number '. For a detailed description of generating the key, see SAP note.317096.
Migration Key: 1W5gdEM50D001eqtdQQ011e3. Migration Steps/Screenshots - 3 Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 21 SAP HANA SCALE OUT Are you running a SAP HANA Scale Out Landscape as a target for this migration?.If so, you can enable the landscape reorganization during the preprocessing of the migration. 01) Execute Landscape Reorg Enter a number/range/'all' to change selection or 'ok' or to complete Test cycle This option will stop the tool after the downtime migration phase, enabling a simple repetition of it to optimize the procedure by tuning the parameters (like R3load processes). You should in no case use this option for a productive run! 01) X Enable Migration Repetition Option Migration Repetition Choose an execution strategy for transaction SGEN. Select option ‘Do not start ABAP load generation during the update’.
There is more flexibility when doing it as a post-task (e.g. Use more servers) NOT for production.
Migration Steps/Screenshots - 4 Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 22 PREPCONFIGURATION/SUBMODMIGINSTCLIENT/HDBINSTCLIENT Target database client The tool needs access to the target database client. Enter the following information: Path to 'hdbinst' for client installation: (This is where the HANA DB Client will be installed in LINUX. For Windows, this should be installed before starting DMO) Database Migration Initialization You are going to migrate your system to a new database. Enter the following parameters of the target database: Target Hostname: xxxxxxxx Enter the SID and instance number of the target database instance (might be different from your SAP system): SID of the target database: A4H Target Instance Number: 00 Tenant DB name. If it does not exist yet, it will be created during the process.
See next slide. Migration Steps/Screenshots - 5 Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 23 Enter the path of the SAP License file for your migrated SAP system: Target System License: (License key based on HANA DB).Additional Information:. Specify the database connectivity data of the target database to be used for the SAP system migration. In case you are using a SAP HANA multitenant database container, specify the connectivity data of the target database tenant. In case you are using a SAP HANA multitenant database container, and want to create a new database tenant, specify the connectivity data of the database tenant to be created. Enter password for target database user 'SYSTEM'.
Enter password for target database SYSTEMDB superuser (MultiDB). Migration Steps/Screenshots - 6 Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 24 Parameters for BW-Specific reports Within the next phases certain BI housekeeping tasks will be performed. Please decide which data shall be deleted in the database.Caution:. The data deleted during the next phases as specified in the fields below cannot be restored by resetting update process. Enter the amount of data to be deleted: Delete temporary BW query bookmarks older than.
Days:: 99 Delete sent BW query bookmarks older than. Days:: 9 Delete BW traces older than. Days:: 99 Delete BW statistics older than. Days:: 9 Values agreed with BW team.
Migration Steps/Screenshots - 7 Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 25 Perform Scale Up (Single Node) Prerequisite on SAP HANA if necessary.Action Required (if condition is met):.You decided to NOT run the SAP HANA Landscape Reorganization. However, if you run an SAP HANA Single-Node system with scale-up, you must manually import a file with specific SQL-information to enable the optimal table partition. Carry out the following procedure:. 1. Download the appropriate file that is in the attachment of the following SAP Notes:. For SAP Business Warehouse on SAP HANA, see SAP Note 1908075.
From the attachment TABLEPLACEMENTBW.zip, select the suitable SQL-file. For SAP Business Suite on SAP HANA or SAP S/4HANA, see SAP Note 1899817.
Choose the attachment: TABLEPLACEMENTERP. or TABLEPLACEMENTS4H. according to the version and SP level of the target system. Edit the downloaded file by replacing all occurrences of $$PLACEHOLDER with your SAP. Import the edited files to SAP HANA using one of the following commands on OS level of the managed system:./usr/sap/ABA/hdbclient/hdbsql -U SYSTEM -I -E 1./usr/sap/ABA/hdbclient/hdbsql -U SUPER -I -E 1. 4.
After the import, continue with the migration procedure. Migration Steps/Screenshots – Export/Import/Downtime Author: Terry Kempis Editor: Linh Nguyen ITConductor.com 26 Checks after phase MAINSWITCH/SUBMODMIGSWITCHORG/SUBMODMIGDOWNTIMERUN/EUCLONE MIGDTRUN were negative! Last error code set: Found 12 failed export processes Found 64 failed import processes.