| |
|
|
|
|
|
|
|
|
1. |
Record Nr. |
UNINA9910450159103321 |
|
|
Titolo |
SAP on DB2 Universal Database for OS/390 and z/OS [[electronic resource] ] : Multiple Components in One Database (MCOD) / / Florence Dubois ... [et al.] |
|
|
|
|
|
|
|
Pubbl/distr/stampa |
|
|
White Plains, N.Y., : IBM, c2003 |
|
|
|
|
|
|
|
Edizione |
[1st ed.] |
|
|
|
|
|
Descrizione fisica |
|
|
|
|
|
|
Collana |
|
|
|
|
|
|
Disciplina |
|
|
|
|
|
|
Soggetti |
|
IBM computers - Programming |
Business - Computer programs |
Computer systems - Evaluation |
Electronic books. |
|
|
|
|
|
|
|
|
Lingua di pubblicazione |
|
|
|
|
|
|
Formato |
Materiale a stampa |
|
|
|
|
|
Livello bibliografico |
Monografia |
|
|
|
|
|
Note generali |
|
"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." |
"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." |
|
|
|
|
|
|
|
|
Nota di bibliografia |
|
Includes bibliographical references and index." |
|
|
|
|
|
|
Sommario/riassunto |
|
The 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. |
|
|
|
|
|
| |