Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Transcription

1 1

2 Upgrade to Oracle Database 12c 何革新

3 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

4 Upgrade to Oracle Database 12c Upgrade Overview What s new in upgrades to Oracle 12c Upgrade and Plug into CDB Upgrade to Non-CDB Plug into CDB Wrap Up 4

5 Is It Time To Upgrade? 5

6 Lifetime Support Policy today Oracle 9.2 (GA: Jul 2002) Oracle 10.1 (GA: Jan 2004) JAN 2007 JAN 2009 JUL 2010 JAN 2012 Oracle 10.2 (GA: Jul 2005) JUL 2010 JUL 2013 Oracle 11.1 (GA: Aug 2007) AUG 2012 AUG 2015 Oracle 11.2 (GA: Sep 2009) JAN 2015 JAN 2018 Oracle 12.1 (GA: Jun 2013) JUN 2018 JUN 2021 today Premier Support Waived Extended Support Extended Support Sustaining Support 6

7 Upgrade and Migration Paths exp/imp, expdp/impdp UPGRADE/MIGRATION CTAS, COPY, SQL Loader N Stay on same OS? Y SQL Apply & Transient Standby N Downtime >30min? Y Transportable Tablespaces DBUA Full Transportable Export/Import Oracle Golden Gate CLI $> catctl.pl 7

