DOCSLIB.ORG

Advanced Functions and Administration on DB2 Universal Database for Iseries

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Advanced Functions and Administration on DB2 Universal Database for Iseries IBM Advanced Functions and Administration on DB2 Universal Database for iSeries Learn about referential integrity and constraints See how Database Navigator maps your database Discover the secrets of Visual Explain Hernando Bedoya Daniel Lema Vijay Marwaha Dave Squires Mark Walas ibm.com/redbooks International Technical Support Organization Advanced Functions and Administration on DB2 Universal Database for iSeries December 2001 SG24-4249-03 Take Note! Before using this information and the product it supports, be sure to read the general information in “Special notices” on page 345. Fourth Edition (December 2001) This edition applies to Version 5, Release 1 of OS/400, Program Number 5722-SS1. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. JLU Building 107-2 3605 Highway 52N Rochester, Minnesota 55901-7829 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1994, 1997, 2000, 2001. All rights reserved. Note to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Contents . iii Preface . ix The team that wrote this redbook. ix Special notice. xi IBM trademarks . xi Comments welcome. xii Part 1. Background. 1 Chapter 1. Introducing DB2 UDB for iSeries . 3 1.1 An integrated relational database . 4 1.2 DB2 UDB for iSeries: An overview . 4 1.2.1 DB2 UDB for iSeries basics . 5 1.2.2 DB2 UDB for iSeries advanced functions . 6 1.3 DB2 Universal Database for iSeries sample schema . 8 Chapter 2. Using the advanced functions: An Order Entry application. 11 2.1 Introduction to the Order Entry application . 12 2.2 Order Entry application overview . 12 2.3 Order Entry database overview. 14 2.4 DB2 UDB for iSeries advanced functions in the Order Entry database . 17 2.4.1 Referential integrity . 17 2.4.2 Two-phase commit . 18 Part 2. Advanced functions . 19 Chapter 3. Referential integrity . 21 3.1 Introduction . 22 3.2 Referential integrity concepts . 22 3.3 Defining a referential integrity relationship . 24 3.3.1 Constraint prerequisites . 24 3.3.2 Journaling and commitment control requirements . 25 3.3.3 Referential integrity and access paths . 25 3.4 Creating a referential constraint . 28 3.4.1 Primary key and unique constraints . 29 3.4.2 Referential constraint . 30 3.4.3 Another example: Order Entry scenario . 32 3.4.4 Self-referencing constraints . 34 3.5 Constraints enforcement . 35 3.5.1 Locking considerations . 35 3.5.2 Referential integrity rules ordering . 36 3.5.3 A CASCADE example. 39 3.6 Journaling and commitment control . 43 3.6.1 Referential integrity journal entries . 45 3.6.2 Applying journal changes and referential integrity . 49 3.7 Referential integrity application impact . 50 3.7.1 Referential integrity I/O messages . 50 3.7.2 Handling referential integrity messages in applications . 51 © Copyright IBM Corp. 1994, 1997, 2000, 2001 iii 3.8 Referential integrity constraint management. 52 3.8.1 Constraint states . 52 3.8.2 Check pending . 53 3.8.3 Constraint commands . 53 3.8.4 Removing a constraint . 56 3.8.5 Save and restore considerations . 59 3.8.6 Restore and journal apply: An example . 61 3.8.7 Displaying constraint information . 61 Chapter 4. Check constraint. 67 4.1 Introduction . 68 4.1.1 Domain or table constraints . 68 4.1.2 Referential integrity constraints. 68 4.1.3 Assertions . 68 4.2 DB2 UDB for iSeries check constraints. 69 4.3 Defining a check constraint . 70 4.4 General considerations . 75 4.5 Check constraint integration into applications. 77 4.5.1 Check constraint I/O messages . 77 4.5.2 Check constraint application messages . 78 4.6 Check constraint management . 79 4.6.1 Check constraint states. 80 4.6.2 Save and restore considerations . 81 4.7 Tips and techniques . 82 Chapter 5. DRDA and two-phase commitment control . 83 5.1 Introduction to DRDA . 84 5.1.1 DRDA architecture . 84 5.1.2 SQL as a common DRDA database access language . 84 5.1.3 Application requester and application server . 84 5.1.4 Unit of work . 85 5.1.5 Openness . ..
Load more

