BW System Copy

© SAP 2008 /

1. Homogenous vs. heterogeneous System copy

2. New BI BW specific activities before, during and after System copy2.1 Details about SourceSystem Connections 2.2 System renaming2.3 System copy BW-system2.4 System copy SourceSystem

Agenda

© SAP 2008 /

Homogeneous vs. heterogeneous System copy

System copy

homogeneous heterogeneous

Version and type of OS and DB identical for source and target system

Version or type of OS or DB different between source and target system.

QBW PBW

Example: Refresh of QAS System

PBW(Oracle)

PBW(MAXDB)

Example: Refresh of QAS System

Windows LinuxQA-System PRD-System

© SAP 2008 /

Homogeneous System Copy: General Aspects

Basically you can use R3LOAD, but other DB specific methods are usually more comfortable and faster

Different methods and tools are possible depending on the database type

General procedure for most of the homogeneous System copies: Installation of BW System with Installation Tool SAPINST until the

database has to be imported (SAPINST for homogeneous system copies is mainly used to build up the SAP Instance)

Interrupt installation and use Backup or Mirror Technology for the database copy from the Original System

Finish Installation with SAPINST

Database

SAPINST

SAP + Oracle Instance

Restore Database Backup

SAPINST

SAP+ Oracle Instance

1122

33

11

22

33Specified

more in detail on the next

slides

© SAP 2008 /

Oracle - Homogeneous System Copy (typical method): BRBACKUP/BRRESTORE

QAS-DatabasePRD-Database

BRBACKUPSAP-Tool for Backup of an Oracle Database

BRRESTORESAP-Tool for Backup of an Oracle Database

SAP Instance

Oracle Instance

SAP Instance

Oracle Instance

Create new Control file

BRBACKUPBRRESTORE

© SAP 2008 /

Oracle - Homogeneous System Copy (for huge systems): Usage of File System Copy/Split Mirror Technology

Production Server (or split Mirror)

Backup Server

Database Instance Database Instance

11

22

33

1. Suspend all write operations to database or split mirror (if available)

2. Create a database copy on file system level

3. Resume all write operations

4. Create new Control File

…

Database Database

© SAP 2008 /

DB6 - Homogeneous System Copy (typical method): SAP Redirected Restore Tool: brdb6brt

DatabaseDatabase

brdb6brt -bm bothBackup and create

DB2 CLP script

brdb6brt -bm retrieveOnly create

DB2 CLP script

<DBSID>.SCR-File

Redirectedrestore using the DB2 CLP script

Edit

Use backup image

© SAP 2008 /

DB6 - Homogeneous System Copy (Huge System): Split-Mirror Backup: Preparation on Source (1)

Production Server (or split Mirror)

Backup Server

Database Instance Database Instance

11

22

33

1. Suspend all write operations to database or split mirror (if available)

2. Create a database copy on file system level

3. Resume all write operations

Database Database

© SAP 2008 /

DB6 - Homogeneous System Copy (Huge System): Split-Mirror Backup: Cloning a Database (2)

1. The following command performs the redo and undo phase of a restart recovery:Database instance

db2inidb <dbsid> as snapshot

Database

QASThis method can be used to create a homogeneous system copy.

© SAP 2008 /

MAXDB - Homogeneous System Copy (typical method): Backup type migrate

QAS-DatabasePRD-Database

DBMGUI -> Backup of type migrate

DBMGUI -> Restore of Database

SAP Instance

DB Instance

SAP Instance

DB Instance

Backup type Migration

Restore with other SID

© SAP 2008 /

Heterogeneous System copy: SAP NetWeaver BI 7.0 – Availability Matrix

SAP NetWeaver BI 7.0 – Availability Matrix

The general note for migrating a NetWeaver BI 7.0 system is 771209.The documentation is database independent. You will find the migration guide here.In case of a heterogeneous migration, please check if the OS/DB combination of your target release is supported by SAP.For SAP NetWeaver BI 7.0 you will find the Product Availability Matrix here (August 2005)

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=771209

