OpenEdge® Data Management: Database Administration ppt

OPENEDGE ® 10 PROGRESS ® OpenEdge ® Data Management: Database Administration © 2009 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved. These materials and all Progress® software products are copyrighted and all rights are reserved by Progress Software Corporation. The information in these materials is subject to change without notice, and Progress Software Corporation assumes no responsibility for any errors that may appear therein. The references in these materials to specific platforms supported are subject to change. Actional, Apama, Apama (and Design), Artix, Business Empowerment, DataDirect (and design), DataDirect Connect, DataDirect Connect64, DataDirect Technologies, DataDirect XML Converters, DataDirect XQuery, DataXtend, Dynamic Routing Architecture, EdgeXtend, Empowerment Center, Fathom, IntelliStream, IONA, IONA (and design), Making Software Work Together, Mindreef, ObjectStore, OpenEdge, Orbix, PeerDirect, POSSENET, Powered by Progress, PowerTier, Progress, Progress DataXtend, Progress Dynamics, Progress Business Empowerment, Progress Empowerment Center, Progress Empowerment Program, Progress OpenEdge, Progress Profiles, Progress Results, Progress Software Developers Network, Progress Sonic, ProVision, PS Select, SequeLink, Shadow, SOAPscope, SOAPStation, Sonic, Sonic ESB, SonicMQ, Sonic Orchestration Server, SonicSynergy, SpeedScript, Stylus Studio, Technical Empowerment, WebSpeed, Xcalia (and design), and Your Software, Our Technology–Experience the Connection are registered trademarks of Progress Software Corporation or one of its affiliates or subsidiaries in the U.S. and/or other countries. AccelEvent, Apama Dashboard Studio, Apama Event Manager, Apama Event Modeler, Apama Event Store, Apama Risk Firewall, AppsAlive, AppServer, ASPen, ASP-in-a-Box, BusinessEdge, Business Making Progress, Cache-Forward, DataDirect Spy, DataDirect SupportLink, Fuse, Fuse Mediation Router, Fuse Message Broker, Fuse Services Framework, Future Proof, GVAC, High Performance Integration, ObjectStore Inspector, ObjectStore Performance Expert, OpenAccess, Orbacus, Pantero, POSSE, ProDataSet, Progress ESP Event Manager, Progress ESP Event Modeler, Progress Event Engine, Progress RFID, Progress Software Business Making Progress, PSE Pro, SectorAlliance, SeeThinkAct, Shadow z/Services, Shadow z/Direct, Shadow z/Events, Shadow z/Presentation, Shadow Studio, SmartBrowser, SmartComponent, SmartDataBrowser, SmartDataObjects, SmartDataView, SmartDialog, SmartFolder, SmartFrame, SmartObjects, SmartPanel, SmartQuery, SmartViewer, SmartWindow, Sonic Business Integration Suite, Sonic Process Manager, Sonic Collaboration Server, Sonic Continuous Availability Architecture, Sonic Database Service, Sonic Workbench, Sonic XML Server, StormGlass, The Brains Behind BAM, WebClient, Who Makes Progress, and Your World. Your SOA. are trademarks or service marks of Progress Software Corporation or one of its affiliates or subsidiaries in the U.S. and other countries. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Any other trademarks contained herein are the property of their respective owners. For the latest documentation updates see OpenEdge Product Documentation on PSDN (http://communities.progress.com/ pcom/docs/DOC-16074 ). December 2009 Last updated with new content: Release 10.2B Product Code: 4496; R10.2B Third party acknowledgements — See the “Third party acknowledgements” section on page Preface–10. Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface–1 Part I Database Basics 1. Creating and Deleting Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1 Ways to create an OpenEdge database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2 Creating a database with PROSTRCT CREATE . . . . . . . . . . . . . . . . . . . . . . . . . 1–3 Creating a structure description file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3 Create a database structure extent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10 Adding schema to a void database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12 Creating a database with the PRODB utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–13 Creating a database with a Data tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–15 Using an OpenEdge database as an Actional repository . . . . . . . . . . . . . . . . . . . 1–16 Converting a Progress Version 9 database to OpenEdge Release 10 . . . . . . . . . 1–17 Using the Schema Mover after conversion . . . . . . . . . . . . . . . . . . . . . . . 1–18 Migrating from Release 10.1A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–20 Database migration and interoperability . . . . . . . . . . . . . . . . . . . . . . . . . 1–20 RDBMS client connections from prior releases . . . . . . . . . . . . . . . . . . . 1–22 Reverting your database to Release 10.1A. . . . . . . . . . . . . . . . . . . . . . . 1–22 Database conversion utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–25 Copying a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–26 Copying a database using PROCOPY . . . . . . . . . . . . . . . . . . . . . . . . . . 1–26 Deleting a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–28 2. OpenEdge RDBMS Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1 Database block sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2 Maximum number of records per block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3 Number and size of storage areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4 Recovery sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–9 Table and index limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10 Number and size of sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11 Maximum size of the primary recovery (BI) area . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12 Maximum database size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13 Contents Contents–2 Number of connections per database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14 Number of simultaneous transactions per database . . . . . . . . . . . . . . . . . . . . . . . 2–15 OpenEdge database name limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–16 File Handles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–17 Shared memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–18 Shared memory interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–18 Data types and values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–19 3. Starting Up and Shutting Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1 Management tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2 OpenEdge Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2 OpenEdge Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2 Progress Explorer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2 Starting a server or broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5 Specifying international character sets. . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5 Network addressing using -S and -H . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6 Starting multiple brokers using the same protocol . . . . . . . . . . . . . . . . . . 3–6 Accessing a server behind a firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–8 Starting database brokers for SSL connections. . . . . . . . . . . . . . . . . . . . 3–8 Starting and stopping background writers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10 Starting and stopping an APW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–10 Starting and stopping a BIW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–11 Starting and stopping an AIW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–11 Stopping a server or broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12 PROSHUT command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–12 PROMON shut down database option . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16 Part II Protecting Your Data 4. Backup Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1 Identifying files for backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2 Determining the type of backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3 Full backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4 Incremental backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4 Online backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6 Offline backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6 Choosing backup media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7 Creating a backup schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8 Database integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8 Database size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8 Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9 Unscheduled backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9 5. Backing Up a Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1 Using PROBKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2 Performing an online full backup with PROBKUP . . . . . . . . . . . . . . . . . . 5–2 Testing backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4 Archiving backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–5 Performing an offline backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6 Performing an online backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–8 Using database quiet points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9 Performing an operating system backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–11 Contents Contents–3 Database backup examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–13 Incremental backup example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–13 Full backup example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–15 Verifying a backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–18 CRC codes and redundancy in backup recovery . . . . . . . . . . . . . . . . . . . . . . . . . 5–19 CRC codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–19 Error-correction blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–19 Restoring a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–20 Using the PROREST utility to restore a database . . . . . . . . . . . . . . . . . 5–20 Important rules for restoring backups . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–21 Obtaining storage area descriptions using PROREST . . . . . . . . . . . . . 5–22 Database restore examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–22 6. Recovering a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1 Introduction to recovery mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2 Crash recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–3 Roll-forward recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4 Two-phase commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5 File locations that ensure safe recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6 Developing a recovery plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7 Time needed for recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7 Recovery guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8 Sample recovery plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–9 Example 1: Low availability requirements . . . . . . . . . . . . . . . . . . . . . . . . 6–9 Example 2: Moderate availability requirements . . . . . . . . . . . . . . . . . . . 6–9 Example 3: Moderate-to-high availability requirements . . . . . . . . . . . . . 6–10 Example 4: high availability requirements . . . . . . . . . . . . . . . . . . . . . . . 6–11 Sample recovery scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–12 After-imaging and roll-forward recovery commands . . . . . . . . . . . . . . . . . . . . . . . 6–17 Recovering from system failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–18 System crash while running RFUTIL ROLL FORWARD. . . . . . . . . . . . . 6–18 System crash while running other utilities . . . . . . . . . . . . . . . . . . . . . . . . 6–18 System crash while backing up the database . . . . . . . . . . . . . . . . . . . . 6–19 System crash while database is up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–19 Recovering from media failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–20 Loss of the DB files, BI files, or both . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–20 Loss of the AI file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–21 Loss of database backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–21 Loss of transaction log file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–22 Recovering from a full disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–23 After-image area disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–23 Control or primary recovery area disk . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–23 Transaction log file disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–24 Truncating the BI file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–25 Releasing shared memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–26 Recovering from a lost or damaged control area . . . . . . . . . . . . . . . . . . . . . . . . . 6–27 Unlocking damaged databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–28 Dumping tables from a damaged database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–29 Forcing access to a damaged database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–30 7. After-imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1 After-image areas and extents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–2 Estimating after-imaging disk space requirements . . . . . . . . . . . . . . . . . . . . . . . . 7–4 Creating after-image areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–5 Contents Contents–4 Enabling after-imaging offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–7 Enabling encrypted after-imaging offline for an encryption-enabled database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–7 Enabling unencrypted after-imaging offline for an encryption-enabled database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–7 Enabling after-imaging online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–8 Enabling encrypted after-imaging online for an encryption-enabled database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–8 Enabling unencrypted after-imaging online for an encryption-enabled database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–8 Managing after-imaging files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–9 Monitoring AI file status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–9 Switching to a new AI file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–11 Archiving an AI file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–13 Making an AI file available for reuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–15 AI File Management utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–16 Automatic extent archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–16 Enabling your database for automated AI file management . . . . . . . . . . 7–19 Monitoring and adjusting automated AI File Management. . . . . . . . . . . . 7–20 Restarting the AI file management utility daemon . . . . . . . . . . . . . . . . . . 7–21 Archived extents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–21 Archive log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–22 Database recovery with an archival log . . . . . . . . . . . . . . . . . . . . . . . . . . 7–26 Add and reorder AI extents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–28 Performing roll-forward recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–30 Roll forward with the OPLOCK qualifier . . . . . . . . . . . . . . . . . . . . . . . . . 7–31 After-image sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–33 Sequence not required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–34 Sequence required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–35 Disabling after-imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–36 Disabling encryption of AI files when disabling after-imaging . . . . . . . . . 7–36 8. Maintaining Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1 Establishing an OpenEdge user ID and password . . . . . . . . . . . . . . . . . . . . . . . . . 8–2 OpenEdge user ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2 OpenEdge password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2 Validating an OpenEdge user ID and password . . . . . . . . . . . . . . . . . . . 8–3 Establishing authentication for your OpenEdge database . . . . . . . . . . . . . . . . . . . 8–4 ABL tables only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4 SQL tables only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4 Both ABL and SQL tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–4 Connection security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–5 Designating valid users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–5 Designating a security administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–6 Deleting a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–7 Changing a password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–8 Running a user report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–9 Schema security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–10 Operating systems and database security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–11 9. Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–1 Auditable events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–2 Audit events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–2 Security events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–3 Schema events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–3 Data events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–3 Contents Contents–5 Administration events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4 Utility events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4 User events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4 Application events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–5 Auditing states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–6 Enabling and disabling auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–7 Enabling auditing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–7 Disabling auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–8 Auditing tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–10 Indexes on auditing tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–11 Archiving audit data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–13 Audit archive process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–13 Auditing impact on database resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–15 Auditing impact on database utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–16 Identifying the privileged user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–16 Utility modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–19 10. Transparent Data Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2 Before you start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–2 What is encryptable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–3 Data considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–4 Database key store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–4 OpenEdge supported ciphers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–6 Enabling Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–7 Adding an encryption policy area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–7 Running ENABLEENCRYPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–8 Enabling BI file encryption after enabling encryption . . . . . . . . . . . . . . . 10–9 Enabling AI file encryption after enabling encryption . . . . . . . . . . . . . . . 10–10 Verifying enablements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–10 Creating encryption policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–12 Creating encryption policies with PROUTIL EPOLICY . . . . . . . . . . . . . . 10–12 Creating encryption policies with Data Admin . . . . . . . . . . . . . . . . . . . . 10–13 Encrypting your existing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–14 EPOLICY MANAGE UPDATE EXAMPLE . . . . . . . . . . . . . . . . . . . . . . . 10–14 All new data is encrypted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–15 Running with Transparent Data Encryption enabled . . . . . . . . . . . . . . . . . . . . . . . 10–16 Manual start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–16 Autostart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–17 Temporary files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–18 Restricted utility access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–18 Database backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–19 Moving tables and indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–19 Binary dump and load of data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–22 Auditing Transparent Data Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . 10–22 Replication support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–26 Maintaining Transparent Data Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–27 Rekey encryption policies with Data Admin . . . . . . . . . . . . . . . . . . . . . . 10–27 Rekey encryption policies with PROUTIL EPOLICY. . . . . . . . . . . . . . . . 10–28 Viewing encryption policy history in Data Admin. . . . . . . . . . . . . . . . . . . 10–29 Disabling encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–30 OpenEdge SQL support for Transparent Data Encryption . . . . . . . . . . . . . . . . . . 10–32 Contents Contents–6 11. Replicating Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–1 Replication schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–2 Trigger-based replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–2 Log-based site replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–2 Replication models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–2 Database ownership models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–3 Distribution model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–3 Consolidation model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–3 Implementing log-based site replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–6 Log-based replication procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–6 12. Failover Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–2 Related software and hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–4 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–5 Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–5 Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–5 Required cluster components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6 Network considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–8 Terms and concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–9 Resources and dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–9 Failure and recovery action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–9 Fail over policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–9 Using the PROCLUSTER command-line interface . . . . . . . . . . . . . . . . . . . . . . . . 12–11 Cluster-enabling a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–11 Disabling a cluster-enabled database . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–12 Starting a cluster-enabled database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–13 Stopping a cluster-enabled database. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–13 Terminating a cluster-enabled database . . . . . . . . . . . . . . . . . . . . . . . . . 12–14 Isalive and looksalive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–14 Results of enabling an OpenEdge database for fail over . . . . . . . . . . . . . . . . . . . . 12–15 Database UUID file (HPUX 32 and 64 bit only) . . . . . . . . . . . . . . . . . . . . 12–15 Changing the structure of the database . . . . . . . . . . . . . . . . . . . . . . . . . . 12–15 Adding extents on a volume group or file system different from the database (AIX only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–15 Platform-specific considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–17 Adding nodes where the database can be run for AIX. . . . . . . . . . . . . . . 12–17 Upper limit on the number of packages for HPUX 32 bit and 64 bit. . . . . 12–17 Directory of registered packages for HPUX 32 bit and 64 bit . . . . . . . . . 12–18 Using a cluster-enabled database with the AdminServer . . . . . . . . . . . . . . . . . . . . 12–19 Using a cluster-enabled database with standard commands . . . . . . . . . . . . . . . . . 12–21 Using the Windows Cluster Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–22 Emergency disabling of a cluster-enabled database . . . . . . . . . . . . . . . . . . . . . . . 12–24 UNIX cluster management commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–25 13. Distributed Transaction Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–1 Distributed transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–2 Two-phase commit with ABL clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–3 How the database engine implements two-phase commit. . . . . . . . . . . . 13–3 Two-phase commit and roll-forward recovery . . . . . . . . . . . . . . . . . . . . . 13–6 Enabling two-phase commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–6 Modifying the database nickname and priority . . . . . . . . . . . . . . . . . . . . . 13–7 Transaction log area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–8 Deactivating two-phase commit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–8 Contents Contents–7 Limbo transactions with two-phase commit . . . . . . . . . . . . . . . . . . . . . . 13–9 Resolving limbo transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–10 Resolving limbo transaction scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . 13–14 Two-phase commit case study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–15 Java Transaction API (JTA) support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–18 JTA resource impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–18 JTA processing impact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–19 Enabling JTA support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–19 Disabling JTA support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–19 Monitoring JTA transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–20 Resolving JTA transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–20 Part III Maintaining and Monitoring Your Database 14. Managing Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–1 Introduction to performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–2 Tools for monitoring performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–3 PROMON utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–3 Virtual system tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–3 Windows Performance tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–3 Server performance factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–4 CPU usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–4 Disk I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–5 Database I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–5 Before-image I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–15 After-image I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–22 Direct I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–25 Memory usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–26 Process address space overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–26 Controlling memory use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–27 Shared memory allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–27 Monitoring memory use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–28 Shared memory consumption and allocation impact . . . . . . . . . . . . . . . 14–28 Shared memory summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–30 Alternate Buffer Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–31 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–31 Designating objects to the Alternate Buffer Pool. . . . . . . . . . . . . . . . . . . 14–32 Viewing Alternate Buffer Pool selections . . . . . . . . . . . . . . . . . . . . . . . . 14–33 Allocating Alternate Buffer Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–35 Operating system resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–36 Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–36 Semaphores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–36 Spin locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–39 File descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–39 Database fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–40 Analyzing database fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–40 Eliminating database fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–41 Managing fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–41 Index use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–44 Analyzing index use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–44 Compacting indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–45 Rebuilding indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–46 Activating a single index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–52 Virtual system tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–53 Contents Contents–8 15. Maintaining Database Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–1 OpenEdge Structure utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–2 OpenEdge Structure Statistics utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–3 OpenEdge Structure List utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–6 OpenEdge Structure Add utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–8 PROSTRCT ADD and pathnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–9 Adding extents to existing storage areas . . . . . . . . . . . . . . . . . . . . . . . . 15–10 OpenEdge Structure Add Online utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–11 Area numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–15 Area number assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–15 Trimming unused area memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–19 Error checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–21 Validating structure description files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–22 OpenEdge Structure Remove utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–24 Maintaining indexes and tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–25 Moving tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–25 Moving indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–26 Compacting indexes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–27 Performing chain analysis online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–28 Using virtual system tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–30 16. Dumping and Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–1 Overview of dumping and loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–2 Dump and load limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–2 Dumping ABL database definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–3 Definition file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–5 Creating an incremental ABL data definitions file. . . . . . . . . . . . . . . . . . . 16–6 Dumping sequence definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–7 Dumping auto-connect records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–8 Dumping database contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–9 Dumping table contents with PROUTIL . . . . . . . . . . . . . . . . . . . . . . . . . . 16–9 Dumping selective contents with PROUTIL . . . . . . . . . . . . . . . . . . . . . . . 16–11 Dumping table contents with a Data tool . . . . . . . . . . . . . . . . . . . . . . . . . 16–13 Contents file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–14 Dumping sequence values with a Data tool . . . . . . . . . . . . . . . . . . . . . . 16–16 Dumping user table contents with a Data tool . . . . . . . . . . . . . . . . . . . . . 16–16 Dumping an SQL view file’s contents with a Data tool . . . . . . . . . . . . . . 16–17 Loading database definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–18 Loading updated ABL data definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–18 Loading database contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–20 Loading table contents in binary format with PROUTIL . . . . . . . . . . . . . . 16–20 Loading table contents with a Data tool . . . . . . . . . . . . . . . . . . . . . . . . . 16–22 Loading user table contents with a Data tool . . . . . . . . . . . . . . . . . . . . . . 16–23 Loading an SQL view file contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–23 Loading sequence values using a Data tool. . . . . . . . . . . . . . . . . . . . . . . 16–24 Bulk loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–25 Creating a Bulk Loader description file. . . . . . . . . . . . . . . . . . . . . . . . . . . 16–25 Modifying a Bulk Loader description file. . . . . . . . . . . . . . . . . . . . . . . . . . 16–26 Loading table contents with the Bulk Loader qualifier . . . . . . . . . . . . . . . 16–27 Reconstructing bad load records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–29 Specialized dump and load techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–30 Creating a starting version of a database. . . . . . . . . . . . . . . . . . . . . . . . . 16–30 Using a constant table in multiple databases. . . . . . . . . . . . . . . . . . . . . . 16–31 Economizing disk space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–31 [...]... shut down an OpenEdge database Part II, Protecting Your Data Chapter 4, “Backup Strategies” Discusses various approaches to backing up your database Chapter 5, “Backing Up a Database Describes the mechanics of backing up your database with the PROBKUP utility Chapter 6, “Recovering a Database Examines recovery strategies and how to use the PROREST utility to restore an OpenEdge database Chapter 7,... manual This book is organized into four complementary parts: • Part I, Database basics,” describes the basic commands for creating and deleting, and starting up and shutting down databases, along with detailing database limits • Part II, “Protecting your data, ” describes the procedures a database administrator uses to protect a database in a flexible business environment Each chapter discusses a particular... 18–6 18–7 18–9 18–11 18–15 19 Database Startup Parameters Issuing startup parameters Database server performance parameters Database server-type parameters Database server internationalization parameters Database server statistics... cluster-enabled database Chapter 13, “Distributed Transaction Processing” Explains distributed transaction processing, and discusses support for two-phase commit and the Java Transaction API (JTA) Part III, Maintaining and Monitoring Your Database Chapter 14, “Managing Performance” Discusses how to monitor tune database performance Chapter 15, “Maintaining Database Structure” Describes methods to manage the database. .. File (_Checkpoint) Code Features (_Code-Feature) Database connection file (_Connect) Database features ( _Database- Feature) Database status file (_DbStatus) Database file status file (_Filelist) Index statistics file (_IndexStat) ... and Loading” Explains how to dump and load databases, including tables, indexes, and sequences Chapter 17, “Logged Data Examines the process of logging significant database events Part IV, Reference Chapter 18, “Startup and Shutdown Commands” Catalogs the OpenEdge RDBMS commands for starting up and shutting down database sessions and processes Chapter 19, Database Startup Parameters” Lists and details... for monitoring your database Preface–3 Preface Chapter 21, “PROUTIL Utility” Details the PROUTIL Utility used for maintaining your database Chapter 22, “PROSTRCT Utility” Details the PROSTRCT Utility used for creating and updating the physical structure of your database Chapter 23, “RFUTIL Utility” Details the RFUTIL Utility used for managing after imaging Chapter 24, “Other Database Administration Utilities”... reference for OpenEdge Database Administrators Organization Part I, Database Basics Chapter 1, “Creating and Deleting Databases” Describes how to create and delete OpenEdge databases Chapter 2, “OpenEdge RDBMS Limits” Catalogs limits of the OpenEdge RDBMS, including all aspects of database size, operating system limits, naming conventions, and data types Chapter 3, “Starting Up and Shutting Down” Describes... Original database AI extents Database AI Extents after PROSTRCT ADD of two new extents Database AI extents after PROSTRCT REORDER AI Audit archive process Output of PROUTIL DESCRIBE Data distribution model Data consolidation models... statistics parameters Database server consistency check parameters Database server SSL connection parameters Database server network parameters Startup parameter usage categories Alphabetical listing of database startup parameters . Empowerment, DataDirect (and design), DataDirect Connect, DataDirect Connect64, DataDirect Technologies, DataDirect XML Converters, DataDirect XQuery, DataXtend,. OPENEDGE ® 10 PROGRESS ® OpenEdge ® Data Management: Database Administration © 2009 Progress Software Corporation and/or its