SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

FORMAT 2
CODE 563
EXT ( 128 PAGES, 256 PAGES, MAXEXTENTS 512 )
PACKED REC 48
BLOCK 4096
KEY ( COLUMN 0, ASC ,
COLUMN 1, ASC )
AUDIT
BUFFERED
AUDITCOMPRESS
OWNER -1
SECURITY (RWEP): *SQL
DATA MODIF: 19 Jan 2011, 17:24, OPEN
CREATION DATE: 27 Nov 2009, 19:40
REDEFINITION DATE: 27 Nov 2009, 19:40
LAST OPEN: 28 Jan 2011, 3:01
EOF: 12288 (0.0% USED)
EXTENTS ALLOCATED: 1
INDEX LEVELS: 1
PARTITION ARRAY FORMAT2ENABLED
Displaying Catalog Information
This subsection discusses:
• “Displaying a Catalog UID” (page 118)
• “Displaying all Catalogs Visible on a Node” (page 119)
• “Determining Whether a Catalog is Local or Remote” (page 119)
• “Displaying all Schemas in a Catalog” (page 119)
• “Displaying the Guardian Location of the Metadata Tables for a Catalog” (page 120)
• “Displaying the Attributes of a Catalog” (page 120)
Related topic:
• “Displaying all Tables in a Catalog” (page 125)
The CATSYS table on each node is the system schema table that lists all catalogs visible from the
node. For more information about all metadata tables, see Figure 3 (page 109) in this manual or
the SQL/MX Reference Manual.
Displaying a Catalog UID
Because catalog names can be up to 128 characters in length, each catalog is assigned a unique
identifier (SQL/MXUID). Use the catalog UID to efficiently join between metadata tables to display
relationships.
This example displays, for each catalog, the catalog name, the catalog UID, and all the nodes
where the catalog is visible:
>> set schema nonstop_sqlmx_figaro.system_schema;
>> select substring(cat_name, 1, 20) as cat_name, cr.cat_uid,
node_name
from catsys cs, cat_references cr
where cs.cat_uid = cr.cat_uid
and cr.replication_rule='A'
for read uncommitted access
order by cs.cat_name;
NODE_NAME
---------
CAT_UID
--------------------
CAT_NAME
-------------------—
\FIGARO
\FIGARO
6739902643326133620
6739902642481382249
CAT
NONSTOP_SQLMX_FIGARO
118 Querying SQL/MX Metadata