http://service.sap.com/~sapidb/011000358700009331552004E

http://service.sap.com/~form/handler?_APP=00200682500000001303&_EVENT=RELEASE&00200682500000002804=01200314690900000192&00200682500000003818=PLTFRM

© SAP 2008 /

General Aspects for heterogeneous System copies

SAP recommends to use R3load for DB Export/Import

Specific activities have to be done for each database, e.g. 'SMIGR_CREATE_DDL' program before you export the data from the source system. The

program allows you to copy database objects that do not meet SAP standards. These objects include partitioned (fragmented) tables and bitmap indexes. Special files of type '<TABART>.SQL' are generated for these objects. These files contain 'native DDL' (create) statements and can be analyzed by R3load

more details: see notes771209 NW04: System copy (supplementary note)777024 BW3.0 and BW3.1 System Copy (supplementary note)

© SAP 2008 /

Documentation

Guidelines:

Alias BI: Services&Implementation -> System Copy and Migration

General notes:

547314 FAQ: System Copy procedure

BW specific notes:

543715 Projects for BW Migrations and System Copies 771209 NW04: System copy (supplementary note)777024 BW3.0 and BW3.1 System Copy (supplementary note)

© SAP 2008 /

1. Homogenous vs. heterogeneous System copy 2. New BI BW specific activities before, during and after System Copy

2.1 Details about SourceSystem Connections 2.2 System renaming2.3 System copy BW-system2.4 System copy SourceSystem

Agenda

© SAP 2008 /

System copy BW-system – Typical scenarios

BW

BWP

BW

BWQ

copy

original BWold BW

target BWBWP

BW

BWP

copy

original BW

target BW

BWP

R3

R3P

R3

R3Q original R3old R3

copytarget R3R3P

BW

BWP

BW

BWQ

System copy on SourceSystem sideClient copy on SourceSystem side

R3

R3Q_100original client

copy

R3Q_200

BW

BWQ

target client

System copy on BW side: Install on a new system or refresh an existing system

© SAP 2008 /



Agenda

© SAP 2008 /

BW SourceSystem Connection

Sourcesystem Table RSBASIDOC

BW-System Table RSBASIDOC

RFC-connectionALE

RSRQST

RSINFO RSSEND

A BW SourceSystem Connection is based on

an ALE configuration with 3 types of IDocs

RFC Connection on the technical level

© SAP 2008 /

Logical system name

The logical system name is the unique identification of a system client in an SAP-system-landscape Client-specific Table T000 Don‘t try to connect two systems with the same logical system name!

Exception: Just in case of (temporary) standalone system copies (like test system for upgrade)

sometimes changing the logical system name after the system copy is not necessary.

© SAP 2008 /

Table RSBASIDOC

Table RSBASIDOC lists all SourceSystem-connections. You should find an identical record in both systems:

In BW-system B35:

In SourceSystem QB8:

© SAP 2008 /

Table RSBASIDOC

Details about the fields of table RSBASIDOC: RLOGSYS Receiving logical system SLOGSYS Sending logical system BIDOCTYPE Basis IDoc type TSPREFIX Two-digit identification code, which is used in the

generated IDoc-Type, the transfer structure names and in the DDIC-structures of this SourceSystem-connection

SRCTYPE SourceSystem type 3 – R/3-system M – Myself-system F – Flatfile

Do not change this table manually!

© SAP 2008 /

Partner profiles

Exists in BW and in the SourceSystem, client-dependent

Transaction WE20 Partner type LS (logical system) choose logical system name of the partner

Consists of inbound and outbound-parameters Inbound: Message types which

the partner can receive and process link to a process code and finally to a function module

Outbound: Message types which the partner can send link to a port

© SAP 2008 /

Ports

Transaction WE21 or “doubleclick” from the partner profiles outbound parameters Message type (RSRQST in BW, RSINFO and RSSEND in SourceSystem) Receiver port

