Oracle Database 12c Enables Quad Graphics to Quickly Migrate from Sybase to Oracle Exadata

Oracle Database 12c Enables Quad Graphics to Quickly Migrate from Sybase to Oracle Exadata Presented with Prakash Nauduri Technical Director Platform Migrations Group, Database Product Management Sep 30, 2014 Kevin Bott Quad/Graphics Oracle DBA Lead

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.

Program Agenda 1 2 3 4 Database migration drivers and challenges Oracle offerings for migrations First hand account of Migrating to Oracle Database 12c by Quad Graphics Q&A

Program Agenda 1 2 3 4 Database migration drivers and challenges Oracle offerings for migrations First hand account of migrating to Oracle Database 12c by Quad Graphics Q&A

Database migration drivers Lower IT costs AND improve Quality of Service Consolidate & Reduce Server Sprawl Improve OLTP & DW Performance Simplify Management & Reduce Overhead

Database migration challenges Database Migrations have an impact on applications SQL statements changes, error handling, database API changes Application changes due to database platform migration is time-consuming Database centric code may be spread across many applications on many systems Use of dynamic SQL statements makes it difficult to identify and modify SQL statements Testing application changes is also difficult Differences in database functionality introduces learning curve for DBAs/Developers Re-training of administrators/developers is a must Managing many instances of Oracle database is a challenge when migrating from other databases/platforms May need to deploy multiple Oracle database instances for isolation, schema namespace collision issues

Oracle offerings for migrations - Strategy Focusing on all aspects of migrations Schema, data, application migration, testing, deployment tasks Increase automation of migration tasks Migration Lifecycle Scoping/Analysis Enable IT staff in performing migrations Migrations cannot be automated 100% with tools/software Provide subject matter expertise to customers and partners if needed Provide turn key solution approach for migrations Reduce learning curve for DBAs and developers Introduce features/functionality commonly used by users on other platforms Deployment User Acceptance Migration Testing

Oracle products enabling migrations Migration Tasks Analysis/Scoping Database Migration Application Migration Oracle Products Oracle SQL Developer, Application Migration Assistant Oracle SQL Developer SQL Developer( Application Migration Assistant), SQL Translation Framework Bulk data migration, production rollout (0 downtime), Data Integration Testing Oracle SQL Developer/database Utilities, Golden Gate/Oracle Data Integrator/Database Gateways SQL Developer Unit Tests, SQL Translation Framework, Testing Suite

Oracle Database 12c enabling faster migrations Migration Challenges Reduce application migration effort Oracle database 12c Features SQL Translation Framework Can translate non-oracle SQL statements to Oracle SQL statements and execute them Database Provider for DRDA Pre-compiled (COBOL) Applications accessing DB2 on zseries, iseries or LUW systems can be connect to Oracle Reduce database migration effort and learning curve for DBAs and developers Oracle Database 12c features IDENTITY column support Support for implicit result sets from stored procedures/functions Top N SQL Support VARCHAR2 Datatype length = 32K Support for LEFT OUTER JOIN clause Consolidation of Databases/Instances Pluggable Databases (Oracle Multi-tenant) Migrated Databases are treated just as they were in the source database and avoid namespace collision

SQL Translation Framework Run non-oracle apps against Oracle, translate SQL on-the-fly SQL Translation Framework SQL Translation Profile collection of translated statements Each application can have its own profile SQL Translator java engine that translates the SQL SQL Developer can install Sybase & SQL Server translators SQL Translation Framework Benefits Test and Verify application code before production Helps define Task List of modifying the application code Convert Applications To Oracle Quicker Temporary measure before migrating application fully or retiring it

Oracle 12c Migration Features SQL Translation Framework: 1 st time Sybase Application Framework receives Select Top 2 * Sybase Top 3 * From T1 From T1 Performs static lookup of a conversion in the SQL Translation Dictionary Not Available: Generate the Fingerprint Select Top <ora:literal type=integer order=1> * From T1 Lookup fingerprint in the SQL Translation Dictionary Available: Gets the Fingerprint Select * From T1 FETCH FIRST <ora:literal type=integer order=1> ROWS ONLY Processes the Template with values acquired Select * From T1 FETCH FIRST 3 ROWS ONLY Returns the translated SQL to the Framework SQL Translation Framework handles binds if necessary Oracle Database 12c SQL Translation Framework Generate Fingerprint fingerprint Select top Sybase Translator SQL Translation Dictionary template Select * Translate Error Code Dictionary Source Target

