LEADER 03521nam  2200589Ia 450 
001 9910450159103321
005 20200520144314.0
035   $a(CKB)1000000000023255
035   $a(SSID)ssj0000943209
035   $a(PQKBManifestationID)11593667
035   $a(PQKBTitleCode)TC0000943209
035   $a(PQKBWorkID)10975318
035   $a(PQKB)10264899
035   $a(MiAaPQ)EBC3306701
035   $a(CaSebORM)0738429007
035   $a(Au-PeEL)EBL3306701
035   $a(CaPaEBR)ebr10112788
035   $a(OCoLC)80245797
035   $a(EXLCZ)991000000000023255
100   $a20041111d2003      uy             0
101 0 $aeng
135   $aurcn|||||||||
181   $ctxt
182   $cc
183   $acr
200 00$aSAP on DB2 Universal Database for OS/390 and z/OS$b[electronic resource] $eMultiple Components in One Database (MCOD) /$fFlorence Dubois ... [et al.]
205   $a1st ed.
210   $aWhite Plains, N.Y. $cIBM$dc2003
215   $axvi, 279 p. $cill
225 1 $aRedbooks
300   $a"This edition applies to SAP Basis Release 4.6C, 4.6D, 6.10, and 6.20, as well as all SAP products based on these SAP Basis Releases, for use with IBM DB2 Universal Database for OS/390 and z/OS."
300   $a"Hands-on scenarios to merge SAP components into an MCOD landscape. How to clone one SAP component using the Control Center. Recovery considerations in an MCOD landscape."
311   $a0-7384-2900-7 
320   $aIncludes bibliographical references and index."
330   $aThe Multiple Components in One Database (MCOD) feature of SAP enables a reduction in the number of DB2 systems that need to be installed and maintained. This significantly simplifies overall database administration and is considered one of the major DB2 competitive advantages. This IBM Redbooks publication will help systems administrators, database administrators, managers, and operation staff to plan, implement, and administer an SAP MCOD landscape with DB2 Universal Database (UDB) for OS/390 and z/OS as the database management system. We describe how to merge existing systems into a single DB2 subsystem. Two different methods are developed, each of them addressing different needs. For small-to-medium SAP systems where high availability is not a requirement, we explain how to use SAP tools. For large systems, where the down time needed by SAP standard procedures is not acceptable, we document a technique to merge SAP components without moving the data. We also provide a cloning procedure using the Control Center. We show how to clone one component out of an MCOD landscape. We address the backup and recovery implications in an MCOD environment, to help database administrators plan accordingly. We also describe how to set up and use the Computer Center Management System (CCMS) in an MCOD landscape. Please note that the additional material referenced in the text is not available from IBM.
410  0$aIBM redbooks.
606   $aIBM computers$xProgramming
606   $aBusiness$xComputer programs
606   $aComputer systems$xEvaluation
608   $aElectronic books.
615  0$aIBM computers$xProgramming.
615  0$aBusiness$xComputer programs.
615  0$aComputer systems$xEvaluation.
676   $a650/.0285/53769
702   $aDubois$b Florence$4aut
801  0$bMiAaPQ
801  1$bMiAaPQ
801  2$bMiAaPQ
906   $aBOOK
912   $a9910450159103321
996   $aSAP on DB2 Universal Database for OS$91985226
997   $aUNINA