Français dropdown-ico

IBM V7.2 manuel d'utilisation

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41

Aller à la page of

Les manuels d’utilisation similaires

Un bon manuel d’utilisation

Les règles imposent au revendeur l'obligation de fournir à l'acheteur, avec des marchandises, le manuel d’utilisation IBM V7.2. Le manque du manuel d’utilisation ou les informations incorrectes fournies au consommateur sont à la base d'une plainte pour non-conformité du dispositif avec le contrat. Conformément à la loi, l’inclusion du manuel d’utilisation sous une forme autre que le papier est autorisée, ce qui est souvent utilisé récemment, en incluant la forme graphique ou électronique du manuel IBM V7.2 ou les vidéos d'instruction pour les utilisateurs. La condition est son caractère lisible et compréhensible.

Qu'est ce que le manuel d’utilisation?

Le mot vient du latin "Instructio", à savoir organiser. Ainsi, le manuel d’utilisation IBM V7.2 décrit les étapes de la procédure. Le but du manuel d’utilisation est d’instruire, de faciliter le démarrage, l'utilisation de l'équipement ou l'exécution des actions spécifiques. Le manuel d’utilisation est une collection d'informations sur l'objet/service, une indice.

Malheureusement, peu d'utilisateurs prennent le temps de lire le manuel d’utilisation, et un bon manuel permet non seulement d’apprendre à connaître un certain nombre de fonctionnalités supplémentaires du dispositif acheté, mais aussi éviter la majorité des défaillances.

Donc, ce qui devrait contenir le manuel parfait?

Tout d'abord, le manuel d’utilisation IBM V7.2 devrait contenir:
- informations sur les caractéristiques techniques du dispositif IBM V7.2
- nom du fabricant et année de fabrication IBM V7.2
- instructions d'utilisation, de réglage et d’entretien de l'équipement IBM V7.2
- signes de sécurité et attestations confirmant la conformité avec les normes pertinentes

Pourquoi nous ne lisons pas les manuels d’utilisation?

Habituellement, cela est dû au manque de temps et de certitude quant à la fonctionnalité spécifique de l'équipement acheté. Malheureusement, la connexion et le démarrage IBM V7.2 ne suffisent pas. Le manuel d’utilisation contient un certain nombre de lignes directrices concernant les fonctionnalités spécifiques, la sécurité, les méthodes d'entretien (même les moyens qui doivent être utilisés), les défauts possibles IBM V7.2 et les moyens de résoudre des problèmes communs lors de l'utilisation. Enfin, le manuel contient les coordonnées du service IBM en l'absence de l'efficacité des solutions proposées. Actuellement, les manuels d’utilisation sous la forme d'animations intéressantes et de vidéos pédagogiques qui sont meilleurs que la brochure, sont très populaires. Ce type de manuel permet à l'utilisateur de voir toute la vidéo d'instruction sans sauter les spécifications et les descriptions techniques compliquées IBM V7.2, comme c’est le cas pour la version papier.

Pourquoi lire le manuel d’utilisation?

Tout d'abord, il contient la réponse sur la structure, les possibilités du dispositif IBM V7.2, l'utilisation de divers accessoires et une gamme d'informations pour profiter pleinement de toutes les fonctionnalités et commodités.

Après un achat réussi de l’équipement/dispositif, prenez un moment pour vous familiariser avec toutes les parties du manuel d'utilisation IBM V7.2. À l'heure actuelle, ils sont soigneusement préparés et traduits pour qu'ils soient non seulement compréhensibles pour les utilisateurs, mais pour qu’ils remplissent leur fonction de base de l'information et d’aide.

