Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 35 views

    DB2 L2

    Uploaded by

    kushagra
    The document discusses various DB2 database objects and utilities. It describes what various tablespaces like the SKELETON CURSOR TABLESPACE (SCT02) and SYSTEM UTILITIES TABLESPACE (SYSUTILX) contain. It also summarizes the purpose of utilities like LOAD, UNLOAD, RUNSTATS, REORG TABLESPACE, and RECOVER. The document discusses locking modes and concurrency considerations with different lock sizes. It provides details on pending and copy pending tablespace states and database maintenance authorities.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd

    DB2 L2

    Uploaded by

    kushagra
    35 views2 pages
    The document discusses various DB2 database objects and utilities. It describes what various tablespaces like the SKELETON CURSOR TABLESPACE (SCT02) and SYSTEM UTILITIES TABLESPACE (SYSUTILX) contain. It also summarizes the purpose of utilities like LOAD, UNLOAD, RUNSTATS, REORG TABLESPACE, and RECOVER. The document discusses locking modes and concurrency considerations with different lock sizes. It provides details on pending and copy pending tablespace states and database maintenance authorities.

    Original Title

    DB2-L2.txt

    Copyright

    © © All Rights Reserved

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses various DB2 database objects and utilities. It describes what various tablespaces like the SKELETON CURSOR TABLESPACE (SCT02) and SYSTEM UTILITIES TABLESPACE (SYSUTILX) contain. It also summarizes the purpose of utilities like LOAD, UNLOAD, RUNSTATS, REORG TABLESPACE, and RECOVER. The document discusses locking modes and concurrency considerations with different lock sizes. It provides details on pending and copy pending tablespace states and database maintenance authorities.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Download as txt, pdf, or txt
    35 views2 pages

    DB2 L2

    Uploaded by

    kushagra
    The document discusses various DB2 database objects and utilities. It describes what various tablespaces like the SKELETON CURSOR TABLESPACE (SCT02) and SYSTEM UTILITIES TABLESPACE (SYSUTILX) contain. It also summarizes the purpose of utilities like LOAD, UNLOAD, RUNSTATS, REORG TABLESPACE, and RECOVER. The document discusses locking modes and concurrency considerations with different lock sizes. It provides details on pending and copy pending tablespace states and database maintenance authorities.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Download as txt, pdf, or txt
    You are on page 1of 2

    SKELETON CURSOR TABLESPACE (SCT02) CONTAINS PLANS

    LOG RANGE TABLE SPACE (SYSLGRNX) CONTAINS THE RBA (RELATIVE BYTE ADDRESS ) THE LOG
    DATASET

    SYSTEM UTILITIES TABLE SPACE (SYSUTILX) CONTAINS THE INFORMATION ABOUT RUNNING
    UTILITIES

    The Database Descriptor Tablespace (DBD01) contains internal control blocks that
    describe the databases existing within DB2

    Buffer pools, also known as virtual buffer pools, are areas of virtual storage used
    temporarily to store pages of table spaces or indexes.

    Load utility is used to load data from a sequential/VSAM file to a TABLE in a table
    space.

    RESUME NO REPLACE: This causes the utility to over write the existing data.

    RESUME YES: This allows the utility to add new rows to the existing table.

    The LOG NO command instructs the utility not to record data in the log as they are
    loaded .

    The UNLOAD online utility copies data from one or more source objects to one or
    more BSAM sequential data sets

    The RUNSTATS utility reads tablespaces and indexes to collect statistics describing
    the data.

    The REORG TABLESPACE online utility reorganizes a table space

    The RECOVER online utility recovers data to the current state or to a previous
    point in time by restoring a copy and then applying log records.

    Check pending is a tablespace/index status set when DB2 has reason to believe that
    an object might be in an inconsistent state.
    Usually happens as a result of running LOAD on a tablespace containing a table
    that has Referential Integrity constraints, but that was not enforced during the
    LOAD OPERATION (ENFORCE NO).

    COPYPENDING
    Any table space will be in copy pending status after load is performed on the DB2
    table,
    with log no parameter
    or
    if load is performed without taking an image copy
    or
    if the job abend during load
    or
    if NOCOPYPEND parameter is not specified in syspunch dataset

    VIEW MECHANISM CAN BE USED TO PROTECT SENSITIVE DATA FROM USERS BY CREATING A VIEW
    ON COLUMNS OF THE BASE TABLE THAT ARE NOT SENSITIVE.

    DBMAINT
    DATABASE MAINTENANCE AUTHORITY on a specific database allows the holder to execute
    read only maintenance functions on the database
    SYSOPR
    SYSTEM OPERATOR AUTHORITY allows the holder to carry out console operator functions
    on the system.

    DELETE RULE
    DELETION OF A PRIMARY KEY VALUE WHEN A CORRESPONDING VALUE EXISTS
    WILL BE BARRED IF THE FOREIGN KEY CONSTRAINT HAS BEEN SPECIFIED AS RESTRICT

    All data changes and other significant activities are recorded in logs by DB2.
    Database manager may use the backup copies and the logs to re-establish the data
    base to the last committed unit of work.

    LOCK SIZES AND TYPES


    A locksize of tablespace allows a process to lock the tablespace which controls all
    tables inside the table space.
    On the other hand row lock will only lock the row which the application program
    wants.

    Locking larger or smaller amounts of data allows you to trade performance for
    concurrency.
    When you use page or row locks instead of table or tablespace locks concurrency
    usually improves, meaning better response times.
    When you use only table or tablespace locks then processing time and storage used
    is reduced.
    But concurrency is also reduced , meaning longer response times for some users.

    For maximum concurrency, locks on a small amount of data held for a short duration
    are better than locks on a large amount of data held for a long duration of time.

    If the application process returns to the same page and reads the same row again,
    the data cannot have changed, although additional rows might have been inserted by
    another application process.
    A similar situation can also occur if a row or page that is not returned to the
    application is updated by another application process. If the row now satisfies the
    search condition, it appears.

    But the application is in danger of reading data that was changed by another
    operation but not yet committed.

    The locking modes IS IX SIX are used at the TABLE OR TABLESPACE level to support
    row or page locks.

    You might also like