DOCSLIB.ORG

Progress Database Administration Guide and Reference © 2002 Progress Software Corporation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Progress Database Administration Guide and Reference © 2002 Progress Software Corporation Progress Database Administration Guide and Reference © 2002 Progress Software Corporation. All rights reserved. Progress® software products are copyrighted and all rights are reserved by Progress Software Corporation. This manual is also copyrighted and all rights are reserved. This manual may not, in whole or in part, be copied, photocopied, translated, or reduced to any electronic medium or machine-readable form without prior consent, in writing, from Progress Software Corporation. The information in this manual is subject to change without notice, and Progress Software Corporation assumes no responsibility for any errors that may appear in this document. The references in this manual to specific platforms supported are subject to change. Progress, Powered by Progress, Progress Fast Track, Progress Profiles, Partners in Progress, Partners en Progress, Progress en Partners, Progress in Progress, P.I.P., Progress Results, ProVision, ProCare, ProtoSpeed, SmartBeans, SpeedScript, and WebSpeed are registered trademarks of Progress Software Corporation in the U.S. and other countries. A Data Center of Your Very Own, Allegrix, Apptivity, AppsAlive, AppServer, ASPen, ASP-in-a-Box, Empowerment Center, Fathom, Future Proof, IntelliStream, OpenEdge, PeerDirect, POSSE, POSSENET, Progress Dynamics, Progress Software Developers Network, SectorAlliance, SmartObjects and WebClient are trademarks or service marks of Progress Software Corporation in the U.S. and other countries. SonicMQ is a registered trademark of Sonic Software Corporation in the U.S. and other countries. Vermont Views is a registered trademark of Vermont Creative Software 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 and/or service marks contained herein are the property of their respective owners. Progress Software Corporation acknowledges the use of Raster Imaging Technology copyrighted by Snowbound Software 1993- 1997, the IBM XML Parser for Java Edition, and software developed by the Apache Software Foundation (http:// www.apache.org/). © IBM Corporation 1998-1999. All rights reserved. U.S. Government Users Restricted Rights — Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Progress is a registered trademark of Progress Software Corporation and is used by IBM Corporation in the mark Progress/400 under license. Progress/400 AND 400® are trademarks of IBM Corporation and are used by Progress Software Corporation under license. The implementation of the MD5 Message-Digest Algorithm used by Progress Software Corporation in certain of its products is derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. May 2002 Product Code: 4590 Item Number: 89434;V9.1D Contents Preface . xxiii Purpose . xxiii Audience . xxiii Organization of This Manual . xxiii Part I Planning . xxiii Part II Administration . xxiv Part III Reference . xxv How To Use This Manual . xxvi Typographical Conventions . xxvi Syntax Notation . xxvii Example Procedures . xxxi Progress Messages . xxxiv Other Useful Documentation . xxxvi Getting Started . xxxvi Development Tools . xxxvii Reporting Tools . xxxviii 4GL . xxxix Database . xl DataServers. xl SQL-89/Open Access . xli SQL-92 . xli Deployment . xlii WebSpeed. xlii Reference . xliii 1. The Progress Database . 1–1 1.1 Progress Database Architecture . 1–2 1.1.1 Other Database-related Files . 1–4 1.2 Storage Design Overview . 1–5 Contents 1.2.1 Storage Objects . 1–7 1.2.2 Extents . 1–7 1.2.3 Storage Areas . 1–7 1.3 Determining Configuration Variables . 1–9 1.3.1 System Platform . 1–9 1.3.2 Connection Modes . 1–9 1.3.3 Database Location . 1–10 1.3.4 Database Configurations. 1–10 1.4 Operating System Resources . 1–12 1.5 Multi-threaded Architecture . 1–13 1.6 Multi-tier and Cluster Configurations . 1–14 1.7 Self-service and Network Clients . 1–15 1.8 Relative- and Absolute-path Databases . 1–15 2. Administrative Planning . 2–1 2.1 Block Size Considerations . 2–2 2.1.1 Guidelines For Choosing Storage Area Locations . 2–3 2.2 Calculating Database Disk Requirements . 2–3 2.3 Storing Database Extents On Raw Partitions . 2–7 3. Progress Database Limits . 3–1 3.1 Database Block Sizes . 3–2 3.2 Number and Size Of Storage Areas . 3–2 3.3 Maximum Number Of Records Per Block . 3–5 3.4 Table and Index Limits . 3–5 3.5 Number Of Sequences . 3–5 3.6 Maximum Size Of the Primary Recovery (BI) Area . 3–6 3.7 Maximum Database Size . 3–6 3.8 Number Of Connections Per Database . 3–7 3.9 Number Of Simultaneous Transactions Per Database . 3–7 3.10 Size Of Database Buffer Pool . 3–7 3.11 Progress Database Name Limits . 3–8 3.12 Applicable Operating System Limits . 3–8 3.13 Data Types and Values . 3–10 4. Creating and Deleting Databases . 4–1 4.1 Ways To Create a Progress Database . 4–2 4.2 Creating a Database With PROSTRCT CREATE . 4–2 4.2.1 Creating a Structure Description File . 4–3 4.2.2 Create a Database Structure Extent . 4–10 4.2.3 Adding Schema To a Void Database . 4–11 4.3 Creating a Database With the PRODB Utility . 4–12 4.4 Creating a Database With the Data Administration Tool . 4–14 4.5 Migrating Version 8 Databases To Version 9 Databases . 4–15 iv Contents 4.5.1 Converting a Single-volume Version 8 Database With PROCOPY . 4–16 4.5.2 Converting a Single-volume Version 8 Database With PROREST . 4–17 4.5.3 Converting a Single-volume Version 8 Database With PROSTRCT . 4–18 4.5.4 Converting a Version 8 Database To Version 9. 4–18 4.6 Using the Schema Mover After Conversion . 4–19 4.7 Copying a Database . 4–22 4.8 AutoConvert Utility . 4–24 4.9 Deleting a Database . 4–24 5. Starting Up and Shutting Down . 5–1 5.1 The Progress Explorer Framework . 5–2 5.1.1 AdminServer.
Load more

Recommended publications
  • Developing Multiuser and Enterprise Applications
    26_0672329328_ch22.qxd 5/3/07 3:28 PM Page 909 CHAPTER 22 IN THIS CHAPTER . Why This Chapter Is Important Developing Multiuser . Designing Your Application with Multiuser Issues in Mind and Enterprise . Understanding Access’s Applications Locking Mechanisms . Understanding the Client/Server Model . Deciding Whether to Use the Client/Server Model Why This Chapter Is Important . Understanding the Roles That Many people forge right into the application development Access Plays in the Application process with little worry about the scalability of the appli- Design Model cation. Even a simple application that begins as a single- . Learning the Client/Server user application can develop into a multiuser or Buzzwords enterprise-wide application. Unfortunately, the techniques . Upsizing: What to Worry About you can get away with in the single-user application can wreak havoc in a network or client/server environment. It . Proactively Preparing for is therefore necessary to think about the future when you Upsizing design any application. Although the initial development . Using Transaction Processing process might be more complex, if written properly, the . application will survive any growth that it experiences. Practical Examples: Getting Your Application Ready for an This chapter focuses on writing applications that transition Enterprise Environment easily from the single-user environment through the enter- prise client/server environment. Designing Your Application with Multiuser Issues in Mind When you develop applications that multiple users will access over the network, you must make sure they effec- tively handle sharing data and other application objects. Many options are available for developers when they design multiuser applications, and this chapter covers the pros and cons of these options.
    [Show full text]
  • Databases and SQL
    Introduction to Computer Science Databases Databases and SQL Table of Contents Useful resources...................................................1 Queries using WHERE................................14 Flat files................................................................1 LIKE............................................................14 Relational databases.............................................2 GROUP BY.................................................15 Database servers...................................................3 DROP...........................................................15 Database systems architecture..............................4 ORDER BY.................................................15 Normalisation.......................................................5 UPDATE fields values.................................16 Users, groups and permissions.............................7 JOIN tables..................................................17 Views....................................................................7 DELETE rows.............................................17 Schema and data dictionary..................................7 Nested queries..................................................18 Advantages of database use..................................8 Referential integrity..........................................18 SQL......................................................................8 DDL and DML.................................................19 SQL Tutorial.........................................................9
    [Show full text]
  • VAX Rdb/VMS Guide to Using RDO, RDBPRE, and RDML
    AA–N038F–TE VAX Rdb/VMS Guide to Using RDO, RDBPRE, and RDML December 1990 This manual provides information about data manipulation and programming with relational databases using the following VAX Rdb/VMS interfaces: interactive RDO, Callable RDO, and the RDBPRE and RDML preprocessors. Revision/Update Information: This manual is a revision and supersedes previous versions. Operating System: VMS Software Version: VAX Rdb/VMS Version 4.0 digital equipment corporation maynard, massachusetts The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. Any software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software or equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1989,1990. All rights reserved. Printed in U.S.A. The Reader’s Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: ALL–IN–1, CDD/Plus, DEC, DEC/CMS, DECdecision, DECdtm, DECforms, DECintact, DEC/MMS, DECnet, DECtp, DECtrace, DECwindows, MicroVAX, ULTRIX, UNIBUS, VAX, VAX ACMS, VAX Ada, VAX BASIC, VAX C, VAX CDD, VAXcluster, VAX COBOL, VAX DATATRIEVE, VAX DBMS, VAXELN, VAX FMS, VAX FORTRAN, VAX Pascal, VAX RALLY, VAX Rdb/ELN, VAX Rdb/VMS, VAX RMS, VAX SPM, VAXstation, VAX TEAMDATA, VIDA, VMS, VT, and the DIGITAL Logo.
    [Show full text]
  • Spatial Database Systems Lecture 1 Ft Okyere Differences Between a Database Management System and a File-Processing System
    SPATIAL DATABASE SYSTEMS LECTURE 1 FT OKYERE DIFFERENCES BETWEEN A DATABASE MANAGEMENT SYSTEM AND A FILE-PROCESSING SYSTEM 1. BOTH SYSTEMS CONTAIN A COLLECTION OF DATA AND A SET OF PROGRAMS WHICH ACCESS THAT DATA. A DATABASE MANAGEMENT SYSTEM COORDINATES BOTH THE PHYSICAL AND THE LOGICAL ACCESS TO THE DATA, WHEREAS A FILE- PROCESSING SYSTEM COORDINATES ONLY THE PHYSICAL ACCESS. 2. A DATABASE MANAGEMENT SYSTEM REDUCES THE AMOUNT OF DATA DUPLICATION BY ENSURING THAT A PHYSICAL PIECE OF DATA IS AVAILABLE TO ALL PROGRAMS AUTHORIZED TO HAVE ACCESS TO IT, WHEREAS DATA WRITTEN BY ONE PROGRAM IN A FILE-PROCESSING SYSTEM MAY NOT BE READABLE BY ANOTHER PROGRAM. 3. A DATABASE MANAGEMENT SYSTEM IS DESIGNED TO ALLOW FLEXIBLE ACCESS TO DATA (I.E., QUERIES), WHEREAS A FILE- PROCESSING SYSTEM IS DESIGNED TO ALLOW PREDETERMINED ACCESS TO DATA (I.E., COMPILED PROGRAMS). 4. A DATABASE MANAGEMENT SYSTEM IS DESIGNED TO COORDINATE MULTIPLE USERS ACCESSING THE SAME DATA AT THE SAME TIME. A FILE-PROCESSING SYSTEM IS USUALLY DESIGNED TO ALLOW ONE OR MORE PROGRAMS TO ACCESS DIFFERENT DATA FILES AT THE SAME TIME. IN A FILE-PROCESSING SYSTEM, A FILE CAN BE ACCESSED BY TWO PROGRAMS CONCURRENTLY ONLY IF BOTH PROGRAMS HAVE READ-ONLY ACCESS TO THE FILE FILE LOCKING • FILE LOCKING IS A MECHANISM THAT RESTRICTS ACCESS TO A COMPUTER FILE BY ALLOWING ONLY ONE USER OR PROCESS ACCESS AT ANY SPECIFIC TIME. • A RACE CONDITION IS AN UNDESIRABLE SITUATION THAT OCCURS WHEN A DEVICE OR SYSTEM ATTEMPTS TO PERFORM TWO OR MORE OPERATIONS AT THE SAME TIME, BUT BECAUSE OF THE NATURE OF THE DEVICE OR SYSTEM, THE OPERATIONS MUST BE DONE IN THE PROPER SEQUENCE TO BE DONE CORRECTLY.
    [Show full text]
  • VSI COBOL for Openvms DBMS Database Programming Manual
    VSI OpenVMS VSI COBOL for OpenVMS DBMS Database Programming Manual Document Number: DO-DCOBPG-01A Publication Date: May 2020 This manual explains how to develop Oracle DBMS database programs with VSI COBOL on the OpenVMS Alpha, OpenVMS I64, and the OpenVMS VAX operating systems. Revision Update Information: This is a new manual. Operating System and Version: VSI OpenVMS I64 Version 8.4-1H1 VSI OpenVMS Alpha Version 8.4-2L1 Software Version: VSI COBOL Version 3.1-7 for OpenVMS VMS Software, Inc., (VSI) Bolton, Massachusetts, USA VSI COBOL for OpenVMS DBMS Database Programming Manual Copyright © 2020 VMS Software, Inc. (VSI), Bolton, Massachusetts, USA Legal Notice Confidential computer software. Valid license from VSI required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for VSI products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. VSI shall not be liable for technical or editorial errors or omissions contained herein. HPE, HPE Integrity, HPE Alpha, and HPE Proliant are trademarks or registered trademarks of Hewlett Packard Enterprise. Intel, Itanium and IA64 are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Oracle is a registered trademark of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group.
    [Show full text]
  • VSI COBOL DBMS Database Programming Manual
    VSI OpenVMS VSI COBOL DBMS Database Programming Manual Document Number: XX-XXXXXX-XXX Publication Date: month 2018 This manual explains how to develop Oracle DBMS database programs with VSI COBOL on the OpenVMS Alpha, OpenVMS I64, and the OpenVMS VAX operating systems. Revision Update Information: This is a new manual. Operating system and Version: VSI OpenVMS Version X.X Software Version: VSI COBOL Version X.X VMS Software, Inc., (VSI) Bolton, Massachusetts, USA VSI OpenVMS VSI COBOL DBMS Database Programming Manual: Copyright © 2018 VMS Software, Inc., (VSI), Bolton Massachusetts, USA Legal Notice Confidential computer software. Valid license from VSI required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for VSI products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. VSI shall not be liable for technical or editorial errors or omissions contained herein. HPE, HPE Integrity, HPE Alpha, and HPE Proliant are trademarks or registered trademarks of Hewlett Packard Enterprise. UNIX is a registered trademark of The Open Group. Oracle is a registered trademark of Oracle and/or its affiliates. The VSI OpenVMS documentation
    [Show full text]
  • Introduction to Database Systems Narain Gehani CS
    Introduction to Database Systems Narain Gehani © Narain Gehani Introduction to Databases Slide 1 CS 431 •Welcome • Who should take this course • Syllabus • Book – copies / volunteer / $ • TA • Your background • If I go faster, I will have a review class if you like © Narain Gehani Introduction to Databases Slide 2 1 Introduction • What is a database? – Any repository of data (paper file cabinets, Word files, Excel spread sheets, database systems) – Facilitates for storage, manipulation, retrieval, persistence, concurrency, fast access • Users of databases – End users – Database users – Database designers – Database administrators (DBAs) – Application programmers – Database system implementers © Narain Gehani Introduction to Databases Slide 3 Introduction (Contd.) • Will teach you how database systems work, not how database systems are implemented. • Why the above? • Focus on concepts & fundamentals on how to use (relational) databases effectively. • SQL – great for querying/manipulating relational databases but not a full-fledged language • Host language such as Java/C++ make up for deficiencies – control structures, formatting, networking, etc © Narain Gehani Introduction to Databases Slide 4 2 MySQL • We will use MySQL • “Open source” relational database • Over 5 million installed systems © Narain Gehani Introduction to Databases Slide 5 Relational Database Model • Relational database – Data stored as tables – Data is extracted by throwing away unwanted rows and columns. – Tables can be joined in the process of extracting data • Relational
    [Show full text]
  • VAX Rdb/VMS Guide to Data Manipulation
    VAX Rdb/VMS Guide to Data Manipulation Order No. AA-N036C-TE VAX Rdb/VMS Guide to Data Manipulation Order No. AA-N036C-TE November 1987 This manual provides information about retrieving, modifying and erasing data in a database· using the VAX RdbNMS interactive Relational Database Operator. OPERATING SYSTEM: VMS Micro VMS SOFTWARE VERSION: VAX Rdb/VMS V2.3 digital equipment corporation, maynard, massachusetts The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by DIGITAL or its affiliated companies. Copyright© 1984, 1985, 1987 by Digital Equipment Corporation. All Rights Reserved. The postage-paid READER'S COMMENTS form on the last page of this document requests your critical evaluation to assist us in preparing future documentation. The following are trademarks of Digital Equipment Corporation: ACMS PDP VAX CDD RALLY VAXcluster DATATRIEVE Rdb/ELN VAXinfo DEC RdbNMS VAX Information Architecture DECnet ReGIS VIDA DEC US TDMS VMS MicroVAX TEAMDATA VT MicroVMS UNIBUS Contents How to Use This Manual vii Technical Changes and New Features xi 1 Introduction to VAX Rdb/VMS Data Manipulation 1.1 What Is a Relational Database? . 1·2 1.1.1 Using Normalization to Eliminate Data Redundancy.
    [Show full text]