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