Upload
docong
View
234
Download
1
Embed Size (px)
Citation preview
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Oracle Database 12c for SAP Oracle Multitenant
Christoph Kersten Oracle/SAP Global Technology Center Walldorf, Germany November 2016
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Safe Harbor Statement The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.
3
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Program Agenda
4
Introduction: Oracle Database for SAP Strategy
Background Information • Oracle Multitenant Architecture and Benefits • Oracle Multitenant for SAP Certification and Prerequisites
Oracle Multitenant for SAP Administration & Tool Support • SAP SWPM: Installation & Database Creation • Oracle Commands and Tools: Managing CDBs and PDBs • Oracle Commands and Tools: Standalone to PDB Migration • SAP BR*Tools: BRSPACE, BRBACKUP
1
2
3
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
ORACLE DATABASE 12C
SAP APPLICATION OPTIMIZATION SUPPORT
Oracle Database In-Memory
Information Lifecycle Management
Oracle Multitenant Data Model Optimization (Flat Cubes)
Performance Optimizations for SAP ERP
Core Data Services (Code Pushdown)
ORACLE DATABASE FOR SAP STRATEGY
Base Certification Features
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Oracle Database 12c for SAP Certification Roadmap
7
Base Certification (March 2015)
Oracle Database In-Memory (June 2015)
ACO ILM Features, HCC, Database Vault
(December 2015)
Oracle Multitenant (Early Adopters: July 2016,
Planned GA: Q1 2017)
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Oracle Multitenant Architecture
9
Separate Databases
Pluggable Databases (PDBs)
Root
Container Database (CDB)
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 10
SAP HANA Multitenant Database Containers Architecture and Terminology Comparison
System DB
Tenant DB 1 (= Container 1)
Tenant DB 2 (= Container 2)
Application 1 Application 2
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 11
Oracle Multitenant Architecture and Terminology Comparison
Container DB
Pluggable DB 1 Pluggable DB 2
Application 1 Application 2
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Oracle Multitenant Benefits
• Multiple copies of same system/database – Same data, same applications – Ex.: development or training systems
• Consolidation of different systems/databases – Different data, different applications – Same requirements (e.g. software releases, configuration parameters)
and admin tasks – In the past: MCOD (Multiple Components, One Database)
12
Candidates
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Oracle Multitenant Benefits Better Resource Utilization
13
OLTP benchmark comparison Only 3GB of memory vs. 20GB memory used for 50 databases
Multitenant architecture scaled to over 250 db’s while separate database instances maxed at 50
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
• No application changes required • Better resource utilization • Better resource management • Simplified patching
(but: no loss of flexibility)
• Simplified backup (but: no recovery restrictions)
• One Standby DB covers all Pluggable Databases (PDBs)
• PDBs can be quickly provisioned from seed
• Fast cloning of PDBs
14
Oracle Multitenant Benefits: Administration
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
• Certified for all NetWeaver-based SAP applications
• Early adopter customer shipment as of July 07, 2016
• General availability planned for Q1 2017
• Initial limitations (no RAC, no ASM, no SAP updates) will be removed before GA
16
Certification: Overview
ERP CRM
HR
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Prerequisites (as of November 2016)
• Oracle Database 12c – Release 12.1.0.2 or higher – For minimum patch level (SAP Bundle Patch) see SAP Note 2336881
• Oracle Multitenant – Oracle Multitenant license (ASFU or Full Use) – Special case: For "singletenant installations" (only one PDB in CDB)
no Multitenant license needed
17
Oracle Software
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Prerequisites (as of November 2016)
• SAP NetWeaver – SAP NetWeaver 7.40 and newer (Unicode only)
with minimum SAP Kernel 7.45 Patch 210 – For required corrections see SAP Note 2336881
• SWPM 1.0 SP18
• BR*Tools 7.40 Patch 24
18
SAP Software
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Information Resources • SAP Notes 2333995 – BR*Tools Support for Oracle Multitenant Database 2335850 – Transformation of Existing Standalone Database into Pluggable Database 2336881 – Using Oracle Multitenant with SAP NetWeaver-based Products
• not yet released for customer
19
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
SWPM: Overview
• Installation / database creation scenarios: – Creation of new CDB with one PDB ("singletenant") – Creation of a new (additional) PDB into existing CDB
• Unix/Linux platforms: only Oracle Standard user concept supported
• Installation and configuration of CDBs/PDBs only through SWPM
• Configuration of CDBs/PDBs through DBCA or Oracle Enterprise Manager not supported.
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 22
SWPM: Initial Database (CDB+PDB) Creation
• No difference (yet) between traditional and Multitenant installation: DB SID = CDB SID
• As of November 2016: ̶ no ASM ̶ no RAC
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 23
SWPM: Initial Database (CDB+PDB) Creation
• Here you indicate that you want a Multitenant DB to be created
• CDB SID and (first) PDB SID required
• CDB only (without PDB) currently not possible.
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 24
SWPM: Creation of Additional PDB(s)
• Start SWPM again
• Enter SID of existing CDB
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 25
SWPM: Creation of Additional PDB(s)
• SWPM detects existing CDB
• Select "Install additional Pluggable DB in existing Container DB"
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 26
SWPM: Creation of Additional PDB(s)
• SWPM provides list of all existing PDB SIDs
• Enter SID for additional PDB
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Modify Configuration Parameters for CDB and/or PDBs • Choices that can be made only for the CDB/system as a whole:
– Oracle Database software version, and platform specifics
• spfile, control files, password file are common for the CDB/system as a whole
• Parameter values set at PDB level using ALTER SYSTEM stored in appropriate data dictionary tables
• Check parameters modifiable at PDB level: – SQL> select name, value from v$system_parameter where ispdb_modifiable = 'TRUE' order by name;
28
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 29
Starting and Stopping Databases CD
B (C
DT)
PD2
PDBs
Root
PD3 SEED SQL> select name, open_mode from v$database;
NAME OPEN_MODE ------ ------------ CDT READ WRITE
SQL> select con_id, name, open_mode from v$pdbs;
CON_ID NAME OPEN_MODE ------ ---------- ------------ 2 PDB$SEED READ ONLY 3 PD2 READ WRITE 4 PD3 MOUNTED
PDBs are not automatically open after CDB has been opened.
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 30
Check System Files SQL> alter session set container = cdb$root; /* OR */ SQL> alter session set container = PD2;
SQL> show parameter control_files;
NAME TYPE VALUE ------------- ------ -------------------------------------------------------------------- control_files string /oracle/CDT/origlogA/cntrl/cntrlCDT.dbf, /oracle/CDT/origlogB/cntrl/ cntrlCDT.dbf, /oracle/CDT/sapdata1/cntrl/cntrlCDT.dbf
SQL> select a.group#, a.member, b.bytes from v$logfile a, v$log b where a.group# = b.group#;
GROUP# MEMBER BYTES ------ ---------------------------------- --------- 1 /oracle/CDT/origlogA/log_g11m1.dbf 209715200 1 /oracle/CDT/mirrlogA/log_g11m2.dbf 209715200 2 /oracle/CDT/origlogB/log_g12m1.dbf 209715200 2 /oracle/CDT/mirrlogB/log_g12m2.dbf 209715200 […]
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 31
Check Tablespaces and Tablespace Files (CDB) SQL> alter session set container = cdb$root;
SQL> select tablespace_name, status from dba_tablespaces;
TABLESPACE_NAME STATUS --------------- ------ SYSTEM ONLINE SYSAUX ONLINE PSAPUNDO ONLINE PSAPTEMP ONLINE
SQL> select file_name as datafile, bytes/1024/1024 as mb_size from dba_data_files;
DATAFILE MB_SIZE ------------------------------------------- ------- /oracle/CDT/sapdata1/system_1/system.data1 370 /oracle/CDT/sapdata1/system_1/sysaux.data1 340 /oracle/CDT/sapdata1/undo_1/undo.data1 1680
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 32
Check Tablespaces and Tablespace Files (PDB) SQL> alter session set container = PD2;
SQL> select tablespace_name, status from dba_tablespaces;
TABLESPACE_NAME STATUS --------------- ------ SYSTEM ONLINE SYSAUX ONLINE PSAPTEMP ONLINE PSAPSR3 ONLINE PSAPSR3750 ONLINE PSAPSR3USR ONLINE
SQL> select file_name as datafile, bytes/1024/1024 as mb_size from dba_data_files;
DATAFILE MB_SIZE ------------------------------------------------------ ------- /oracle/CDT/pd2_sapdata1/pd2_system_1/pd2_system.data1 370 /oracle/CDT/pd2_sapdata1/pd2_sysaux_1/pd2_sysaux.data1 240 /oracle/CDT/pd2_sapdata2/pd2_sr3_1/pd2_sr3.data1 11540 […]
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 33
No Global PSAPTEMP
Database Instance
ROOT Container
SYSTEM Data File
SYSAUX Data File
UNDO Data File
TEMP Temp File
Online Redo Log
PD2 Pluggable Database
SYSTEM Data File
SYSAUX Data File
SAP Data File
TEMP Temp File
PD3 Pluggable Database
SYSTEM Data File
SYSAUX Data File
SAP Data File
TEMP Temp File
Control File
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Standalone to PDB Migration
• Double check SAP Note 2335850 for details
• Prerequisites: Standalone DB and CDB must have the same – endian format – character sets and national character sets – database options installed – Oracle release and patch set – SAP Bundle Patches installed
35
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Standalone to PDB Migration • Standalone DB:
– startup read only
– execute dbms_pdb.describe ('<path>/<file_name>.xml');
• XML file describing source database: tablespaces (location), spfile parameters, patches, etc. – shutdown immediate;
• optional: Copy datafiles to target server (CDB)
• CDB: – SQL> create pluggable database <SID> using '<path>/<file_name>.xml' nocopy tempfile reuse;
36
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Standalone to PDB Migration • PDB:
– SQL> alter session set container = <PDB_SID>;
– @?/rdbms/admin/noncdb_to_pdb;
• Check output carefully: If there are any warnings, check with SAP support on possible resolutions. If no warnings are given, open the database
– SQL> alter database open read write;
37
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
SAP BR*Tools
• Operations such as – database backup with BRBACKUP – space management with BRSPACE
require compliance with the file naming conventions described above.
• For information about required users and authorizations see SAP Note 2333995
39
Prerequisites
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
SAP BR*Tools
• Local operations – Work with one PDB only – Examples: Create Tablespace, Update Statistics
• Global operations – Work with CDB and all PDBs – Example: Complete backup of Multitenant DB
• Mixed operations – Can affect one or more PDBs – Example: Start up / shut down database
40
Types of Operations
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
SAP BR*Tools
• BR*Tools are <sapsid>adm-based and involve corresponding PDB <SID>
• Working Database (PDB) – Target of all BR*Tools actions – Used for BR*Tools logging – Determined by the environment variable ORA_PDB_NAME
• Primary Database (PDB) – PDB linked to a specific <sapsid>adm OS user – Can be defined in a new init<DBSID>.sap configuration parameter:
• primary_pdb = PD1
41
Target Databases
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
SAP BR*Tools
• Effective Database – Allows administrator to work with a different DB for a short period of time – Example: Start Up, Shut Down – Determined via –pdb option of BR*Tools commands
• Active PDBs – Defined in init<DBSID>.sap:
• active_pdbs = all_pdbs | (<PDB_NAME1>[:<SAP_SID1>][,<PDB_NAME2>[:<SAP_SID2>],...])
– PDBs not mentioned here are excluded from global operations (such as complete database backup)
42
Target Databases
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Safe Harbor Statement The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.
43