Recommended publications
  • Create Trigger Schema Postgresql
    Create Trigger Schema Postgresql Diligent Gallagher sometimes gallants any harp reinforms single-mindedly. Lumpier and exarate Scott tongue limitedly and isolated his interactions approvingly and incorruptly. Tinniest and unabolished Berkie never opaquing quiveringly when Morton fall-back his duress. The legitimate unique identifier for house person. Now is are going to supervise an SQL file for adding data argue the table. You might declare a CURSOR, use case query. The privileges required by postgres function level, more triggers are processed by a predefined set of a particular order to store structured data. Use bleach if exists option and remove one arm more views from pan database database in not current. This is considered more consistent. Already loaded into different schemas live inside hasura became a create triggers and creates a couple of creating user? We can prevent all kinds of looping code in procedures with aggregate queries to a client like where tp where not a logical view! CREATE then REPLACE FUNCTION public. This way to be buffered to delete on geometry columns changes have created in postgresql create trigger against by trigger automatically drops an insert and occasional baby animal gifs! This is impossible except by anyone, check before insert or functions in which takes a create trigger postgresql create additional tables are enabled when date? For application that makes their first. We did with respect to spot when a system section provides an audit table belongs to remove trigger is used inside their twin daughters. Such as mentioned in postgresql create schema objects scripted would not. Many explanations from this document have been extracted from there.
    [Show full text]
  • Creating Triggers with Trigger-By-Example in Graph Databases
    Creating Triggers with Trigger-By-Example in Graph Databases Kornelije Rabuzin a and Martina Sestakˇ b Faculty of Organization and Informatics, University of Zagreb, Pavlinska 2, 42000 Varazdin,ˇ Croatia Keywords: Trigger-By-Example, Graph Databases, Triggers, Active Databases. Abstract: In recent years, NoSQL graph databases have received an increased interest in the research community. Vari- ous query languages have been developed to enable users to interact with a graph database (e.g. Neo4j), such as Cypher or Gremlin. Although the syntax of graph query languages can be learned, inexperienced users may encounter learning difficulties regardless of their domain knowledge or level of expertise. For this reason, the Query-By-Example approach has been used in relational databases over the years. In this paper, we demon- strate how a variation of this approach, the Trigger-By-Example approach, can be used to define triggers in graph databases, specifically Neo4j, as database mechanisms activated upon a given event. The proposed ap- proach follows the Event-Condition-Action model of active databases, which represents the basis of a trigger. To demonstrate the proposed approach, a special graphical interface has been developed, which enables users to create triggers in a short series of steps. The proposed approach is tested on several sample scenarios. 1 INTRODUCTION Example approach has been introduced to simplify the process of designing database triggers. The The idea of active mechanisms able to react to a spec- approach uses the Query-By-Example (QBE) as a ified event implemented in database systems dates graphical interface for creating triggers (Lee et al., from 1975, when it was first implemented in IBM’s 2000b), and makes the entire trigger design process System R.
    [Show full text]
  • Chapter 10. Declarative Constraints and Database Triggers
    Chapter 10. Declarative Constraints and Database Triggers Table of contents • Objectives • Introduction • Context • Declarative constraints – The PRIMARY KEY constraint – The NOT NULL constraint – The UNIQUE constraint – The CHECK constraint ∗ Declaration of a basic CHECK constraint ∗ Complex CHECK constraints – The FOREIGN KEY constraint ∗ CASCADE ∗ SET NULL ∗ SET DEFAULT ∗ NO ACTION • Changing the definition of a table – Add a new column – Modify an existing column’s type – Modify an existing column’s constraint definition – Add a new constraint – Drop an existing constraint • Database triggers – Types of triggers ∗ Event ∗ Level ∗ Timing – Valid trigger types • Creating triggers – Statement-level trigger ∗ Option for the UPDATE event – Row-level triggers ∗ Option for the row-level triggers – Removing triggers – Using triggers to maintain referential integrity – Using triggers to maintain business rules • Additional features of Oracle – Stored procedures – Function and packages – Creating procedures – Creating functions 1 – Calling a procedure from within a function and vice versa • Discussion topics • Additional content and activities Objectives At the end of this chapter you should be able to: • Know how to capture a range of business rules and store them in a database using declarative constraints. • Describe the use of database triggers in providing an automatic response to the occurrence of specific database events. • Discuss the advantages and drawbacks of the use of database triggers in application development. • Explain how stored procedures can be used to implement processing logic at the database level. Introduction In parallel with this chapter, you should read Chapter 8 of Thomas Connolly and Carolyn Begg, “Database Systems A Practical Approach to Design, Imple- mentation, and Management”, (5th edn.).
    [Show full text]
  • IDUG NA 2007 Michael Paris: Hitchhikers Guide to Data Replication the Story Continues
    Session: I09 Hitchhikers Guide to Data Replication The Story Continues ... Michael Paris Trans Union LLC May 9, 2007 9:50 a.m. – 10:50 a.m. Platform: Cross-Platform TransUnion is a global leader in credit and information management. For more than 30 years, we have worked with businesses and consumers to gather, analyze and deliver the critical information needed to build strong economies throughout the world. The result? Businesses can better manage risk and customer relationships. And consumers can better understand and manage credit so they can achieve their financial goals. Our dedicated associates support more than 50,000 customers on six continents and more than 500 million consumers worldwide. 1 The Hitchhiker’s Guide to IBM Data Replication • Rules for successful hitchhiking ••DONDON’’TT PANICPANIC •Know where your towel is •There is more than meets the eye •Have this guide and supplemental IBM materials at your disposal 2 Here are some additional items to keep in mind besides not smoking (we are forced to put you out before the sprinklers kick in) and silencing your electronic umbilical devices (there is something to be said for the good old days of land lines only and Ma Bell). But first a definition Hitchhike: Pronunciation: 'hich-"hIk Function: verb intransitive senses 1 : to travel by securing free rides from passing vehicles 2 : to be carried or transported by chance or unintentionally <destructive insects hitchhiking on ships> transitive senses : to solicit and obtain (a free ride) especially in a passing vehicle -hitch·hik·er noun – person that does the above Opening with the words “Don’t Panic” will instill a level of trust that at least by the end of this presentation you will be able to engage in meaningful conversations with your peers and management on the subject of replication.
    [Show full text]
  • Forensic Attribution Challenges During Forensic Examinations of Databases
    Forensic Attribution Challenges During Forensic Examinations Of Databases by Werner Karl Hauger Submitted in fulfilment of the requirements for the degree Master of Science (Computer Science) in the Faculty of Engineering, Built Environment and Information Technology University of Pretoria, Pretoria September 2018 Publication data: Werner Karl Hauger. Forensic Attribution Challenges During Forensic Examinations Of Databases. Master's disser- tation, University of Pretoria, Department of Computer Science, Pretoria, South Africa, September 2018. Electronic, hyperlinked versions of this dissertation are available online, as Adobe PDF files, at: https://repository.up.ac.za/ Forensic Attribution Challenges During Forensic Examinations Of Databases by Werner Karl Hauger E-mail: [email protected] Abstract An aspect of database forensics that has not yet received much attention in the aca- demic research community is the attribution of actions performed in a database. When forensic attribution is performed for actions executed in computer systems, it is nec- essary to avoid incorrectly attributing actions to processes or actors. This is because the outcome of forensic attribution may be used to determine civil or criminal liabil- ity. Therefore, correctness is extremely important when attributing actions in computer systems, also when performing forensic attribution in databases. Any circumstances that can compromise the correctness of the attribution results need to be identified and addressed. This dissertation explores possible challenges when performing forensic attribution in databases. What can prevent the correct attribution of actions performed in a database? The first identified challenge is the database trigger, which has not yet been studied in the context of forensic examinations. Therefore, the dissertation investigates the impact of database triggers on forensic examinations by examining two sub questions.
    [Show full text]
  • SUGI 23: an Investigation of the Efficiency of SQL DML Operations Performed on an Oracle DBMS Using SAS/Accessr Software
    Posters An Investigation of the Efficiency of SQL DML Operations Performed on an ORACLE DBMS using SAS/ACCESS Software Annie Guo, Ischemia Research and Education Foundation, San Francisco, California Abstract Table 1.1: Before Modification Of Final Records Id Entry MedCode Period1 Period2 Indication AG1001 Entry1 AN312 Postop Day1 Routine AG1001 Entry2 AN312 Postop Day1 Routine In an international epidemiological study of 2000 cardiac AG1001 Final AN312 Postop Day1 Non-routine ← To be updated surgery patients, the data of 7000 variables are entered AG1001 Final HC527 Intraop PostCPB Maintenance ← To be deleted AG1002 Entry1 PV946 Intraop PreCPB Non-routine ← To be inserted through a Visual Basic data entry system and stored in 57 AG1002 Entry2 PV946 Intraop PreCPB Non-routine as ‘Final’ large ORACLE tables. A SAS application is developed to Table 1.2: After Modification Of Final Records automatically convert the ORACLE tables to SAS data sets, Id Entry MedCode Period1 Period2 Indication AG1001 Entry1 AN312 Postop Day1 Routine perform a series of intensive data processing, and based AG1001 Entry2 AN312 Postop Day1 Routine AG1001 Final AN312 Postop Day1 Routine ← Updated upon the result of the data processing, dynamically pass AG1002 Entry1 PV946 Intraop PreCPB Non-routine AG1002 Entry2 PV946 Intraop PreCPB Non-routine ORACLE SQL Data Manipulation Language (DML) AG1002 Final PV946 Intraop PreCPB Non-routine ← Inserted commands such as UPDATE, DELETE and INSERT to ORACLE database and modify the data in the 57 tables. A Visual Basic module making use of ORACLE Views, Functions and PL/SQL Procedures has been developed to The modification of ORACLE data using SAS software can access the ORACLE data through ODBC driver, compare be resource-intensive, especially in dealing with large tables the 7000 variables between the 2 entries, and modify the and involving sorting in ORACLE data.
    [Show full text]
  • Chapter 1 - Introduction to Pl/Sql
    CHAPTER 1 - INTRODUCTION TO PL/SQL TRUE/FALSE 1. A programming language allows the actions of an end user to be converted into instructions that a computer can understand. ANS: T PTS: 1 REF: 2 2. Structured Query Language (SQL) is considered a procedural language. ANS: F PTS: 1 REF: 2 3. PL/SQL fully supports SQL data types. ANS: T PTS: 1 REF: 3 4. PL/SQL allows blocks of statements to be sent to Oracle in a single transmission. ANS: T PTS: 1 REF: 4 5. Database security can be increased with application processing supported by PL/SQL stored program units. ANS: T PTS: 1 REF: 4 6. Program units can enable the access of database objects to users without the users being granted privileges to access the specific objects. ANS: T PTS: 1 REF: 4 7. If you have a piece of code that has the potential of being used by various applications, saving this code on the server allows it to be shared by several applications. ANS: T PTS: 1 REF: 5 8. A database model is a general framework or design that describes how the various components of an application will be addressed. ANS: F PTS: 1 REF: 5 9. The three-tier application model is also referred to as a client/server application. ANS: F PTS: 1 REF: 5 10. The term named program unit indicates that the program is saved in a database and, therefore, can be used or shared by different applications. ANS: F PTS: 1 REF: 6 11. An event can range from a user action, such as clicking the button on the screen, to a table update statement that automatically calls a database trigger.
    [Show full text]
  • Ten Years of Critical Review on Database Forensics Research
    Digital Investigation 29 (2019) 180e197 Contents lists available at ScienceDirect Digital Investigation journal homepage: www.elsevier.com/locate/diin Ten years of critical review on database forensics research * Rupali Chopade , V.K. Pachghare Department of Computer Engineering & IT, College of Engineering, Pune, India article info abstract Article history: The database is at the heart of any digital application. With the increased use of high-tech applications, Received 22 January 2019 the database is used to store important and sensitive information. Sensitive information storage leads to Received in revised form crimes related to computer activities. Digital forensics is an investigation process to discover any un- 30 March 2019 trusted or malicious movement, which can be presented as testimony in a court of law. Database fo- Accepted 7 April 2019 rensics is a subfield of digital forensics which focuses on detailed analysis of a database including its Available online 11 April 2019 contents, log files, metadata, and data files depending on the type of database used. Database forensics research is in its mid age and has not got awareness as compare to digital forensics research. The reason Keywords: Database forensics behind this is the internal complications of the database as well as the different dimensions to be Digital forensics considered for analysis. This review paper is focusing on the last ten years of research related to forensic Artifact analysis of relational and NoSQL databases along with the study of artifacts to be considered for database Recovery forensics. This review of the current state of database forensics research will serve as a resource to move SQL forward as far as research and investigation are concerned.
    [Show full text]
  • CREATE OR REPLACE TRIGGER Logon Trigg AFTER LOGON on DATABASE BEGIN INSERT INTO Log Table (User Id, Logon Date) VALUES (USER, SYSDATE); END;
    Database Programming with PL/SQL 13-1 Introduction to Triggers Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Objectives This lesson covers the following objectives: • Describe database triggers and their uses • Define a database trigger • Recognize the difference between a database trigger and an application trigger • List two or more guidelines for using triggers • Compare and contrast database triggers and stored procedures PLSQL S13L1 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 3 Introduction to Triggers Purpose • In this lesson, you learn about a database trigger. • Triggers allow specified actions to be performed automatically within the database, without having to write extra application code. • Triggers increase the power of the database, and the power of your application. • You will learn more about triggers in the following lessons. PLSQL S13L1 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 4 Introduction to Triggers Need For A Trigger • Let’s start with an example: A business rule states that whenever an employee’s salary is changed, the change must be recorded in a logging table. • You could create two procedures to do this: UPD_EMP_SAL to update the salary, and LOG_SAL_CHANGE to insert the row into the logging table. • You could invoke LOG_SAL_CHANGE from within UPD_EMP_SAL, or invoke LOG_SAL_CHANGE separately from the calling environment. PLSQL S13L1 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 5 Introduction to Triggers Need For A Trigger • But you do not have to do this. • Instead, you create a trigger. • The next slide shows how. PLSQL S13L1 Copyright © 2016, Oracle and/or its affiliates.
    [Show full text]
  • Sql Databas Schema Design
    Sql Databas Schema Design Instrumentalist and chained Isa remigrate her crew quests dandily or rusticated designedly, is Wendel deliberate? Is Thaine loutish when Sebastian immortalize decussately? Morton glaired his inevitableness wiretap additively, but plausive Peirce never phlebotomises so vengefully. The how information do an owner of schema design sql language but it took me incredible flexibility without leaving the application with much space to examine the evolution of intricate structure that solution for The suspend reason may use the dbo schema is convenience so you don't have i plan your schemas roles rights and requirements out very great detail. The familiar SQL syntax for table partitioning specifies how rows should be partitioned across shards For example of following SQL statement creates a sharded. We propagate a MySQL schema design that helps in analyzing and tuning query. Database schema types NoSQL example SQL server example. For three you never use a SQL query has a LIMIT ten get up most. Plan projects on their own code tabs to sql databas schema design modification event happens when joining multiple schemas provide forward. By Jim Evans Updated 2019-12-17 Comments 5 Related More Database Design. SQL Server Database Diagram Examples Download ERD. What a database schema design? What do database schemas 5 minute drive with examples. Microsoft SQL Server Database Design Principles Part 1. Simply reflects the schema to sql schema. At year end within our design stage the logical schema will be specified by SQL data definition language DDL statements which tax the maid that needs. What legal Entity Relationship Diagram ERD How to either Database Specification How great Reverse Database Schema into Entity Relationship Diagram.
    [Show full text]
  • Oracle Fusion Middleware Error Messages Guide
    Oracle® WebLogic Server Error Messages Reference 12c Release 1 (12.1.1) E26117-01 December 2011 This document contains the Message Catalogs for Oracle WebLogic Server. Oracle WebLogic Server Error Messages Reference, 12c Release 1 (12.1.1) E26117-01 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. 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, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Nosql for Dummies®
    NoSQL For Dummies® by Adam Fowler NoSQL For Dummies® Published by: John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030-5774, www.wiley.com Copyright © 2015 by John Wiley & Sons, Inc., Hoboken, New Jersey Media and software compilation copyright © 2015 by John Wiley & Sons, Inc. All rights reserved. Published simultaneously in Canada No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without the prior written permission of the Publisher. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at http://www.wiley.com/go/permissions. Trademarks: Wiley, For Dummies, the Dummies Man logo, Dummies.com, Making Everything Easier, and related trade dress are trademarks or registered trademarks of John Wiley & Sons, Inc. and may not be used without written permission. All other trademarks are the property of their respective owners. John Wiley & Sons, Inc. is not associated with any product or vendor mentioned in this book. LIMIT OF LIABILITY/DISCLAIMER OF WARRANTY: THE PUBLISHER AND THE AUTHOR MAKE NO REPRESENTATIONS OR WARRANTIES WITH RESPECT TO THE ACCURACY OR COMPLETENESS OF THE CONTENTS OF THIS WORK AND SPECIFICALLY DISCLAIM ALL WARRANTIES, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE. NO WARRANTY MAY BE CREATED OR EXTENDED BY SALES OR PROMOTIONAL MATERIALS.
    [Show full text]