This presentation is an overview of things all IT management team needs to consider before upgrading to Oracle Database 12c and were presented in a webinar: bit.ly/1yzSdsd Oracle ACE Director Dan Morgan was a 12c beta tester and is intimately familiar with changes in architecture and how they will impact existing infrastructure and planning and budgeting considerations. In 2015, most organizations will begin to migrate to the latest version of Oracle Database 12c, but few are aware of the challenges to management, planning and budgeting that need to be addressed before executing such a project. Dan Morgan presents what needs to be considered and shares a few tips about 12c new features. If you have any questions regarding your future Oracle migrations and upgrades, feel free to visit Performance Tuning Corporation at www.perftuning.com

1. Database 12c is ready for you ...
Are you ready for 12c?
Tips for IT Management by Oracle ACE Director Dan Morgan
Brought to you by Performance Tuning Corporation

2. Outline
• What is Different?
– Container Database
– Multi-tenant Consolidation
– In-Memory Database
– Integrated Lifecycle
Management
• Planning and Budgeting
Impact
– Existing Databases
– Hardware Considerations
– Training Requirements
• Conclusion
• About Dan Morgan and
PTC

3. What is different: Container Architecture
Listener
Dev 1
PDB
Dev 2
PDB
Test
PDB
Seed
PDB$SEED
ContainerDB

4. The critical questions
• To create a container DB: Yes or Yes?
• Improved separation of duties
• Faster and more flexible deployment
• You don't have a choice
• To multi-tenant consolidate: Yes or No?
• Patching requirements
• Upgrade requirements
• Backup and restore requirements
• Security requirements
• Infrastructure
• DR Replication
• To enable in-memory database: Yes or No?
• Mixed OLTP and DSS loads

5. What is different: multi-tenant consolidation
What are the implications of consolidation?
– Processes
– Transactions
– Connections
– Memory
– CPU
– I/O
• Do you really want to use only one TEMP tablespace?
• How do you calculate space allocation for UNDO?
• What is size and distribution of the AWR data in the SYSAUX tablespace?
– Networks Latency and Bandwidth
– Backups and Restores
– DataGuard Replication
– Resource Management

6. What is different: multi-tenant consolidation
Can we use our current servers for consolidation ...
or more importantly "should" we use our current servers?
– Pizza Boxes (1U, 2U, 3U)
– Blades (H/P and Cisco UCS)
– M10 (Fujitsu)
– P Series (IBM)
– Z Series (IBM)
– T Series (Sun-Oracle)
– M Series (Sun-Oracle)
– ODA
– Sparc SuperCluster (T5-8)
– Exadata

7. Database-level tiering
• Integrated Lifecycle
Management: Data Tiering
– Storage vendors have provided
data tiering for quite some time.
But their data tiering is based
not on an understanding of the
database but rather on access to
specific storage blocks
– ILM means that you can write
and enforce data-dependent
rules
-- Tablespace Level Policy
ALTER TABLE uwclass.servers
ILM ADD POLICY TIER TO ilmtbs;
-- Compress segments after there have been no
modifications for one week
ALTER TABLE uwclass.servers
ILM ADD POLICY ROW STORE
COMPRESS ADVANCED SEGMENT
AFTER 7 DAYS OF NO MODIFICATIONS;
-- Compress rows after one week of not being updated
ALTER TABLE uwclass.servers
ILM ADD POLICY ROW STORE
COMPRESS ADVANCED ROW
AFTER 14 DAYS OF NO MODIFICATIONS;

8. Planning and budgeting impact
• Difference in architecture means changes in
– Management code
– Management processes and procedures
– Supporting process and procedure documentation
– Most likely every shell script and cron job you have written will break
– The rules are far stricter with respect to what is automatically upgradeable
• Multi-tenant consolidation can potentially lower your TCO
– But it won't lower your TCO if you do not plan consolidation with a thorough
understanding of where the value can be found
– Consolidation may require different hardware choices
• In-Memory Database
– Putting a database into memory requires more memory