8 Upgrade to Oracle Database 12c Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle 7.3 (GA: 1996) Oracle 8.0 (GA: Oracle 8.1 (GA: 1998) Oracle 9.0 (GA: 2001) Oracle 9.2 (GA: Jul 2002) Oracle 10.1 (GA: Jan 2004) Oracle 10.2 (GA: Jul 2005) DIRECT Oracle 11.1 (GA: Aug 2007) DIRECT Oracle 11.2 (GA: Sep 2009) DIRECT Oracle 12.1 (GA: Jun 2013) Please note: This graph will apply to database upgrades only! 8

9 Upgrade to Oracle Database 12c Upgrade Overview What s new in upgrades to Oracle 12c Upgrade case study Upgrade to Non-CDB Plug into CDB Wrap Up 9

10 What's new in upgrades to Oracle 12c? New Multitenant Architecture in Oracle 12c New SQL Automation FixUp Scripts Fixing issues before and after upgrade Parallel Upgrade Some scripts are run parallel to speed up the upgrade process Full Transportable Export/Import Transport an entire database in a single operation Cross Platform Incremental Backup/Restore/Recover Reduce downtime for cross platform migration 10

11 Multitenant Database 12c New Concept! Consolidation Reduce maintenance Simplified and fast provisioning, cloning and migration Option is called Oracle Multitenant 11

12 Basic Architecture of Multitenant Multitenant container database => CDB DBA administers on the CDB level A CDB contains always a PDB$SEED and in addition zero, one, or many pluggable databases (PDBs) Applications will connect to the PDBs Up to 252 PDBs in one CDB PDB$ SEED PDB PDB PDB PDB CDB 12

13 Caution!! Many of the well known concepts will get changed Around 150 pages new documentation in the Administrator s Guide 13

14 The earth is still a sphere You don't have to use pluggable databases... yet Oracle Database 12c non-cdb works as expected But you can also use the new features and this will require changing old habits 14

15 New preupgrade script in Oracle 12c New preupgrade script preupgrd.sql loads the new preupgrade package utluppkg.sql It will be delivered with the Oracle 12c home to be run in the source database generates its output in directory: $ORACLE_BASE/cfgtoollogs/V102/preupgrade preupgrade.log has detailed information about any findings, suggestions, warnings, corrections and errors in your source database preupgrade_fixups.sql is the script you will need run in your source database it will fix some issues or direct to fixes the DBA has to implement postupgrade_fixups.sql is meant to run shortly after the upgrade and will fix open issues and it will contain directions for manual interaction as well (eg time zone change) 15

16 New Parallel Upgrade in Oracle 12c New parallel upgrade script Default feature in Oracle Database SERVER component upgrade scripts get executed in parallel, where possible Other non-dependent components are run in parallel Overall time to upgrade is reduced between 20% and 40% Parallel upgrade is driven by a PERL script: catctl.pl Database needs to be in STARTUP UPGRADE mode script1.sql script4.sql script5.sql catctl.pl script2.sql script7.sql script8.sql script3.sql script9.sql script10.sql script6.sql script11.sql script6.sql 16

17 New Parallel Upgrade in Oracle 12c Already used with selected customers for upgrade to Oracle Database Payback's Exadata V1 to X2 migration Parallel upgrade went 37% faster ORACLE SERVER Component Upgrade Serial/Default Parallel Electronic world market leader Parallel upgrade used for over 100 SAP systems 17

18 Concept Transportable Tablespaces Transportable Tablespaces feature exists since Oracle 8i Can be used cross version Version to transport to must be always equal or higher Cross platform Transportable Tablespaces got introduced in Oracle Database 10g Can be used cross version and cross platform Required tablespaces to be in read-only mode Extra work necessary for everything in SYSTEM/SYSAUX 18

19 Full Transportable Export/Import Transport an entire database in a single operation Cross version and cross platform Can include the database upgrade Combination of TTS for data tablespaces and Data Pump for administrative tablespaces (SYSTEM, SYSAUX...) Supports information from database components such as Spatial, Text, Multimedia, OLAP, etc. Full transportable export supported since Oracle Full transportable import supported since Oracle

20 Full Transportable Export/Import 1. Set data tablespaces READ ONLY and copy to destination SOURCE Database DESTINATION Database VIEWS VIEWS APP HUGO USERS SYSTEM SYSAUX UNDO TEMP CODE PRIVS 2. Data Pump APP HUGO SYSTEM SYSAUX UNDO TEMP CODE PRIVS 20

21 Full Transportable Export/Import 3 Phases 1. Pre-transport data file migration Easiest: copy datafiles after setting tablespaces READ ONLY OR: Less Downtime: apply incrementally-updated RMAN level 0 and level 1 backups 2. Transport using network import Data Pump over database link to migrate all the metadata Downtime here because tablespaces have to be read-only 3. Post-transport cleanup 21

22 Cross Platform Incremental Backup/Recover Usually the biggest pain points with TTS Downtime ranges from tablespace read-only on source to tablespace read-write on destination Duration to copy a very large amount of data Duration to convert many tablespaces cross Endianness New technique: Avoid the copy & convert phase as part of downtime RMAN has learned to convert backups cross platform Incremental backups will be used to bring source and destination into close sync Available since Oracle for Exadata only Available generally with Oracle and Oracle 12c See MOS Note: for a detailed description 22

23 Cross Platform Incremental Backup/Recover Online operation Step 1: Take level 0 incremental backup (image copy) at source DB Step 2: Convert datafiles in target platform Step 3: Take level 1 incremental backup at source DB Step 4: Convert backupset of step 3 and apply to converted datafile Repeat Step 3/4 to keep target datafiles sync with source DB Begin of downtime Step 5: Take tablespace in source DB READ ONLY Step 6: Take final level 1 incremental backup at source DB Step 7:Convert backupset of step 3 and apply to converted datafile Step 8:Start the DataPump to transport tablespaces 23

24 Combination of FTEI & CPIBR Conventional xtts Tablespaces read-only Generate scripts for nonsegmented objects Export meta information Copy datafiles 12c xtts Copy datafiles with RMAN Convert datafiles Create, copy, convert & apply incremental backups Tablespaces read-only Convert datafiles Create user Import Meta Information Execute scripts for nonsegmented objects Tablespaces read-write Down time Create, copy, convert & apply final incremental backup Do Full Transport expport/import Post-transport cleanup 24

25 Upgrade to Oracle Database 12c Upgrade Overview What s new in upgrades to Oracle 12c Upgrade and Plug into CDB Upgrade to Non-CDB Plug into CDB Wrap Up 25

26 Upgrade first, then plug in To plug in a database into a multitenant environment it has to be upgraded to Oracle Database 12c first The upgrade steps are independent from the Multitenant concept Upon upgrade completion it will be set read-only A description XML file will be gererated Then the database can be plugged in and become a pluggable database 26

27 Upgrade to Non-CDB Step 1: Pre-upgrade script Run preupgrade script preupgrd.sql in source DB Check the output and logs generates its output in directory: $ORACLE_BASE/cfgtoollogs/V102/preupgrade preupgrade.log has detailed information about any findings, suggestions, warnings, corrections and errors in your source database preupgrade_fixups.sql is the script you will need run in your source database it will fix some issues or direct to fixes the DBA has to implement postupgrade_fixups.sql is meant to run shortly after the upgrade and will fix open issues and it will contain directions for manual interaction as well (eg time zone change) 27

28 Upgrade to Non-CDB Step 2: Pre-upgrade fix-up Run preupgrade_fixups.sql in source DB Fix up any other issues 28

29 Upgrade to Non-CDB Step 3: Parallel upgrade scripts Shutdown source DB and startup upgrade in DB12c environment. Start the upgrade on the Shell with catctl.pl in parallel: catctl.pl is the PERL driver Will execute the upgrade scripts in parallel where possible Executes catuppst.sql and catbundle.sql as well -n y determines the parallel degree Maximum of 8 parallel threads 29

30 Upgrade to Non-CDB Step 3: Parallel upgrade scripts Monitoring while catctl.pl is running: 30

31 Upgrade to Non-CDB Step 4: Post-upgrade fix-up script Run post upgrade fix up script. 31

32 Upgrade to Oracle Database 12c Upgrade Overview What s new in upgrades to Oracle 12c Upgrade and Plug into CDB Upgrade to Non-CDB Plug into CDB Wrap Up 32

33 Plug into CDB Step 5: Create and empty CDB Two options: DBCA Highly recommended Command line CREATE DATABASE Not recommend as all options will have to be created CREATE DATABASE cdb12 [...] ENABLE PLUGGABLE DATABASE SEED FILE_NAME_CONVERT=('/oradata/cdb12/','/oradata/pdbseed/') SYSTEM DATAFILES SIZE 125M AUTOEXTEND ON NEXT 10M MAXSIZE [ ] 33

34 Plug into CDB Step 6: Put non-cdb database in unplug mode Change database to read-only mode Create XML file XML Oracle V102 PDB$SEED CDB$ROOT 34

35 Plug into CDB Step 7: Plug the non-cdb database into CDB Stop non-cdb database and plug it into the CDB TEMPFILE REUSE; XML Oracle V102 PDB$SEED Oracle PDB1 CDB$ROOT 35

36 Plug into CDB Step 8: Migrate the non-cdb to PDB Define TNS alias and connect to the PDB via TNS: sqlplus as sysdba" Sanity with noncdb_to_pdb.sql Restart PDB as the last step PDB$SEED Oracle PDB1 CDB$ROOT 36

37 Upgrade to Oracle Database 12c Upgrade Overview What s new in upgrades to Oracle 12c Upgrade and Plug into CDB Upgrade to Non-CDB Plug into CDB Wrap Up 37

38 Wrap Up Upgrade to Oracle Database 12c Easier and automated Faster as it is parallel Migration can be done cross operating systems now a lot easier with Full Transportable Export/Import and Cross Platform Incremental backup/recover. 38

39 Upgrade Companion Note: Upgrade Companion 12c (coming soon) Note: Upgrade Companion

40 Upgrade OTN Page

41 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. 41

42 42

43 43