Specifies how the other system can be reached, contains the RFC-destination

© SAP 2008 /

Myself-connection / Flatfile-connection

Myself connection Used for DataMart functionality within the BW system itself Different setups for the RFC-destination possible:

RFC-Destination can be completely empty (except for destination name and connection type) No RFC-connection during call, function is executed on the same system.

When the RFC-Destination is maintained with logon details, an RFC-call is done to the same system.

Flatfile connection Only locally defined organization-node Normally not more than one File SourceSystem needed Contains the following parts on BW-side:

ALE and Idocs TCP/IP-Destination

© SAP 2008 /



Agenda

© SAP 2008 /

System renaming

Overview about the necessary steps:

Execute BDLS - notes 121163 and 369758

Check RFC-Destinations - note 524554

Reactivate partner profiles

© SAP 2008 /

Conversion of logical system names

Use transaction BDLS for the conversion Execute it in the system to be renamed AND in all connected systems. The program determines all the relevant tables and converts the corresponding

entries. No other activities can be performed in the system during conversion. Restart capability

Renaming of a productive system is not officially supported!

© SAP 2008 /

Conversion of logical system names

Read the program documentation in BDLS VERY CAREFULLY!

To improve performance, this value should be as large as possible, depending on the limits of the database roll area.

© SAP 2008 /

Check table RSLOGSYSDEST

Table RSLOGSYSDEST Mapping Logical System name to RFC-Destination In BW-systems, the RFC-Destination can be named differently than the logical

system. In R/3-systems, the names are identical. BDLS renames the LOGSYS field of the table, but the DESTINATION field has to

be changed manually!

© SAP 2008 /

Check RFC-Destinations

RFC-Destinations have to be maintained manually in the renamed system and in all connected systems (transaction SM59)

Check target host

Check logon data

© SAP 2008 /

Reactivate partner profiles

Transaction WE20 Partner type LS (logical system) choose logical system name of the partner Tab „classification“ change partner status from „I“ (inactive) to „A“ (active) Save

© SAP 2008 /

Check table RSLOGSYSMAP

Table RSLOGSYSMAP Used in the AFTER_IMPORT of a transport to change the SourceSystem-

depended objects (e. g. TransferStructures) to the correct new SourceSystem

© SAP 2008 /



Agenda

© SAP 2008 /

System copy BW-system

You want to replace an existing BW by copying a different BW. That is, a BW was already installed on the target host.

BW

BWP

BW

BWQ

copy

original BWold BW

target BWBWP

You want to install a new BW by copying an existing BW. That is, you import the copy onto an empty system.

BW

BWP

copy

original BW

target BWBWP

© SAP 2008 /

System copy BW-system – Step 1

Create a special transport with source system dependent objects (transport collector → grouping: system copy) for each R/3- or DataMart SourceSystem

Depending on your scenario, you have to create this transport request in the old BW or in the original BW „Which SourceSystem-connections do you want to have in the new BW-system?“

Don‘t forget to choose the correct SourceSystems

© SAP 2008 /

System copy BW-system – Step 2 and 3

In the old BW, delete all R/3 and DataMart SourceSystems in the Administrator Workbench SourceSystem tree.

DO NOT delete the Myself system!

Import the DB Backup.

© SAP 2008 /


Directly after the copy, a connection exists between the target-BW and the SourceSystems of the original BW !

The SourceSystem-connections from the target-BW have to be deleted without touching the SourceSystem-connections on the original R/3-side.

BW

BWP

BW

BWP

copy

original BWtarget BW

R3

R3P

delete! keep!

© SAP 2008 /


How to do this:

Set the number of BATCH-processes to „0“ in SAP Profile of the target BW before you start the system again, so that no scheduled processes can run on the „wrong“ system.

In the target BW, change the contents of the "target host" field in all RFC-destinations for R/3 and DataMart SourceSystems to a nonexistent address (transaction SM59).