9. Upgradeable Database Rules
• The undocumented DBMS_PREUP package details the issues. Here is a partial list
– A user or role with the name AUDIT_ADMIN" found in the database. This is an Oracle defined role. you must drop this role or user prior to upgrading
– Starting with Oracle Database 12c, OLAP is desupported
– APPQOSSYS" user found in database. This is an internal account used by Oracle Application Quality of Service Management. Please drop this user prior to upgrading
– A user or role with the name "AUDIT_VIEWER" found in the database. This is an Oracle defined role. You must drop this role or user prior to upgrading
– A user or role with the name "AUDSYS" found in the database. This is an internal account used by Oracle Database Auditing. You must drop this user or role prior to upgrading
– A user or role with the name "CAPTURE_ADMIN" found in the database. This is an Oracle defined role. You must drop this user or role prior to upgrading
– Compatible set too low "compatible" currently set at and must be set to at least 11.0.0 prior to upgrading the database
– Existing DBMS_LDAP dependent objects Database contains schemas with objects dependent on DBMS_LDAP package. Refer to the Upgrade Guide for to configure Net ACLs.
– Process Count may be too low Database has a maximum process count of 300 which is lower than the default value of 300 for this release
– Please gather dictionary statistics 24 hours prior to upgrading the database
– Starting with release 12.1, it is REQUIRED that Database Vault be disabled prior to database upgrade
– Enterprise Manager Database Control repository found in the database In Oracle Database 12c, Database Control is removed during the upgrade
– Table sys.enabled$indexes exists in the database. DROP TABLE sys.enabled$indexes prior to upgrading the database
– Expression Filter (EXF) or Rules Manager (RUL) exist in database and will be removed during the upgrade
– There are files in backup mode Ensure no files are in backup mode prior to upgrade
– There are files which need media recovery Ensure no files need media recovery prior to upgrade
– Your current setting is: log_archive_format='%t_%s_%r.dbf'
– Database contains INVALID objects prior to upgrade. The list of invalid SYS/SYSTEM objects was written to registry$sys_inv_objs
– Invalid Oracle supplied table data found in your database
– Invalid user table data found in your database
– job_queue_processes set too low. This parameter must be removed or updated to a value greater than (default value if not defined is 1000) prior to upgrade
– Existing schemas with network ACLs exist. Database contains schemas with objects dependent on network packages
– New Timezone File in use. Database is using a time zone file newer than version 18.
– ORACLE_OCM" user found in database. This is an internal account used by Oracle Configuration Manager. Please drop this user prior to upgrading.
– An error occurred retrieving a count from SYSTEM.AUD$. This can happen when the table has already been cleaned up. The olspreupgrade.sql script should be re-executed.
– ORDSYS.OrdImageIndex in use. The previously desupported Oracle Multimedia image domain index, ORDSYS.
– It is REQUIRED that the recycle bin is empty prior to upgrading your database

10. Location matters and training is required
You've been a DBA for years so answer these basic questions
– You logon as SYS ... what database did you connect to?
– You started the database ... what did you start?
– You did a shutdown abort ... why can most users still connect and work?
– The database just crashed ... what crashed?
– You moved system01.dbf ... what did you move?
– You created a tablespace but no one can use it ... why?
– You created a new user ... what type and where?
– You created a new role ... what type and where?
– You patched the database ... what did you patch?
– You performed an RMAN backup ... what did you back up?
– You assigned privileges to a role and they do not work ... why?
– Every cron job that worked in 11gR2 no longer works ... why?

11. Conclusion
• 2015 is the year to begin moving to Database 12c
• An evaluation of existing applications and ancillary code is required to identify
required changes
• An evaluation of existing management tools and techniques is required to identify
required changes
• If consolidation is under consideration application databases must be categorized
to identify opportunities
• If consolidation is under consideration a hardware inventory is required to identify
hardware with sufficient resources and to identify hardware replacement costs
• If data-tiering is under consideration to lower storage costs an analysis of
requirements to move to partitioning is essential

12. About Daniel Morgan
• Oracle ACE Director
• Wrote Oracle curriculum and primary program instructor at University of Washington
• Oracle consultant to Harvard University
• The Morgan behind Morgan's Library on the web
www.morganslibrary.org
• 10g, 11g, and 12c Beta tester
• Member: New York Oracle Users Group
• Retired chair Washington Software Assoc. Database SIG
• Co-Founder International GoldenGate Users Group
• Never an employee of Oracle Corp.

13. • Founded in 1997
– Team spun out of Compaq Performance Lab
– Focused on solving the tough/complex and messy data architecture problems
– Very Senior team of EXPERTS
• Over 1000 clients & counting
• Key industries: Financial Services, Telecom, Oil & Gas,
Healthcare
• Oracle Platinum Partner: Oracle Ace Director and Oracle Ace on
staff
About PTC Select Clients
Focus on:
High Performance Architectures
• Database & Engineered Sys.
• Storage, Server and Network
• Consulting, Managed Services &
Training

14. Thank you!
Expert Data Services team with deep
performance tuning and Oracle
technology backgrounds.
EXPERTS
More info:
www.perftuning.com
info@perftuning.com
@perftuning