DOCSLIB.ORG

Oracle® Exadata Database Machine Error Message Reference Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Oracle® Exadata Database Machine Error Message Reference Guide Oracle® Exadata Database Machine Error Message Reference Guide 21.2 F29253-03 June 2021 Oracle Exadata Database Machine Error Message Reference Guide, 21.2 F29253-03 Copyright © 2019, 2021, Oracle and/or its affiliates. Primary Author: Peter Fusek 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 embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle. Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Conventions v 1 Error and Alert Messages 1.1 Understanding Alert, Incident, and Trace Files 1-1 1.1.1 About Alert Files 1-2 1.1.2 About Trace Files 1-2 1.1.3 Automatic Diagnostic Repository (ADR) 1-2 1.1.3.1 About Incidents and Incident Packages 1-3 1.1.3.2 Diagnostic File Locations 1-4 1.1.4 Managing Diagnostic Files 1-4 1.2 Alert Messages 1-5 1.2.1 Format of Alert Messages for E-mail Notification 1-5 1.2.2 Format of Alert Messages for SNMP Notification 1-5 1.2.3 Threshold Alert Messages 1-6 1.2.4 ADR Alert Messages 1-7 1.3 Using Diagnostic Packages 1-7 1.4 Contacting Oracle Support Services 1-9 2 Oracle Exadata System Software Error Messages 2.1 CELL-00001 to CELL-00500 2-1 2.2 CELL-00501 to CELL-01000 2-17 2.3 CELL-01001 to CELL-01500 2-18 2.4 CELL-01501 to CELL-02000 2-18 2.5 CELL-02001 to CELL-02500 2-25 2.6 CELL-02501 to CELL-03000 2-29 2.7 CELL-03001 to CELL-03500 2-69 2.8 CELL-03501 to CELL-04000 2-69 iii 2.9 CELL-04001 to CELL-04500 2-70 2.10 CELL-04501 to CELL-05000 2-70 2.11 CELL-05001 to CELL-05500 2-85 2.12 CELL-05501 to CELL-06000 2-86 2.13 CELL-06001 to CELL-06200 2-87 3 Oracle Exadata Database Machine Command-Line Interface Error Messages 3.1 DBM-00001 to DBM-00500 3-1 3.2 DBM-10001 to DBM-10500 3-6 4 ExaCLI Error Messages 5 Hardware Alert Messages for Oracle Exadata Database Machine and Oracle Exadata Rack 5.1 HALRT-00001 to HALRT-00500 5-2 5.2 HALRT-00513 to HALRT-00600 5-5 5.3 HALRT-00616 to HALRT-00700 5-6 5.4 HALRT-00717 to HALRT-00800 5-6 5.5 HALRT-00912 to HALRT-01000 5-7 5.6 HALRT-01001 to HALRT-01200 5-8 5.7 HALRT-01209 to HALRT-01300 5-33 5.8 HALRT-01301 to HALRT-01400 5-37 5.9 HALRT-01401 to HALRT-01500 5-37 5.10 HALRT-02001 to HALRT-02100 5-42 5.11 HALRT-02101 to HALRT-02200 5-45 5.12 HALRT-02401 to HALRT-02550 5-53 5.13 HALRT-10001 to HALRT-10500 5-54 5.14 HALRT-10503 to HALRT-11000 5-58 5.15 Generic Actions for Alert Messages: HALRT-11001 to HALRT-11100 5-60 5.16 HALRT-20000 to HALRT-21000 5-61 6 MS REST Servlet Error Messages 7 Software Alert Messages iv Preface This guide describes Oracle Exadata Database Machine for online transaction processing (OLTP) and enterprise data warehousing. It includes information about the error messages you might encounter using the tools included with Oracle Exadata Database Machine. • Audience • Documentation Accessibility • Diversity and Inclusion • Conventions Audience This guide is intended for Oracle Exadata Database Machine customers and those responsible for configuring, maintaining, and troubleshooting Oracle Exadata Database Machine. Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc. Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired. Diversity and Inclusion Oracle is fully committed to diversity and inclusion. Oracle respects and values having a diverse workforce that increases thought leadership and innovation. As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation. We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve. Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation. Conventions The following text conventions are used in this document: v Preface Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. $ prompt The dollar sign ($) prompt indicates a command run as the oracle user. # prompt The pound (#) prompt indicates a command that is run as the root user. vi 1 Error and Alert Messages The various software components of Oracle Exadata System Software generate error and alert messages. • Understanding Alert, Incident, and Trace Files Alert, incident, and trace files provide a diagnostic record of useful information. • Alert Messages • Using Diagnostic Packages The DiagPack diagnostic package contains logs and traces that are useful for troubleshooting all type of issues for Oracle Exadata Database Machine. • Contacting Oracle Support Services Some error messages or alerts recommend contacting Oracle Support Services to report a problem. Related Topics • Using Messages • Diagnosing and Resolving Problems 1.1 Understanding Alert, Incident, and Trace Files Alert, incident, and trace files provide a diagnostic record of useful information. Alert files contain information about internal errors and administrative tasks. Incident files contain information about single occurrences. Trace files can contain information about server and background processes. • About Alert Files An alert file is a log file that records information about internal errors and administrative activities, such as backups. • About Trace Files A trace file is created each time an Oracle instance starts or an unexpected event occurs in a user process or background process.
Load more

