Arcsde Configuration and Tuning Guide for Oracle

Total Page:16

File Type:pdf, Size:1020Kb

Arcsde Configuration and Tuning Guide for Oracle ArcSDE® Configuration and Tuning Guide for Oracle® ArcGIS® 9 Copyright © 1999-2004 ESRI All Rights Reserved. Printed in the United States of America. The information contained in this document is the exclusive property of ESRI. This work is protected under United States copyright law and the copyright laws of the given countries of origin and applicable international laws, treaties, and/or conventions. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying or recording, or by any information storage or retrieval system, except as expressly permitted in writing by ESRI. All requests should be sent to Attention: Contracts Manager, ESRI, 380 New York Street, Redlands, CA 92373-8100, USA. The information contained in this document is subject to change without notice. U. S. GOVERNMENT RESTRICTED/LIMITED RIGHTS Any software, documentation, and/or data delivered hereunder is subject to the terms of the License Agreement. In no event shall the U.S. Government acquire greater than RESTRICTED/LIMITED RIGHTS. At a minimum, use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR §52.227-14 Alternates I, II, and III (JUN 1987); FAR §52.227-19 (JUN 1987) and/or FAR §12.211/12.212 (Commercial Technical Data/Computer Software); and DFARS §252.227-7015 (NOV 1995) (Technical Data) and/or DFARS §227.7202 (Computer Software), as applicable. Contractor/Manufacturer is ESRI, 380 New York Street, Redlands, CA 92373-8100, USA. ESRI, ArcView, ArcIMS, ArcInfo Librarian, MapObjects, ArcInfo, ArcSDE, ArcCatalog, ArcMap, ArcToolbox, ArcStorm, and ArcGIS are trademarks, registered trademarks, or service marks of ESRI in the United States, the European Community, or certain other jurisdictions. Other companies and products mentioned herein are trademarks or registered trademarks of their respective trademark owners. Contents Contents iii Getting started 1 Tuning and configuring the Oracle instance 1 Arranging your data 2 Creating spatial data in an Oracle database 3 ArcSDE geodatabase maintenance 3 National language support 3 Backup and recovery 4 Essential Oracle configuring and tuning 5 How much time should you spend tuning? 5 Reducing disk I/O contention 6 Setting the Oracle initialization parameters 28 Enabling the optional Oracle startup trigger 31 Updating Oracle statistics 32 Updating ArcSDE compressed binary statistics 33 Configuring DBTUNE storage parameters 35 The DBTUNE table 36 Managing the DBTUNE table 38 Using the DBTUNE table 40 Defining the storage parameters 42 Arranging storage parameters by keyword 46 Oracle Spatial DBTUNE storage parameters 62 Oracle default parameters 66 Converting previous versions of SDE storage parameters into the DBTUNE table 66 The complete list of ArcSDE 9 storage parameters 69 Managing tables, feature classes, and raster columns 79 Data creation 79 Creating and populating raster columns 85 Creating views 85 Exporting data 86 Schema modification 86 Choosing an ArcSDE log file configuration 86 iv ArcSDE Configuration and Tuning Guide for Oracle Using the ArcGIS Desktop applications 88 Efficiently registering large business tables with ArcSDE 92 National language support 97 Oracle database character sets 97 Setting the NLS_LANG variable on the client 97 Setting the NLS_LANG for the ArcSDE server 100 Backup and recovery 103 Recording database changes 103 Database backup 108 Database recovery 111 Appendix A: Estimating the size of your tables and indexes The business table 113 The feature table 114 The spatial index table 115 The version delta tables 116 The network tables 117 The raster data tables 121 The indexes 123 Appendix B: Storing raster data Raster schema 128 Appendix C: ArcSDE compressed binary Compressed binary 137 The spatial grid index 140 Creating tables with compressed binary schema 146 Tuning LOB storage 147 Referential integrity 148 Appendix D: Oracle Spatial geometry type What is Oracle Spatial? 149 How does ArcSDE use Oracle Spatial? 151 How ArcSDE uses existing Oracle Spatial tables 156 Interoperability considerations 158 Appendix E: The well-known binary representation Numeric type definitions 164 XDR (big endian) encoding of numeric types 164 NDR (little endian) encoding of numeric types 164 Conversion between the NDR and XDR representations of WKB geometry 164 Description of WKBGeometry byte streams 165 Contents v Assertions for well-known binary representation for geometry 169 Appendix F: Storing locators 71 Locator schema 172 Appendix G: Making a direct connection What files do you need? 181 How to get your database set up files 182 Environment variables 183 Client/database compatability 185 Registration and authorization 185 Setting up clients for Oracle direct connect 186 Index vi ArcSDE Configuration and Tuning Guide for Oracle CHAPTER 1 Getting started Creating and populating a geodatabase is arguably a simple process, especially if you use ESRI® ArcCatalogTM or ArcToolboxTM to load the data. So why is there a configuration and tuning guide? Well, while database creation and data loading can be relatively simple, the resulting performance may not be acceptable. It requires some effort to build a database that performs optimally. Also, as an Oracle® user, you have some choices for storing the geometry of your spatial data. This book provides instruction for configuring the physical storage parameters of your data in the database management system (DBMS) as well as information about the available options you have to store the geometry. This book also provides some important guidelines for configuring and tuning the Oracle instance itself. Tuning and configuring the Oracle instance Building an efficient geodatabase involves properly tuning and configuring the Oracle instance and proper arrangement and management of the database’s tables and indexes. Chapter 2, ‘Essential Oracle configuring and tuning’, teaches you how to do just that. Chapter 2 lists the necessary steps to create a geodatabase. You will learn how to properly: • Create an Oracle database. • Create the tablespaces that will store your tables and indexes. • Tune the Oracle instance that will mount and open the database. 2 ArcSDE Configuration and Tuning Guide for Oracle • Manage the optimization statistics of the tables and indexes after they have been created and populated. Arranging your data Every table and index created in a database has a storage configuration. How you store your tables and indexes affects your database’s performance. DBTUNE storage parameters How is the storage configuration of the tables and indexes controlled? ArcSDE® reads storage parameters from the SDE.DBTUNE table to define physical data storage parameters of ArcSDE tables and indexes. The storage parameters are grouped under configuration keywords. You assign configuration keywords to your data objects (tables and indexes) when you create them from an ArcSDE client program. The initial source of storage parameters is the dbtune.sde file found under the ArcSDE etc directory. When the ArcSDE sdesetupora* setup command executes, the configuration parameters are read from the file and written into the DBTUNE table. Most ArcSDE storage parameters are configuration strings and represent the entire storage configuration for a table or index. Most SDE.DBTUNE storage parameters hold the parameters of an Oracle CREATE TABLE or CREATE INDEX statement. The sdedbtune command provides the ArcSDE administrator with an easy way to maintain the SDE.DBTUNE table. The sdedbtune command exports and imports all the records of the SDE.DBTUNE table to a file in the ArcSDE etc directory. The ArcSDE installation creates the SDE.DBTUNE table. If the dbtune.sde file is absent or empty, sdesetupora* creates the SDE.DBTUNE table and populates it with default configuration keywords representing the minimum ArcSDE configuration. In almost all cases, you will populate the SDE.DBTUNE table with specific storage parameters for your database. Chapter 3, ‘Configuring DBTUNE storage parameters’, describes in detail the SDE.DBTUNE table and all possible storage parameters and default configuration keywords. Spatial data storage choices The SDE.DBTUNE storage parameter GEOMETRY_STORAGE allows you to select from three possible spatial column storage formats. The three possible storage formats are: • ArcSDE compressed binary with LONG RAW. The ArcSDE geometry is stored in a ‘LONG RAW’ column in a separate feature table. A business table’s spatial column is a foreign key reference to the records of a feature table. This is the default spatial storage format for ArcSDE. Chapter 1—Getting started 3 • ArcSDE compressed binary with binary large object (BLOB). The schema of this storage format is the same as the previous one except that the geometry is stored in the BLOB data type. • Oracle Spatial geometry type. The object-relational model extends the database model to include an SDO_GEOMETRY type. Under this storage format, the spatial column is an SDO_GEOMETRY data type, and no foreign key reference to another table storing a geometry column is required. These spatial storage choices are discussed more fully later in this book. Appendix C, ‘ArcSDE compressed binary’, describes the ArcSDE compressed binary for both LONG RAW and BLOB. Appendix D, ‘Oracle Spatial geometry type’, describes ArcSDE support for the Oracle Spatial storage format. Creating spatial data in an Oracle database ArcCatalog and ArcToolbox are graphical user interfaces (GUIs) specifically designed
Recommended publications
  • Windows NLS Considerations Version 2.1
    Windows NLS Considerations version 2.1 Radoslav Rusinov [email protected] Windows NLS Considerations Contents 1. Introduction ............................................................................................................................................... 3 1.1. Windows and Code Pages .................................................................................................................... 3 1.2. CharacterSet ........................................................................................................................................ 3 1.3. Encoding Scheme ................................................................................................................................ 3 1.4. Fonts ................................................................................................................................................... 4 1.5. So Why Are There Different Charactersets? ........................................................................................ 4 1.6. What are the Difference Between 7 bit, 8 bit and Unicode Charactersets? ........................................... 4 2. NLS_LANG .............................................................................................................................................. 4 2.1. Setting the Character Set in NLS_LANG ............................................................................................ 4 2.2. Where is the Character Conversion Done? .........................................................................................
    [Show full text]
  • Zeichensätze/ Character Sets Anhang/ Appendix
    BA6x Zeichensätze/ Character sets Anhang/ Appendix We would like to know Ihre Meinung/ Your your opinion on this opinion: publication. Please send us a copy of this page if you have any constructive criticism. We would like to thank you in advance for your comments. With kind regards, Uns interessiert Ihre Meinung zu dieser Druckschrift. Schicken Sie uns bitte eine Information, wenn Sie uns konstruktive Hinweise geben wollen: Dafür bedanken wir uns im voraus. Mit freundlichen Grüßen Wincor Nixdorf International GmbH Dokumentation RD PD1 Rohrdamm 7 Haus 16 D-13629 Berlin eMail: [email protected] Bestellnummer dieser Druckschrift/Order No.: 017501544 08 BA6x Be die ner an zei ge/ Cas hier Dis play Zei chen sät ze/Cha rac ter Sets An hang/ Ap pen dix Pen ti um™ ist ein eingetragenes Wa ren zei chen der In tel Cor po ra ti on MS-DOS™, Wind ows 95™, Wind ows 98™, Wind ows NT™ und Wind ows CE™ sind eingetragene Wa ren zei chen der Mi cro soft Corpo rati on BEET LE™ ist ein ein ge tra ge nes Wa ren zeichen der Win cor Nix dorf In ter na tio nal GmbH Co py right © Win cor Nix dorf In ter na tio nal GmbH, 2008 Alle Rech te vor be hal ten, ins be son de re (auch aus zugs wei se) die der Über set zung, des Nach drucks, Wie der ga be durch Ko pie ren oder ähn li che Ver fah ren. Zu wi der - hand lun gen ver pflich ten zu Scha dens er satz.
    [Show full text]
  • Network Working Group D. Spinellis Request for Comments: 1947 SENA S.A
    Network Working Group D. Spinellis Request for Comments: 1947 SENA S.A. Category: Informational May 1996 Greek Character Encoding for Electronic Mail Messages Status of This Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Overview and Rational This document describes a standard encoding for electronic mail [RFC822] containing Greek text and provides implementation guide- lines. The standard is based on MIME [RFC1521] and the ISO 8859-7 character encoding. Although the implementation of this standard is straightforward several non-standard but "functional" - though unlikely to inter-operate - alternatives are in common use. For this reason we highlight common implementation and mail user agent setup errors. Description In order to transfer Greek text via electronic mail the text is first translated into the ISO 8859-7 character set, and then encoded using either the Base64 (preferable for text that is mainly Greek) or the Quoted-Printable (justifiable in cases where some Greek words appear inside predominately Latin text) method, as defined in MIME. The following table provides most common Greek encodings (see also [RFC1345]): 0646 37 M7 51 MC 23 69 LG L1 G7 GO GC 28 97 Description ---- -- -- -- -- -- -- -- -- -- -- -- -- -- ----------- 0386 ea a2 86 cd 71 86 b6 Capital alpha with acute 0388 eb b8 8d ce 72 8d b8 Capital epsilon with acute 0389 ec b9 8f d7 73 8f b9 Capital eta with acute 038a ed ba 90 d8 75 90 ba Capital iota
    [Show full text]
  • Fonts & Encodings
    Fonts & Encodings Yannis Haralambous To cite this version: Yannis Haralambous. Fonts & Encodings. O’Reilly, 2007, 978-0-596-10242-5. hal-02112942 HAL Id: hal-02112942 https://hal.archives-ouvertes.fr/hal-02112942 Submitted on 27 Apr 2019 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. ,title.25934 Page iii Friday, September 7, 2007 10:44 AM Fonts & Encodings Yannis Haralambous Translated by P. Scott Horne Beijing • Cambridge • Farnham • Köln • Paris • Sebastopol • Taipei • Tokyo ,copyright.24847 Page iv Friday, September 7, 2007 10:32 AM Fonts & Encodings by Yannis Haralambous Copyright © 2007 O’Reilly Media, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (safari.oreilly.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Printing History: September 2007: First Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Fonts & Encodings, the image of an axis deer, and related trade dress are trademarks of O’Reilly Media, Inc.
    [Show full text]
  • Programming Guide
    A798II Thermal Receipt Printer Programming Guide Made under one or more of the following U.S. patents: 4886381, 5579043, 5613787, 5651624, 5713678, 5752779, 5789916, 5800080, 5879090, 5887999, 5975776, 6027266, 6085973, 6089450, 6129465, 6155483, 6404452, 6486902, 6504331, 5749277, 6722754, 6739773, 6784909. Federal Communications Commission (FCC) Radio Frequency Interference Statement Warning Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment. Note This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense. Information to the User This equipment must be installed and used in strict accordance with the manufacturer’s instructions. However, there is no guarantee that interference to radio communications will not occur in a particular commercial installation. If this equipment does cause interference, which can be determined by turning the equipment off and on, the user is encouraged to contact CognitiveTPG immediately. CognitiveTPG is not responsible for any radio or television interference caused by unauthorized modification of this equipment or the substitution or attachment of connecting cables and equipment other than those specified by CognitiveTPG.
    [Show full text]
  • Diebold Nixdorf TH250 Programmers Guide EN
    TH250 Thermal Printer Programmer’s Guide (Edition 2018) TH250 Thermal Printer Programmer’s Guide Edition 2018 All brand and product names mentioned in this document are registered trademarks of the respective owners. The reproduction, transmission or use of this document or its contents is not permitted without express authority. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Delivery subject to availability; technical modifications possible. Copyright © Diebold Nixdorf Contents About this Guide ....................................................................................................................... 1 How to use this guide ......................................................................................................................... 1 Where to find the basics .................................................................................................................... 1 Where to find advanced technical information ................................................................................. 1 Support 1 Diagnostics and Configuration ................................................................................................... 2 Start-up Diagnostics ........................................................................................................................ 2 Runtime Diagnostics ..........................................................................................................................
    [Show full text]
  • Naming Text Encodings to Demystify Them
    Naming Text Encodings to Demystify Them Document #: P1885R6 Date: 2021-08-14 Programming Language C++ Audience: LEWG Reply-to: Corentin Jabot <[email protected]> Peter Brett <[email protected]> If you can’t name it, you probably don’t know what it is If you don’t know what it is, you don’t know what it isn’t Tony Van Eerd Target C++23 Abstract For historical reasons, all text encodings mentioned in the standard are derived from a locale object, which does not necessarily match the reality of how programs and systems interact. This model works poorly with modern understanding of text, ie the Unicode model separates encoding from locales which are purely rules for formatting and text transformations but do not affect which characters are represented by a sequence of code units. Moreover, the standard does not provide a way to query which encodings are expected or used by the environment, leading to guesswork and unavoidable UB. This paper introduces the notions of literal encoding, environment encoding, and a way to query them. Examples Listing the encoding #include <text_encoding> #include <iostream> void print(const std::text_encoding & c) { std::cout << c.name() << " (iana mib: " << c.mib() << ")\n" << "Aliases:\n"; 1 for(auto && a : c.aliases()) { std::cout << '\t' << a << '\n'; } } int main() { std::cout << "Literal Encoding: "; print(std::text_encoding::literal()); std::cout << "Wide Literal Encoding: "; print(std::text_encoding::wide_literal()); std::cout << "environment Encoding: "; print(std::text_encoding::environment());
    [Show full text]
  • Thermal Printer
    TH210 Thermal Printer Programmer’s Guide (Edition 2018) Contents About this Guide ........................................................................................................................... 1 How to use this guide .................................................................................................................... 1 Where to find the basics ................................................................................................................ 1 Where to find advanced technical information .............................................................................. 1 Support 1 Diagnostics and Configuration ...................................................................................................... 2 Start-up Diagnostics ................................................................................................................... 2 Runtime Diagnostics ...................................................................................................................... 3 Remote Diagnostics ....................................................................................................................... 3 Accessing the remote diagnostic tallies ...................................................................................... 4 Indicators ...................................................................................................................................... 5 Error conditions and correcting them........................................................................................
    [Show full text]
  • City of Fort Lauderdale Contractor List
    City of Fort Lauderdale Contractor List CONTRACTOR ID CONTRACTOR TYPE CONTRACTOR NAME PHONE ADDRESS 1 ADDRESS 2 CITY STATE ZIP CAC057892 AIR CONDITIONING CONTRACTOR ADVANCE SOLAR AND SPA INC (954) 938-8507 990 NW 53 ST FORT LAUDERDALE FL 33309 CAC1817179 AIR CONDITIONING CONTRACTOR FRAITAS,JOSE M SR (561) 926-0422 4311 CRYSTAL LAKE DRIVE #307 POMPANO BEACH FL 33064 RA13067467 AIR CONDITIONING CONTRACTOR FROZE-ZONE (305) 299-7259 75 SW 116 AV MIAMI FL 33174 905712AX B - CNTY - ACOUSTIC CEILING A BEAUTIFUL CEILING (561) 391-1649 3333 S DIXIE HWY DELRAY BEACH FL 33483 009362AR B - CNTY - ACOUSTIC CEILING ATLANTIC INTERIOR SERVICES INC (561) 575-4499 208 N US HWY 1 #2 TEQUESTA FL 33469 10A16471X B - CNTY - ACOUSTIC CEILING LIBERTY INSULATION & FIREPROOFING (954) 491-9739 1050 NW 55 ST FORT LAUDERDALE FL 33309 07AL14007 B - CNTY - ALUMINUM SPECIALTY ABC ALUMINUM HOME IMPROVEMENT IN(954) 772-7002 5404 NW 10 TER FORT LAUDERDALE FL 33309 0310727AL B - CNTY - ALUMINUM SPECIALTY ALL AMERICAN ACCORDION RAIL & SCRE(754) 581-4236 1421 SE 4 AVE DEERFIELD BEACH FL 33441 08AL15198X B - CNTY - ALUMINUM SPECIALTY ALL FLORIDA SCREEN & SHUTTERS (954) 254-6089 2764 N DIXIE HWY WILTON MANORS FL 33305 0310901ALX B - CNTY - ALUMINUM SPECIALTY ALUMINUM SCREEN INSTALLERS INC (954) 463-9186 7351 DAVIE RD EXT HOLLYWOOD FL 33024-2421 978372ALX B - CNTY - ALUMINUM SPECIALTY AWARD ALUMINUM INC (954) 978-8803 359 SW 65 AVE MARGATE FL 33068-1002 08AL14782X B - CNTY - ALUMINUM SPECIALTY B & L SCREENING & SHUTTERS LLC (954) 579-5980 8542 SHADOWWOOD BLVD CORAL SPRINGS FL
    [Show full text]
  • SP700 Product Specifications
    Product Specifications Manual SP700 Series Rev. No. 0.14 Star Micronics Co., Ltd. Special Products Operating Division Contents 1. GENERAL DESCRIPTION 1-1 1.1 Features 1-1 1.2 Model Name Display Directions 1-2 2. GENERAL SPECIFICATIONS 2-1 2.1 Printing Specifications 2-1 2.2 Character Specifications 2-2 2.3 NV Logo Specifications 2-5 2.4 Paper Specifications 2-6 2.4.1 Tear Bar, Auto-cutter Specifications (Only with Horizontal Layout) 2-6 2.4.2 Take-up Mechanism Specifications 2-7 2.5 Black Mark Specifications 2-8 2.5.1 Overview of the Black Mark Sensor 2-8 2.5.2 Dimensions, Positions and Printing Ranges of Black Marks 2-8 2.5.3 Black Mark PCS Value 2-8 2.5.4 How to Use TOF 2-8 2.6 Ink Ribbon Specification 2-11 2.6.1 Specifications 2-11 2.6.2 Sub-ribbon 2-11 2.6.3 Sub-ribbon Replacement Method 2-11 2.7 Cutting Specification 2-12 2.7.1 Auto-cutter Specifications (SP742, SP747) 2-12 2.7.2 Changing from a Partial Cutter to a Full Cutter 2-12 2.7.3 Auto-cutter Precautions 2-14 2.7.4 Tear-bar Specifications (SP712, SP717) 2-14 2.8 Take-up Mechanism Specifications (SP712R, SP717R, SP742R, SP747R) 2-14 2.9 Electrical Specifications 2-14 2.9.1 Power Specification 2-14 2.9.2 Power Consumption 2-14 2.9.3 Current Consumption 2-15 2.10 Compatibility Ratings 2-15 2.11 Reliability Specifications 2-16 2.12 Environment Specifications 2-16 2.12.1 Ambient Environment 2-16 212.2 Storage Environment 2-16 2.12.3 Vibration Tests (When Packaged) 2-16 2.12.4 Drop Tests (When Packaged) 2-17 2.12.5 Static Electricity Tolerance (ESD) 2-17 2.12.6 AC Line Noise Tolerance 2-17 2.13 Noise 2-17 2.14 Dust 2-17 2.15 External Specifications 2-17 2.15.1 Case Specifications 2-17 2.15.2 Weight 2-17 2.15.3 External Dimensions 2-18 2.16 How to Set the Roll Paper 2-19 2.16.1 Tear-bar and Auto-cutter Specifications (SP712, SP717, SP742, SP747) 2-19 2.16.2 Take-up Mechanism Specifications (SP712R, SP717R, SP742R, SP747R) 2-20 2.16.3 Mounting the Accessory Roll Paper Guide 2-23 3.
    [Show full text]
  • Administering Oracle Goldengate
    Oracle® Database Administering Oracle GoldenGate 21c (21.1.0) F25360-02 April 2021 Oracle Database Administering Oracle GoldenGate, 21c (21.1.0) F25360-02 Copyright © 2017, 2021, Oracle and/or its affiliates. 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
    [Show full text]
  • 6 Java Overview of Oracle8i Java Support
    Oracle8i National Language Support Guide Release 2 (8.1.6) December 1999 Part No. A76966-01 National Language Support Guide, Release 2 (8.1.6) Part No. A76966-01 Copyright © 1996, 1999, Oracle Corporation. All rights reserved. Primary Author: Paul Lane Contributors: Winson Chu, Jason Durbin, Jessica Fan, Yu Gong, Josef Hasenberger, Claire Ho, Peter Linsley, Tom Portfolio, Den Raphaely, Linus Tanaka, Makoto Tozawa, Gail Yamanaka, Michael Yau, Hiro Yoshioka, Sergiusz Wolicki, Simon Wong Graphic Designer: Valarie Moore The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee’s responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs. The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation.
    [Show full text]