Update to Object Restore v2.1 User’s Guide

Product documentation


Abstract

Updates that apply to Object Restore v2.1 User’s Guide (SC18-9135-03)

Content

The most recent update is listed first.

Update 2
Date of change: January 23, 2012
Topic: Cloned table restriction
Change description: Multiple topics updated to add content for DB2 Version 10 Exploitation

The following section details the content changes to the IBM DB2 Object Restore for z/OS Version 2 Release 1 User’s Guide (SC18-9135-03).

Restrictions

On page 5, a new restriction has been added:

DB2 Object Restore does note support data recovery for cloned tables. Only the DLL can be recovered.

Update 1
Date of change: September 28, 2011
Topic: DB2 Version 10 Exploitation
Change description: Multiple topics updated to add content for DB2 Version 10 Exploitation

The following sections detail the content changes to the IBM DB2 Object Restore for z/OS Version 2 Release 1 User’s Guide (SC18-9135-03).

Restrictions
Summary of changes
Saving JCL
New DB2 Version 10 System Privileges
Migrating an existing Object Restore installation to DB2 Version 10
Glossary
New Messages

Restrictions

On page 5, new restrictions have been added:

  • Relating to Inline LOB support that was added for DB2 V10, if an object contains an inline LOB, and REORG or RECOVER is specified, then the base table space and the LOB table space must be recovered together.
  • DB2 Object Restore does not support the Native SQL Routines (functions and procedures) that were added in DB2 Version 9.
  • DB2 Object Restore does not support the DEFINE NO clause for LOB and XML table spaces and their dependent index spaces.

Summary of changes

On page 7, new items have been added to the list of changes:

DB2 Object Restore has been updated to exploit the new features available in DB2 version 10. There are no special requirements for using these features beyond installing DB2 Object Restore on a DB2 V10 subsystem or migrating a DB2 Object Restore installation from a DB2 V9 system after the DB2 environment has been migrated to DB2 V10. Unless documented in sections that follow, no user interface elements have changed for these enhancements.

    Versioned table support

    DB2 Version 10 added the ability for a DB2 system to keep track of versioned (or historical) data automatically. This involves creating a separate table space and table to hold the related history data.

    New DB2 V10 System Privileges

    There were some new system privileges added in V10. The System Privileges screen (option UA off the DB2 Object Restore main menu) displays these new privileges.

    Timestamp precision and Timezone support

    DB2 Version 10 allows a TIMESTAMP data type to be defined with more sub-second digits. The number of sub-second (or fractional-second) digits is called the precision.

    Inline LOB support

    DB2 Version 10 introduced an inline LOB, which allows the inline portion of the LOB to reside in the same table space along with the other non-LOB columns.

    Organized By Hash clause for tables

    Hash access allows direct access of a table row without using an index. This new access method will employ the use of a hashing technique to transform the key into a physical location of the row, such that a query with an equal predicate will almost always result in a single page access to retrieve the matching row.

    Index INCLUDE column support

    This feature allows a DB2 V10 NFM user to add ‘non-key’ (non-constraint enforcing) columns to existing UNIQUE indexes to gain ‘index-only’ access performance. These columns that do not participate in the UNIQUE constraint key, but are included in a UNIQUE index, are called INCLUDE columns.

    Support FlashCopy Image Copies

    Many of the IBM utilities allow for FlashCopy to be driven to create an image copy. DB2 Object Restore now supports those image copies.

    Implement MEMBER CLUSTER clause of the create TABLESPACE statement

    This impacts Object Restore’s dropped object recovery function. Object Restore SLR tables have been updated to track the new table space attributes required for this feature.

    Timestamp with Time Zone

    DB2 Version 10 allows a TIMESTAMP data type to be defined with a TIME ZONE attribute. DB2 Object Restore now supports those data type definitions.

Saving JCL

On pages 53, 107, and 109, new information has been added to the Save JCL panel. This text states that:
“Dataset must be RECFM=FB LRECL=80”.

New DB2 Version 10 System Privileges

Starting on page 97, new columns have been added to the System Privileges panel:

EXPLAINAUTH
SQLADMAUTH
SDBADMAUTH
DATAACCESSAUTH
ACCESSCTRLAUTH
CREATESECUREAUTH

These new columns only display on DB2 V10 systems.

Migrating an existing Object Restore installation to DB2 Version 10

On page 116, a section has been added before the Edit SAUOSAMP members heading. This is new text:

    Overview
    If you have an existing Object Restore installation on a DB2 version prior to version 10, there are migration tasks that you must run in order to migrate the existing Object Restore installation to be compatible with DB2 version 10.

    Migrating the schema level repository from DB2 V8 NFM to DB2 V10 NFM

    This section details each of the tasks that are necessary to migrate the DB2 Object Restore schema level repository from DB2 V8 NFM to a DB2 V10 NFM schema level repository. The first step in this process is to migrate the DB2 Object Restore schema level repository from DB2 V8 NFM to support DB2 V10 CM8/ENFM8. The second step in the process is to migrate the schema level repository from DB2 V10 CM8/ENFM8 to support DB2 V10 NFM.

    1. Migrating the schema level repository from DB2 V8 NFM to support DB2 V10 CM8/ENFM8
    • AUOMIG91 – alters and updates the existing repository tables.
    • AUOMIG92 – creates new objects and performs inserts into new repository tables.

    Migrating the schema level repository from DB2 V9 NFM or DB2 V10 CM8/ENFM8 to support DB2 V10 NFM

    After completing the migration of the schema level repository from DB2 V8 NFM to DB2 V10 CM8/ENFM8, you can perform the second step in the migration process. The second step is to migrate from DB2 V10 CM8/ENFM8 to DB2 V10 NFM. This process is the same as migrating from DB2 V9 NFM.

    This section details each of the tasks that are necessary to migrate the DB2 Object Restore schema level repository from DB2 V9 NFM or DB2 V10 CM8/ENFM8 to a DB2 V10 NFM schema level repository.

    AUOMIGA1 - creates new objects, performs alters to existing repository tables, and performs inserts into new repository tables.

Glossary

On page 151, new terms have been added to the DB2 Object Restore glossary:

    Include Columns--Columns that do not participate in the UNIQUE constraint key, but are included in a UNIQUE index, are called INCLUDE columns.

    Length--(Column length) The number of bytes that comprise a column internally.

    Precision--The number of fractional second digits kept in a timestamp.



New Messages

The following message has been added to DB2 Object Restore:

AUO082I - SQL Undo/Redo not allowed for spaces with VERSIONING.
Explanation: You have attempted to generate redo or undo SQL for a table space that uses table versioning. This action is not allowed.
User Response: None.

Publication number

SC18-9135-03

Copyright date

2001, 2011

Original publication date

2011/9/28

Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 Tools for z/OS
DB2 Object Restore

Software version:

2.1.0

Operating system(s):

z/OS

Reference #:

7023157

Modified date:

2012-01-23

Translate my page

Machine Translation

Content navigation