Using SQL Developer to Move to Oracle DB Official Database Migration Tool for Oracle Support for Migrating Applications to Oracle Can scan applications for SQL statements and produce reports Perform in-place SQL translations (works with static SQL only) GUI interface to manage SQL Translation Framework environment Comprehensive reports for analyzing source databases and determine migration tasks status, complexity Supports Oracle Database 12c features, ad-hoc SQL translation Single tool for migrating non-oracle databases as well as on-going Oracle Database development activities Provides flexible data migration approaches

Oracle Database 12c New migration features Identity Columns Source TSQL Pre 12C Migration 12C Migration create table tabel1 (id int identity, name varchar(100) not null) CREATE TABLE table1 ( Id NUMBER(12), name VARCHAR2(100 CHAR) NOT NULL ); CREATE SEQUENCE t1_id_seq MINVALUE 1 MAXVALUE 999999999999 INCREMENT BY 1 NOCYCLE ; CREATE OR REPLACE TRIGGER t1_id_trg BEFORE INSERT ON t1 FOR EACH ROW DECLARE v_newval NUMBER(12) := 0; v_incval NUMBER(12) := 0; BEGIN IF INSERTING AND :new.id IS NULL THEN SELECT t1_id_seq.nextval INTO v_newval FROM DUAL; -- If this is the first time this table have been inserted into (sequence == 1) IF v_newval = 1 THEN --get the max indentity value from the table SELECT NVL(max(col1),0) INTO v_newval FROM t1; v_newval := v_newval + 1; --set the sequence to that value LOOP EXIT WHEN v_incval>=v_newval; SELECT t1_id_seq.nextval INTO v_incval FROM dual; END LOOP; END IF; -- save this to emulate @@identity utils.identity := v_newval; -- assign the value from the sequence to emulate the identity column :new.col1 := v_newval; END IF; END; CREATE TABLE table1 ( Id NUMBER(12) GENERATED BY DEFAULT ON NULL AS IDENTITY, name VARCHAR2(100 CHAR) NOT NULL );

Oracle Database 12c New migration features Implicit Cursors Source TSQL Pre 12C Migration 12C Migration create procedure testproc1 as begin select top 10 * from table1 select top 10 * from table2 end; CREATE OR REPLACE PROCEDURE testproc1 ( cv_1 OUT SYS_REFCURSOR, cv_2 OUT SYS_REFCURSOR) AS BEGIN OPEN cv_1 FOR SELECT * FROM table1 WHERE ROWNUM <= 10 ; OPEN cv_2 FOR SELECT * FROM table2 WHERE ROWNUM <= 10 ; END; CREATE OR REPLACE PROCEDURE testproc1 AS v_cursor SYS_REFCURSOR; BEGIN OPEN v_cursor FOR SELECT * FROM table1 FETCH FIRST 10 ROWS ONLY ; DBMS_SQL.RETURN_RESULT(v_cursor) ; OPEN v_cursor FOR SELECT * FROM table2 FETCH FIRST 10 ROWS ONLY ; DBMS_SQL.RETURN_RESULT(v_cursor) ; END;

Oracle Database 12c New migration features Fetch First Rows Source T-SQL Pre 12c Migration 12c Migration SELECT TOP 10 PERCENT * FROM T1 WITH query AS ( SELECT * FROM T1 ) SELECT * FROM query WHERE ROWNUM <= CEIL( 10 / 100 * ( SELECT COUNT(*) FROM query ) ) ; SELECT * FROM T1 FETCH FIRST 10 PERCENT ROWS ONLY ;

Oracle Database 12c New migration features VARCHAR2(32000) Source T-SQL Pre 12c Migration 12c Migration create table tabel1 (id int, address varchar(6000) not null) CREATE TABLE table1 ( Id NUMBER, address CLOB NOT NULL); CREATE TABLE table1 ( Id NUMBER, address VARCHAR2(6000) NOT NULL); NOTE: Oracle Database kernel has to be re-linked with parameters associated with this feature. Refer to Oracle documentation for instructions

Oracle Database 12c New migration features Outer Joins & Temporary tables Improved Global Temporary Performance Enhanced Oracle Native LEFT OUTER JOIN Syntax Allows multiple tables on the left of an outer join Previously had to convert to ANSI Joins Source T-SQL Pre 12c Migration 12c Migration SELECT * FROM T1, T2, T3 WHERE T1.ID =* T2.ID AND T1.ID =* T3.ID FAILS Multi table outer joins on old syntax was not supported SELECT * FROM T1 LEFT OUTER JOIN T2 ON T1.ID = T2.ID LEFT OUTER JOIN T3 ON T1.ID = T3.ID SELECT * FROM T1,T2,T3 WHERE T1.ID(+) =T2.ID AND T1.ID(+) =T3.ID;

