Basic knowledge of DB2 database-operation procedure of DB2catalog

Today we will mainly talk about DB2catalog, a basic knowledge of the DB2 database. We all know that the catalog in the DB2 database is catalogued. This word is hard to understand. In other words, the cataloguing has a directory node, cataloguing databases. To understand the cataloguing.

First, let me briefly talk about the architecture of the DB2 database. The biggest concept in the DB2 database is the system node) that is, the host. The following is an instance. The instance is the database, and then the tablespace, then the database object.

Now suppose you have a database server on p570, and you have a client on windows, linux, or any platform. Now you want to establish a client-to-server connection, what are the specific steps?

Step 2:

You must identify the remote server on the client machine. How can this problem be solved? The catalog Method Used in DB2 is to write the remote server into a file on the local client through the catalog:

 
 

  
  
db2 catalog tcpip node p570 remote 172.10.10.10 server 50000 
 
 

In the above command, p570 is a node name that must be unique on a machine), remote is followed by the server IP address, and server is the port number corresponding to the instance on the remote server. DB2 records the remote server information in the local SQLNODIR file in this way. Therefore, the cataloguing node maps the remote server to the local server, the records in SQLNODIR can be used to locate the remote server and instance, similar to the address pointer pointing to the remote server and instance.

Step 2:

After the remote server IP address and instance are catalogued, the database under the instance should be catalogued locally in step 2.

 
 

  
  
db2 catalog db REMOTEDB at node p570 
 
 

In this command, REMOTEDB is the database under the remote instance, and p570 is the name of the target node in step 1.

After this command is executed, the remote database information is recorded in the local SQLDBDIR file, which can be understood as ing the database under the remote server instance to a local alias.

The preceding example shows that the client and server are not on the same machine, and the database is catalogued through the cataloguing node to connect the client to the database on the server. If the client is connected to the same machine, at this time, do not display the cataloguing nodes. However, when we create an instance on the server, there is an implicit process of cataloging the instance locally, assume that an instance named db2inst1 is created on p570, there is an implicit

Db2 catalog local node db2inst1 instance db2inst1 system p570 ostype aix steps,

Similarly, when you create a database MYDB under db2inst1, there is an implicit catalog) database step:

Steps for db2 catalog db mydb at node db2inst1

So far, you can understand the catalog). cataloguing is the purpose of establishing a database connection from the client to the server locally or remotely. The above content is the description of DB2catalog, hoping to help you in this regard.

The above content is an introduction to DB2catalog, and I hope you will get some benefits.