Recommended publications
  • Linux from Scratch 版本 R11.0-36-中⽂翻译版 发布于 2021 年 9 ⽉ 21 ⽇
    Linux From Scratch 版本 r11.0-36-中⽂翻译版 发布于 2021 年 9 ⽉ 21 ⽇ 由 Gerard Beekmans 原著 总编辑：Bruce Dubbs Linux From Scratch: 版本 r11.0-36-中⽂翻译版 : 发布于 2021 年 9 ⽉ 21 ⽇ 由 由 Gerard Beekmans 原著和总编辑：Bruce Dubbs 版权所有 © 1999-2021 Gerard Beekmans 版权所有 © 1999-2021, Gerard Beekmans 保留所有权利。 本书依照 Creative Commons License 许可证发布。 从本书中提取的计算机命令依照 MIT License 许可证发布。 Linux® 是Linus Torvalds 的注册商标。 Linux From Scratch - 版本 r11.0-36-中⽂翻译版 ⽬录 序⾔ .................................................................................................................................... viii i. 前⾔ ............................................................................................................................ viii ii. 本书⾯向的读者 ............................................................................................................ viii iii. LFS 的⽬标架构 ............................................................................................................ ix iv. 阅读本书需要的背景知识 ................................................................................................. ix v. LFS 和标准 ..................................................................................................................... x vi. 本书选择软件包的逻辑 .................................................................................................... xi vii. 排版约定 .................................................................................................................... xvi viii. 本书结构 .................................................................................................................
    [Show full text]
  • Basic Performance Measurements of the Intel Optane DC Persistent Memory Module
    Basic Performance Measurements of the Intel Optane DC Persistent Memory Module Or: It’s Finally Here! How Fast is it? Joseph Izraelevitz Jian Yang Lu Zhang Juno Kim Xiao Liu Amirsaman Memaripour Yun Joon Soh Zixuan Wang Yi Xu Subramanya R. Dulloor Jishen Zhao Steven Swanson* Computer Science & Engineering University of California, San Diego arXiv:1903.05714v3 [cs.DC] 9 Aug 2019 *Correspondence should be directed to [email protected]. Copyright © 2019 the authors. 1 2019-08-09 7041bc9 Abstract After nearly a decade of anticipation, scalable nonvolatile memory DIMMs are finally commercially available with the release of the Intel® Optane™ DC Persistent Memory Module (or just “Optane DC PMM”). This new nonvolatile DIMM supports byte-granularity accesses with access times on the order of DRAM, while also providing data storage that survives power outages. This work comprises the first in-depth, scholarly, performance review of Intel’s Optane DC PMM, exploring its capabilities as a main memory device, and as persistent, byte-addressable memory exposed to user-space applications. For the past several months, our group has had access to machines with Optane DC memory and has investigated the Optane DC PMM’s performance characteristics. This report details the chip’s performance under a number of modes and scenarios, and across a wide variety of both micro- and macro-scale benchmarks. In total, this report represents approximately 330 hours of machine time. Optane DC memory occupies a tier in-between SSDs and DRAM. It has higher latency (346 ns) than DRAM but lower latency than an SSD. Unlike DRAM, its bandwidth is asymmetric with respect to access type: for a single Optane DC PMM, its max read bandwidth is 6.6 GB/s, whereas its max write bandwidth is 2.3 GB/s.
    [Show full text]
  • Object Storage on Berkeley DB1
    Object Storage on Berkeley DB1 Casey Marshall University of California, Santa Cruz CMPS 229: Storage Systems Abstract took one person less than three months to write a fairly stable and efficient object store, the benefits We have implemented an object storage system, of using an existing, stable system are quite clear. intended to simulate the operation of an Object We also believe that robust, simple, and scalable Storage Device (OSD), on Berkeley DB, a simple storage systems built on top of database systems database library distributed by Oracle Corporation such as Berkeley DB are feasible. (formerly Sleepycat Software) [1]. This object storage layer is used in the Ceph [2] distributed file system as an alternative to the EBOFS object 2 Implementation storage system. Our results indicate that object The implementation of our object store is as an storage systems built on Berkeley DB provide implementation of the C++ class ObjectStore, good performance for many small objects, and that Ceph uses internally for its object storage. competitive performance for large objects; inte- The ObjectStore interface provides a simple grating this system into Ceph has revealed a few set of commands that emulate the command set of performance problems. the T10 object storage specification [3]. These commands fall into the following logical groups: 1 Introduction 1. Object storage commands. These include ba- Ceph is an advanced, distributed, scalable file sys- sic operations for reading, writing, and query- tem being developed at UCSC. Ceph uses smart ing objects. Objects are plain byte sequences, object storage devices managed by an object dis- and are referenced by 128-bit object identifi- tribution and lookup layer called RADOS (reli- ers.
    [Show full text]
  • LFS-BOOK.Pdf
    Linux From Scratch Версия 7.3 Автор Gerard Beekmans Редакторы Matthew Burgess и Bruce Dubbs Перевод Иван Лабутин Linux From Scratch: Версия 7.3 by Автор Gerard Beekmans, Редакторы Matthew Burgess и Bruce Dubbs, Перевод Иван Лабутин Copyright © 1999-2013 Gerard Beekmans Copyright © 1999-2013, Gerard Beekmans Все права защищены. Эта книга выпущена под лицензией Creative Commons License. Команды для компьютера могут быть извлечены из книги под лицензией MIT License. Linux® зарегистрированная торговая марка Linus Torvalds. Linux From Scratch - Версия 7.3 Содержание Пролог ......................................................................................................................... viii i. Предисловие ........................................................................................................ viii ii. Кому адресована эта книга? ............................................................................... ix iii. Целевые архитектуры LFS .................................................................................. x iv. LFS и стандарты .................................................................................................. x v. Пояснения к выбранным пакетам ..................................................................... xii vi. Необходимые знания ....................................................................................... xvii vii. Требования к хост-системе ........................................................................... xviii viii. Соглашения, используемые в книге .............................................................
    [Show full text]
  • Model Based Fuzzing of the WPA3 Dragonfly
    Humboldt-Universität zu Berlin Mathematisch-Naturwissenschaftliche Fakultät Institut für Informatik Model based fuzzing of the WPA3 Dragonfly handshake Masterarbeit zur Erlangung des akademischen Grades Master of Science (M. Sc.) eingereicht von: Nikolai Philipp Tschacher geboren am: 1. Mai 1991 geboren in: Tübingen Gutachter/innen: Prof. Dr. Jens-Peter Redlich Prof. Dr. Björn Scheuermann eingereicht am: verteidigt am: Contents 1 Introduction1 1.1 Motivation..................................1 1.2 Objectives..................................2 1.3 WPA3....................................3 1.4 Fuzzing Methodology............................5 1.4.1 Fuzzing Strategy.......................... 10 1.5 Related Work................................. 11 2 Cryptographic Fundamentals 14 2.1 Public-key Cryptosystems based on the Discrete Logarithm Problem. 14 2.2 Elliptic Curve Cryptosystems....................... 20 3 The SAE Handshake 23 3.1 SAE is a PAKE Scheme.......................... 23 3.2 Dragonfly.................................. 24 3.3 Deriving the Password Element...................... 28 3.4 Commit Exchange............................. 28 3.5 Confirm Exchange............................. 30 3.6 Security................................... 30 3.7 Practical Attacks against SAE....................... 31 4 Fuzzing Environment 36 4.1 Kernel 802.11 Architecture......................... 37 4.2 Using Virtualization and Emulation Software............... 37 4.3 Virtual Wi-Fi radios with mac80211_hwsim ............... 42 4.3.1 WPA3-SAE with mac80211_hwsim
    [Show full text]
  • LFS-BOOK-10.1.Pdf
    Linux From Scratch Version 10.1 Published March 1st, 2021 Created by Gerard Beekmans Managing Editor: Bruce Dubbs Linux From Scratch: Version 10.1 : Published March 1st, 2021 by Created by Gerard Beekmans and Managing Editor: Bruce Dubbs Copyright © 1999-2021 Gerard Beekmans Copyright © 1999-2021, Gerard Beekmans All rights reserved. This book is licensed under a Creative Commons License. Computer instructions may be extracted from the book under the MIT License. Linux® is a registered trademark of Linus Torvalds. Linux From Scratch - Version 10.1 Table of Contents Preface ......................................................................................................................................................................... viii i. Foreword ............................................................................................................................................................ viii ii. Audience ........................................................................................................................................................... viii iii. LFS Target Architectures .................................................................................................................................. ix iv. Prerequisites ........................................................................................................................................................ x v. LFS and Standards .............................................................................................................................................
    [Show full text]
  • Building Key-Value Stores Using Fragmented Log-Structured Merge
    PebblesDB: Building Key-Value Stores using Fragmented Log-Structured Merge Trees Pandian Raju Rohan Kadekodi University of Texas at Austin University of Texas at Austin Vijay Chidambaram Ittai Abraham University of Texas at Austin and VMware Research VMware Research ABSTRACT Key-value stores such as LevelDB and RocksDB offer excel- lent write throughput, but suffer high write amplification. The write amplification problem is due to the Log-Structured Merge Trees data structure that underlies these key-value stores. To remedy this problem, this paper presents a novel data structure that is inspired by Skip Lists, termed Frag- mented Log-Structured Merge Trees (FLSM). FLSM intro- Figure 1: Write Amplification. The figure shows the duces the notion of guards to organize logs, and avoids total write IO (in GB) for different key-value stores rewriting data in the same level. We build PebblesDB, a high- when 500 million key-value pairs (totaling 45 GB) are performance key-value store, by modifying HyperLevelDB inserted or updated. The write amplification is indi- to use the FLSM data structure. We evaluate PebblesDB us- cated in parenthesis. ing micro-benchmarks and show that for write-intensive ACM Reference Format: workloads, PebblesDB reduces write amplification by 2.4-3× Pandian Raju, Rohan Kadekodi, Vijay Chidambaram, and Ittai Abra- compared to RocksDB, while increasing write throughput by ham. 2017. PebblesDB: Building Key-Value Stores using Fragmented 6.7×. We modify two widely-used NoSQL stores, MongoDB Log-Structured Merge Trees. In Proceedings of ACM Symposium and HyperDex, to use PebblesDB as their underlying storage on Operating Systems Principles (SOSP’17).
    [Show full text]
  • Ait 513 Advanced Programming in Bioinformatics 3 (1+2)
    AIT 513 ADVANCED PROGRAMMING IN BIOINFORMATICS 3 (1+2) Objective: Looking to volume and complexity of biological data, advanced programming skills are required for researchers in order to get the most out of their data analyses. This course will provide the expanded programming skills necessary to develop software that can exploit the complex information landscape of bioinformatics. Theory: UNIT I Introduction to Molecular Biology, Central Dogma, Sequencing technologies, etc., Introduction to different programming languages used in biological sciences,Perl , Python, R, Ruby etc. UNIT II Unix/Linux shell programming, Perl: Introduction, Scalar Data, Arrays and list Data, Control Structures harhes, Regular Expressions; Suboutines, File handles and file tests; Function;formats, Directory Access, Process management, Other data Transfomation; Finding a sub string, Extracting and replacing a sub string. Bio-Perl: Introduction, Architecture, Uses of bioperl ,: Introduction to python/ Bio-Python UNIT III R: open-source language and environment for statistical computing and graphics. UNIT IV Bioconductor - open-source software for the analysis of biomedical andgenomic data, mainly R packages.Analysis of microarray data, Next Generation Sequencing (NGS) data etc. UNIT V Parallel programming/ Computing – MapReduce , Interfaces with other languages: C, Java, Perl, Python, XML,etc. – Omega Project (www.omegahat.org) ,Formatting Data: sorting, Trasliteration Database manipulation:DBM Databases and DBM Harshes, Opening and closing DBM Harshes, Fixed-Length Random –Access Databases, Variable-Length (Text) Databases, Win32 Databases Interfaces. Practical: 1. Unix/Linux shell scripting 2. Active perf- 3. R, Map reduce Reference Books: 1. The R Project for Statistical Computing [http://www.R-project.org/]. 2. Perl.org [http://www.perl.org/].
    [Show full text]
  • An Overview of Attacks and Defences on Intelligent Connected Vehicles
    1 An Overview of Attacks and Defences on Intelligent Connected Vehicles Mahdi Dibaei, Xi Zheng, Member, IEEE, Kun Jiang, Member, IEEE, Sasa Maric, Robert Abbas, Member, IEEE, Shigang Liu, Member, IEEE, Yuexin Zhang, Member, IEEE, Yao Deng, Sheng Wen, Member, IEEE, Jun Zhang, Member, IEEE, Yang Xiang, Senior Member, IEEE, and Shui Yu, Senior Member, IEEE, Abstract—Cyber security is one of the most significant chal- policies are not followed by the industry standards for in- lenges in connected vehicular systems and connected vehicles vehicle and vehicular communications because of hardware are prone to different cybersecurity attacks that endanger pas- constraints and differences in network configuration [1], [2]. sengers’ safety. Cyber security in intelligent connected vehicles is composed of in-vehicle security and security of inter-vehicle Previous reports have illustrated highly practical wireless communications. Security of Electronic Control Units (ECUs) and attacks on core functions of vehicles and disengaging the the Control Area Network (CAN) bus are the most significant engine and the brakes [3], [4], [5], [6]. For instance, by parts of in-vehicle security. Besides, with the development of 4G hijacking the steering and brakes of a Ford Escape and a LTE and 5G remote communication technologies for vehicle-to- Toyota Prius, Miller and Valasek indicated that a vehicle everything (V2X) communications, the security of inter-vehicle communications is another potential problem. After giving a system is not just a simple machine of glass and steel [3]. short introduction to the architecture of next-generation vehicles In contrast, it is important to realize that it is also a hackable including driverless and intelligent vehicles, this review paper network of computers.
    [Show full text]
  • Data Persistence, Object Serialization, Dbm Package
    Data Persistence, object Serialization, dbm Package Gaurav Kr. suman MIT14 The word ‘persistence’ means "the continuance of an effect after its cause is removed". The term data persistence means it continues to exist even after the application has ended. Thus, data stored in a non-volatile storage medium such as, a disk file is a persistent data storage. Python's built-in file object returned by Python's built-in open() function has one important shortcoming. When opened with 'w' mode, the write() method accepts only the string object. That means, if you have data represented in any non-string form, the object of either in built-in classes (numbers, dictionary, lists or tuples) or other user-defined classes, it cannot be written to file directly. Before writing, you need to convert it in its string representation. numbers=[10,20,30,40] file=open('numbers.txt','w') file.write(str(numbers)) file.close() For a binary file, argument to write() method must be a byte object. For example, the list of integers is converted to bytes by bytearray() function and then written to file. numbers=[10,20,30,40] data=bytearray(numbers) file.write(data) file.close() To read back data from the file in the respective data type, reverse conversion needs to be done. file=open('numbers.txt','rb') data=file.read() print (list(data)) This type of manual conversion, of an object to string or byte format (and vice versa) is very cumbersome and tedious. It is possible to store the state of a Python object in the form of byte stream directly to a file, or memory stream and retrieve to its original state.
    [Show full text]
  • Installation Guide
    IBM Spectrum Protect for Linux Version 8.1.10 Installation Guide IBM Note: Before you use this information and the product it supports, read the information in “Notices” on page 191. This edition applies to version 8, release 1, modification 10 of IBM Spectrum® Protect (product numbers 5725-W98, 5725-W99, 5725-X15), and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 1993, 2020. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this publication..........................................................................................vii Who should read this guide........................................................................................................................vii Installable components............................................................................................................................. vii Publications .............................................................................................................................................. viii What's new.......................................................................................................... ix Part 1. Installing and upgrading the server.............................................................1 Chapter 1. Planning to install the IBM Spectrum Protect server................................................................3 What you should
    [Show full text]
  • LFS-BOOK-9.0.Pdf
    Linux From Scratch Version 9.0 Published September 1st, 2019 Created by Gerard Beekmans Managing Editor: Bruce Dubbs Linux From Scratch: Version 9.0 : Published September 1st, 2019 by Created by Gerard Beekmans and Managing Editor: Bruce Dubbs Copyright © 1999-2019 Gerard Beekmans Copyright © 1999-2019, Gerard Beekmans All rights reserved. This book is licensed under a Creative Commons License. Computer instructions may be extracted from the book under the MIT License. Linux® is a registered trademark of Linus Torvalds. Linux From Scratch - Version 9.0 Table of Contents Preface ......................................................................................................................................................................... viii i. Foreword ............................................................................................................................................................ viii ii. Audience ........................................................................................................................................................... viii iii. LFS Target Architectures .................................................................................................................................. ix iv. LFS and Standards ............................................................................................................................................. x v. Rationale for Packages in the Book ..................................................................................................................
    [Show full text]