Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Detailed explanation of DB2 data dictionary

2025-04-06 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)06/01 Report--

For each database, a set of system catalog tables is created and maintained. These tables contain information about the definition of database objects, such as tables, views, indexes, and packages, as well as security information about the types of user access to these objects.

For DB2 databases, these tables are stored in SYSCATSPACE tablespaces with reserved system schema names:

SYSIBM, SYSFUN, and SYSPROC: a set of routines, including functions and stored procedures, where SYSIBM is the mode of the basic system catalog (it is not recommended to access it directly).

SYSCAT: a set of read-only views of system catalog tables that record structural information about database objects.

SYSSTAT: a set of updatable catalog views. These updatable views allow you to update certain statistics to simulate and test the performance of the database, or to update statistics without using the RUNSTATS utility.

SYSIBMADM: a set of dynamic performance views from which you can obtain database performance operation information.

SYSIBM.SYSCHECKS: stores information about CHECK constraints in the system, and the system creates a record for each CHECK constraint of each table.

SYSIBM.SYSCOLUMNS: the table stores the description of the data columns of all the tables in the system, and the system creates a record for each row of each table defined in the DB2.

SYSIBM.SYSDATABASE: the system saves one record for each DATABASE

SYSIBM.SYSFOREIGNKEYS: create a record for each FOREIGNKEY constraint

SYSIBM.SYSINDEXES: create a record for each index.

SYSIBM.SYSKEYS: the system creates a record for each key value of each INDEX.

SYSIBM.SYSTABLES: the system creates a row of records in the table for each table, view, and alias.

SYSIBM.SYSPACKSTMT every SQL statement in each PACKAGE has a record

SYSIBM.SYSPACKAGE has one record for each PACKAGE

SYSIBM.SYSPACKLIST has one or more records for each PLAN associated with each PACKAGE LIST

SYSIBM.SYSPLAN has one record for each PLAN

Federated object SYSCAT catalog view description wrapper SYSCAT.WRAPPERS

SYSCAT.WRAPOPTIONS

These two views show the registered wrappers and their specific options ServersSYSCAT.SERVERS

SYSCAT.SERVEROPTIONS

These two views show the registered remote data sources and their specific option user mapping SYSCAT.USEROPTIONS this view shows the user authentication of a registered DB2 user for a specific server. Password settings are stored in encrypted, nicknamed SYSCAT.TABLES

SYSCAT.TABOPTIONS

SYSCAT.COLUMNS

SYSCAT.COLOPTIONS

SYSCAT.INDEXES

SYSCAT.INDOPTIONS

SYSCAT.INDEXCOLUSE

SYSCAT.KEYCOLUSE

This set of views displays information about registered nicknames

In SYSCAT.TABLES, nicknames are identified by TYPE that is set to "N".

SYSCAT.TABOPTIONS displays specific options for nicknames

SYSCAT.COLOPTIONS displays specific options for nickname columns

SYSCAT.INDEXCOLUSE lists the columns that participate in an index

SYSCAT.KEYCOLUSE stores information about primary keys

Index specification SYSCAT.INDEXES

SYSCAT.INDEXCOLUSE

These two views display the index specification information constraints SYSCAT.TABCONST created for nicknames

SYSCAT.CHECKS

SYSCAT.COLCHECKS

SYSCAT.CONSTDEP

SYSCAT.REFERENCES

This set of views displays the information constraints defined for nicknames

SYSCAT.TABCONST displays each defined constraint

SYSCAT.CHECKS and SYSCAT.COLCHECKS display information about checking constraints

SYSCAT.CONSTDEP lists the objects on which the constraint depends

SYSCAT.REFERENCES lists reference constraints

Type mapping SYSCAT.TYPEMAPPINGS this view shows the user-defined type mappings used in nickname registration and remote table creation. The default built-in type mapping is not stored in the function template SYSCAT.FUNCTIONS in this catalog view

SYSCAT.ROUTINES

These two views show the registered user-defined functions

In V8, SYSCAT.ROUTINES replaces SYSCAT.FUNCTIONS (SYSCAT.FUNCTIONS still exists, but is not specified in the documentation)

Function mapping SYSCAT.FUNCMAPPINGS

SYSCAT.FUNCMAPOPTIONS

SYSCAT.FUNCMAPPARMOPTIONS

These views show the user-defined function mapping Passthru permissions SYSCAT.PASSTHRUAUTH used to map a local function to a remote function this view shows the authorization that allows the user to query a specific server using PASSTHRU

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report