Table des matières du manuel d’utilisation

  • Page 1

    Using IBM TotalStorage Enterprise Storage Server (ESS) ® with IBM ® DB2 ® UDB Enterprise Edition V7.2 and SAP ® R/3 ® October 2002 Brigit t e Bläser – IBM Germ any Böblingen Laboratory Enzo Cialini – IBM T oronto Laboratory Aslam Nomani – IBM T oronto Laboratory David Davis – IBM Storage Systems Group[...]

  • Page 2

    . © Copy right International Business Machines Corporation 2002. All r ights reserved.[...]

  • Page 3

    Trademarks ii Trademarks The f ollowing terms are t r adem ar k s or reg istered tradem ar ks of Internat ional Business Machines Corporation in the United St at es, ot her countries, or both: AIX DB2 DB2 Universal Database Enterprise St or age Server (ESS) ESCON FlashCopy IBM iSeries zSer ies The f ollowing terms are t rademark s SAP AG in Ger m a[...]

  • Page 4

    Table of contents iii Table of contents ABSTRACT....................................................................................................................... .......................... IV ABOUT THE AUTHORS ........................................................................................................................... V DB2 UDB [...]

  • Page 5

    Abstract iv A bstract SAP ® R/3™ and its components have been the success of more than 19, 000 installations in enter pr ises of every size in more than 106 countries worldwide. The SAP R/3 system is an open, int eg rated system t hat covers all business applicat ions including accounting and cont r olling , production and m at er ials managemen[...]

  • Page 6

    About the authors v A bout the authors A slam No mani has been working with the I BM Database Technolog y team in the Toront o Labor at or y f or f ive years. For the past four years, he has work ed in t he DB2 UDB System Verificat ion Test depar tment. Aslam has worked extensively in testing DB2 UDB EE and DB2 UDB EEE in a high availability enviro[...]

  • Page 7

    DB2 UDB sus pended I/O ov erview 1 DB2 UDB suspended I/O over vi ew DB2 UDB v 7.2 has implemented suspended I/O technology, w hich prov ides the capability to use split mirroring technology while DB2 is online. Suspended I/O supports continuous system availability by providing a full im plementation f or splitt ing a mirr or (pair) without shutt in[...]

  • Page 8

    DB2 UDB co mmands 2 DB2 UDB commands W e use t he f ollowing commands: set w rite suspend The suspend command ( db2 set write suspend for dat abase) suspends all write operations to t he DB2 UDB dat abase (i.e., t o t ablespaces and log f iles) . Read operations are not suspended and ar e t hus allowed to continue. Applications can continue to proc[...]

  • Page 9

    DB2 UDB co mmands 3 Universal Database V7 http://www7b.software.ibm.com/dmdd/library /techarticle/0204quazi/0204quazi.html ..[...]

  • Page 10

    Overvi ew of IBM 2105 Ent erprise St orage Serv er 4 Overv iew of IBM 2105 Enterprise Storage Server The IBM 2105 Enterprise St or ag e Server (ESS) pr ovides superior st orage sharing for Unix®, W indows NT®, W indow s 2000®, Novell Netware, iSeries™ and zSeries™ servers. W ith the ESS any combination of t hese het er og eneous platf or ms [...]

  • Page 11

    Overview of FlashC opy 5 Overv iew of Copy Serv ices Copy Services is a separately priced feat ur e of the ESS, which provides powerful funct ions f or replicat ion of mission-crit ical dat a. For the O pen System s environment Copy Services off er point - in-time replicat ion with FlashCopy and dynamic synchronous mirror ing to a remot e ESS with [...]

  • Page 12

    Overview of FlashC opy 6[...]

  • Page 13

    Overview of ESS Copy Services Web Interf ace 7 Overview of the ESS Copy Services Web interface The ESS Copy Services W eb int er f ace is used to creat e and m anage Copy Services tasks. T his W eb int er f ace consists of a number of HTML screens and Java™ applets and can be accessed from a standard W eb browser. A Copy Services task consists of[...]

  • Page 14

    Overview of ESS Com man d Line In terface (CL I) 8 Overview of ESS Command Line Interface (CLI) The ESS Command Line I nterf ace consists of a num ber of scripts t o com m unicate with the ESS Copy Services server. The Comm and Line I nterf ace is Java-based and theref ore requir es the Java JDK version 1.1.8 to be installed on each host system fr [...]

  • Page 15

    ESS Copy Serv ices CLI C omm an d Description 9 ESS Copy Serv ices CLI command description rsExecuteTask Executes one or more predef ined Copy Services Server tasks and waits f or the task s t o complete execution. T he com m and r eturns 0 f or successf ul completion and g reater-t han zero if t her e is an er r or. . Note : For FlashCopy task s, [...]

  • Page 16

    Overview of Standard SAP R/3 Sy stem Ins tallation w ith DB2 UDB 10 Overview of standar d SA P R/3 sy stem installa ti on w ith DB2 UDB A SAP R/3 system is identif ied by a three character system identif ier <SI D> and a two digit system number bet ween 00 and 96. The f ollowing informa t ion about t he dir ect ory structure applies t o a Cen[...]

  • Page 17

    Overview of Standard SAP R/3 Sy stem In stallation w ith DB2 UDB 11 Detailed discussions about the layout of a SAP R/3 system on an ESS ar e cont ained in the f ollowing white papers: • Sanjoy Das, Siegf ried Schmidt , Jens Claussen, BalaSanni Godavari: “ St or ag e Management f or SAP and DB2 UDB: Split Mirror Back up / Recovery with IBM Enter[...]

  • Page 18

    SAP R/3 with DB2 UDB and ESS Sample Config uration 12 Sample configur ati on of SA P R/3 w ith DB2 UDB and IBM ESS In this conf igurat ion, we will w ork with a standard SAP R/3 installat ion and describe the following dif fer ent scenarios that use t he DB2 UDB split mirror f unctionality: • Creating a clone SAP system ( Snapshot dat abase scena[...]

  • Page 19

    SAP R/3 with DB2 UDB and ESS Sample Config uration 13 volume groups are cr eat ed on t he Primary server f or the SAP system and the dat abase, respecti vely . DB2 Universal Database v7.2 for AIX® is used; DB2 UDB suspended I/O capabilities are available on all platfor m s suppor t ed by DB2 UDB. An IBM ESS 2105 F20 is used. The same scenarios als[...]

  • Page 20

    SAP R/3 with DB2 UDB and ESS Sample Config uration 14 lsdev –C | grep 2105 3. Use the ESS Command Line I nt erf ace com m and r s List 2105s t o display the mapping of host physical volume name to ESS volume serial num ber f or all disk s assigned to the host system: cd /usr/opt/ibm2105cli ./rsList2105s.sh 4. Determine t he SCSI pat hs and disks [...]

  • Page 21

    Configuri ng a Two Ho st System 15 Configuring a system with two hosts Overv iew 1. Install t he ESS CLI on t he Primary Server. 2. Assign ESS disks to both servers. 3. Install DB2 f or AIX on bot h servers. 4. Install a standar d SAP R/3 system on the Pr im ar y Server. Figure 2 shows the conf iguration we used f or t he FlashCopy examples. Pr i m[...]

  • Page 22

    Configuri ng a Two Ho st System 16 • The host nam e of the Back up ser ver is MACHB. • The host nam e of the ESS Copy Services Server is ESSCSS. • The name of the SAP system is T S1; it s system num ber is 00. • To achieve optimal perf ormance t he disks are spr ead eq ually over all 8 LSSs of the ESS. • The Primar y server uses the sourc[...]

  • Page 23

    Configuri ng a Two Ho st System 17 o hdisk42 o hdisk40 o hdisk38 o hdisk37 o hdisk43 • The source and t ar g et volume of each FlashCopy pair reside in t he same ESS LSS. Note: T he root userid must be used to execute all ESS and AIX com m ands, and to install DB2 and create t he DB2 inst ance. The rem ainder of t he DB2 commands are executed fro[...]

  • Page 24

    Configuri ng a Two Ho st System 18 For the Split Mirror Rest or e Scenar io we need FlashCopy tasks f or the database data f ilesystems only without the ‘no copy’ option. W e also need FlashCopy tasks f or establishing r everse FlashCopy pairs for t he dat abase data f ilesystems. Alt hough these could be def ined with the no copy option this i[...]

  • Page 25

    Configuri ng a Two Ho st System 19 Alternatively , issue the following command: mkvg –f –y sapvg –s 64 hdisk15 # smit vg ->A dd a Volume Group Alternatively, issue the f ollowing command : mkvg –f –y dbvg –s 64 hdisk9 hdisk11 hdisk21 hdisk26 hdisk28 hdisk29 hdisk33 hdisk34 hdisk41 Create logical volumes The f ollowing procedure creat[...]

  • Page 26

    Configuri ng a Two Ho st System 20 Alternatively, issue the f ollowing command: mklv –y saplv sapvg 60 #smit lv ->A dd a Logical Volume - > VO LUME GROUP name [dbvg][...]

  • Page 27

    Configuri ng a Two Ho st System 21 Alternatively, issue the f ollowing commands: mklv –y dblv dbvg 60 hdisk26 mklv –y data1lv dbvg 295 hdisk9 mklv –y data2lv dbvg 295 hdisk33 mklv –y data3lv dbvg 295 hdisk11 mklv –y data4lv dbvg 295 hdisk29 mklv –y data5lv dbvg 295 hdisk21 mklv –y data6lv dbvg 295 hdisk41 mklv –y data7lv dbvg 295 hd[...]

  • Page 28

    Configuri ng a Two Ho st System 22 Alternatively, issue the f ollowing command: crfs –v jfs –d saplv –m /usr/sap –A yes –p rw #smit fs ->A dd / Ch ange / Show / Delete File Sy stems ->Jou rnaled File Sy stems - >A dd a Journal ed Fi l e Sy stem on a Previously Defined Logical Volume ->A dd a Standard Journaled Fil e System Alt[...]

  • Page 29

    Configuri ng a Two Ho st System 23 chfs -a size=14000000 /db2/TS1/sapdata6 chfs -a size=14000000 /db2/TS1/sapdata7 chfs -a size=14000000 /db2/TS1/log_dir chfs -a size=14000000 /db2/TS1/db2ts1/NODE0000 Mount the file systems: mount /usr/sap mount /db2/TS1/db2ts1/NODE0000 mount /db2/TS1/sapdata1 mount /db2/TS1/sapdata2 mount /db2/TS1/sapdata3 mount /[...]

  • Page 30

    Configuri ng a Two Ho st System 24 /db2/TS1/log_dir . Loading the dat a int o t he database may last several hours. For more det ails about installing an SAP R/ 3 system please r ef er to t he SAP R/3 Install ation Gui de . 8. Flash the SAP sof t ware to t he t arget disk and system: a. Create the g roup dbts1adm and t he user t s 1adm on t he t ar[...]

  • Page 31

    Configuri ng a Two Ho st System 25 11. On t he Backup server f rom the db2inst 1 inst ance, catalog t he dat abase T S1 even though the f ile systems that cont ain t he dat abase TS1 does not curr ent ly exist on the Backup server: db2 “catalog db TS1 on /db2/TS1” The base conf iguration is now done and the f ollowing sections will provide exam[...]

  • Page 32

    Snapshot Databas e Scenario 26 Snapshot database scenario This scenario st ar t s with SAP R/3 system T S1 running on t he Pr im ar y server and clients using the Pr im ar y database. T he Backup server has T S1 and DB2 stopped and DB2 file systems for dat a and log s unmounted. 1. From the Pr im ar y Server issue t he suspend com m and on t he Pri[...]

  • Page 33

    Snapshot Databas e Scenario 27[...]

  • Page 34

    Standby Database Scenario 28 Standby database scenario This scenario st ar t s with the SAP R/ 3 system T S1 running on the Pr imary server. On t he Backup server, T S1 is stopped and the DB2 f ilesystems for dat a and logs are unmounted. T his scenario assumes that t he FlashCopy pairs and t ask s are already defined on t he ESS Copy Services Serv[...]

  • Page 35

    Standby Database Scenario 29 6. Start t he DB2 inst ance db2ts1 on the Back up ser ver: db2start 7. Place the Backup dat abase int o a rollf or ward pending st at e, and tak e it out of it s suspended state: db2inidb ts1 as standby 8. As DB2 log f iles are successfully g et t ing archived to the ar chive direct or y on the Primary database, m ak e [...]

  • Page 36

    Standby Database Scenario 30 befor e t he log ic error occurr ed. I f the dat abase needs t o be recovered to the point when the Primary server f ailed, then a r ollf orward to end of logs should be perf ormed: db2 “rollforward database ts1 to end of logs and stop” or db2 “rollforward database ts1 to 2000-06-19-20.57.00.0000 and stop” 15. S[...]

  • Page 37

    Split-Mirror Online Backup Scenario 31 Split-Mirror online backup scenario This scenario st ar t s with the SAP R/ 3 system T S1 running on the Pr imary server. The Backup server has T S1 st opped and DB2 f ile systems f or data and logs unmount ed. A tt ention: T his scenar io is cur r ently not supported f or databases t hat cont ain SMS tablespa[...]

  • Page 38

    Split-Mirror Online Backup Scenario 32 7. The f ollowing command places the Back up dat abase into a rollf orward pending state and tak e it out of a suspended state: db2inidb ts1 as standby 8. Perf or m a DB2 back up on the Backup ser ver using the support ed back up system: db2 “backup database ts1 to /backupfs” 9. Stop the DB2 instance on t [...]

  • Page 39

    Split-Mirror Online Backup Scenario 33 5. Start t he SAP system T S1 by logging on as t s1adm user and issuing t he following comm and: startsap[...]

  • Page 40

    Split-Mirror Restore Scenario 34 Split-mirror restore scenario This scenario st ar t s with the SAP R/ 3 system T S1 running on the Pr imary server. The Back up ser ver has T S1 st opped and DB2 f ile system f or data and logs unmounted. 1. Edit the userexit pr og ram and place it in t he appropriate dir ect ory on the Primar y server so DB2 knows [...]

  • Page 41

    Split-Mirror Restore Scenario 35 mount /db2/TS1/sapdata6 mount /db2/TS1/sapdata7 9. Start t he DB2 instance on the Prim ar y server: db2start 10. On t he Pr im ar y database issue the db2inidb command to t ak e the database image out of a suspended state and place it into a rollf orward pending state: db2inidb ts1 as mirror 11. O n t he Pr im ary d[...]