Experimental results - variable angle incidence at the air

variable angle incidence at the air–liquid interface

3.2.4 Experimental results

Lesson: Introduction

Lesson Overview Lesson Objectives

After completing this lesson, you will be able to:

• Distinguish between an SAP homogeneous system copy and an SAP OS/DB Migration

• Estimate the problems involved with a system copy or migration

• Understand the functions of the SAP OS/DB Migration Check

Business Example

You want to understand which system copy / migration tools are provided by SAP and what is the difference between a homogeneous and a heterogeneous system copy. Furthermore you are interested in the scope of the OS/DB Migration Check service.

Figure 1: Definition of Terms

Please note: Improved functionality was often introduced with new SAP Kernel versions. If the new SAP Kernel was backward compatible to older SAP releases, the new functionality was available for the older releases as well. Example: a SAP Web AS 6.20 running on SAP Kernel 6.40 can make use of R3LOAD 6.40 features.

Throughout the SAP Documentation and SAP Notes, the term NetWeaver ‘04S and NetWeaver 7.00 is used in a mixed way, meaning the same.

ADM545 Lesson: Introduction

The initial SAP service offering for OS/DB Migrations was originally called “SAP OS/DB Migration Service”, but was renamed to “SAP OS/DB Migration Check Service”. Today, the term “SAP OS/DB Migration Service” is used for SAP fix price projects, in which SAP consultants migrate customer systems to a different database and/or operating system, mainly from remote.

Figure 2: Copying a SAP System

A client transport is not a true SAP System copy or migration. The copy function cannot transport all of the system settings and data to the target system, nor is it intended to do so. This applies particularly to production systems. Of course client transports have no meaning to JAVA-based SAP Systems. For further reference see SAP Note 96866 “DB copy by client transport not supported”.

Databases can be duplicated by restoring a backup. In most cases, this is the fastest and easiest way to perform a homogeneous system copy. Some databases even allow a database backup to be restored in a different operating system platform (OS migration).

Note: 3rd party database tools and methods suitable for switching the operating system (OS migration) or even the database (DB migration) are not supported by SAP, if not explicitly mentioned in SAP documents or SAP Notes. Nevertheless, the usage of unsupported tools or methods is not forbidden in general (the tool and method support must be provided by the 3rd party organization in such a case).

SAP cannot be made responsible for erroneous results. After the system copy, the migrated SAP system is still under maintenance, but efforts to fix problems caused by the unsupported tool or method, can and will be charged to the customer!

SAP System copy tools can be used for system copies or migrations on any SAP supported operating system and database combination as of R/3 Release 3.0D.

Since NetWeaver '04 (6.40) JAVA based systems can also be copied or migrated to any SAP supported operating system and database combination by SAP System copy tools.

3

Unit 1: Introduction ADM545

Figure 3: SAP System Copy / Migration Tools (1)

The SAP System copy tools are used for homogeneous and heterogeneous system copies. SAP System copy tools used for heterogeneous system copies are called SAP Migration Tools. In the remainder of this document, the the term SAP Migration Tools will be used.

Figure 4: SAP System Copy Tools / Migration Tools (2)

BW functionality is part of the ABAP Web AS 6.40 standard. Since then, every SAP System can contain non-standard objects! Special post- and pre-migration activities are required for them.

The generated DDL statements of SMIGR_CREATE_DDL are used to tell R3LOAD how to create non-standard objects in the target database.

The RS_BW_POST_MIGRATION program adapts the non-standard objects to the requirements of the target system.

ADM545 Lesson: Introduction

The reports SMIGR_CREATE_DDL and RS_BW_POST_MIGRATION are required since BW 3.0, and for all systems based on BW functionality (i.e.

SCM/APO). They are also mandatory for NetWeaver '04 (Web AS 6.40) and later.

JLOAD is available since NetWeaver '04 (Web AS 6.40). Earlier versions of the JAVA Web AS (i.e. Web AS 6.20) did not store data in a database.

JSIZECHECK is available since NetWeaver 04S / 7.00.

JLOAD and JSIZECHECK are JAVA programs which are called by SAPINST.

Figure 5: Support Tools for ABAP System Copies (1)

The PACKAGE SPLITTER is available in a JAVA and in a Perl implementation.

R3SETUP is using the Perl PACKAGE SPLITTER. SAPINST provides the Perl and JAVA PACKAGE SPLITTER or the JAVA version only (release dependent).

Two TABLE SPLITTERs exist: One is database independent and is called R3TA, the other is a PL/SQL script implementation and is available for Oracle only.

Table splitting is supported since R3LOAD 6.40 in combination with MIGMON.

MIGCHECK is implemented in JAVA.

5

Unit 1: Introduction ADM545

Figure 6: Support Tools for ABAP System Copies (2)

