下载文档原格式
oracle12c创建实例Oracle12c是一款功能强大的数据库管理系统，它在企业级应用中被广泛使用。
要使用Oracle12c，我们首先需要创建一个实例。
本文将详细介绍如何在Oracle12c中创建一个实例。
步骤一：安装Oracle12c在创建实例之前，我们需要先安装Oracle12c数据库软件。
可以从Oracle官网上下载Oracle12c的安装包，并按照安装向导的指示进行安装。
在安装过程中，需要选择安装类型，通常选择“安装数据库软件和创建数据库”。
步骤二：打开Oracle12c配置助手安装完成后，可以通过点击开始菜单中的“Oracle Database 12c”打开Oracle12c配置助手。
在配置助手中，我们可以进行各种数据库相关操作，包括创建实例。
步骤三：创建实例在Oracle12c配置助手中，选择“创建和配置数据库”选项，并点击“下一步”按钮。
在接下来的界面中，选择“创建数据库”选项，并点击“下一步”。
在“数据库识别”界面中，我们需要填写相关信息。
首先，填写“全局数据库名”。
该名字是数据库在整个网络中的唯一标识，通常以字母开头，由字母、数字和下划线组成。
然后，填写“管理密码”，这是数据库管理员账户的密码，需要确保密码的复杂性和安全性。
此外，还需要填写“管理员账户”的密码。
在“数据库文件位置”界面中，设置数据库文件的存放路径。
我们可以选择默认路径，也可以自定义路径。
建议将数据库文件存放在独立的磁盘上，以提高性能。
在“初始化参数”界面中，可以对一些数据库参数进行调优。
如果不确定具体的参数设置，可以选择使用默认值。
随后，点击“下一步”。
在“模板”界面中，选择“创建一个数据库模板”。
然后，选择适合的模板，可以根据自己的需求进行选择。
点击“完成”。
步骤四：等待实例创建完成完成以上步骤后，系统将开始创建数据库实例。
这个过程可能需要一些时间，请耐心等待。
创建完成后，可以在Oracle12c配置助手中查看数据库实例的状态。
oracle12c操作手册摘要：I.简介- Oracle 12c 简介- 安装Oracle 12c 的准备工作II.安装Oracle 12c- 安装环境要求- 解压缩文件- 运行安装向导- 安装选项- 完成安装III.Oracle 12c 数据库管理- 数据库创建与管理- 表空间管理- 数据表管理- 用户与权限管理IV.Oracle 12c 数据库查询与维护- SQL 查询语言- 数据备份与恢复- 数据库性能优化- 常见问题及解决方案V.总结- Oracle 12c 的优点与不足- 对Oracle 12c 的展望正文：I.简介Oracle 12c 是Oracle 公司于2013 年发布的一款关系型数据库管理系统，它具有高性能、高可靠性、高安全性等特点，被广泛应用于企业级数据库领域。
本文将为您介绍Oracle 12c 的安装与使用方法。
II.安装Oracle 12c在安装Oracle 12c 之前，您需要确保您的系统满足以下条件：- 操作系统：Windows 7 以上版本- 内存：8GB 以上- 硬盘：20GB 以上准备好以上条件后，您可以下载Oracle 12c 安装包，并解压缩到任意目录。
然后双击运行解压缩后的安装向导程序，按照提示进行操作。
在安装过程中，您需要选择安装选项，这里建议选择“桌面类”安装方式，以满足一般用户的需求。
III.Oracle 12c 数据库管理在成功安装Oracle 12c 后，您可以开始创建和管理数据库。
首先，通过SQL*Plus 或其他工具连接到数据库，然后使用CREATE DATABASE 语句创建数据库。
接下来，您可以创建表空间、数据表，并为用户分配权限。
IV.Oracle 12c 数据库查询与维护Oracle 12c 提供了强大的查询与维护功能。
您可以使用SQL 语言对数据库进行查询、插入、更新和删除等操作。
此外，Oracle 12c 还支持数据备份与恢复功能，以保障数据的安全性。
oracle12c benchmark results -回复题目：Oracle 12c基准测试结果与分析：提升数据库性能的关键引言：随着大数据和云计算时代的到来，数据库系统的性能和可扩展性变得越来越重要。
针对这一需求，Oracle 12c作为业内领先的关系数据库管理系统之一，通过进行基准测试来评估其性能和可靠性。
本文将详细分析一份Oracle 12c基准测试结果，并探讨关键因素对于提升数据库性能的作用。
一、基准测试简介1. 基准测试的定义：基准测试是通过模拟真实环境下的工作负载和数据量，在数据库系统中进行一系列测试和测量，以便评估其性能和可靠性指标。
2. 基准测试的意义：基准测试可以帮助数据库管理员（DBA）了解数据库系统的瓶颈以及优化需求，并为决策者提供参考，以支持系统升级和性能优化的决策。
二、Oracle 12c基准测试结果分析1. 性能指标分析：- 响应时间：基准测试中最常用的性能指标之一，表示数据库系统响应用户操作的速度。
- 吞吐量：表示数据库系统在单位时间内处理的事务或查询的数量，也是衡量性能的重要指标。
- 并发性能：指数据库系统在同时处理多个并发用户操作时的性能表现。
2. 测试用例和工作负载分析：- 测试用例：基准测试中通常会涵盖常见的数据库操作，如插入、查询、更新和删除等，以模拟真实环境下的工作场景。
- 工作负载：基准测试中采用的工作负载可以是事务型的（以完成某个业务功能为目标）或者是查询型的（以执行某个复杂查询为目标）。
3. 关键因素分析：- 硬件配置：硬件资源的优化对数据库系统的性能至关重要，如CPU、内存、硬盘及网络等。
合理配置硬件资源可以显著提升数据库系统的性能。
- 数据库参数调优：Oracle 12c提供了许多参数用于调优数据库系统的性能和稳定性，包括缓冲区大小、日志写入策略等。
合理设置这些参数可以最大程度地提升数据库性能。
- 索引和分区：索引和分区技术可以加速数据库的查询操作，降低数据检索的成本。
oracle 12c 参数Oracle 12c参数Oracle是一款非常强大的数据库管理软件，可以为企业提供高效稳定的数据管理支持。
Oracle数据库的运行需要众多参数的配合，针对每个参数的设置可以使得Oracle 的运行更加稳定、高效。
在Oracle 12c中，有大量的数据库参数需要进行设置，本文将介绍一些关键的参数设置方法。
1、SGA参数设置SGA是Oracle中非常重要的内存区域，被用于缓存数据和元数据，减少磁盘I/O。
通过调整SGA大小可以实现提高访问性能的目的。
可以使用下面的命令来查询SGA参数的值：SQL> show parameter sga可以通过编辑初始化文件ORACLE_HOME/dbs/initoradb.ora或使用ALTER SYSTEM语句在SGA参数或组件级别上设置SGA参数。
设置SGA最重要的是备份与恢复，为此可以将SGA的大小保存在PFILE 或SPFILE中，以便在备份与还原过程中使用。
SGA参数的设置包括：shared_pool_size：由SQL语句共享池的大小决定。
在高流量情况下，共享池的尺寸应适当增加以提高查询的效率。
db_cache_size：用于缓存数据块和索引块的缓冲池大小。
它决定了数据块的内存使用量。
large_pool_size：在执行如连接服务器，排序操作等任务时，处理多个连接的顶层堆栈使用的内存。
java_pool_size：用于Java等对象的内存池大小。
2、PGA参数设置Oracle数据库中的PGA（Process Global Area）是实现Oracle“进程内内存”概念的关键，它由每个进程的私有内存组成。
PGA存储了一个进程的全局变量信息，设计合理的PGA大小，可以使得Oracle各个进程的访问效率更高。
可以使用下面的命令来查询PGA参数的值：SQL> show parameter pga可以通过编辑初始化文件ORACLE_HOME/dbs/initoradb.ora或者使用ALTER SESSION 语句在针对性的设置PGA参数。
Oracle Database 12c RAC for AIX 7.1一、安装说明服务器：IBM Power 750（两台）共享存储：华为DS6800OS：AIX 7.1.3ORACLE：12.1.0.1.0网络（hosts文件解析）：二、环境检查查看内存：# lsattr-E -l sys0 -a realmem系统架构：# getconf HARDWARE_BITMODE（或# bootinfo -K或# getconf KERNAL_BITMODE//输出64才可以查看Swap空间：# lsps -a，使用chps -s增加目录大小：# df -g（默认的不太大，最好扩展一下smitty chfs）检查软件包：# lslpp -l bos.adt.base bos.adt.lib bos.adt.libm bos.perf.libperfstatbos.perf.perfstat bos.perf.proctools rsct.basic.rte pat.clients.rte xlC.aix61.rte.11.1.0.4 xlC.rte.11.1.0.4（最后两个有版本要求）相关补丁：# instfix -i -k "IV16737IV21116 IV21235 IV28925 IV34869 IV35057 IV39136 IV41415 IV45072 IV45073"由于系统版本7.1.3，安装系统时已包括相关补丁集，安装过程中会有相关WARNING，忽略即可安装12c必须的其它软件包：ssh——建立信任关系、安装过程scp都需要的sshbash——如没有此包，安装GRID时会报INS-06001 Failed toperform operation due to internal driver errorunzip——AIX默认不支持.zip解压1.安装ssh相关包，一般系统盘中就有，smitty installp或mkdir dvdmount -v cdrfs -o ro /dev/cd0 /mnt/dvdcd /mnt/dvd/usr/sys/inst.immagesinstallp -ac -Y -d . openssh.base openssl.base openssl.man.en_US openssh..man.en_US①在/etc/security/login.cfg文件中，将usw下auth_type的默认值std_auth改为pam_auth②/etc/pam.conf中添加sshd auth required pam_aixsshd account required pam_aixsshd password required pam_aixsshd session required pam_aix③将/etc/ssh/sshd_config中#LoginGraceTime 2m改为 LoginGraceTime 0④重启sshstopsrc -s sshdstartsrc-s sshd2.bash需要网上下载（ftp:///gnu/bash/ 据说版本没有限制）后，上传到服务器，使用root用户执行：# rpm -ivh bash-4.2-1.aix6.ppc.rpm在/etc/security/login.cfg的usw:下添加/usr/bin/bash（此操作不知道是不是有效）3. 同样下载unzip_aix.Z文件，上传到服务器，解压uncompress unzip_aix（这里使用刻盘上传时会把.Z改为.z，解压前要改回来，否则报错）chmod 751 unzip将文件cp到/usr/bin# cp -v /u01/unzip_aix /usr/bin/unzip三、系统参数查看异步io：# ioo-a |grep aio_maxreqs（此版本为131070，不用修改）虚拟内存参数：# vmo –aF 与下面值不一致时，修改为下面值（调整后重启生效）：vmo -p -o minperm%=3vmo -p -o maxperm%=90vmo -p -omaxclient%=90vmo -p -olru_file_repage=0vmo -p -ostrict_maxclient=1vmo -p -o strict_maxperm=0系统分配的块大小（建议值128-1024）：chdev-l sys0 -a ncargs=1024用户允许的最大进程数：chdev–l sys0 –a maxuproc=16384网络参数：no -a | more查看兼容性：lsattr –E –l sys0 –a pre520tune1.如返回结果是pre520tuneenable Pre-520 tuning compatibity mode True，在/etc/添加如下：if [ -f /usr/sbin/no ] ; then/usr/sbin/no -o udp_sendspace=65536/usr/sbin/no -o udp_recvspace=655360/usr/sbin/no -o tcp_sendspace=65536/usr/sbin/no -o tcp_recvspace=65536/usr/sbin/no -o rfc1323=1/usr/sbin/no -o sb_max=4194304/usr/sbin/no -o ipqmaxlen=512fi2.如返回结果是pre520tunedisable Pre-520 tuning compatibity mode True，执行下面命令no -r -o ipqmaxlen=512 //此参数要求重启系统生效no -p -o rfc1323=1no -p -o sb_max=4194304no -p -o tcp_recvspace=65536no -p -o tcp_sendspace=65536no -p -o udp_recvspace=655360no -p -o udp_sendspace=65536其它网络参数：no -p -o tcp_ephemeral_low=9000-o tcp_ephemeral_high=65535no -p -o udp_ephemeral_low=9000-o udp_ephemeral_high=65535关闭NTPmv -v /etc/ntp.conf /etc/ntp.conf.bakstopsrc -s xntpd修改用户限制，将/etc/security/limits文件中部分内容如下：default:fsize = -1core = -1cpu = -1data = -1rss = -1stack = -1nofiles = -1四、添加IP解析、创建用户等信息在/etc/hosts添加解析地址（使用hosts解析IP）192.168.10.1 nc180p001192.168.10.2 nc180p002192.168.10.3 nc180p001-vip192.168.10.4 nc180p002-vip10.10.10.1 nc180p001-pri10.10.10.2 nc180p002-pri192.168.10.5 racscan创建组mkgroup -'A' id='1000' adms='root' oinstallmkgroup -'A' id=' 1001' adms='root' dbamkgroup -'A' id='1002' adms='root' opermkgroup -'A' id='1003' adms='root' asmadminmkgroup -'A' id='1004' adms='root' asmopermkgroup -'A' id='1005' adms='root' asmdba创建用户mkuser id='1000' pgrp='oinstall'groups='dba,asmdba,oper,asmadmin,asmdba’home='/home/grid' –s /usr/bin/bash gridmkuser id='1001' pgrp='oinstall'groups='dba,oper,asmadmin,asmdba,asmoper' home='/home/oracle' –s /usr/bin/bash oracle修改密码echo oracle | passwd --stdin oracleecho oracle | passwd --stdin grid添加用户能力lsuser -a capabilities gridchusercapabilities=CAP_NUMA_ATTACH,CAP_BYPASS_RAC_VMM,CAP_PROPAGATE grid lsuser -a capabilities oraclechusercapabilities=CAP_NUMA_ATTACH,CAP_BYPASS_RAC_VMM,CAP_PROPAGATE oracle信任关系（可选）1.生成密钥对（两个节点，两个用户oracle,grid）ssh-keygen -t rsassh-keygen -t dsa2.配置信任关系（一个节点）cat .ssh/id_rsa.pub>>.ssh/authorized_keyscat .ssh/id_dsa.pub>>.ssh/authorized_keysssh nc180p002 cat .ssh/id_rsa.pub>>.ssh/authorized_keysssh nc180p002 cat .ssh/id_dsa.pub>>.ssh/authorized_keysscp .ssh/authorized_keysnc180p002:~/.ssh3.验证信任关系（两个节点，两个用户）ssh nc180p002 datessh nc180p002-pri datessh nc180p001 datessh nc180p001-pri date创建目录设置权限mkdir -p /u01/app/11.2.0/gridmkdir -p /u01/app/oraclechown -R grid:oinstall /u01chown oracle:oinstall /u01/app/oraclechmod -R 775 /u01/共享存储生成PV：chdev -l hdiskn -a pv=yes设置共享文件系统的权限供grid和oracle用户使用1.改变用于数据库存储的PV的属主chown grid:asmadmin /dev/rhdisk[2-12]2.改变用于数据库存储的PV的权限chmod 660 /dev/rhdisk[2-12]3.检测和设置保持策略lsattr -E -l hdisk[2-12] | grep reserve_设置保持策略:chdev -l hdisk[2-12] -areserve_policy=no_reserve (如果是reserve_policy)chdev -l hdisk[2-12] -areserve_lock=no (如果是reserve_lock)添加环境变量节点1上Oracle用户，在~/.bash_profile文件umask 022export EDITOR=viexport ORACLE_BASE=/u01/app/oracleexport ORACLE_HOME=$ORACLE_BASE/product/11.2.0/db_1export ORACLE_SID=ora11g1exportPATH=.:${PATH}:$ORACLE_HOME/bin:/bin:/usr/bin:/usr/sbin:/usr/local/bin exportLD_LIBRARY_PATH=$ORACLE_HOME/lib:${LD_LIBRARY_PATH}export NLS_LANG=AMERICAN_AMERICA.UTF8 #此变量最好安装完再加上节点2上Oracle用户，在~/. bash_profile文件添加：umask 022export EDITOR=viexport ORACLE_BASE=/u01/app/oracleexport ORACLE_HOME=$ORACLE_BASE/product/11.2.0/db_1export ORACLE_SID=ora11g2export PATH=.:${PATH}:$ORACLE_HOME/bin:/bin:/usr/bin:/usr/sbin:/usr/local/bin exportLD_LIBRARY_PATH=$ORACLE_HOME/lib:${LD_LIBRARY_PATH}export NLS_LANG=AMERICAN_AMERICA.UTF8#此变量最好安装完再加上节点1上Grid用户，在~/. bash_profile文件添加：umask 022export EDITOR=viexport ORACLE_BASE=/u01/app/gridexport GRID_HOME=/u01/app/11.2.0/gridexport ORACLE_SID=+ASM1exportPATH=.:${PATH}:$ORACLE_HOME/bin:/usr/bin:/bin::/usr/local/binexportLD_LIBRARY_PATH=$ORACLE_HOME/lib:${LD_LIBRARY_PATH}节点2上Grid用户，在~/. bash_profile文件添加umask 022export EDITOR=viexport ORACLE_BASE=/u01/app/gridexport GRID_HOME=/u01/app/11.2.0/gridexport ORACLE_SID=+ASM2export PATH=.:${PATH}:$ORACLE_HOME/bin:/usr/bin:/bin:/usr/local/binexportLD_LIBRARY_PATH=$ORACLE_HOME/lib:${LD_LIBRARY_PATH}五、安装GI1.解压grid两个安装包cd /u01unzip aix.ppc64_12c_grid_1of2.zipunzip aix.ppc64_12c_grid_2of2.zip2.解压目录属主改为grid用户cd /u01chmod -R grid:oinstsall grid/3.进入解压目录执行使用root用户rootpre.sh，将此文件传到第二个节点同样使用root 执行cd /u01/grid./rootpre.sh4.grid用户进入解压目录验证su - gridcd /u01/grid./runcluvfy.shstage -pre crsinst -n nc180p001,nc180p002 -fixup -verbose5.开始安装：$ ./runInstaller输入Y，回车继续进入图形界面。
Trouble-free Upgrade to Oracle Database 12c with Real Application TestingKurt EngeleiterPrincipal Product ManagerSafe Harbor StatementThe 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.Program Agenda▪Oracle Database Upgrades▪Validating Upgrades with Real Application Testing ▪Two Upgrade Use Cases:‒Consolidation into Multi-Tenant‒Database In-Memory▪Customer StoriesOracle Database UpgradesWhy Upgrade to Database 12c? •Database Consolidation to Multitenant–Ease management–Standardize on most recent version–Simplify future upgrades•Database In-Memory–Real time analytics•Migration to a new environment–Hardware / Software•Take advantage of other new database featuresValidating Upgradeswith Real Application TestingDatabase Upgrade Testing - Why•Every customer has a unique environment–Hardware configuration–Application use of the database•Upgrade testing in your environment provides validation ofperformance and correctness–Validates your unique hardware and software stack–Assures most important databases / applications perform to meet SLAsReal Application Testing provides real-workload testing solution that is comprehensive & easy-to-use for system change assessmentResponse Time TestingLoadTestingComprehensiveTestingSolutionSQL Performance Analyzer DatabaseReplayRealApplicationTestingReal Application Testing – Two Complementary SolutionsSQL Performance Analyzer •Helps users predict the impact of system changes on SQL workload response time•Low overhead capture of SQL workload to SQL Tuning Set (STS) on production system•Build different SQL trials (experiments) of SQL statements performance by test execution •Analyzes performance differences•Offers fine-grained performance analysis on individual SQL•Integrated with STS, SQL Plan Baselines, & SQL Tuning Advisor to form an end-to-end solutionAnalysis ReportCompareSQL PerformanceSQL plans + stats SQL plans + stats Pre-change Trial Post-change TrialSQL WorkloadSTSSPA Report1 2 345Database Replay •Database load and performance testing with real production workloads–Production workload characteristicssuch as timing, transactiondependency, think time, etc., fullymaintained•Identify and remediate application scalability and concurrency problems in multitenant and non-CDB databases •Allows scheduling, scaleup, subsetting, of multiple workloads•Concurrent database replay available for 11.2.0.2 and above, MOS Note: 1453789.1Database Upgrade Testing Best Practices•Always use SPA first–Unit test before load test•Capture and replay a manageable amount of time – e.g. 1 to 2 hours •Key metric for Database Replay is DB Time•Capture SQL Tuning Sets during capture and replay for additional validation•Use Enterprise Manager 12c with the latest DB Plugin–Implements best practices–Wizards guide you through the capture and replay process–Long term repository for storing and analyzing test results*Check MOS Note 560977.1 for recommended patch bundlesDB Time Definition•Total time in database calls by foreground sessions •Includes–CPU time –IO time–Active wait (non-idle wait) time•Basic unit for Oracle performance analysisCPUI/O WaitDB TimeDatabase Consolidation Into MultitenantDatabase Workload Compatibility: Challenges•Applications have different workload profiles –CPU–Memory –Storage –Network •Will my Multitenant database handle peak workloads and co-exist? •Is there enough headroom? •How do I minimize risk? •Use Real Application Testing to assess Multitenantworkload compatibility and conduct capacity planning ✓✗✓ ✓Using SPA in Multitenant EnvironmentCRM DW ERP HCMValidate SQL performance forconsolidated database:•Capture SQL workload foreach database in STS•Execute SPA for all workloadstogether in consolidatedenvironment•Identify errors & SQLregressions•Review response time•RemediateERP STSCRM STSHCM STSDWSTSSALESHRERPCRMMultitenant Load Testing: Use Consolidated DB Replay•Capture workload on different databases that needs to co-exists concurrently •Works for schema consolidation and Pluggable Databases•Use scaleup, subsetting, scheduling of multiple workloads•Use for schema and CDB consolidation •Identify and remediate inter-application scalability and concurrency problems •Available for 11.2.0.2 and above, MOS Note: 1453789.1TestCapture Process ReplayAnalysis & ReportingProductionReplay DriverClientsStorage StorageMultitenant Load Testing: Use Consolidated Database ReplayWindows DB 10.2 Capture 1Capture 2Capture 3Production SystemsCRM- DB1 HCM-DB2 DW-DB3DirectoriesAIXDB 9.2.0.8 HP-UX DB 11gMay: Month-end Close June15: Daily PeakJune 18: DW - ETL…CDB – DB12cReplay on CDBCapture 1Capture 2Capture 3Test SystemConsolidated Replay DirectoryDirectoriesHow to Test For Consolidation•If consolidating a few databases–Use SPA–Use Consolidated Replay•If consolidating a large number of databases–Identify databases with similar workload profiles–Categorize them into small, medium and large–Scale up each category with workload scheduling and Consolidated ReplayUse Case Example•Move to new platform and consolidate to multitenant databaseCapture SQL Tuning Sets on each databaseCapture Workload on each database with Database ReplayUpgrade Database to12cConfigure PDBsRun SPA TestRun Database ReplayTarget1 Node, 4 CPU, 16 GB MemoryProduction2 Nodes with 2 CPUs, 8 GB MemoryCapture Production WorkloadDatabase 1 Database 2•Capture SQL for each database into SQL Tuning Sets for SPA test •Capture workloads for Database ReplayOn Test System•Install Database 12c with Multitenant configuration•Restore production backups into individual PDBs and run upgrade scripts•Run SPA–Convert captured production STS into trial 1–Execute SPA trial 2 on each PDB–Evaluate results–Remediate any regressions before database replayConsolidated Database SPA - Execution Plans Unchanged•For consolidation into multitenant,most SQL should have unchangedexecution plan•For OLTP workload- ‘Buffer Gets’ isbest metric•Most SQL also have unchangedperformanceTest System – Consolidated Replay •Execute Consolidated Replay on test system–Remap captured TNS connections to individuals PDBs –Run Consolidated Replay–Evaluate resultsConsolidated Database Replay Result•Replay ‘user calls’ identical tocapture – same amount ofdatabase work was done•DB Time slightly reduced•Conclusion: Upgraded andconsolidated databaseperformance matches sourceStress Test with Workload Scheduling•Consolidated Database Replay also includes workload scheduling •Workload peaks can be aligned to maximize stress on replay systemUpgrading to Database In-MemoryOracle Database In-MemoryBoth row and column in-memory formatsSimultaneously active and transactionally consistentensuring access to freshest dataEliminates manual tuning and expensive analytic indexesUnique Dual-Format ArchitectureColumn FormatMemoryRow Format MemoryAnalyticsOLTPSales Sales Up-to-date analyticsOptimizing Transaction and Query Performance Row Format Databases versus Column Format DatabasesRow ▪Transactions run faster on row format –Insert or query a sales order–Fast processing few rows, many columnsColumn▪Analytics run faster on column format–Report on sales totals by state–Fast accessing few columns, many rows ORDERSALESSALESSTATEOracle 12c: Stores Data in Both Formats SimultaneouslySimple Implementation1.Upgrade to database 12.1.0.2 (or higher)2.Configure Memory Capacity‒inmemory_size = XXX GB3.Configure tables or partitions to be in memory ‒alter table | partition … inmemory;4.Drop analytic indexes to speed up OLTPUse Case Example•Upgrade to database 12.1.0.2 and Database In-MemoryRun In-MemoryAdvisorCapture SQLTuning SetCapture Workload withDatabase ReplayUpgrade Database to12cConfigureDatabase In-Memory UsingAdvisor OutputRun SPA TestRunDatabaseReplayProduction TestUpgrade and Testing Steps•Run Database In-Memory Advisor in existing database 11.2 environment•Capture SQL Tuning Set•Capture workload with Database Replay•In test environment–Upgrade database and implement Database In-Memory Advisor recommendations–Run SPA trial–Run Database Replay–Evaluate resultsRun Oracle Database In-Memory Advisor•New In-Memory Advisor •Analyzes existing DB workloadvia AWR & ASH repositories•Provides list of objects that would benefit most from being populated into IM column store•Works on database versions 11.2 and aboveObject TypeObjectEstimated In-Memory Size EstimatedAnalyticPerformance Improve mentTable SALES.ORDERS 2.19 GB 9.3X TableSALES.LINEITEM1.03 GB5.2XPartition SALES.PRODUCTS.201404 415 MB 4.3X Sub-partitionSALES.PRODUCTS.20140330200 MB2.7XCapture Production Workload•Capture SQL into a SQL Tuning Set •Capture workload for Database ReplayConfigure In-Memory on Test System•Restore production database•Upgrade to database 12.1.02 or higher•Set init.ora parameter inmemory_size to size In-Memory column store•Restart database•Execute SQL script from In-Memory Advisor to configure objects In-MemoryValidate In-Memory ConfigurationEnterprise Manger 12c In-Memory Central Object map – displaysrelative sizes of objectsIn-MemoryObject Table – Listsdetails of segmentsloaded In-MemorySPA – Look for Expected Plan Changes•Convert production STS to trial 1•Execute trial SPA trial 2•Produce comparison report•Best metric for analytic queryworkload is ‘Elapsed Time’•Analytic SQL have changedexecution plan with plan line‘Table Access In Memory Full’•SQL are benefitting from In-MemoryIdentify Plan Change Improvements Real Time SQL MonitoringExecute Database Replay•Validate concurrency and loadimprovement for consolidatedworkload•Database Replay trial results:•User calls identical – same workloadwas executed•DB Time substantially reduced•SuccessDatabase In-Memory DB Time ImprovementDatabase 11.2.0.4 Database 12.1.0.2 + In-MemoryCustomer Case StudiesSumitomo Heavy Industries,Ltd. Database Upgrade ProjectUsing RAT & GG VeridataCustomer ProfileCompany Name: Sumitomo Heavy Industries, Ltd.Head Office: ThinkPark Tower, 1-1 Osaki 2-chome, Shinagawa-ku, Tokyo 141-6025, JapanFounded: November 20, 1888Incorporated: November 1, 1934Capital: JPY 30,871,650,000 (as of March 31, 2014) Employees: Consolidated: 17,941 (as of March 31, 2014)Annual Revenue: Consolidated: JPY 615,270,000,000(for the 2013 Fiscal Year)Challenge & SolutionDatabase Upgrade 9i /10g -> 11gR2Solution•Perform application test with completely the same workload using Oracle Real Application Testing •Automate the Performance management using Diagnostics Pack & Tuning Pack•Guarantee data consistency after testing on new environment using Oracle GoldenGate Veridata •Use Oracle GoldenGate for minimizing downtime and fallback plan (under proposing)Challenge •Aim to reduce costs to around $2.5 M to 30-50% •Upgrading in parallel in a short period of time about 30DB •The data migration in a short period of time large-scale DB and Mission-Critical DB environment, to minimize business downtime •Standardizing method for migrating and upgrading multiple databases efficiently •Performing and automating application test by DBA for minimize costSolution ArchitectureArchitecture•1st step: Measure the SQL Elapsed timeCheck the workload consistency by using Veridata•2nd step: Check whether the new database has been created successfully by using Veridata•3rd step: Compare the whole throughput and workload between the production and the new production by using RATPerformanceTest Performance and Consistency TestProduction (9i) Test (9i)Test (11g)Veridata Server New Production(11g)1st Step3rd StepDatabaseConfiguration Test2nd StepVeridata ServerSumitomo Heavy Industries, Ltd.30DBs Upgrade, reduce the verification Cost to take advantage of support toolsCustomer ProfileName： Sumitomo Heavy Industires, Ltd.（http://www.shi.co.jp/english/）Location： Tokyo (Japan)Industry： manufacturing IndustryEmployees： 17,961Oracle Products•Oracle Real Application Testing (RAT)•Oracle Diagnostics Pack /Oracle Tuning Pack (Diag/Tuning) •Oracle GoldenGate Veridata(Veridata)•Oracle GoldenGate (GG) CUSTOMER PERSPECTIVE“I heard that Other Oracle Customer has efficiently implementedDB upgrade, to take advantage of tools(RAT, GG etc).Therefore ,We accept the Challenge!!”Engineer / Takayuki Okoshi INFORMATION SYSTEMS DEVELOPMENT DEPT.Sumitomo Heavy Industries Business Associates, Ltd.CHALLENGES/OPPORTUNITIES• Upgrading in parallel in a short period of time about 30DB •Aim to reduce costs to around $2.5 M to 30-50% •Establishing an upgrade method utilizing a tool for efficient operation while ensuring the quality• The data migration in a short period of time large-scale DB environment, to minimize business downtime• Adopt the DB performance improvement technique method RESULTS•RAT realized the accurate verification and efficient online processing performance•Diag/Tuning realized the performance improvement technique method•Veridata realized the data validation of the old and new environment accurate and efficiently to a large extent•To maintain business continuity, used GG to data migrate on the Critical DBs.。
Oracle 12c 操作手册是一本详细介绍如何使用和操作 Oracle 12c 数据库的指南。
该手册首先介绍了 Oracle 12c 的基础知识，包括数据库体系结构、数据类型、SQL 语言等方面的内容。
接着，手册详细介绍了如何创建和管理数据库对象，如表、视图、索引等，以及如何进行数据查询和操作。
此外，手册还介绍了Oracle 12c 的高级功能，如存储过程、触发器、分区等。
同时，手册还提供了大量的示例和练习，帮助读者更好地理解和掌握 Oracle 12c 的操作技巧。
总之，Oracle 12c 操作手册是一本非常实用的工具书，对于需要进行 Oracle 数据库管理和开发的用户来说具有重要的参考价值。
通过阅读该手册，用户可以更好地了解Oracle 12c 的功能和特点，提高数据库的管理和开发效率。
Oracle Database 12c版本介绍Oracle Database 12c有三种版本，提供多种企业版选件来满足客户对各种领域（性能和可用性、安全性和合规性、数据仓储和分析、非结构化数据和可管理性）的特定需求。
Oracle Database 12c标准版1企业级的性能和安全性Oracle Database 12c标准版1经过了优化，适用于部署在小型企业、各类业务部门和分散的分支机构环境中。
该版本可在单个服务器上运行，最多支持两个插槽。
Oracle Database 12c标准版1可以在包括Windows、Linux和Unix在内的所有Oracle支持的操作系统上使用。
概述l快速安装和配置，具有内置的自动化管理l适用于所有类型的数据和所有应用l公认的性能、可靠性、安全性和可扩展性l使用通用代码库，可无缝升级到Oracle Database 12c标准版或Oracle Database 12c企业版优势l以极低的每用户180美元起步（最少5个用户）l以企业级性能、安全性、可用性和可扩展性支持所有业务应用l可运行于Windows、Linux和Unix操作系统l通过自动化的自我管理功能轻松管理l借助Oracle Application Express、Oracle SQL Developer和Oracle 面向Windows的数据访问组件简化应用开发Oracle Database 12c标准版经济实惠、功能全面的数据库Oracle Database 12c标准版是面向中型企业的一个经济实惠、功能全面的数据管理解决方案。
该版本中包含一个可插拔数据库用于插入云端，还包含Oracle真正应用集群用于实现企业级可用性，并且可随您的业务增长而轻松扩展。
概述l支持使用一个可插拔数据库实现入门级云计算和整合l跨平台恢复l内置的Oracle真正应用集群支持更高水平的系统正常运行时间l简化的安装和配置l适用于所有类型的数据和所有应用l向上兼容Oracle Database 12c企业版，从而保护您的初期投资优势l每用户350美元（最少5个用户），您可以只购买目前需要的许可，然后使用Oracle真正应用集成随需扩展，从而节省成本l提高服务质量，实现企业级性能、安全性和可用性l可运行于Windows、Linux和Unix操作系统l通过自动化的自我管理功能轻松管理l借助Oracle Application Express、Oracle SQL Developer和Oracle面向Windows的数据访问组件简化应用开发Oracle Database 12c企业版插入云端全球首屈一指的数据库推出最新版本——Oracle Database 12c现已推出，可在各种平台上使用。
Top Oracle Database 12cHigh Availability Innovations A Technical DrilldownWei Hu, Vice President of Development, High Availability Technologies, OracleBest Innovations Make Things Easy▪Any sufficiently advanced technology is indistinguishable from magic - Arthur C. Clarke▪Any technology that is distinguishable from magic is not sufficiently advanced - Gregory Benford▪This talk will give an overview of the new high availability features introduced in Oracle Database 12c▪Then describes some of the internal innovations that make these features powerful and easy to useOracle Database 12c▪Oracle Database 12c introduces significant new HA capabilities that–Drastically cut down planned and unplanned downtime –Eliminate compromises between HA and Performance –Tremendously boost operational productivity▪These take Availability to unprecedented new levels–Next-generation Maximum Availability Architecture (MAA) –Optimized for OracleExtreme AvailabilityOracle Maximum Availability ArchitectureActive Data Guard–Data Protection, DR–Query OffloadGoldenGate–Active-active –HeterogeneousRMAN, Oracle Secure Backup–Backup to tape / cloudActive ReplicaEdition-based Redefinition,Online Redefinition, Data Guard, GoldenGate– Minimal downtime maintenance, upgrades, migrationsRAC–Scalability –Server HAFlashback–Human error correctionProduction SiteApplication Continuity–Application HAGlobal Data Services–Service Failover / Load BalancingOracle Database 12cHigh Availability Key* New Features ▪Application Continuity▪Global Data Services▪Data Guard Enhancements▪RMAN Enhancements▪Flex ASM▪Other HA Enhancements▪GoldenGate Update▪MAA at PayPal▪ *Nearly a hundred new HA features in 12cDatabase outages can cause in-flightwork to be lost, leaving users and applications in-doubt -–User frustration –Cancelled work –Duplicate submissions –Rebooting mid-tiers –Developer painsPre-12c SituationIn-Flight Work: Dealing with OutagesApplication ServersDatabase ServersEnd User▪Replays in-flight work on recoverable errors▪Masks many hardware, software, network, storage errors and outages ▪Supports JDBC-Thin, Universal Connection Pool (UCP), WebLogic Server, 3rd Party Java apps/mid-tiers ▪RAC, RAC One, & Active Data Guard ▪Better end user experienceApplication ContinuityMasks unplanned/planned outages when successfulApplication ServersDatabase ServersEnd UserDatabase RequestReplayedApplication Continuity SubtletiesThe hardest part of replay is deciding when NOT to replay▪Application Continuity minimizes divergence by re-executing SQL at original SCN (when possible) and rebuilding original environment–Stops replay (and returns error) if replayed request returns different result than original (e.g., two users concurrently updating same row)▪Application Continuity does not attempt replay (and returns error) if –Error is not recoverable – e.g., constraint violation–DDLs such as SHUTDOWN ABORT, DROP TABLESPACE are executed–Request has been explicitly disabled for replay – e.g., disbursing money–Failure occurred too long ago – don’t automatically replay a request from yesterday ▪Application Continuity is safe; only replays incomplete requests – Will not pay for the same item twiceafter outagesTransaction GuardPreserve & Retrieve COMMIT Outcome▪Tracks outcome of the last transaction ▪Without Transaction Guard, retry can cause logical corruption▪Transaction Guard allows applications to deal correctly with failures▪Application Continuity uses Transaction Guard▪Transaction Guard also available for applications that do not use Application ContinuityApplication Continuity I nternalsOracle Database 12cHigh Availability Key New Features▪Application Continuity▪Global Data Services▪Data Guard Enhancements▪RMAN Enhancements▪Flex ASM▪Other HA Enhancements▪GoldenGate UpdateDatabases in Replicated EnvironmentsChallenges▪Maximum Availability ArchitectureActive Data Guard and GoldenGate with RAC▪Want to optimize utilization ofActive Data Guard and GoldenGate databases–Efficiently use all availabledatabases–Automated load balancing and faulttolerancePrimary Active Standby Active StandbyGlobal Data Services•Extends RAC-style service failover, loadbalancing (within and across datacenters), and management capabilities to a set of replicated databases•Takes into account network latency,replication lag, and service placement policies•Achieve higher availability, improvedmanageability and maximize performanceLoad Balancing and Service Failover for Replicated Databases▪Reporting client routed to ‘best’ database–Based on location, response time, data, acceptabledata lag–Reports will automatically run on least loaded server▪Reporting client failover–If preferred database not available, will route toanother database in same region or a remote database▪Global service migration–Automatically migrates services based onfailover/switchover - if primary database is down, start Call Center service on the new primaryActive Data Guard ExampleActive Data GuardReporting ServiceCall Center Service▪Call Center Client connections andrequests transparently routed to the closest / best database–Runtime load balancing metrics give client real-timeinformation on which database to issue next request▪If a database fails, its global services arerestarted on another replicaGoldenGate ExampleGoldenGateCall Center ServiceLoad Balancing is Very ComplicatedGlobal Data Service (GDS) Load Balancing▪Supports connect-time and run-time (per-request) load balancing▪Load balancing is easy if all your machines and workload are uniform–GDS supports heterogeneous environment – RAC + non-RAC, powerful and less powerful machines (important since some customers have less powerful machines for DR)▪Load balancing is NOT equal load on all machines–Instead, GDS minimizes average response time across all requests–If database 1 much faster than database 2, then 100% of requests might go to machine database 1–Sometimes, request to lightly-loaded database in remote region might complete faster than request to heavily loaded database in local region–Equalization of average response time done for all clients in each region (remote requests expected to be longer) ▪Load balancing must balance responding rapidly to changing workloads and avoiding oscillations▪Uses internal database metrics, does not blindly rely on external metrics–More accurate (factors out network variability), handles workload generated external to global services, & handles planned shutdown caseGlobal Data Services: SummaryGlobally Replicated, High Availability Architecture••• GSM - Global Service ManagerLocal StandbyLocal StandbyData Center #2 EMEAAPACGuardData GuardPrimaryLocal StandbyActiveData GuardGDSCTLGDS Catalog PrimaryGDS Catalog StandbyMasterOracleGoldenGate Active GuardSALES POOL (sales_reporting_srvc, sales_entry_srvc)HR POOL(hr_apac_srvc, hr_emea_srvc)All GDS client databases connected to all GSMsMasterRemote StandbyReader FarmActive Data GuardGlobal Service ManagersGlobal Service ManagersOracle Database 12cHigh Availability Key New Features▪Application Continuity▪Global Data Services▪Data Guard Enhancements▪RMAN Enhancements▪Flex ASM▪Other HA Enhancements▪GoldenGate UpdateZero Data Loss ChallengeThe longer the distance, the larger the performance impactSynchronous Communication Leads To Performance Trade-OffsPrimaryStandbyCommitCommit AckNetwork SendNetwork AckStandbyData Guard Async – TodaySome Data Loss Exposure Upon DisasterZero Data Loss For Async Deployments▪Far Sync: light-weight Oracle instance: standby control file, standby redo logs, archived redo logs, no data files▪Receives redo synchronously from primary, forwards redo asynchronously in real-time to standby▪Upon Failover: Async standby transparently obtains last committed redo from Far Sync and applies: zero data loss failover▪Second Far Sync Instance can be pre-configured to transmit in reverse direction after failover/switchover▪Terminal standbys required to be Active Data Guard StandbysPrimaryStandbyFar SyncInstanceStandbyFar SyncInstanceActive Data Guard Far SyncMuch work done to make things work ‘like magic’▪Looks just like SYNC. So Fast Start Failover (FSFO) works – automatic, zero data loss failover to far destination▪If Far Sync instance fails, can failover to another Far Sync (recommended), or go into async mode directly to standby (using remote alternate log_archive_dest_x)▪Sophisticated logic to make failovers seamless–When primary dies, Far Sync keeps track of state of async connections to terminal standby to ship the exact redo needed for zero data loss–Works with RAC (multiple threads of redo)▪Smart gap resolution – if the primary is missing redo, it can fetch from Far Sync instance. Far Sync instance will transparently fetch from primary & forward to standbyActive Data Guard Far SyncSummary of Benefits▪Best data protection, least performance impact▪Low cost and complexity▪Best way to implement a near DR + Far DR model▪Relevant to existing Data Guard ASYNC configurations▪Data Guard Failover? No Problem! Just do it – No Data Loss!Active Data Guard Real-Time CascadingEliminates Propagation DelayPrimary▪In 12.1, Standby 1 forwards redo to Standby 2 in real-time, as it isreceived: no propagation delay for a log switch▪Standby 2 (Active Data Guard Standby) is up-to-date for offloadingread-only queries and reports▪In 11.2, Standby 1 waits till log switch before forwarding redo fromarchived logs to Standby 2Data Guard Fast SyncReduced Primary Database Impact for Maximum AvailabilityLogsStandbyRedoLogsCommitCommitAcknowledge▪For SYNC transport: remote siteacknowledges received redo beforewriting it to standby redo logs▪Reduces latency of commit on primary▪Better DR – increased SYNC distance▪If network round-trip latency less thantime for local online redo log write,synchronous transport will not impactprimary database performance▪Can use Fast Sync from Primary to FarSync , and Fast Sync works with FSFO CommitCommitAcknowledgeAcknowledgereturned on receiptLogsStandbyRedoLogsData GuardOther New Features in Oracle Database 12cOracle Database 12cHigh Availability Key New Features▪Application Continuity▪Global Data Services▪Data Guard Enhancements▪RMAN Enhancements▪Flex ASM▪Other HA Enhancements▪GoldenGate UpdateFine-grained Table Recovery From Backup▪Simple RECOVER TABLE command torecover one or more tables (mostrecent or older version) from an RMANbackup▪Eliminates time and complexityassociated with manual restore, recover& export–Enables fine-grained point-in-timerecovery of individual tables instead ofthe contents of the entire tablespaceRMANBackupsCross-Platform Backup & Restore▪Simplifies procedure for platform migration▪Minimize read-only impact with multiple incremental backupsSimplified Platform MigrationSource Database (AIX)Backup to Disk/Tape (data files, optional endian conversion,metadata export)Restore Backup (optional endian conversion, metadata import)Destination Database (Solaris)▪Backup and recover specific pluggable databases with new PLUGGABLE DATABASE keywords:RMAN> BACKUP PLUGGABLE DATABASE <PDB1>, <PDB2>;▪Familiar BACKUP DATABASE command backs up CDB, including all PDBs ▪PDB Complete Recovery–RESTORE PLUGGABLE DATABASE <PDB>; –RECOVER PLUGGABLE DATABASE <PDB>;▪PDB Point-in-Time Recovery–RMAN> RUN {–SET UNTIL TIME 'SYSDATE-3'; –RESTORE PLUGGABLE DATABASE <PDB>; –RECOVER PLUGGABLE DATABASE <PDB>;–ALTER PLUGGABLE DATABASE <PDB> OPEN RESETLOGS; }▪Familiar RECOVER DATABASE command recovers CDB, including all PDBsPluggable Database Backup & RestoreFine-Grained Backup & Recovery to Support ConsolidationOracle Database 12cHigh Availability Key New Features▪Application Continuity▪Global Data Services▪Data Guard Enhancements▪RMAN Enhancements▪Flex ASM▪Other HA Enhancements▪GoldenGate UpdateAutomatic Storage Management (ASM) OverviewASM Cluster Pool of StorageDisk Group BDisk Group A Shared Disk GroupsWide File StripingOne to OneMapping of ASM Instances to ServersASM InstanceASM DiskRAC ClusterNode4Node3Node2Node1Node5ASMASM ASM ASMASMASM InstanceDatabase InstanceDB ADB A DB BDB BDB CDB BCurrent StateFlex ASM: Eliminate 1:1 Server MappingNew: ASM Storage Consolidation in Oracle Database 12cASM Cluster Pool of StorageDisk Group BDisk Group A Shared Disk GroupsWide File StripingDatabases share ASM instancesASM InstanceDatabase InstanceASM DiskRAC ClusterNode5Node4Node3Node2Node1Node5 runs as ASM Client to Node4Node1Node2 Node4Node2 runs as ASM Client to Node3 ASM ASM ASMASM InstanceDB ADB A DB BDB BDB CDB BFlex ASM: Supporting Oracle Database 11gPrevious Database Versions Will Host Local ASM InstanceASM Cluster Pool of StorageDisk Group BDisk Group A Shared Disk GroupsWide File StripingDatabases share ASM instancesASM InstanceDatabase InstanceASM DiskRAC ClusterNode5Node4Node3Node2Node1ASM ASM ASMDB ADB A DB BDB BDB C DB BASMASM11.2DB11.2DBOracle Database 12cHigh Availability Key New Features▪Application Continuity▪Global Data Services▪Data Guard Enhancements▪RMAN Enhancements▪Flex ASM▪Other HA Enhancements▪GoldenGate UpdateOther HA EnhancementsOracle Database 12cHigh Availability Key New Features▪Application Continuity▪Global Data Services▪Data Guard Enhancements▪RMAN Enhancements▪Flex ASM▪Other HA Enhancements▪GoldenGate UpdateNote: A single DR copy may be multi-purposed for any combination of the use cases describedData Guard Redo TransportSYNC or ASYNCOracle DatabaseOracle Active Data GuardReal-Time Data Protection and AvailabilityStandby First Patching, Exact copy of primary Query & Report OffloadOpen Read-Only Snapshot StandbyConvert to Test Database(open read-write)Single Command Refresh of primary Offload RMAN Backups of primary Far Sync, Database Backup Appliance, GoldenGateExact copy of primarySource for thin snaps/clones Exact copy of primary Extract offload, source for GoldenGate ALO modeOracle & Non-OracleMessage BusOracle Database12c *Oracle GoldenGate 12c*Low-Impact, Real-Time Data Integration & Transactional ReplicationData IntegratorNew DB/ HW/OS/APP Fully Active Distributed DBReporting Database DataWarehouse ODSZero Downtime Upgrade& Migration Query & Report Offloading Data Synchronization within theEnterprise Real-time BI, OperationalReporting, MDMEvent Driven Architecture, SOAActive-Active High AvailabilityMessage BusGlobal Data Centers Logical Copy of Primary Disaster Recovery for Non-Oracle Databases *: GoldenGate 12c for Oracle Database 12c will be available in CY2013GoldenGate Zero Downtime Migration/Upgrade Seamless Migration and Upgrades to Oracle Database 12c* •Consolidate/migrate/maintain systems withoutdowntime•Minimize risk withfailback option•Validate data beforeswitchover•Use Active-Active replication for phased user migrationERP Oracle ERP*: GoldenGate 12c for Oracle Database 12c will be available in CY2013 Oracle10.2CRM11.2DWOracle GoldenGate for Active-Active DatabasesIncrease ROI on Existing Servers & Synchronize Data•Utilize secondarysystems for transactions •Enable continuousavailability during unplanned & planned outages•Synchronize data acrossglobal data centers •Use intelligent conflictdetection & resolution*: GoldenGate 12c for Oracle Database 12c will be available in CY2013Oracle 10.2 App2Oracle 11.2 App3Non-Oracle AppHeterogeneous Bi-DirectionalOracle Database 12c▪Oracle Database 12c offers a tremendously sophisticatedset of high availability (HA) capabilities▪These capabilities–Further reduce downtime–Significantly improve productivity–Eliminate traditional compromisesExtreme Availability: SummaryResources▪OTN HA Portal:/goto/availability▪Maximum Availability Architecture (MAA):/goto/maa▪MAA Blogs:/maa▪Exadata on OTN:/technetwork/database/exadata/index.html▪Oracle HA Customer Success Stories on OTN:/technetwork/database/features/ha-casestudies-098033.htmlKey HA Sessions and Demos by Oracle DevelopmentMonday, 23 September Moscone South10:45a Oracle DB 12c—Eng’d for Clouds and Big Data, North D1:45p Oracle Exadata—What’s New and What’s Coming, 1033:15p Top Oracle DB 12c HA Innovations - A Technical Drill-down, 103 4:45p RMAN in Oracle DB 12c: New Features and Best Practices, 102 4:45p Compression and Performance in Oracle Database 12c, 104Tuesday, 24 September Moscone South10:30a Always Available: Oracle Exadata and Oracle MAA, 10210:30a Oracle RAC 12c Best Practices, 10412:00p A Revolutionary New Way to Do DB Backup and Recovery, 102 12:00p Oracle Flex Cluster: Optimized Resource Mgmt. for Cloud, 104 12:00p Storage Optimization with Oracle Database 12c, 3013:45p Oracle DB 12c Best Practices for Data Availability andDisaster Protection, 1025:15p Optimize Oracle Active Data Guard and Oracle GoldenGate:Wednesday, 25 September Moscone South10:15a Best Practices for Integrating GoldenGate w/ Act. Data Guard, 104 11:45a The Next Big Thing!, 10311:45a Best Practices for Oracle Exadata Backup and Recovery, 20011:45a Cloning and Snapshots with Oracle Database 12c, 1021:15p Redefining Backup and Recovery with Oracle Eng’d Systems, 200 3:30p Oracle Active Data Guard: Next-Generation Data Protection, 103 5:00p Oracle Exadata Storage Availability Best Practices, 2005:00p Integrated Apply: Scalable Replication with GoldenGate, North 131 5:00p Exadata Planned Maintenance for Zero Downtime, Westin Metro. IThursday, 26 September Moscone South11:00a Oracle Database-Aware Flash: Maximizing Performance andAvailability for Your Database, 2362:00p Oracle MAA Best Practices for the Oracle Multitenant Option, 102 2:00p Maximize Availability by Using DB Services with Oracle RAC, 103。
