2020-01-30 98524

98524 - DB6: Description of DB2DART

Version 16 Type SAP Note
Language Inglés Master Language Alemán
Priority Recommendations / Additional Info Category Help for error analysis
Release Status Released for Customer Released On 05.07.2012
Component BC-DB-DB6 ( DB2 Universal Database for Unix / NT )

Please find the original document at https://launchpad.support.sap.com/#/notes/ 98524

Symptom

You use DB2 for Linux, UNIX, and Windows (referred to as DB2 below) and want to
check your database or parts of your database for consistency.

Other Terms

db2dart, db2, db6, udb, luw, consistency, consistencycheck

Reason and Prerequisites

The program db2dart is part of the DB2 UDB delivery. It is used for the check of
the physical consistency of the database. For example, you use db2dart to find
an error that has been reported in the db2diag.log.

db2dart is an offline tool, which means that it can be used only if the database
is stopped.

Call db2dart only if the SAP Support asks you to do so. A regular consistency
check of productive DB2 databases with db2dart is not required. If you want to
check your DB2 database online for consistency, you can use the utility INSPECT.

Solution

The options of db2dart that are mentioned in this SAP Note can be used without
problems for the database because the serve only for the analysis of the data
structure.

The options not mentioned in this SAP Note must not be used without consulting SAP first or without
following the instructions by SAP because they are repair functions that can damage the database if
they are used inappropriately.

The program db2dart is part of the DB2 UDB delivery and is used to check the
physical consistency of the database. You must call it as database administrator
db2<dbsid>.

db2dart must be used when the database is stopped. Otherwise the result is invalid.

You can run db2dart in parallel on different tables.

db2dart can be run interactively or in batch mode.

You call db2dart as follows:

db2dart <dbsid> [Option] [Option] ...

© 2020 SAP SE or an SAP affiliate company. All rights reserved 1 of 4

2020-01-30 98524

For all options, uppercase or lowercase is irrelevant.

If you call db2dart without command lines option, you receive a list of
available options.

db2dart writes two log files:

• <DB SID>.RPT: Contains the results of the checks.

• DART.ERR: Contains return codes.

Both files are written to the directory (DIAGPATH)/DART0000. For this,

(DIAGPATH) is the relevant parameter in DBM CFG.

If no errors are found in the checked data area, the following lines display at
the end of the file <SID>.RPT:

__________________________________________________________
SUCCESS!!!
The requested DART processing has completed.
All operation completed without error;
no problems were detected in the database.
__________________________________________________________

Otherwise, an indicator for an error displays here.

If you call db2dart you must use only one of the following options:

• /DB Analysis of the entire database

• /T Analysis of a single table

• /TSF Analysis of the tablespace files and the containers

• /TSC Analysis of a tablespace but not the tables contained in it

• /TS Analysis of a single tablespace and the tables contained in it

Depending on the option, other details may be required. If these details were
not specified during the call, db2dart prompts you to provide these
specifications.

For example: You want to analyze the table "RFBLG" and start db2dart as follows:

db2dart <sid> /T

For the option "/T" (Analysis of a table), you must specify, which table you
want to be analyzed. The system therefore displays the following prompt:

Please enter Table ID or name, and tablespace ID:

Now, enter the table name (in this example RFBLG) and the tablespace ID. Use the
following SQL statement to determine the tablespace ID:

db2 "select tabname, tbspaceid from syscat.tables where tabname = 'RFBLG'"

For this example, the tablespace ID is 15. You must enter the following for the
db2dart prompt:

© 2020 SAP SE or an SAP affiliate company. All rights reserved 2 of 4

2020-01-30 98524

RFBLG 15

Specifying the following options is helpful, if db2dart must be started without

additional interactions with the user.

• /OI object-id: Object ID

• /TN table-name: Table name

• /TSI tablespace-id: Tablespace ID

• /PS number: Page number with which you want to start

• /NP number: Number of pages that are to be checked.

The following options control the size and the location of the paging file.

• /V Y/N: Verbose mode on/off. "/V N" reduces the output significantly.

• /RPT path: Use of <path> as the path for the output file instead of
(DIAGPATH)

• /RPTN file-name: Use of "file_name" as file name for the output file.

• /ERR Y/N: Complete details in the file DART.ERR log (default value). "/ERR
N" reduces the size of the output file significantly.

db2dart displays further options and short instructions when calling it without
parameter.

For example: You want to start a check of the table RFBLG in the tablespace with
the ID 15. Use the following command:

db2dart <dbsid> /T /TN RFBLG /TSI 15

Note:

In particular, if you use the option /DB (check of the entire database), the
volume of the involved data is significant (several GB). The runtime for this
particular option may be longer than 24 hours.

For this reason, it may make sense to divide consistency checks of the entire
database into portions and always check only a few tables per available time
frame.

Dieses Dokument referenziert auf

SAP-Hinweis/KBA Titel

919950 A dump occurs in the Business Process Maintenance session.

486559 DB6: Reducing the high-water mark (HWM)

© 2020 SAP SE or an SAP affiliate company. All rights reserved 3 of 4

2020-01-30 98524
332747 DB6: Incorrect Long Field Data Structures

Dieses Dokument wird referenziert von

SAP-Hinweis/KBA Titel

2099517 How to mark an index as bad using DB2DART tool

2681795 Improving the runtime of db2dart with fastdart

2632926 How to Monitor the Create/Rebuild of Bad Indexes - DB6 IBM

486559 DB6: Reducing the high-water mark (HWM)

919950 A dump occurs in the Business Process Maintenance session.

332747 DB6: Incorrect Long Field Data Structures

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2020 SAP SE or an SAP affiliate company. All rights reserved 4 of 4