Migration Assistance From Oracle Customer Led Platform Migration Group can provide Migration Training Scoping/estimating, Project Planning Prototyping/Proof of Concept, Knowledge Transfer Technical issue resolution Best Practices Oracle Led Oracle can provide a turn key solution through Oracle Consulting Services Migration Factory offering. 2013 Oracle Corporation Oracle Proprietary and Confidential: Signed NDA Required

The Oracle Migration Factory Changes Everything People Process The right mix of people, process, and technology to maximize performance and value with the lowest cost and risk Technology People: Dedicated team of migration experts Flexible onshore/offshore model Process: Proven methodology and re-usable tools built from 25 years of handson migration experience Benefits Technology: Real-time management & visibility into projects Management tools to ensure quality delivery

Quad/Graphics 23 Global provider of print and related multichannel solutions to Fortune 500 client base $4.8 billion in annual sales 25,000+ full-time employees 2 nd largest printer in Western Hemisphere 71 printing plants in 8 countries

24 Global Platform (print plants only) North America 59 plants 22,000 employees 90% of revenue Europe 2 plants 1,450 employees 4% of revenue Latin America 10 plants 2,850 employees 6% of revenue Asia Strategic Partnership with India s ManipalTech

Business Challenges and Strategy 25 Transforming Industry > Traditional long run print on the decline > Postage rates on the rise > Continued downward pricing pressures One Common Platform > Both Manufacturing Platform & IT Tools > Allows work to be shifted between plants Adopted M&A Strategy for Growth > Nine Acquisitions in Five Years > Rollout common toolset

IT Challenges 26 Infrastructure Maintaining system performance with increasing print volumes and shorter turn around time Scale Up Strategy > Hitting the Ceiling Development Continuing requests for features and new development Each acquisition brings new integration challenges > One size does not fit all > Contention increasing with CPU count. Acquisitions bring more disparate systems

IT Strategy 27 Infrastructure Migrate to Oracle Database > Benefits from Concurrency Model Oracle Exadata Development Oracle Database 12c SQL Translation Framework > TSQL Translator > Allows us to scale out as applications migrate

Environment Overview 28 Four main Sybase Environments running on IBM Power7 / AIX > Front Office, Back Office, Transportation, Warehousing, etc. Approximately 1000 applications, organized into 160 systems > 1900 application users and roles Mix of PowerBuilder,.Net, and Java

Project History 29 2010 2011 > Quad/Graphics acquired WorldColor, doubling in size overnight > Saw the need for long term strategy > Oracle Insight Program 2012 > Sybase to Oracle POC completed, partnered with Neos LLC 2013 > Migrated first application from Sybase to Oracle, partnered with Neos LLC > Exadata POC, 11gR2 > Oracle 12c Released 2014 SQL Translation Framework POC > Running four migration projects for different business areas > Development work on first translated application

30 SQL Translation Framework The Impact on Our Migration Enables an intermediate migration step for applications Application testing can start after driver and connection string change It helps minimize the investment on low value applications Time and effort saved is redirected > More Testing > More Migration Work > Other Strategic Work It helps reduce pressures of normal project management constraints > Cost, Scope and Schedule The SQL Translation Framework is a key enabler for Quad/Graphics to complete our Migration Program on schedule

Lessons Learned 31 Don t forget your internal processes > How will developers review translations? > Are translation changes Code Changes? > Will developers be able to edit their own translations? User and Profile Management > Use a login trigger to enable translations > Store relationship in a table

Lessons Learned 32 Profile Owner Dev Team > Determines privilege requirements Profile Granularity > At which level should the profile be created? System System > Trade-offs of manageability and redundant translations > Be flexible in your design App App App Login Login Login Login

Lessons Learned 33 Some code will need to change > Not 100% will translate Dynamic SQL > Real time translation will add to query execution time > Apply /*+ NO_SQL_TRANSLATION */ hint if possible Not good for Ad-Hoc TSQL Scripts > Convert to PL/SQL or Stored Procedure Upfront analysis > Longevity of application > Good candidate for translation? > Feature compatibility with old software Reserved word translations > Profile Owner should also own the Migration Repository

Keep Current on Versions 34 Oracle 12.1.0.2 > DBA_TRANSLATIONS view has new columns for auditing and tracking creation of translations TSQL Translator > Install and retest problem translations UTILS Package > Compare with previous version for changes > If UTILS package was customized, merge in new changes appropriately