MIGMON and MIGTIME are implemented in JAVA. The JAVA based tools are release independent and can be utilized on any SAP platform which supports the required JAVA version.

The Distribution Monitor can be used if the R3LOAD caused CPU load should be distributed over several application servers. This can improve the database server performance significantly. It is often seen in Unicode conversion scenarios.

Normally the Distribution Monitor makes sense only, if more than one application server is planned to use. It was developed to support system copies based on Web AS 6.x and later.

Figure 7: Support Tools for JAVA System Copies

JPKGCTL (also called JSPLITTER) was developed to reduce the export/import run-time for large JAVA systems. A single JLOAD process exporting the whole database (like implemented in previous SAPINST versions) was often too slow as soon as the database was exceeding a certain size, so it was necessary to provide package and table splitting for JLOAD as for R3LOAD.

ADM545 Lesson: Introduction

JMIGMON and JMIGTIME do offer a similar functionality like MIGMON and MIGTIME.

Figure 8: Possible Negative Consequences of a System Copy

The goal of this training is to prevent problems, such as those mentioned above, by providing in-depth knowledge about each SAP System copy step and the tools which are involved. Following the SAP guidelines ensures a smooth migration project.

Figure 9: Definition: SAP Homogeneous System Copy

For the target system, the same operating system can also mean an SAP certified successor like Windows 2003 / Windows 2008.

Depending on the method used for executing the homogeneous system copy, it might be necessary to upgrade the database or the operating system of the source system first. On older SAP System releases, even an upgrade might be necessary.

This can happen if the target platform requires a database or operating system version that was not backward released for the SAP System version that is to be copied, etc.

7

Unit 1: Introduction ADM545

New hardware on the target system might be supported by the latest operating system and database version only.

With or without assistance from a consultant, customers can execute a homogeneous system copy by themselves. If you plan to use a new hardware type or make major expansions to the hardware (such as changing the disk configuration), we recommend involving the hardware partner as well.

Figure 10: Reasons for Homogeneous System Copies

The term MCOD is used for SAP installations where [M]ultiple [C]omponents are stored in [O]ne [D]atabase.

If a system was installed with an SAP reserved SAPSID, a homogeneous system copy can be used to change the SAPSID. To see if a change is required, check with SAP.

All the mentioned reasons above are also applicable to heterogeneous system copies.

ADM545 Lesson: Introduction

Figure 11: Definition: SAP Heterogeneous System Copy

An OS/DB migration is a complex process. Consultants are strongly advised to do all they can to minimize the risk with regard to the availability and performance of a production SAP System.

Depending on the method used for executing the heterogeneous system copy, it might be necessary to upgrade the database or the operating system of the source system first. On older SAP System releases, even an upgrade might be necessary.

This can happen if the target platform requires a database or operating system version that was not backward released for the SAP System version that is to be migrated, etc.

New hardware on the target system might be supported by the latest operating system and database version only.

The decisive factors for performance in a SAP System are the parameter settings in the database, the operating system, and the SAP System itself (which depends on the operating system and the database system). During an OS/DB migration, the old settings cannot simply be taken unchanged. Determining the new parameter values requires an iterative process, during which the availability of the migrated system is restricted.

9

Unit 1: Introduction ADM545

Figure 12: Common Heterogeneous System Copy Reasons

The above mentioned points are the primary reasons for changing an operating system or database, but the reasons for homogeneous system copies also apply.

The reasons also partially apply to homogeneous system copies.

Figure 13: Frequently used SAP Terms

The above table shows which term is being used for SAP System copies. For example, when changing the operating system, this is called an OS migration and is a heterogeneous system copy. Generally, the term heterogeneous system copy implies that it is some kind of OS and/or DB migration.

The term “SAP System copy” is used in a more unspecific way.

ADM545 Lesson: Introduction

Figure 14: Homogeneous or Heterogeneous System Copy?

The table above is only valid when using R3LOAD or JLOAD. Homogeneous system copies using Backup/Restore will require the same database version on source and target system, or must be upgraded after the system copy.

Note: If the hardware architecture in a system copy does change, but the operating system type stays the same, it is a homogenous system copy.

In other words, if the operating system is called the same on source and target, it is a homogeneous system copy. This does not automatically imply the possibility of a backup/restore to copy the database (i.e. system copy from Solaris SPARC to Solaris Intel). It only points out, SAP treats it like a homogeneous system copy and no “SAP OS/DB Migration Check” is required. SAP assumes the operating system behavior will be the same without regards of the underlying platform. Please check the database documentation for details on available system copy procedures.

Further examples are: HP-UX PA-RISC to HP-UX IA64, LINUX X86 to LINUX POWER, etc.

11

Unit 1: Introduction ADM545

Figure 15: SAP OS/DB Migration Check (1)

The cost for the SAP OS/DB Migration Check is specific to the customer location and may differ from country to country.