Then, delete ALL R/3 and DataMart source systems in the RSA1 SourceSystem tree of the target BW. Caution: This step deletes all PSA tables of these source systems - the data is lost. A message is generated stating that the source system cannot be accessed (since

you deleted the host of the RFC connection). Select "Ignore".

© SAP 2008 /

System copy BW-system – Steps 5 - 8

Rename the target BW Assign the same name to the target BW system that was assigned to the old BW

system (logical system name, Table T000). See last chapter for details about BDLS

Connect the SourceSystems that were connected to the old BW-system Use the Administrator Workbench, right mouseclick on SourceSystems – Create

Import the transport request which was created before the system copy Don‘t forget to adjust RSLOGSYSMAP

© SAP 2008 /

System copy SourceSystem

You replaced a source system of a BW with another system, to refresh e. g. your R/3 test system by a copy of the R/3 production system.

The copy destroyed the SourceSystem-connection from BWQ to R3Q (because R3Q is overwritten). But there is a SourceSystem-connection between the new copied R3P and the BWP.

R3

R3P

R3

R3Q original R3old R3

copytarget R3R3P

BW

BWP

BW

BWQ

R3

R3P

R3

R3P original R3

copy

target R3

BW

BWP

BW

BWQ

before system copy after system copy

© SAP 2008 /

Postprocessing system copy SourceSystem – Step 1

Set the number of BATCH-processes to „0“ in SAP Profile before you start the SourceSystem again after the copy, so that no scheduled processes can run on the „wrong“ system.

How to delete the SourceSystem-connection between the BWP and the fresh copied target R/3 without touching the original R3P:

Check table RSBASIDOC in the fresh copied target R/3 to determine all existing SourceSystem-connections If the table is empty, skip step 2 If entries exist: Note down all these entries: fields RLOGSYS and SLOGSYS.

© SAP 2008 /

Postprocessing system copy SourceSystem – Step 2

Only if necessary:

Execute function module RSAP_BIW_DISCONNECT in the TARGET R/3 system parameters

I_BIW_LOGSYS = <RLOGSYS> I_OLTP_LOGSYS = <SLOGSYS> I_FORCE_DELETE = 'X'

This step deletes all obsolete BW connections. Repeat this for all entries in table RSBASIDOC.

DO NOT enter a value in the field "RFC target sys". This would cause the function module to run in the system specified there!

© SAP 2008 /

Postprocessing – Steps 3 - 6

Change the logical system name to the name known by BWQ

Execute BDLS in the SourceSystem Correct the RFC-Destinations Restore the R/3-system from BWQ

(transaction RSA1)

© SAP 2008 /

System copy SourceSystem via Client copy

You refresh a SourceSystem via a local client copy

If you want to rename the target client, execute transaction BDLS. Ensure that you select the (non-default) option "Conversion of client-specific tables

(e.g. after a client copy)". You must not convert client- independent tables under any circumstances!

In BW, transaction RSA1: Restore the client or (if it is a new SourceSystem) create a new SourceSystem-connection.

R3

R3Q_100original client

copy

R3Q_200

BW

BWQ

target client

© SAP 2008 /

Important Notes

886102 System Landscape Copy for SAP BW 3.X

777024 General note BW system copy

732907 Heterogeneous BW migration

184447 Building a BW-system landscape

524554 Storing destinations in the BW environment

518426 Reset generated programs for ODS-Objects

760949 Deallocating extraction in copied system

415878 Delete Outbound-tRFC-Queues regularly

© SAP 2008 /

Information in SAPNet

alias OSDBMIGRATION

alias BI Service & Implementation Systemcopy & Migration

Alias BI Service & Implementation HOW TO … Guides Guide List SAP BW 3.5 – Part of NW04 How to… System Copy in SAP BI System Landscapes

© SAP 2008 /

Copyright 2008 SAP AGAll rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.

Alle Rechte vorbehalten.

BW System Copy

Documents

Transcript of BW System Copy