Oracle on Linuxone

Total Page:16

File Type:pdf, Size:1020Kb

Oracle on Linuxone Front cover Oracle on LinuxONE Susan Adamovich Sam Amsavelu Armelle Chev Helene Grosch Guilherme Nogueira Jagannath Raju Moshe Reder Mariana Roveri David J Simpson Narjisse Zaki Redbooks International Technical Support Organization Oracle on LinuxONE August 2019 SG24-8384-01 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. Second Edition (August 2019) This edition applies to Oracle Database 12cR1, Oracle Database 12cR2, SUSE Linux Enterprise Server and Red Hat Enterprise Linux Servers. © Copyright International Business Machines Corporation 2019. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix Authors. ix Now you can become a published author, too! . xi Comments welcome. xi Stay connected to IBM Redbooks . xi Chapter 1. A shared commitment to client value with IBM and Oracle Alliance. 1 1.1 Discover the possible . 2 1.2 Solution overview . 2 1.3 LinuxONE family overview and architecture . 2 1.4 How it works . 3 1.5 Competitive advantage . 3 Chapter 2. Setting up Linux guests to install Oracle Database 12c Release 1 . 5 2.1 Obtaining Oracle documentation, Oracle code, and My Oracle Support notes. 6 2.1.1 Master Note of Linux OS Requirements for Database Server . 6 2.1.2 Pre-installation requirements documentation . 6 2.1.3 Obtaining code for Oracle 12cR1 on IBM LinuxONE . 7 2.1.4 Oracle database pre-installation tasks in Oracle online Documentation. 7 2.1.5 Linux Large Pages and Oracle Databases . 7 2.2 Red Hat Enterprise Linux and SUSE Linux Enterprise Server setup . 8 2.2.1 Important information . 8 2.2.2 Pre-installation checking . 9 2.3 Red Hat Enterprise Linux Server 6 or 7 Specific Setup . 16 2.3.1 Important information . 16 2.3.2 Pre-installation checking . 16 2.4 SUSE Linux Enterprise Server specific setup . 17 2.4.1 Important information . 18 2.4.2 Pre-installation checking . 18 2.5 Installation . 20 2.5.1 Oracle Universal Installer . 20 2.5.2 Updating the Oracle user profile . 22 2.5.3 Creating the database. 22 Chapter 3. Using Oracle Enterprise Manager Cloud Control Agent to manage Oracle Database 12c Release 1 . 23 3.1 Basic Enterprise Manager Cloud Control Architecture . 24 3.2 Creating the Enterprise Manager Cloud Control Architectures . 25 3.2.1 Downloading the installation files . 26 3.2.2 Installing and configuring Enterprise Manager Cloud Control 13c . 26 3.3 Updating the agent at the Enterprise Manager Cloud Control to monitor Oracle Databases on LinuxONE (online) . 29 3.3.1 Configuring the Software Library storage space. 30 3.3.2 Acquiring the LinuxONE agent in online mode . 30 3.3.3 Setting up My Oracle Support Credentials . 30 3.3.4 Verifying that Enterprise Manager Cloud Control is in online mode . 30 © Copyright IBM Corp. 2019. All rights reserved. iii 3.3.5 Downloading and applying the LinuxONE Management Agent Software. 31 3.4 Updating the agent at the Enterprise Manager Cloud Control to monitor Oracle Databases on LinuxONE (offline) . 31 3.4.1 Acquiring the LinuxONE agent in offline mode . 32 3.4.2 Verifying that Enterprise Manager Cloud Control is in offline mode . 32 3.4.3 Updating the agents in Enterprise Manager Cloud Control using the Self Update feature. 32 3.5 Deploying the agents from the Cloud Control console . 35 3.6 Deploying the agents in silent mode . 37 3.7 Adding the databases for monitoring . 40 3.8 Summary. 41 Chapter 4. Oracle encryption on LinuxOne . 43 4.1 Oracle Transparent Data Encryption on Oracle Database 12cR2 . 44 4.1.1 Benefits of the use of Transparent Data Encryption . 44 4.1.2 Installing Transparent Data Encryption. 44 4.1.3 Configuring and administering Transparent Data Encryption . 44 4.2 Enabling encryption on Oracle Database . 48 4.3 Managing TDE master keys and wallets. 54 4.4 Performance . 56 4.5 Using Oracle TDE on Oracle RAC . 59 4.6 Summary. 60 Chapter 5. Successful consolidation project: From sizing to migration . 61 5.1 Delimitation of the project scope . 62 5.1.1 Certification and support . 62 5.1.2 Best candidates for consolidation . 62 5.1.3 Non-functional requirements. 62 5.1.4 Business value analysis . 63 5.2 Sizing . 63 5.2.1 CPU . 63 5.2.2 Memory . 64 5.2.3 I/O . 66 5.3 Proof of concept . 67 5.3.1 PoC qualification . 67 5.3.2 Execution . 68 5.3.3 Analyzing and reporting . 70 5.4 Migration . ..
Recommended publications
  • Oracle Solaris: the Carrier-Grade Operating System Technical Brief
    An Oracle White Paper February 2011 Oracle Solaris: The Carrier-Grade Operating System Oracle White Paper—Oracle Solaris: The Carrier-Grade OS Executive Summary.............................................................................1 ® Powering Communication—The Oracle Solaris Ecosystem..............3 Integrated and Optimized Stack ......................................................5 End-to-End Security ........................................................................5 Unparalleled Performance and Scalability.......................................6 Increased Reliability ........................................................................7 Unmatched Flexibility ......................................................................7 SCOPE Alliance ..............................................................................7 Security................................................................................................8 Security Hardening and Monitoring .................................................8 Process and User Rights Management...........................................9 Network Security and Encrypted Communications .......................10 Virtualization ......................................................................................13 Oracle VM Server for SPARC .......................................................13 Oracle Solaris Zones .....................................................................14 Virtualized Networking...................................................................15
    [Show full text]
  • Tampere University Research Portal
    Tampereen teknillinen yliopisto. Julkaisu 800 Tampere University of Technology. Publication 800 Francis Tam Service Availability Standards for Carrier-Grade Platforms: Creation and Deployment in Mobile Networks Thesis for the degree of Doctor of Technology to be presented with due permission for public examination and criticism in Tietotalo Building, Auditorium TB222, at Tampere University of Technology, on the 15th of May 2009, at 12 noon. Tampereen teknillinen yliopisto - Tampere University of Technology Tampere 2009 ISBN 978-952-15-2134-8 (printed) ISBN 978-952-15-2158-4 (PDF) ISSN 1459-2045 Abstract The rapid development of the mobile network industry has raised considerably the expectations and requirements of the whole chain of stakeholders, from the end users through the mobile network operators and ultimately to the network equipment providers. A key expectation from an end user is service availability, which is a perception that services are continuously operational even in the presence of failures in the mobile network. Network equipment providers have been using carrier-grade platforms to provide various support functions including high availability as reusable assets for products creation. The term carrier-grade refers to a class of systems used in public telecommunications network that deliver up to five nines or six nines (99.999% or 99.9999%) availability. The convergence of communications and information technology in the industry has led to more competition and pressure to reduce development efforts. By creating a service availability standard, Commercial Off-The-Shelf (COTS) software can be bought and integrated into a carrier-grade platform, enabling a company to focus on the core business and concentrate the resource investment onto new innovations.
    [Show full text]
  • Wireless Network Virtualization: Ensuring Carrier Grade Availability
    ™ AN INTEL COMPANY Wireless Network Virtualization: Ensuring Carrier Grade Availability WHEN IT MATTERS, IT RUNS ON WIND RIVER WIRELESS NETWORK VIRTUALIZATION: ENSURING CARRIER GRADE AVAILABILITY EXECUTIVE SUMMARY The wireless industry’s battle to acquire new subscribers and retain existing ones is accelerating the need for new services. Profit margins are under pressure from the increased infrastructure and operations costs required to satisfy the growing demand. Network functions virtualization (NFV), a rapidly growing initiative in telecom networks, promises to revolutionize how networks are architected and managed. It allows communications service providers (CSPs) to virtualize network functions and consolidate them on standard off-the-shelf servers. Although 4G LTE is effective at meeting the increasing bandwidth demands at lower costs than its predecessors, its mobile base station, E-UTRAN Node B (eNB), located at the edge of the radio access network (RAN), is underutilized at certain times of the day and has grown in complexity, resulting in higher downtime and field maintenance costs. As a result, the eNB is a good candidate for NFV. Cloud-RAN (C-RAN) is the virtualization of the eNB’s control plane and data plane functions, consolidating it in one or more data centers. The result is significantly higher equipment utilization, cost-efficient redundancy to achieve high availability, and lower operations and maintenance costs. However, to realize these benefits, the foundation for virtualized eNBs must be a robust, carrier grade NFV platform that incorporates advanced fault management features. Poor implementation results in lower quality execution with excessive outage and maintenance costs. Wind River® Titanium Cloud is the industry’s first NFV-ready solution that incorporates advanced carrier grade fault, security, performance, and network management features.
    [Show full text]
  • Carrier Grade Virtualization
    Carrier Grade Virtualization Leveraging virtualization in Carrier Grade Systems Abstract Network Equipment Providers (NEPs) have been building networking infrastructure equipment able to deliver “carrier grade” services, typically mission-critical services such as voice telephony. In decades past, NEPs have achieved high degrees of availability through purpose-built hardware and software implementations. Today they increasingly build on COTS (Commercial Off The Shelf) hardware and Open Source Software (OSS), freeing their engineering resources to focus on core telephony competencies. The move to COTS and OSS requires that these hardware and software components be available from an ecosystem of suppliers, and that they interoperate seamlessly. Bodies such as The Linux Foundation (LF), the Service Availability Forum (SA Forum) and PICMG have defined standards and specifications such as carrier grade OSes (CGLinux), Service Availability Forum APIs and AdvancedTCA hardware to target carrier grade applications. Recent advances have made virtualization appealing for carrier class equipment by permitting significant cost reduction through consolidation of workloads and of physical hardware. Virtualization also transparently lets NEPs and other OEMs (Original Equipment Manufacturers) leverage multi-core processors to run legacy software designed for uniprocessor hardware. However, virtualization needs to meet specific requirements to enable network equipment deploying this technology to meet industry expectations for carrier grade systems. This
    [Show full text]
  • Energy Efficiency in Office Computing Environments
    Fakulät für Informatik und Mathematik Universität Passau, Germany Energy Efficiency in Office Computing Environments Andreas Berl Supervisor: Hermann de Meer A thesis submitted for Doctoral Degree March 2011 1. Reviewer: Prof. Hermann de Meer Professor of Computer Networks and Communications University of Passau Innstr. 43 94032 Passau, Germany Email: [email protected] Web: http://www.net.fim.uni-passau.de 2. Reviewer: Prof. David Hutchison Director of InfoLab21 and Professor of Computing Lancaster University LA1 4WA Lancaster, UK Email: [email protected] Web: http://www.infolab21.lancs.ac.uk Abstract The increasing cost of energy and the worldwide desire to reduce CO2 emissions has raised concern about the energy efficiency of information and communica- tion technology. Whilst research has focused on data centres recently, this thesis identifies office computing environments as significant consumers of energy. Office computing environments offer great potential for energy savings: On one hand, such environments consist of a large number of hosts. On the other hand, these hosts often remain turned on 24 hours per day while being underutilised or even idle. This thesis analyzes the energy consumption within office computing environments and suggests an energy-efficient virtualized office environment. The office environment is virtualized to achieve flexible virtualized office resources that enable an energy-based resource management. This resource management stops idle services and idle hosts from consuming resources within the office and consolidates utilised office services on office hosts. This increases the utilisation of some hosts while other hosts are turned off to save energy. The suggested architecture is based on a decentralized approach that can be applied to all kinds of office computing environments, even if no centralized data centre infrastructure is available.
    [Show full text]
  • Aware, Workstation-Based Distributed Database System
    THE ARCHITECTURE OF AN AUTONOMIC, RESOURCE- AWARE, WORKSTATION-BASED DISTRIBUTED DATABASE SYSTEM Angus Macdonald PhD Thesis February 2012 Abstract Distributed software systems that are designed to run over workstation machines within organisations are termed workstation-based. Workstation-based systems are characterised by dynamically changing sets of machines that are used primarily for other, user-centric tasks. They must be able to adapt to and utilize spare capacity when and where it is available, and ensure that the non-availability of an individual machine does not affect the availability of the system. This thesis focuses on the requirements and design of a workstation-based database system, which is motivated by an analysis of existing database architectures that are typically run over static, specially provisioned sets of machines. A typical clustered database system — one that is run over a number of specially provisioned machines — executes queries interactively, returning a synchronous response to applications, with its data made durable and resilient to the failure of machines. There are no existing workstation-based databases. Furthermore, other workstation-based systems do not attempt to achieve the requirements of interactivity and durability, because they are typically used to execute asynchronous batch processing jobs that tolerate data loss — results can be re-computed. These systems use external servers to store the final results of computations rather than workstation machines. This thesis describes the design and implementation of a workstation-based database system and investigates its viability by evaluating its performance against existing clustered database systems and testing its availability during machine failures. ACKNOWLEDGEMENTS I’d like to thank my supervisors, Professor Alan Dearle and Dr Graham Kirby, for the opportunities, the support, and the education that they have given me.
    [Show full text]
  • Providing High Availability for SAP Resources with Oracle Clusterware 11 Release 2
    Providing High Availability for SAP Resources with Oracle Clusterware 11 Release 2 An Oracle White Paper September 2011 Document Version 6.0 Providing High Availability for SAP Resources Overview of High Availability for SAP Resources.................................................... 3 New Functionality...................................................................................................... 3 SAP Support for High Availability ............................................................................ 4 Installation and Management ..................................................................................... 7 Overview Of Installation and Configuration.............................................................. 8 Functionality............................................................................................................. 13 Conclusion................................................................................................................ 16 Worked Example...................................................................................................... 17 Appendix 1 – Sample profile scripts........................................................................ 22 Appendix 2 – Troubleshooting and Log Files.......................................................... 24 Appendix 2 - SAPCTL Bill of Materials.................................................................. 25 Appendix 3 – CRS resources and types ................................................................... 25 Appendix 4 –
    [Show full text]
  • Using Oracle Goldengate 12C for Oracle Database
    An Oracle White Paper Updated September 2013 Using Oracle GoldenGate 12c for Oracle Database Using Oracle GoldenGate 12c for Oracle Database Executive Overview ........................................................................... 2 Introduction ....................................................................................... 3 Architecture Overview ....................................................................... 4 Oracle GoldenGate Capture .......................................................... 5 Oracle GoldenGate Trail Files ....................................................... 6 Oracle GoldenGate Delivery .......................................................... 7 Oracle GoldenGate Manager ......................................................... 9 Associated Products ...................................................................... 9 One Platform, Many Solutions ......................................................... 11 Zero Downtime Migrations and Upgrades .................................... 12 Query Offloading ......................................................................... 12 Disaster Recovery and Data Protection ....................................... 13 Active-Active Database Replication ............................................. 13 Operational Reporting and Real-Time Data Warehousing ........... 13 Data Distribution and Synchronization for OLTP Systems ........... 14 Oracle GoldenGate for Oracle Database ......................................... 15 Capture (Extract) ........................................................................
    [Show full text]
  • Providing High Availability for SAP Resources
    Providing High Availability for SAP Resources An Oracle White Paper April 2006 Providing High Availability for SAP Resources Overview of High Availability for SAP Resources .......................................3 SAP Support for High Availability..................................................................3 Installation and Management ...........................................................................5 Overview Of Installation and Configuration.................................................6 Functionality.......................................................................................................9 Usage ...............................................................................................................9 Conclusion........................................................................................................ 12 W orked Example............................................................................................. 13 Appendix 1 – Standard SAP Script Modifications..................................... 18 Script: startsap............................................................................................. 18 Script: stopsap............................................................................................. 21 Appendix 2 – Sample profile scripts - ENQUEUE Service (ASC)......... 23 Appendix 3 – Sample profile scripts - REPLICATION Service (ENR)25 Appendix 4 – Troubleshooting and Log Files............................................ 27 Appendix 5 - SAPCTL Bill of Materials.....................................................
    [Show full text]
  • Magic Quadrant for Data Warehouse Database Management Systems
    Magic Quadrant for Data Warehouse Database Management Systems Gartner RAS Core Research Note G00209623, Donald Feinberg, Mark A. Beyer, 28 January 2011, RV5A102012012 The data warehouse DBMS market is undergoing a transformation, including many acquisitions, as vendors adapt data warehouses to support the modern business intelligence and analytic workload requirements of users. This document compares 16 vendors to help you find the right one for your needs. WHAT YOU NEED TO KNOW Despite a troubled economic environment, the data warehouse database management system (DBMS) market returned to growth in 2010, with smaller vendors gaining in acceptance. As predicted in the previous iteration of this Magic Quadrant, 2010 brought major acquisitions, and several of the smaller vendors, such as Aster Data, Ingres and Vertica, took major strides by addressing specific market needs. The year also brought major market growth from data warehouse appliance offerings (see Note 1), with both EMC/Greenplum and Microsoft formally introducing appliances, and IBM, Oracle and Teradata broadening their appliance lines with new offerings. Although we believe that much of the growth was due to replacements of aging or performance-constrained data warehouse environments, we also think that the business value of using data warehouses for new applications such as performance management and advanced analytics has driven — and is driving — growth. All the vendors have stepped up their marketing efforts as the competition has grown. End-user organizations should ignore marketing claims about the applicability and performance capabilities of solutions. Instead, they should base their decisions on customer references and proofs of concept (POCs) to ensure that vendors’ claims will hold up in their environments.
    [Show full text]
  • Oracle Database Net Services Reference, 12C Release 1 (12.1) E17611-13
    Oracle®[1] Database Net Services Reference 12c Release 1 (12.1) E17611-13 December 2014 Oracle Database Net Services Reference, 12c Release 1 (12.1) E17611-13 Copyright © 2002, 2014, Oracle and/or its affiliates. All rights reserved. Primary Author: Caroline Johnston Contributor: The Oracle Database 12c documentation is dedicated to Mark Townsend, who was an inspiration to all who worked on this release. Contributors: Robert Achacoso, Abhishek Dadhich, Santanu Datta, Steve Ding, Feroz Khan, Peter Knaggs, Bhaskar Mathur, Scot McKinley, Ed Miner, Sweta Mogra, Srinivas Pamu, Kant Patel, Hector Pujol, Murali Purayathu, Karthik Rajan, Saravanakumar Ramasubramanian, Sudeep Reguna, Ching Tai, Norman Woo This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S.
    [Show full text]
  • Carrier Grade Linux Requirements Definition
    Carrier Grade Linux Requirements Definition The Linux Foundation Version 5.0 1796 18th Street S u i t e C Prepared by the Carrier Grade Linux Working Group San Francisco CA 94107, USA Copyright (c) 2005, 2006, 2007, 2011 by The Linux +1 (415) 723 - 9 7 0 9 Foundation. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is available at http://www.opencontent.org/opl.shtml/). Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. Linux is a Registered Trademark of Linus Torvalds. Other company, product, or service names may be the trademarks of others. CONTRIBUTORS TO THE CGL 5.0 REQUIREMENTS DEFINITION INCLUDE (IN ALPHABETICAL ORDER): Last Name First Name Company Anderson Matt HP Anderson Tim MontaVista Software Awad Majid Intel Aziz Khalid HP Badovinatz Peter IBM Bozarth Brad Cisco Cauchy Dan MontaVista Software Chacron Eric Alcatel Chen Terence Intel Cherry John OSDL Christopher Johnson Sun Microsystems Cihula Jospeh Intel Cress Andrew Intel Dague Sean IBM Dake Steven MontaVista Software Flaxa Ralf Novell Fleischer Julie Intel Fleischer Julie OSDL Fox Kevin Sun Microsystems Gross Mark Intel Haddad Ibrahim Ericsson Heber Troy HP Howell David P. Intel Hu Michael Radisys Ikebe Takashi NTT Ishitsuka Seiichi NEC Jagana Venkata IBM Johnson Christopher P. Sun Microsystems Kevin Fox Sun Microsystems Kimura Masato NTT Comware Krauska Joel Cisco Kukkonen Mika Nokia La Monte.H.P Yarrol Timesys Lavonius Ville Nokia Liu Bing Wei Intel Lynch Rusty Intel * MacDonald Joe Wind River Systems Manas Saksena Timesys Nakayama Mitsuo NEC Peter-Gonzalez Inaky Intel Pourzandi Makan Ericsson Rossi Frederic Eicsson Saksena Manas Timesys Sakuma Junichi OSDL Saskena Manas Timesys Seiler Glenn Wind River Systems Smarduch Mario Motorola Takamiya Noriaki NTT Software Weijers Gé Witham Timothy D.
    [Show full text]