The single user mode tools are accessible from the Database Utility Functions Panel shown in Figure 138. The single user mode tools are identified as "Single-User" types on the Database Utility Functions panel. Each of these types of tools will be covered in this chapter with the exception of the Single User Mode DBSPACE Reorganization tool (refer to Chapter 28, DBSPACE Reorganization Tools).
Figure 138. Database Utilities Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy CONTROL CENTER hh:mm:ss | | *------------------------ Database Utility Functions -----------------------* | | | Option ===> CTRLID: MSTRSRV1 | | | | Database ===> SQMDBA NODE: VMSYSTM1 | | | | **FUNCTION** **TYPE** *****DESCRIPTION***** | | | | E ADD DBEXTENTS Single-User SQLADBEX utility | | | | C COPY/MOVE DBEXTENTS Single-User SQLCDBEX utility | | | | D DELETE DBEXTENTS Single-User SQLADBEX DELETE | | | | A ADD DBSPACES Single-User SQLADBSP utility | | | | CL COLDLOG Single-User COLDLOG utility (SQLLOG) | | | | RC REORG CATALOG INDEXES Single-User SQLCIREO utility | | | | RS RELOAD SINGLE USER Single-User SUM dbspace reload only | | | | SU REORG SINGLE USER Single-User SUM reorg entirely on DBmachine | | | | R SQLREORG Multi-User DBSPACE reorganization | | | | T SQLTABLE Multi-User Table reorgs/manipulation | | | | M SQLMAINT Multi-User Automated dbspace maintenance | | | | B SQLRBIND Multi-User Rebind Packages | | | | RI REORG INDEX TOOL Multi-User DBSPACE Index Maintenance Tool | | | | RD REORG DRIVER TOOL Multi-User SQLREORG Driver by DBSPACE List | | | | SL SEARCH/LIST Multi-User Search and List DBSPACES/TABLES | | | | | | | *---------------------------------------------------------------SQMDUTIL----* | | PF: 1 Help 3 End 8 Forward (tools continued) | | | +--------------------------------------------------------------------------------+
Before continuing, you should be familiar with the material presented in:
These tools are used to invoke and manage utilities that run on database virtual machines in single user mode (SUM). By using these tools you can fully automate your database's single user mode activities.
When the database utilities run, they ask many processing-related questions. For example, as the SQLADBEX (add DBEXTENT) utility runs, it prompts for the virtual addresses of the dbextents (minidisks) to be added.
Control Center provides this information to the SQLADBEX utility as it is requested. The information used is provided by you through its single user mode tool panels.
Each of its single user mode tools can be invoked to run immediately or scheduled for later execution. When a SUM tool is invoked, the database machine is terminated and the appropriate single user mode utility is started. During the processing of the utility the database is unavailable. Upon completion, the database will be returned to its original starting status (up or down).
The single user mode tools create log files containing the database console messages produced during the specific SUM activity. Log files are stored on Control Center's 191 A-disk, with filenames matching the database's name and filetypes that indicate the type of activity. For example, the database console messages produced during an add dbextent (ADBEX) job for database SQLDBA would be saved in log file SQLDBA ADBEXLOG. Each specific log file created by these tools will be outlined in this chapter.
The single user mode tools maintain individual history files recording the date, time, and other relevant information pertaining to these types of activities. The history files are stored on the its 191 A-disk, with filenames matching the database's name and filetypes that indicate the type of activity. For example, the history information for all add dbextent activities for database SQLDBA would be found in history file SQLDBA ADBEXHIS.
Use of the single user mode tools requires Control Center database Administration-level or greater authorization (refer to the DB2 Server for VM Control Center Program Directory).
Display of log and history files requires Control Center user-level or greater authorization.
| Operational Note: | Control Center provides a default set of tools that are accessible by its database User, Operator, or Administration-level authorizations. These defaults can be changed so as to add or delete Control Center database User, Operator, or Administration authorizations to specific tools. For more details on how your authorization levels can be modified, refer to Appendix E, Authorizations. |
The Add DBEXTENTS tool automates the execution of the SQLADBEX utility. Use this tool when you need to add new dbextents (minidisks) to a database.
Before beginning, you should review and understand all information regarding the adding of new dbextents to a database as outlined in the DB2 Server for VM System Administration manual.
| Note: | All new minidisks for dbextents to be added must be added to the database virtual machine's VM directory prior to the running of the dbextent add process. |
To start the Add DBEXTENTS tool, use the panel interface to provide the virtual addresses and storage pool numbers (refer to the DB2 Server for VM System Administration manual) for each new dbextent (minidisk) to be added.
Once the information has been specified, you can initiate the process immediately or schedule it to run later. When the process runs, the database machine will be terminated and Control Center will start the SQLADBEX utility on the database virtual machine. While the SQLADBEX utility runs, Control Center provides all information that is requested.
Upon completion of the SQLADBEX utility, the database will be returned to its original status (either up or down).
Shown in Figure 139 is the Add DBEXTENTS entry panel used to specify dbextents to be added to a database. The panel consists of two sections: New DBEXTENTS and New NON-RECOVERABLE Storage Pools.
Specify in this section of the panel all new dbextents to be added to the specified database. If a storage pool specified in this section is new and is not specified in the New NON-RECOVERABLE section, then it will be defined to the database as a "recoverable" storage pool. The entry for storage pool 7 in Figure 139 shows an example of how a new "recoverable" storage pool is specified.
|If a storage pool is both new and needs to be defined to the |database as a 'Non-Recoverable' storage pool, then it needs to be |listed in both the 'New Dbextents' and the 'New Non-Recoverable |Storage Pools' sections. Storage pool 9 in Figure 139 shows an example of how a new "non-recoverable" storage pool is specified.
If a storage pool is not new, specify the pool number in the New DBEXTENTS section of the panel and not in the New NON-RECOVERABLE section.
Figure 139. Control Center Add DBEXTENTS Definition Entry Panel
+--------------------------------------------------------------------------------+
| mm/dd/yyyy CONTROL CENTER hh:mm:ss |
| *--------------------------- SQLADBEX Definition ---------------------------* |
| | Command ==> CTRLID: MSTRSRV1 | |
| | Database => SQMDBA NODE: VMSYSTM1 | |
| | ****************************** New DBEXTENTS *************************** | |
| | POOL VADR EXT | POOL VADR EXT | POOL VADR EXT | POOL VADR EXT | |
| | 7 225 ___ | ___ ____ ___ | ___ ____ ___ | ___ ____ ___ | |
| | 9 226 ___ | ___ ____ ___ | ___ ____ ___ | ___ ____ ___ | |
| | ___ ____ ___ | ___ ____ ___ | ___ ____ ___ | ___ ____ ___ | |
| | ___ ____ ___ | ___ ____ ___ | ___ ____ ___ | ___ ____ ___ | |
| | ___ ____ ___ | ___ ____ ___ | ___ ____ ___ | ___ ____ ___ | |
| | ___ ____ ___ | ___ ____ ___ | ___ ____ ___ | ___ ____ ___ | |
| | ___ ____ ___ | ___ ____ ___ | ___ ____ ___ | ___ ____ ___ | |
| | | |
| | ******************* New NON-RECOVERABLE Storage Pools ****************** | |
| | POOL POOL POOL POOL POOL POOL POOL POOL POOL POOL | |
| | |9 ___ ___ ___ ___ ___ ___ ___ ___ ___ | |
| | ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ | |
| | | |
| | Enter New extents and any NEW NON-LOGGING pools, press ENTER to process | |
| | | |
| *---------------------------------------------------------------SQMADE11----* |
| PF: 1 Help 3 End (QUIT) ENTER Process 10 SHOW POOL 11 Q DBEXTENTS |
| |
+--------------------------------------------------------------------------------+
The pool and virtual address (VADR) entry fields must be specified for all DBEXTENTS to be added. There are 28 POOL/VADR/EXT entry fields available within the New DBEXTENTS section of the panel. This limits to 28 as the maximum number of DBEXTENTS that may be added by Control Center in a single execution of the Add DBEXTENTS tool (see note below).
The VADR entry fields must match the virtual addresses for the new minidisks as defined in the VM directory for the database's virtual machine. The POOL entry field entered for each minidisk may be either an existing storage pool or a new storage pool. If an existing storage pool is specified, the minidisk will be added as another DBEXTENT in the storage pool.
When new storage pools are defined, you may optionally designate that they should be non-recoverable by listing them in the lower section of the panel.
| Important: |
|---|
|
Only list pool numbers in the lower section of the data entry panel if you want them to be NON-RECOVERABLE (non-logging) and they are new pools. |
Two files are created based on your entries on the Add DBEXTENTS panel. These files are used by Control Center during the execution of the SQLADBEX utility on the database machine. These control files are identified by database and have filetypes of ADEXTENT and ADNLPOOL. Control Center will invoke the SQLADBEX utility to start the add dbextents process. When the SQLADBEX utility prompts for what is to be done, Control Center uses the information contained in these two files.
| Note: |
|---|
|
The Add DBEXTENTS tool uses a single set of control files for each database machine. You cannot, therefore, schedule multiple add dbextents jobs for the same database because each new job will overlay the previously created control file set for that database. |
A log file is created that contains all the database console messages produced while the SQLADBEX utility runs. This log file is kept for each database on Control Center's 191 A-disk. |The name of the log file is | dbmach |ADBEXLOG; | dbmach |is the database virtual machine.
In addition to the log file, Control Center |maintains a historical record for each database of its Add Dbextents activity. |This is stored in a file named | dbmach| ADBEXHIS; | dbmach| is the database virtual machine. It is kept on its |A-disk.
| Note: | This file is also used to record deleted dbextent information. |
Shown in Figure 140 is an example of an ADBEXHIS file which provides information about all dbextents that have been added to a database. This example shows that pools 7 and 8 were added on 03/16/97 at approximately half an hour past local midnight.
Figure 140. Example Add DBEXTENTS History File (ADBEXHIS)
01/02/97 00:06:49 ADDED (POOL, VADR) 6 222 02/20/97 01:34:21 ADDED (POOL, VADR) 5 224 03/16/97 00:38:26 ADDED (POOL, VADR) 7 225 03/16/97 00:38:26 ADDED (POOL, VADR) 8 226 |
The Delete DBEXTENTS tool automates the execution of the SQLADBEX utility's delete processing. Use this tool when deleting dbextents from a database.
There are many technical considerations and associated precautions involved when deleting a dbextent. Review the sections on deleting a dbextent in the DB2 Server for VM System Administration manual.
Before starting, you must determine the dbextent number(s) for the dbextents that you want to delete. The numbers can be determined by reviewing the report generated by the Query DBEXTENTS/STORPOOL Mapping tool prior to using this tool or by using PF11 from this tool's panel. Only those dbextents that are empty (No. Pages In Use = 0) or those that exist within a storage pool with "enough" free pages in other dbextents may be deleted; "enough" is defined as a number large enough to hold any data that is still in the dbextent to be deleted.
To start the Delete DBEXTENTS tool, you use the panel interface to provide the dbextent numbers for the dbextents that you want deleted.
Once the information has been specified, you can initiate the process immediately or schedule it to run later. When the process runs, the database machine will be terminated and Control Center will start the SQLADBEX utility on the database virtual machine. While the SQLADBEX utility runs Control Center provides all information that is requested.
Upon completion of the SQLADBEX utility, the database is returned to its original status (up or down).
Shown in Figure 141 is the entry panel provided for deleting dbextents. The panel provides for a maximum of ten (10) dbextents to be deleted by a single Delete DBEXTENTS job.
Figure 141. Control Center Delete DBEXTENTS Entry Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy CONTROL CENTER hh:mm:ss | | *------------------------ Delete DBEXTENT Selection ------------------------* | | | Command ==> CTRLID: MSTRSRV1 | | | | Database => SQLDBA NODE: VMSYSTM1 | | | | **************************** Delete DBEXTENTS ************************** | | | | | | | | Dbextent Number to DELETE ==> 57 | | | | Dbextent Number to DELETE ==> 58 | | | | Dbextent Number to DELETE ==> ____ | | | | Dbextent Number to DELETE ==> ____ | | | | Dbextent Number to DELETE ==> ____ | | | | Dbextent Number to DELETE ==> ____ | | | | Dbextent Number to DELETE ==> ____ | | | | Dbextent Number to DELETE ==> ____ | | | | Dbextent Number to DELETE ==> ____ | | | | Dbextent Number to DELETE ==> ____ | | | | | | | | | | | | | | | | Enter Extent Number(s) to DELETE and press ENTER to PROCESS | | | | | | | *---------------------------------------------------------------SQMDDE10----* | | PF: 1 Help 3 End (QUIT) ENTER Process 10 SHOW POOL 11 Q DBEXTENTS | | | +--------------------------------------------------------------------------------+
A control file is created based on inputs to the Delete DBEXTENTS panel. This file will be used by Control Center during the execution of the SQLADBEX utility on the database machine. The control file is kept on Control Center's 191 A-disk and is named dbmach DBDELEXT; dbmach is the database virtual machine name.
| Note: |
|---|
|
The Delete DBEXTENTS tool uses a single control file for each database machine. You cannot, therefore, schedule multiple Delete DBEXTENTS jobs for the same database because each new job (scheduled or immediate invocation) will overlay the previously created control file. |
Control Center creates a log file that contains all the database console messages produced while the SQLADBEX utility runs. This log file is kept for each database on its 191 A-disk. The file is |named |dbmach DDBEXLOG; |dbmach |is the database virtual machine name.
In addition to the log file, Control Center maintains for each database a historical record of its Delete DBEXTENTS activity. This file is kept on the Control Center 191 A-disk and is |named |dbmach ADBEXHIS; |dbmach |is the database virtual machine name.
| Note: | This file is also used to record add dbextents information. |
Shown in Figure 142 is an example of an ADBEXHIS file which provides information about all dbextents that have been added and deleted from a database. This example shows that dbextents 57 and 58 were deleted on 03/16/97 at about 1:30 in the afternoon.
Figure 142. Example Delete DBEXTENTS History File (ADBEXHIS)
12/14/95 00:06:49 ADDED (POOL, VADR) 6 222 01/20/97 01:24:16 ADDED (POOL, VADR) 7 223 01/28/97 01:34:21 ADDED (POOL, VADR) 8 224 02/20/97 00:38:26 ADDED (POOL, VADR) 7 225 02/24/97 00:38:26 ADDED (POOL, VADR) 9 226 03/16/97 13:29:54 DELETED (EXTENT) 57 03/16/97 13:29:54 DELETED (EXTENT) 58 |
Use these tools when it is necessary to move any of your database's dbextents (directory, log, or data) from one minidisk to another.
| Terminology used in this Section: | The terms "dbextent" and "minidisk" are used synonymously throughout the "Copy/Move DBEXTENTS Tools" section. |
Prior to copying any of your database's dbextents, you should review and be familiar with the SQLCDBEX utility information outlined in the DB2 Server for VM System Administration manual.
When these tools run, you are prompted by the Copy/Move DBEXTENTS panels for dbextent information. After indicating which dbextents are to be copied, you then have the option to invoke the tool immediately or to schedule a job for later execution.
When a Copy/Move tool runs, the database will be terminated (if it is not already terminated) and Control Center will invoke and manage the execution of the SQLCDBEX utility. As the utility prompts for inputs, Control Center will use the information that you provided.
Upon completion of the Copy/Move process, the database will be returned to its original status (up or down).
The Copy/Move DBEXTENTS options panel is shown in Figure 143.
Figure 143. Copy/Move DBEXTENTS Options Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy CONTROL CENTER hh:mm:ss | | *---------------------------- Copy/Move Dbextent ---------------------------* | | | Option ===> CTRLID: MSTRSRV1 | | | | Database ===> SQMDBA NODE: VMSYSTM1 | | | | | | | | D DIRECTORY DISK Copy/Expand DB2 Directory | | | | | | | | L LOG DISK Copy/Move Log Disk(s) | | | | | | | | E DATA EXTENT Copy/Move Data DBEXTENT(s) | | | | | | | | Enter OPTION and press ENTER to proceed, or | | | | press PF3 to CANCEL the SQLCDBEX function | | | | | | | *---------------------------------------------------------------SQMCDBEX----* | | PF: 1 Help 3 End | | | +--------------------------------------------------------------------------------+
| Note about Minidisk Sizes: | Only the directory minidisk can be copied to a larger minidisk using these tools. The log and data minidisks must be copied to minidisks of the same size. |
When a Copy/Move tool is run, Control Center creates a file of the database console messages produced during the running of the SQLCDBEX utility. This file is kept on Control Center's 191 A-disk and is |named |dbmach |CDBEXLOG; | dbmach |is the database virtual machine name.
| Note: | The same log file (database CDBEXLOG) is used by each of the Copy/Move DBEXTENTS tools. Therefore, each time a Copy/Move tool is run, a new log is generated, replacing the previously generated log. |
When a Copy/Move tool is run, Control Center updates a history file recording information about the dbextent copied. A separate history file is kept for each database on its 191 A-disk and is |named |dbmach |CDBEXHIS; | dbmach |is the database virtual machine name.
Shown in Figure 144 is an example database Copy/Move DBEXTENTS history file. In this example, the database directory was copied on 03/15/97 to a new virtual address of 207 (N means the new minidisk size is not greater than the original directory disk and 512 specifies the blocking). On 03/15/97, one of the database's log disks was copied to a new minidisk at virtual address 200, and on 03/16/97 dbextent number 5 (DDSK5) was copied to a minidisk at virtual address 205.
Figure 144. Example Copy/Move History File (CDBEXHIS)
03/15/97 11:28:26 COPIED: BDISK 207 N 512 03/15/97 11:38:10 COPIED: LOGDSK2 200 03/16/97 11:38:10 COPIED: DDSK5 205 |
This tool can be used to move a database directory minidisk to another minidisk of equal or greater size. Moving the directory to a larger minidisk should be done when there is not enough space in the current directory to support the addition of new dbspaces. Refer to the DB2 Server for VM System Administration manual for information about the many technical considerations and associated precautions involved when copying the directory minidisk (BDISK).
You must also be sure the new directory minidisk (BDISK) is added to the database virtual machine's VM directory and linked in WRITE mode. You do not, however, need to format and reserve the minidisk, since Control Center will have the SQLCDBEX utility format and reserve it.
To begin, invoke the Copy/Expand Database Directory tool panel interface, Option D and specify the following information:
Once this information has been specified you can initiate the process immediately or schedule it to run later. When the process runs, the database machine will be terminated by Control Center. When the database has ended operations, Control Center starts and manages the copy/move of the directory minidisk in single user mode using the SQLCDBEX utility.
When the copy directory process has completed, the database is returned to its original status (either up or down).
Shown in Figure 145 is the entry panel for the Copy/Expand Database Directory tool.
Figure 145. Control Center Copy/Expand Database Directory Entry Panel
+--------------------------------------------------------------------------------+
| mm/dd/yyyy CONTROL CENTER hh:mm:ss |
| *---------------------- Copy/Expand Database Directory ---------------------* |
| | Command ===> CTRLID: MSTRSRV1 | |
| | Database ===> SQLDBA NODE: VMSYSTM1 | |
| | | |
| | New Disk Address ===> 200 Virtual address of new Directory disk | |
| | | |
| | Output Blocksize ===> 512 512 or |4096 (VMDSS option only) | |
| | | |
| | Expand Directory ===> N Y or N, Expand Directory | |
| | Expansion Type =====> DBSPACE or ALL | |
| | | |
| | Enter the Disk Address of the new directory disk. If the new | |
| | minidisk is larger than the old minidisk and you want to expand | |
| | the size of the directory, enter Y for the Expand Directory | |
| | option. Output Blocksize must be 512 unless VM Dataspaces are | |
| | being used under VM/ESA. | |
| | | |
| | Press ENTER to select IMMEDIATE or SCHEDULED execution, or | |
| | press PF3 to CANCEL the Copy DBEXTENT function | |
| | | |
| *---------------------------------------------------------------SQMCDIR-----* |
| PF: 3 End 9 QUERY HISTORY 10 SHOW POOL 11 QUERY DBEXTENTS |
| |
+--------------------------------------------------------------------------------+
A CDBEXDIR control file is created and kept on the Control Center's 191 A-disk for each database machine (filename matches the database virtual machine name). This file has a record of the virtual address of the new database directory (BDISK) minidisk, the block size for the new minidisk, and an indication of whether the new minidisk is larger than the old. In the example shown in Figure 146, the directory will be copied to a new minidisk with a virtual address of 207, the new 207 minidisk is not (N) larger than the existing directory minidisk, and 207 has a blocksize of 512.
Figure 146. Example Copy/Expand Database Directory Control File (CDBEXDIR)
BDISK 207 N 512 DBSPACE END |
This tool can be used to move a database log minidisk to another minidisk of the same size. Use this tool when it is necessary to relocate a log minidisk to another device in support of migration or device performance requirements.
There are many technical considerations and associated precautions involved when copying a log (LOGDSK1, LOGDSK2) minidisk. Refer to the DB2 Server for VM System Administration manual.
The new log minidisks to be copied to must already be added to the database virtual machine's VM directory. The new minidisks, however, do not need to be formatted and reserved since Control Center will have them reformatted and reserved by the SQLCDBEX utility.
To begin, you invoke the Copy/Move Database Log Disk tool panel interface (option L) and specify the new virtual address for the database log minidisks to be moved.
Once this information has been specified you can initiate the process immediately or schedule it to run later. When the process runs, the database machine will be terminated by Control Center. When the database has ended operations, Control Center starts and manages the copy/move of the log minidisk(s) in single user mode using the SQLCDBEX utility.
When the move/copy tool has completed, the database is returned to its original status (either up or down).
Shown in Figure 147 is the entry panel for the Copy/Move Database Log Disk tool.
Figure 147. Control Center Copy/Move Database Log Disk Entry Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy CONTROL CENTER hh:mm:ss | | *------------------------ Copy/Move Database Log Disk ----------------------* | | | Command ===> CTRLID: MSTRSRV1 | | | | Database ===> SQMDBA NODE: VMSYSTM1 | | | | | | | | New LOGDISK1 virtual address ==> _____ Address of new LOG disk 1 | | | | | | | | New LOGDISK2 virtual address ==> _____ Address of new LOG disk 2 | | | | | | | | | | | | | | | | Enter the Disk Address of the NEW minidisks that will be used | | | | to replace the current database Log disks. You may specify LOG | | | | disk 1 only, LOG disk 2 only, or BOTH log disks as desired. | | | | | | | | | | | | | | | | Press ENTER to select IMMEDIATE or SCHEDULED execution, or | | | | press PF3 to CANCEL the Copy DBEXTENT function | | | | | | | | | | | *---------------------------------------------------------------SQMCLOG-----* | | PF: 3 End 9 QUERY HISTORY 10 SHOW POOL 11 QUERY DBEXTENTS | | | +--------------------------------------------------------------------------------+
The Copy/Move Database Log Disk tool creates a control file on Control Center's 191 A-disk. This control file is identified by a filetype of CDBLOGEX and has a filename matching the database virtual machine name. The file contains information to be used during the copy/move of a database's log minidisk.
The example shown in Figure 148 shows two logs (LOGDSK1 and LOGDSK2) that are to be moved to new minidisks at virtual addresses 301 and 302.
Figure 148. Example Copy/Move Database Log Disk Control File (CDBLOGEX)
LOGDSK1 301 LOGDSK2 302 END |
This tool can be used to move a database data (DDSKn) minidisk (dbextent) from one minidisk to another of the same size. Use this tool when it is necessary to relocate a data minidisk to another device in support of migration or device performance requirements.
There are many technical considerations and associated precautions involved when copying a data minidisk. Refer to the DB2 Server for VM System Administration manual.
The new data minidisks must be added to the database virtual machine's VM directory. The new minidisks, however, do not need to be formatted and reserved since Control Center will have them reformatted and reserved during the copy process.
To begin, you invoke the Copy/Move Data Disk tool panel interface (option E) and specify the dbextent numbers to be moved and the new virtual addresses they will be moved to.
Once this information has been specified, you can initiate the process immediately or schedule it to run later. When the process runs the database machine will be terminated by Control Center. When the database has ended operations, Control Center starts and manages the copy/move of the data minidisk(s) in single user mode using the SQLCDBEX utility.
When the move/copy tool has completed, the database is returned to its original status (either up or down).
Shown in Figure 149 is the entry panel for the Copy/Move Data Disk tool.
Figure 149. Control Center Copy/Move Data Disk Entry Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy CONTROL CENTER hh:mm:ss | | *----------------------- Copy/Move Database Dbextent -----------------------* | | | Command ===> CTRLID: MSTRSRV1 | | | | Database ===> SQMDBA NODE: VMSYSTM1 | | | | | | | | DBEXTENT New Virtual | DBEXTENT New Virtual | | | | Number Address | Number Address | | | | ____ _____ | ____ _____ | | | | ____ _____ | ____ _____ | | | | ____ _____ | ____ _____ | | | | ____ _____ | ____ _____ | | | | | | | | Enter the DBEXTENT Numbers of the database dbextents to copy and | | | | the virtual addresses of the NEW minidisks that will be used as a | | | | replacement. | | | | | | | | | | | | Press ENTER to select IMMEDIATE or SCHEDULED execution, or | | | | press PF3 to CANCEL the Copy DBEXTENT function | | | | | | | | | | | *---------------------------------------------------------------SQMCDATA----* | | PF: 3 End 9 QUERY HISTORY 10 SHOW POOL 11 QUERY DBEXTENTS | | | +--------------------------------------------------------------------------------+
You may enter up to eight dbextent numbers per Copy/Move data disk job (see note below).
The Copy/Move Data Disk tool creates a control file on Control Center's 191 A-disk. This control file is identified by a filetype of CDBEXTNT and has a filename matching the database virtual machine name. The file contains information to be used during the copy/move of a database's data minidisks.
In the example shown in Figure 150, dbextent number 4 will be copied to a new minidisk virtual address of 209, and dbextent number 7 will be copied to a new minidisk virtual address of 210.
Figure 150. Example Copy/Move Data Disk Control File (CDBEXTNT)
4 209 7 210 END |
| Note: |
|---|
|
The Copy/Move Data Disk tool uses a single control file for each database machine. You cannot, therefore, schedule multiple Copy/Move Data Disk jobs for the same database because each new job (scheduled or immediate invocation) will overlay the previously created control file. |
The Add DBSPACE tool automates the execution of the SQLADBSP utility. Use this tool to add new dbspaces to your database's storage pools.
Prior to adding dbspaces to your database's storage pools, you should review and be familiar with the add dbspace information described in the DB2 Server for VM System Administration manual.
You start the Add DBSPACE process by using the panel interface to define new dbspaces and to identify which storage pools they are to be added to.
After defining the new dbspaces to be added, the panel interface will give you the option of executing the Add DBSPACE tool immediately or scheduling it for a later date and time using the Job Scheduling tool.
When the database is terminated, Control Center will manage the execution of the SQLADBSP utility. This DB2 Server for VM-provided utility runs in single user mode on the database machine's console. It will manage the database's console during the execution of this utility.
When the Add DBSPACE job completes, the database will be returned to its original status (either up or down).
If the Archive-addspace parameter (refer to Chapter 16, Database Startup and Termination Tools) in the database's PARMS file is set to Y, then a full database archive will be automatically initiated by Control Center when the Add DBSPACE processing completes.
| Note: |
|---|
|
If the database is not archived after adding dbspaces, the DBA should be aware that a subsequent database recovery will not include the added dbspaces, since this single user mode activity is not logged. Also, any updating done within the added dbspaces will not be applied during a database recovery (since the dbspaces where the updates occurred no longer exist). |
Shown in Figure 151 is an example of the SQLADBSP file which is used to control the addition of dbspaces. You will need to create this file as specified in the DB2 Server for VM System Administration manual. You must specify the internal dbspaces every time that the SQLADBSP process is executed. | The internal dbspace specification record must be the last |statement in this control file. When the Add DBSPACE tool is invoked under Control Center, the previous SQLADBSP file will be provided, allowing the internal statement to be retained for the next execution.
Figure 151. Example Add DBSPACE Control File (SQLADBSP)
PRIVATE 128 7 PRIVATE 128 7 PRIVATE 128 7 PRIVATE 128 7 PUBLIC 512 9 PUBLIC 1024 9 INTERNAL 230 8192 3 <== This entry must be last. |
| Note: |
|---|
|
The Add DBSPACE tool uses a single control file for each database machine. You cannot, therefore, schedule multiple add dbspace jobs for the same database because each new job (scheduled or immediate invocation) will overlay the previously created control file. |
You invoke the Add DBSPACE tool by selecting Option A (ADD DBSPACES) on the Database Utility Functions panel. The next panel displayed is informational only, and pressing ENTER on this panel will display the SQLADBSP control file in edit (XEDIT) mode.
The SQLADBSP control file displayed will be the previous Add DBSPACE control file established. If there is no SQLADBSP control file for the database, then a file will be generated with sample values included.
When the SQLADBSP process runs, Control Center creates a log file of all messages generated during the add dbspace process. This file is kept on Control Center's 191 A-disk and is identified by a filetype of ADDSPLOG (filename matches the database virtual machine name).
Each time a dbspace is added to a database, a new file will be generated, replacing the previous log file.
Shown in Figure 152 is an example of an ADDSPLOG file. The highlighted fields indicate responses made by Control Center. All other lines are messages generated on the database machine while the SQLADBSP utility runs.
Figure 152. Example Add DBSPACE Log File (ADDSPLOG)
09:12:09 SQLDBA SQLADBSP requested
09:12:18 ARI0717I Start SQLADBSP EXEC: 09:12:16 EST.
09:12:18 ARI0646D SQLDBA SQLADBSP A was found. Should the database use this
09:12:18 file for processing? Enter:
09:12:19 0(No) to erase the file, or
09:12:19 1(Yes) to use the file.
09:12:18 1
09:12:19 ARI0638D Do you want to modify the SQLDBA SQLADBSP file?
09:12:20 Enter 0(No) or 1(Yes).
09:12:20 0
09:12:20 ARI6184D Do you want to continue the ADD DBSPACE process?
09:12:21 Enter 0(No) or 1(Yes).
09:12:20 1
09:12:21 ARI0717I Start SQLSTART EXEC: 09:12:21 EST.
09:12:24 ARI0320I The default database name is SQLDBA.
09:12:24 ARI0663I FILEDEFS in effect are:
09:12:25 Z DISK DMSNAM LOADLIB *
09:12:25 ARIARCH TAP1 SL 00001 VOLID QU1192
09:12:25 SYSPRINT TERMINAL
09:12:26 SYSIN DISK SQLDBA SQLADBSP A1
09:12:26 ARISQLLD DISK ARISQLLD LOADLIB Q1
09:12:26 BDISK DISK 200
09:12:26 LOGDSK1 DISK 201
09:12:27 DDSK1 DISK 202
09:12:27 DDSK2 DISK 203
09:12:28 ARIUSRDD DISK USERLIB LOADLIB *
09:12:28 ARITRAC TAP2 SL 00001
09:12:29 ARI0025I The program ARISQLDS is loaded at 622000.
09:12:29 ARI0025I The program ARIXRDS is loaded at 4C9000.
09:12:30 ARI0025I The program ARIXSXR is loaded at 7AF000.
09:12:30 ARI0025I The program ARICMOD is loaded at 7C44B0.
09:12:30 ARI0015I ACCOUNT parameter value is N.
09:12:31 ARI0015I DUMPTYPE parameter value is P.
09:12:31 ARI0015I LOGMODE parameter value is A.
09:12:32 ARI0015I STARTUP parameter value is S.
09:12:32 ARI0015I SYSMODE parameter value is S.
09:12:33 ARI0015I CHARNAME parameter value is ENGLISH.
09:12:34 ARI0015I DBNAME parameter value is SQLDBA.
09:12:36 ARI0016I ARCHPCT parameter value is 80.
09:12:37 ARI0016I CHKINTVL parameter value is 10.
09:12:37 ARI0016I NCUSERS parameter value is 1.
09:12:38 ARI0016I NLRBS parameter value is 512.
09:12:39 ARI0016I NPAGBUF parameter value is 50.
09:12:40 ARI0016I SOSLEVEL parameter value is 10.
09:12:41 ARI0016I DISPBIAS parameter value is 10.
09:12:41 ARI0025I The program ARISDBMS is loaded at 42B000.
09:13:04 ARI0915I One or more DBSPACES were added to database.
09:13:07 ARI0032I The database has terminated.
09:13:07 ARI0043I The database manager return code is 0.
09:13:08 SQLDBA SQLADBSP completed
When the SQLADBSP process runs, Control Center updates a file recording the information about the dbspace being added. This file is kept on Control Center's 191 A-disk for each database machine and is identified by a filetype of ADBSPHIS (filename matches the database virtual machine name).
Shown in Figure 153 is an example of an ADBSPHIS file which provides a history of all dbspaces that have been added to the database using Control Center.
Figure 153. Example Add DBSPACE History File (ADBSPHIS)
02/24/97 11:02:34 ADDED (TYPE, SIZE, POOL) PUBLIC 8192 4
02/24/97 11:02:34 ADDED (TYPE, SIZE, POOL) INTERNAL 230 1024 3
03/16/97 09:43:55 ADDED (TYPE, SIZE, POOL) PRIVATE 128 2
03/16/97 09:43:55 ADDED (TYPE, SIZE, POOL) PRIVATE 128 2
03/16/97 09:43:55 ADDED (TYPE, SIZE, POOL) PRIVATE 128 2
03/16/97 09:43:55 ADDED (TYPE, SIZE, POOL) PRIVATE 512 4
03/16/97 09:43:55 ADDED (TYPE, SIZE, POOL) PRIVATE 1024 4
03/16/97 09:43:55 ADDED (TYPE, SIZE, POOL) INTERNAL 230 1024 3
The Database COLDLOG tool automates the use of the database SQLLOG utility. Use this tool to COLDLOG your database's logs. Refer to the DB2 Server for VM System Administration manual for information on performing a COLDLOG.
The tool is invoked through the panel interface and you have the option of running it immediately or scheduling it for later execution using the Job Scheduling tool.
When the tool runs, Control Center brings the database down and invokes the SQLLOG utility to COLDLOG the database's logs. Control Center will answer no (0 or N) to the database ARI6129D "(do you want to do a CMS FORMAT/RESERVE command)" question for DB2 Release 3.3 and earlier. For Release 3.4 the response is CONTINUE (the message context has been changed).
Upon completion of the COLDLOG, the database is returned to its original status (either up or down).
Figure 154 shows the Database COLDLOG options panel displayed when Option CL (COLDLOG) on the Database Utility Functions panel is selected. COLDLOGs can be scheduled or submitted for immediate execution. If you run the Option I (Immediate), then the database will be terminated and the COLDLOG will begin. Option S will display a panel prompting you for scheduling-related information (refer to Figure 46).
Figure 154. Database COLDLOG Options Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy CONTROL CENTER hh:mm:ss | | *----------------------------- Database Coldlog ----------------------------* | | | Option ===> CTRLID: MSTRSRV1 | | | | Database ===> SQLDBA NODE: VMSYSTM1 | | | | | | | | | | | | I INITIATE COLDLOG Immediate COLDLOG (with SQLEND) | | | | | | | | S SCHEDULE COLDLOG Schedule later COLDLOG | | | | | | | | | | | | | | | | Enter OPTION and press ENTER to process, or | | | | press PF3 to CANCEL the COLDLOG | | | | | | | *---------------------------------------------------------------SQMCOLDL----* | | PF: 1 Help 3 End | | | +--------------------------------------------------------------------------------+
When the Database COLDLOG tool runs, the database's console messages are written to a log file (database COLDLOG), which is kept on Control Center's 191 A-disk. This file will be replaced with a new file containing the latest process log each time the Database COLDLOG tool is run.
Shown in Figure 155 is an example of a COLDLOG file. The highlighted fields indicate responses made by Control Center. All other lines are messages generated on the database machine while the SQLADBSP utility runs.
Figure 155. Example Database COLDLOG Log File (COLDLOG)
03/16/97 10:22:24 COLDLOG request issued for database SQLDBA
03/16/97 10:22:24 DASD 0300 DETACHED
03/16/97 10:22:24 DASD 0201 DETACHED
03/16/97 10:22:25 DASD 0202 DETACHED
03/16/97 10:22:25 DASD 0200 DETACHED
03/16/97 10:22:25 DASD 0204 DETACHED
03/16/97 10:22:25 DASD 0220 DETACHED
03/16/97 10:22:25 DASD 0221 DETACHED
03/16/97 10:22:26 DASD 0222 DETACHED
03/16/97 10:22:26 DASD 0224 DETACHED
03/16/97 10:22:26 DASD 0240 DETACHED
03/16/97 10:22:26 DASD 0243 DETACHED
03/16/97 10:22:26 DASD 0244 DETACHED
03/16/97 10:22:27 DASD 0245 DETACHED
03/16/97 10:22:27 DASD 0225 DETACHED
03/16/97 10:22:27 DASD 0241 DETACHED
03/16/97 10:22:27 ARI0797I End SQLSTART EXEC: 03/16/97 10:22:16 EST
03/16/97 10:22:27 Ready; T=53.80/179.22 10:22:16
03/16/97 10:22:28 TAPE 0181 DETACHED
03/16/97 10:22:28 ARI0717I Start SQLLOG EXEC: 03/16/97 10:22:24 EST.
03/16/97 10:22:28 ARI6129D Do you want to do a CMS FORMAT/RESERVE command
03/16/97 10:22:28 on disks 201 and 202?
03/16/97 10:22:29 Enter 0(No), 1(Yes), or CANCEL to cancel COLDLOG.
03/16/97 10:22:29 Enter 0(No) if you are not reconfiguring the
03/16/97 10:22:29 logs.
03/16/97 10:22:29 Warning: If you are running LOGMODE=L,
03/16/97 10:22:29 a response of 1(Yes) invalidates previous
03/16/97 10:22:30 or current log archive restore sets.
03/16/97 10:22:30 0
03/16/97 10:22:30 ARI0717I Start SQLSTART EXEC: 03/16/97 10:22:28 EST.
03/16/97 10:22:30 ARI0663I FILEDEFS in effect are:
03/16/97 10:22:30 Z DISK DMSNAM LOADLIB *
03/16/97 10:22:31 ARIARCH TAP1 SL 00001 VOLID QU1251
03/16/97 10:22:31 ARISQLLD DISK ARISQLLD LOADLIB Q1
03/16/97 10:22:31 BDISK DISK 300
03/16/97 10:22:31 LOGDSK1 DISK 201
03/16/97 10:22:31 LOGDSK2 DISK 202
03/16/97 10:22:32 DDSK1 DISK 200
03/16/97 10:22:32 DDSK2 DISK 204
03/16/97 10:22:32 DDSK3 DISK 220
03/16/97 10:22:32 DDSK4 DISK 221
03/16/97 10:22:33 DDSK5 DISK 222
03/16/97 10:22:33 DDSK7 DISK 224
03/16/97 10:22:33 DDSK9 DISK 240
03/16/97 10:22:33 DDSK12 DISK 243
03/16/97 10:22:33 DDSK13 DISK 244
03/16/97 10:22:34 DDSK14 DISK 245
03/16/97 10:22:34 DDSK15 DISK 225
03/16/97 10:22:34 DDSK10 DISK 241
03/16/97 10:22:34 ARIUSRDD DISK USERLIB LOADLIB *
03/16/97 10:22:34 ARITRAC TAP2 SL 00001
03/16/97 10:22:35 ARILARC TAP3 SL 00001
03/16/97 10:22:35 ARI0025I The program ARISQLDS is loaded at 6C9000.
03/16/97 10:22:35 ARI0025I The program ARIXRDS is loaded at 570000.
03/16/97 10:22:35 ARI0025I The program ARIXSXR is loaded at 8A9000.
03/16/97 10:22:36 ARI0025I The program ARICMOD is loaded at 8A7000.
03/16/97 10:22:36 ARI0015I DUALLOG parameter value is Y.
03/16/97 10:22:36 ARI0015I ACCOUNT parameter value is N.
03/16/97 10:22:37 ARI0015I DUMPTYPE parameter value is P.
03/16/97 10:22:37 ARI0015I LOGMODE parameter value is Y.
03/16/97 10:22:37 ARI0015I STARTUP parameter value is L.
03/16/97 10:22:38 ARI0015I SYSMODE parameter value is S.
03/16/97 10:22:38 ARI0015I EXTEND parameter value is N.
03/16/97 10:22:39 ARI0015I CHARNAME parameter value is ENGLISH.
03/16/97 10:22:39 ARI0015I DBNAME parameter value is CPVENDBA.
03/16/97 10:22:39 ARI0015I TRACDSC parameter value is 00.
03/16/97 10:22:40 ARI0015I TRACRDS parameter value is 0000000.
03/16/97 10:22:40 ARI0015I TRACDBSS parameter value is 00000000000.
03/16/97 10:22:41 ARI0016I CHKINTVL parameter value is 10.
03/16/97 10:22:41 ARI0016I NCSCANS parameter value is 30.
03/16/97 10:22:41 ARI0016I NCUSERS parameter value is 1.
03/16/97 10:22:42 ARI0016I NDIRBUF parameter value is 14.
03/16/97 10:22:42 ARI0016I NLRBS parameter value is 512.
03/16/97 10:22:43 ARI0016I NLRBU parameter value is 1000.
03/16/97 10:22:43 ARI0016I NPAGBUF parameter value is 14.
03/16/97 10:22:43 ARI0016I SLOGCUSH parameter value is 90.
03/16/97 10:22:44 ARI0016I SOSLEVEL parameter value is 10.
03/16/97 10:22:44 ARI0016I DISPBIAS parameter value is 10.
03/16/97 10:22:45 ARI0920D Cold-log function invoked.
03/16/97 10:22:45 Logs will be formatted and existing log data destroyed.
03/16/97 10:22:45
03/16/97 10:22:46 Enter either:
03/16/97 10:22:46 COLDLOG to continue, or
03/16/97 10:22:46 CANCEL to cancel.
03/16/97 10:22:46 COLDLOG
03/16/97 10:30:05 The database has terminated.
03/16/97 10:30:05 ARI0043I The database manager return code is 0.
The Reorganize Catalog Indexes tool automates the use of the SQLCIREO utility. Use this tool to rebuild the database system catalog indexes.
Prior to using this tool, review the information presented in the DB2 Server for VSE & VM Database Administration manual regarding the SQLCIREO utility.
The tool is invoked through the panel interface and you have the option of running it immediately or scheduling it for later execution using the Job Scheduling tool.
When the tool runs, Control Center will bring the database down and invoke the DB2 SQLCIREO utility to reorganize the catalog indexes.
Upon completion of the SQLCIREO utility, the database will be returned to its original status (either up or down).
Figure 156 shows the reorganize catalog indexes panel displayed when option RC (REORG CATALOG INDEXES) on the Database Utility Functions panel is selected. Reorganizations can be scheduled or submitted for immediate execution. If you run the immediate (I) option, then the database will be terminated and the SQLCIREO utility will begin. The schedule (S) option will display a panel prompting you for scheduling related information (refer to Chapter 10, Job Scheduling Tool).
Figure 156. Reorganize Catalog Indexes Options Panel
+--------------------------------------------------------------------------------+ | mm/dd/yyyy CONTROL CENTER hh:mm:ss | | *------------------------ Reorganize Catalog Indexes -----------------------* | | | Option ===> CTRLID: MSTRSRV1 | | | | Database ===> SQLDBA NODE: VMSYSTM1 | | | | | | | | | | | | I INITIATE SQLCIREO Immediate Index reorganization | | | | | | | | S SCHEDULE SQLCIREO Schedule later reorganization | | | | | | | | | | | | Enter OPTION and press ENTER to process, or | | | | press PF3 to CANCEL the Catalog Index reorganization | | | | | | | *---------------------------------------------------------------SQMCIREO----* | | PF: 1 Help 3 End | | | +--------------------------------------------------------------------------------+
When the Reorganize Catalog Indexes tool runs, the database's console messages are written to a log file (database SQLCIREO), which is kept on Control Center's 191 A-disk. This file will be replaced with a new file containing the latest process log each time the Database COLDLOG tool is run.