The SAP OS/DB Migration Check will be delivered as a remote service.

In the “Remote Project Audit”, SAP checks the OS/DB migration project planning.

The required tools for homogeneous or heterogeneous system copies (installation software) are provided by SAP to customers free of charge. The software can be downloaded from the SAP Service Marketplace.

Figure 16: SAP OS/DB Migration Check (2)

ADM545 Lesson: Introduction

Figure 17: Information on the SAP OS/DB Migration

Complete information about OS/DB migrations is available in the SAP Service Marketplace and the SAP Developer Network.

FAQs = Frequently Asked Questions

The manuals for homogeneous and heterogeneous system copies can be downloaded from the SAP Service Marketplace.

SAP Notes are available on homogeneous and heterogeneous system copies.

Check the homogeneous / heterogeneous system copy manuals for the respective SAP Note numbers.

13

Unit 1: Introduction ADM545

ADM545 Lesson: Introduction

Exercise 1: Introduction

Exercise Objectives

After completing this exercise, you will be able to:

• Differentiate between homogeneous and heterogeneous system copies and to know the procedural consequences for a migration project.

Business Example

In customer projects, you must know whether a system move or a database change is a homogeneous or heterogeneous system copy and in which case it is necessary to order a SAP OS/DB Migration Check Service.

Task 1:

A customer plans to invest in a new and more powerful hardware for his ABAP-based SAP production system (no JAVA Web AS installed). As the operating system and database version are not up-to-date, he also wants to change to the latest software versions in a single step while doing the system move.

Current system configuration: Oracle 10.2, AIX 6.1 Planned system configuration: Oracle 11.2, AIX 7.1

1. Is the planned system move a homogeneous system copy, a DB migration or an OS migration? Describe your solution!

2. If the SAP System copy tool R3LOAD is used, will it be necessary to perform an operating system or database upgrade after the move? Describe your solution!

Task 2:

An SAP implementation project must change the database system before going into production, because of strategic customer decisions. The customer system configuration was setup as a standard three-system landscape (development, quality assurance, production). Each system is configured as ABAP Web AS with JAVA Add-In.

1. Is it necessary to order a SAP OS/DB Migration Check for the planned database change?

2. According the SAP System copy rules, who must do the system copies?

15

Unit 1: Introduction ADM545

Solution 1: Introduction

Task 1:

Current system configuration: Oracle 10.2, AIX 6.1 Planned system configuration: Oracle 11.2, AIX 7.1

1. Is the planned system move a homogeneous system copy, a DB migration or an OS migration? Describe your solution!

a) The system move will be a homogeneous system copy. Neither the database nor the operating system will be changed. During a system copy, an upgrade to a new database or operating system software version is not a problem, as long as the operating system and database combinations are supported by the respective SAP System release and SAP kernel version.

2. If the SAP System copy tool R3LOAD is used, will it be necessary to perform an operating system or database upgrade after the move? Describe your solution!

a) Provided the fact that the installation software is able to install on the target operating system version and also supports the installation of target database release directly, no additional OS/DB software upgrade will be necessary after the R3LOAD import. In the case that the new target database is not supported by the installation software, a database upgrade will have to be done after the system copy.

Task 2:

1. Is it necessary to order a SAP OS/DB Migration Check for the planned database change?

a) a) The system landscape contains a pre-production system only. In this case, no OS/DB Migration Check service is necessary, as its intention is to be used for productive systems only.

Continued on next page

ADM545 Lesson: Introduction

2. According the SAP System copy rules, who must do the system copies?

a) The change of a database involves a heterogeneous system copy, which must be done from someone who is certified for OS/DB migrations.

The fact that the systems are not productive is regardless.

17

Unit 1: Introduction ADM545

Lesson Summary

You should now be able to:

• Distinguish between an SAP homogeneous system copy and an SAP OS/DB Migration

• Estimate the problems involved with a system copy or migration

• Understand the functions of the SAP OS/DB Migration Check

ADM545 Unit Summary

Unit Summary

You should now be able to:

• Distinguish between an SAP homogeneous system copy and an SAP OS/DB Migration

• Estimate the problems involved with a system copy or migration

• Understand the functions of the SAP OS/DB Migration Check

19

Unit Summary ADM545

Unit 2

The Migration Project

Unit Overview

Unit Objectives

After completing this unit, you will be able to:

• Describe the scope of services performed by the SAP OS/DB Migration Check

• Estimate the effort involved in a migration

• Plan a migration project

Unit Contents

Lesson: The Migration Project ... 22 Exercise 2: The Migration Project ... 35

21

In document TITULO: Formación de nuevas estructuras moleculares en películas ultrafinas. Preparación de dispositivos electroluminiscentes y fotovoltaicos. Molecular Arrangement in ultrathin films. Thin films in optoelectronic devices AUTOR: Cristina Roldán Carmona (página 148-157)