2 options
IBM DB2 Data Archive Expert for z/OS : put your data in its place / [Paolo Bruni ... et al.].
- Format:
- Book
- Series:
- IBM redbooks.
- IBM redbooks
- Language:
- English
- Subjects (All):
- Database management.
- IBM Database 2.
- z/OS.
- Physical Description:
- xxiv, 344 p. : ill.
- Edition:
- 1st ed.
- Place of Publication:
- San Jose, CA : IBM, International Technical Support Organization, c2004.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Figures
- Tables
- Examples
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Part 1 Introduction
- Chapter 1. Archiving data with IBM DB2 Data Archive Expert
- 1.1 Need for archiving data
- 1.2 IBM DB2 Data Archive Expert
- 1.2.1 The archive process
- 1.2.2 The tool's architecture
- 1.2.3 Data Archive Expert as DB2 application
- Part 2 Getting ready to use the product
- Chapter 2. The evaluation test data
- 2.1 Our test data
- 2.1.1 Test referential integrity
- Chapter 3. Installing and customizing DB2 Data Archive Expert
- 3.1 Pre-installation activities
- 3.1.1 Program directory
- 3.1.2 Preventive service planning
- 3.1.3 Review PTF cover letters
- 3.1.4 Review and verify product prerequisites
- 3.2 Installation steps: Details
- 3.2.1 Step 1. Create the metadata database and table space
- 3.2.2 Step 2. Create the metadata tables
- 3.2.3 Step 3. Define the DB2 Data Archive Expert stored procedures
- 3.2.4 Step 4. Java environment variable settings
- 3.2.5 Step 5. Insert default properties
- 3.2.6 Step 6. Create temporary database
- 3.2.7 Step 7. Grant the appropriate authorizations
- 3.2.8 Step 8. Verify that DSNUTILS is installed
- 3.2.9 Step 9. Make DB2 Data Archive Expert available to users
- 3.2.10 Optionally add DAE to the Administration Tool Launchpad
- 3.2.11 Optionally install DB2 Grouper
- 3.3 Execute installation verification
- Chapter 4. Installing and customizing DB2 Grouper
- 4.1 Pre-installation activities
- 4.1.1 Program Directory
- 4.1.2 Preventive Service Planning
- 4.1.3 Review PTF cover letters
- 4.1.4 Review and verify product prerequisites
- 4.2 Installation steps for host: Details
- 4.2.1 Step 1. Installing Grouper metadata for z/OS.
- 4.2.2 Step2. Defining Grouper Java stored procedures to DB2
- 4.2.3 Step 3 Java environment variable settings
- 4.2.4 Bind packages and plans
- 4.3 Installation verification
- Chapter 5. Stored procedures and batch execution
- 5.1 Batch processing considerations
- 5.1.1 Preliminary topics
- 5.1.2 Data Archive Expert stored procedures
- 5.2 Example batch jobs
- 5.2.1 Table archive specification
- 5.2.2 Building file archive specifications and using templates
- 5.2.3 Retrieval specification in batch
- 5.2.4 File retrieval from batch
- 5.2.5 Table to file archive specification in batch
- 5.2.6 Continuation of parameters and row filters
- Chapter 6. Optionally defining DB2 Grouper Client
- 6.1 Setting up the Grouper Client
- 6.1.1 Download the Grouper Client
- 6.1.2 Run the install shield
- 6.1.3 z/OS Server connectivity configuration
- 6.1.4 Client configuration
- 6.1.5 Installation verification
- Part 3 Data archival
- Chapter 7. Scenario 1: Archiving from a table to a file
- 7.1 Starting point
- 7.2 Define the archive specification
- 7.3 Run the archive specification
- 7.4 Second run of the archive specification
- 7.5 Result
- 7.6 Considerations
- 7.6.1 Intermediate table used when archiving to file
- 7.6.2 File archives require a complete run
- 7.6.3 Names of the archive data sets
- 7.6.4 How to find describing information to a given archive data set
- 7.6.5 Recommendation for data set names
- Chapter 8. Scenario 2: Archiving from a table to a table
- 8.1 Starting point
- 8.2 Define the archive specification
- 8.3 Run the archive specification
- 8.4 Result of the archive specification
- 8.5 A second run of archive specification
- 8.6 Using different archive tables per archive run
- Chapter 9. Scenario 3: Archiving from RI related tables and deleting from one
- 9.1 The objectives of this scenario.
- 9.2 Digging into the scenario
- 9.3 Data before starting the archive specification
- 9.4 Start by defining the archive unit
- 9.5 Define archive target
- 9.6 Run your specification - Step 1
- 9.7 Run your specification - Step 2
- 9.8 Second run using the same target tables
- 9.9 Checking whether too many rows have been archived
- Chapter 10. Scenario 4: Archiving from RI related tables and deleting from them
- 10.1 Archiving parts in jumbo containers
- 10.2 Step 1 - Defining the table archive specification
- 10.2.1 Define archive unit for jumbo containers
- 10.2.2 Define row filter for the jumbo containers
- 10.2.3 Archive unit table delete rules
- 10.2.4 Define archive table targets
- 10.2.5 Errors when saving the table archive specification
- 10.2.6 Limitations due to "on delete cascade" rule
- 10.2.7 Solution to the On delete cascade rule
- 10.2.8 Running the table archive
- 10.2.9 Table archive job validation
- 10.3 Step 2 - Completing the table archive
- 10.4 Step 3 - Defining archiving a table archive to file
- 10.4.1 Defining the file archive specification
- 10.4.2 Running the file archive specification
- Chapter 11. Scenario 5: Archiving Grouper discovered related tables
- 11.1 Using the Grouper Client with Data Archive Expert
- 11.2 Introduction and some definitions
- 11.3 Using Grouper to manage non-enforced relationships
- 11.4 Using Grouper to discover application relationships
- Chapter 12. Additional archive considerations
- 12.1 Knowing your data
- 12.2 DB2 enforcement
- 12.3 Orphaned rows
- 12.4 REXX exec to locate archived tables
- Part 4 Data retrieval
- Chapter 13. Scenario 1: Retrieving a single table from a table archive
- 13.1 Retrieve overview
- 13.2 Retrieve preparation
- 13.2.1 Default retrieve creator name
- 13.2.2 Retrieve authorizations.
- 13.3 Building and running a single table retrieve specification
- 13.3.1 Building a new retrieve specification
- 13.3.2 Defining a single table retrieve specification
- 13.4 Running a retrieve specification
- 13.4.1 Preparing to run the retrieve specification
- 13.4.2 Defining the single table row filter
- 13.4.3 Confirming the retrieve
- 13.5 Additional tasks
- Chapter 14. Scenario 2: Retrieving multiple tables from a file archive on tape
- 14.1 The tables involved
- 14.2 Define retrieve specification for multiple tables
- 14.3 Job to run retrieve stored procedure
- 14.4 Additional tasks
- Chapter 15. Scenario 3: Retrieving into the original tables
- 15.1 Defining retrieve specification to replace rows
- 15.1.1 Preparing to retrieve from the archive
- 15.1.2 Defining the retrieve specification
- 15.1.3 Add row filter to span archive versions
- 15.1.4 Updating the target table names
- 15.2 Running the retrieve specification
- 15.3 Additional tasks
- Part 5 Operational considerations
- Chapter 16. Planning for and managing change in an archive environment
- 16.1 Schema changes and impact on archival
- Chapter 17. Security and authorizations
- 17.1 DB2 authorizations
- 17.1.1 DB2 installation authorities
- 17.1.2 DB2 archive and retrieve authorities
- 17.2 Data set authorizations
- 17.2.1 Access to archive data sets
- 17.3 Granting access to others
- 17.3.1 Access to table archives
- 17.3.2 Access to retrieve tables
- 17.3.3 Access to file archives
- Chapter 18. Performance
- 18.1 Performance considerations
- Part 6 Appendixes
- Appendix A. REXX sample programs
- A.1 ARCHIVEEXECSP table archive REXX
- A.2 OFFLINEARCHSP file archive REXX
- A.3 RETRIEVEEXECSP table retrieve REXX
- A.4 OFFLINERETEXECSP file retrieve REXX
- A.5 OFFLINEONLARCSP table to file archive REXX
- Appendix B. Additional material.
- Locating the Web material
- Using the Web material
- System requirements for downloading the Web material
- How to use the Web material
- Related publications
- IBM Redbooks
- Other publications
- Online resources
- How to get IBM Redbooks
- Help from IBM
- Abbreviations and acronyms
- Index
- Back cover.
- Notes:
- "February 2004."
- Includes bibliographical references and index.
- OCLC:
- 80245923
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.