Professional Documents
Culture Documents
Customer
Document version 4.0 11/22/2013
Copyright
Copyright 2013 SAP AG. All rights reserved.
SAP Library document classification: PUBLIC
(ii) the fact that SAP provides links to external sites does not
imply that SAP agrees or disagrees with the contents and
information provided on such sites. SAP does not guarantee
the correctness of the information provided.
(III) SAP DOES NOT GIVE ANY REPRESENTATION REGARDING
THE QUALITY, SAFETY, SUITABILITY, ACCURACY OR
RELIABILITY OF ANY EXTERNAL WEBPAGE OR ANY OF
INFORMATION, CONTENT AND MATERIALS PROVIDED
THEREON;
(IV) YOU VISIT THOSE EXTERNAL WEBPAGES
ENTIRELY AT YOUR OWN RISK. SAP SHALL NOT BE
DIRECTLY OR INDIRECTLY RESPONSIBLE OR
LIABLE FOR ANY DAMAGE OR LOSS CAUSED OR
ALLEGED TO BE CAUSED BY OR IN CONNECTION
WITH YOUR USE OF OR RELIANCE ON ANY
CONTENT, GOODS OR SERVICES AVAILABLE ON OR
THROUGH ANY SUCH LINKED WEBPAGE.
Typographic Conventions
Type Style
Example Text
Description
Icons
Icon
Meaning
Caution
Cross-references to other
documentation
Syntax
Example text
EXAMPLE TEXT
Example text
Example text
<Example text>
EXAMPLE TEXT
Example
Note
Recommendation
Contents
1 Introduction ......................................................................................... 5
2 Performing a Conversion Using Report DB6CONV ......................... 8
2.1 Defining a Conversion Job in DB6CONV ............................................. 8
2.2. Using External Conversion Jobs for SAP NetWeaver BW ............... 13
2.3 Maintaining the Conversion Parameters ............................................ 14
2.4 Maintaining the Conversion Queue of a Mass Conversion .............. 14
2.5 Excluding Tables from Conversion .................................................... 17
2.6 Starting a Conversion Job ................................................................... 17
2.7 Monitoring a Running Conversion ...................................................... 18
2.8 Available Actions on the Conversion Overview Screen ................... 18
2.9 Displaying Old Conversion Logs ........................................................ 21
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
1 Introduction
This document describes how you can convert a single table or multiple tables using report
DB6CONV. Table conversion in this document means that you move one or more tables
within the same tablespace or to another tablespace as fast and efficient as possible using
DB2 means without explicitly changing the table structure.
Features
The following are the main features of report DB6CONV:
Single table conversion with one process or mass conversion (conversion of multiple
tables) with one or more parallel processes.
You can perform a conversion in one of the following modes:
ONLINE
The table to be converted is still accessible for INSERT, UPDATE, or DELETE
operations during the conversion.
OFFLINE logged
The table to be converted is only accessible for read-only operations and the
data transfer from the source to the target table is recorded in the database
logs.
OFFLINE not logged
The table to be converted is only accessible for read-only operations and the
data transfer from the source to the target table is not recorded in the database
logs.
You can define conversions using either target tablespaces or target data classes.
As of DB2 V9.1, DB6CONV supports data compression.
You can set the compression attribute for target tables. The compression rate is
optimized by means of sampling.
As of DB2 V9.7, DB6CONV supports index compression.
For target tables, you can set the compression attribute separately for data and
indexes.
As of DB2 10.1, DB6CONV supports the following new features:
o
Hidden columns
Activities
You use report DB6CONV, for example, if you want to:
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
This feature is only available if your database is DB2 V9.7 or higher and your
SAP system has at least SAP basis 7.0 or higher.
Convert regular tables to ITC tables
This feature is only available if your database is DB2 10.1. or higher and if the
database is not using the DB2 pureScale feature.
Add or change the distribution key of a BW table
Convert InfoCubes from using row-organized tables to using column-organized tables
and vice versa.
Usage Requirements
At least DB2 UDB for UNIX and Windows Version 8.2 or higher
At least SAP basis release 6.20 or higher
For conversions with DB2 releases lower than DB2 UDB Version 8.2 and SAP
systems lower than 6.20, you can only use report DB6CONV version 4.10 as
described in SAP Note 362325.
Constraints
Report DB6CONV version 5 or higher is not part of the standard SAP delivery. The
latest version is available as an attachment to SAP Note 1513862.
The attached archive DB6CONV_V<version>_<timestamp>.SAR contains the
following:
The data- and the co-file of the corresponding DB6CONV transport that you
have to import into the SAP system
File DB6CONV_V<version>_<timestamp>_README.TXT
This read-me file provides instructions that you must follow to import DB6CONV
version 5.x into an SAP system that contains data from a DB6CONV version up
to and including version 4.10.
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
Short Name
DB2 10.5
DB2 10.1
DB2 V9.7
DB2 V9.5
DB2 V9.1
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
For single tables and tablespaces, you can perform conversions using either
target tablespaces or the target data class. For more information, see
Performing a Conversion Using the Data Class [page 11].
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
2. In the field Target Data Tablespace, choose the appropriate target tablespace for the
table or tablespace to be converted from the dropdown list.
3. In the field Target Index Tablespace, choose the appropriate target index tablespace of
the table or tablespace to be converted from the dropdown list.
4. Optional:
In the field Target Long Tablespace, choose the appropriate long tablespace for the
table or tablespace to be converted from the dropdown list.
5. For DB2 10.1 or higher and if the database is not using the DB2 pureScale feature:
a. In the Insert Time Clustering field, choose the appropriate option for the table or
tablespace to be converted from the dropdown list. The default value is Keep
Current Status, that is, the cluster attribute of the table or of all tables in a
tablespace is kept.
b. Optional and only available for single table conversions:
If you want to display the ITC characteristics of the table and check or modify
the choice that you made in the previous step a., choose the ITC Status
pushbutton.
6. Optional and only available for mass conversions:
If you want to display and maintain the list of tables that are part of the tablespace
conversion, choose the Conversion Queue pushbutton.
In the Conversion Queue dialog box, you can view and maintain the queue of tables to
be converted as described in Maintaining the Conversion Queue of a Mass Conversion
[page 14].
7. Specify if you want to perform the conversion online or offline (by default, the offline
radio button is selected):
If you choose the Online radio button, specify the following parameters:
Use COPY_WITH_INDEXES
If you select this option, all indexes of the target table are created before
the data transfer.
If you deselect this option, all indexes of the target table are created after
the data transfer. This may result in a shorter total time for the data
transfer itself, but in a higher temporary space request for the creation of
the indexes.
By default, this option is preselected.
Stop Before Switch
If you select this option, the online conversion for a single table is
stopped before the switch from source to target table. This switch causes
a short downtime for the table to be converted. With this option, you can
estimate the point in time when the switch (and thus the short downtime)
takes place more precisely than when the complete table conversion is
performed.
By default, this option is not preselected.
The option Stop Before Switch is only available for the conversion of a single
table.
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
If you choose the Offline radio button, specify the following parameters:
Data Transfer not Logged
This is the fastest conversion method available in DB6CONV.
If you select this option, the data transfer itself is not logged. Therefore,
you have to back up at least the target tablespace after the conversion.
By default, this option is not preselected.
Sort Data by Primary Key
If you select this option, data is sorted according to the definition of the
primary key when data is being transferred to the target table. The result
is identical to the result of the following command:
db2 reorg table <tabname> index <primary key>
By default, this option is not selected. If there is no primary key, this
option is not relevant.
COMMIT Size (MB)
This option is only relevant if you did not select the Data Transfer not
Logged checkbox.
While the data transfer step is being logged, table data is split into data
blocks using a unique index. Each block should have the same size and
should not exceed the value that you specified in the COMMIT Size (MB)
field.
After the data of each data block has been transferred to the target table,
a COMMIT is issued to avoid a log full situation. The total size of
database logs must be at least equal to or higher than the specified
COMMIT size multiplied by the number of batch jobs that you specify to
run in parallel.
The default COMMIT size is 300 MB.
Without a unique index, table data is split according to the non-unique
index with the highest FULLKEYCARD. Therefore, an equal block size or
a maximum block size of the specified COMMIT size cannot be
guaranteed.
8. DB2 V9.1 or higher only:
Specify the compression status that the tables and indexes will have after the
conversion by choosing the relevant option from the dropdown list in the Compression
for Data and Compression for Indexes fields.
9. Specify if you want the source table to be dropped after the conversion by selecting the
checkbox Delete Source Table after Conversion.
Do not select this option if, for example, you want to compare the source table
with the target table after the conversion. In this case, you have to manually
drop the source table at a later point in time.
By default, this option is preselected.
10. Specify if you want statistics to be created for the converted table(s) by selecting the
checkbox Update Statistics After Conversion.
The target table for a conversion is newly created during the conversion. Therefore,
there are no statistics available directly after the conversion. With this option, statistics
10
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
are generated for the converted single table or for all tables of the target tablespace
during the last step of the conversion.
By default, this option is preselected.
11. Save your entries.
(For mass conversions, a message window appears providing a summary of the saved
queue, that is, the total number of entries as well as the number of deleted, excluded,
and rejected objects. Confirm this message window.)
The Conversion Overview screen appears and the new conversion job is displayed
with status PLANNED in the Conversion Jobs area.
12. Optionally, you can check and maintain the conversion parameters and the conversion
queue as described in Maintaining the Conversion Parameters [page 14] and
Maintaining the Conversion Queue of a Mass Conversion [page 14].
13. Start the conversion job [page 17].
Procedure
1. On the New Conversion screen, choose the Specify Target Data Class pushbutton.
2. In the field Name of the Table to Be Converted or Name of the Tablespace to Be
Converted, enter the name of the table or choose a tablespace from the dropdown list.
3. Choose the target data class from the dropdown list.
4. Proceed as described in step 5 to 12 in the above procedure Performing a Table or
Tablespace Conversion [page 8].
November 2013
11
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
During the LONGLOB conversion, all tables with LONG VARCHAR columns are
collected in the conversion queue and are converted within their own tablespaces.
To perform a LONGLOB conversion, choose the Database-Level Conversions tab page
and select the checkbox Replace LONG VARCHAR Columns by LOB Columns
(LONGLOB Conversion). Then proceed as described in step 6 to 13 in Performing a
Table or Tablespace Conversion [page 8].
This option is only available as of DB2 10.1 and if the database is not
using the DB2 pureScale feature.
DB6CONV can create a list of tables that might be candidates for a conversion to ITC
tables. For information about how ITC candidates are chosen, see Insert Time Clustering
(ITC) Tables and Candidates [page 27].
To convert ITC candidates to ITC tables, choose the Database-Level Conversions tab
page and select the relevant checkbox. Then proceed as described in step 6 to 13 in
Performing a Table or Tablespace Conversion [page 8].
This option is only available as of DB2 10.1 and if the database is not
using the DB2 pureScale feature.
To reconvert ITC tables to regular tables, choose the Database-Level Conversions tab page
and select the relevant checkbox. Then proceed as described in step 6 to 13 in Performing a
Table or Tablespace Conversion [page 8].
1. LONGLOB conversion
2. ITC conversion
3. ITC reconversion
Examples:
Naming
Description
<DLCONV>_XOO
<DLCONV>_OXO
<DLCONV>_XOX
al
D
12
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
Name of Conversion
Job
Relevant
SAP
Notes
Convert
InfoCubes
from using
roworganized
tables to
using
columorganized
tables
<EXT>_<C>_ followed
by the name of the
InfoCube to be
converted
Report SAP_CDE_CONVERSION_DB6
1889656
Convert
InfoCubes
from using
columnorganized
tables to
using roworganized
tables
<EXT>_<R>_ followed
by the name of the
InfoCube to be
converted
Report SAP_CDE_CONVERSION_DB6
1889656
Repair
distribution
keys for fact
tables
<EXT>_REP_PK_IC
Function module
RSDU_CHKREP_PKEY_ALL_CUBES_DB6
1574965,
648432
Repair
distribution
keys for
ODS tables
<EXT>_REP_PK_ODS
Function module
RSDU_CHKREP_PKEY_ALL_ODS_DB6
1574965,
648432
Repair
distribution
keys for
PSA tables
<EXT>_REP_PK_PSA
Function module
RSDU_CHKREP_PKEY_ALL_PSA_DB6
1574965,
648432
November 2013
13
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
For more information, see the database administration guide SAP NetWeaver Business
Warehouse 7.0 Administration Tasks: IBM DB2 for Linux, UNIX, and Windows at:
http://service.sap.com/instguidesnw --> <Your SAP NetWeaver Main Release> -->
Operations --> Database-Specific Guides.
14
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
Description
Queue No.
Excluded
Table Name
Size [KB]
For DB2 10.1 or higher and if the database is not using the DB2 pureScale feature:
Column
Description
Clustering
November 2013
15
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
ITC
If you need detailed information about ITC candidates, you can display the following columns
by choosing the ITC Status pushbutton:
Column
Description
Deleted Objects
Archiving Object
Extent Size
For more information, see Insert Time Clustering (ITC) Tables and Candidates [page 27].
16
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
November 2013
17
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
If you want the conversion job to start immediately, choose the radio button
Start Batch Job(s) Immediately.
If you want the conversion job to start at a specified time, choose the radio
button Schedule Batch Job(s).
3. Confirm your entries by choosing the OK pushbutton.
If you specified a certain date and time for the conversion to start, the status of the
conversion job changes from PLANNED to SCHEDULED on the Conversion Overview
screen. As soon as the conversion starts, the status changes from SCHEDULED to
RUNNING.
If you specified the conversion to start immediately, the status of the conversion job
changes from PLANNED to RUNNING.
18
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
Pausing a Conversion
This pushbutton is only available for mass conversions with status RUNNING.
You can interrupt a mass conversion with status RUNNING by selecting the respective
conversion job and choosing the Pause pushbutton. All parallel jobs of the selected mass
conversion stop after each currently ongoing table conversion, which is part of the mass
conversion has finished. You have to manually reset or continue the paused conversion later
on.
Continuing a Conversion
Replaying a Conversion
This pushbutton is only available for ONLINE conversions of single tables with
status PAUSED.
For online conversions of a single table that were defined with the Stop Before Switch option,
the conversion is stopped after the initial data copy, and the conversion status is set to
PAUSED. Continuing a paused conversion will at first apply data modifications of the original
table to the target table (replay) and switch the table afterwards. The more data there is to be
replayed, the longer it takes until the table is finally switched. Therefore, we recommend that
you perform regular replay actions using the Replay pushbutton before continuing the
conversion.
Aborting a Conversion
This pushbutton is only available for single table conversions with status
RUNNING.
You can abort the conversion of a single table by either selecting an entry in the Conversion
Jobs area or in the Tables from Mass Conversion area and choosing the Abort pushbutton.
We recommend that you only use this option in emergency cases, for example, if a
conversion is running too long.
November 2013
19
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
Resetting a Conversion
Be aware that a conversion reset is always executed immediately and with only
one parallel process. This means that you cannot schedule a reset job to start
at a specific time.
20
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
November 2013
21
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
Step 0
Actions:
Checks whether the conversion is possible
Writes the following information to the detailed conversion log:
A header section containing the conversion parameters
For example, the target tablespaces are listed together with their database
partition group and database partition number.
The data class and data, index, and long tablespaces of the source table
together with their database partition group and the data partition number
The page sizes of the source and target tablespaces
Detailed information about the table size and the compression status (only for
DB2 V9.1 or higher)
The structure (DESCRIBE TABLE) of the source table (only when a conversion
is started)
The table type of the source table
The possible values are TRANSP, POOL, or CLUSTER.
All indexes of the table with index name, uniqueness, index type, and index
fields
The kernel release and database release
Step 2
Actions:
Reads and modifies the entries for the table to be converted in the DDSTORAGE table
Renames the original table from <TABLE> to QCM<TABLE>
22
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
Step 3
Action:
Creates the target table QCM8<TABLE> with the field sequence of the original table
QCM<TABLE> as well as the storage parameters (for example, row compression,
distribution key, hashing) according to the entries for the table to be converted in the
DDSTORAGE table
Writes the CREATE TABLE statement to the detailed conversion log
Step 4
Action:
Generates alternative index names that are related to the target table (that is, performs
an index mapping):
For each index that exists on the source table QCM<TAB>, an alternative index name is
generated for target table QCM8<TAB>. If an alternative name cannot be determined,
the index to be created is temporarily named DB6CONV_<#>, where <#> is a unique
number.
Writes the information about the index mapping and the CREATE INDEX statements to
the detailed conversion log
In the detailed conversion log, the number of newly created indexes is displayed and
compared to the number of indexes that were defined for the original table.
Step 5
Action:
Counts the current number of table entries for the tables QCM<TABLE> and
QCM8<TABLE> and writes them to the detailed conversion log
Transfers data as follows:
When tables are converted with content but without the option Data Transfer
not Logged, the table entries are portioned by a unique index according to the
specified COMMIT Size. Each of these blocks is copied to the target table. The
corresponding SQL statement is written to the detailed conversion log. After
each block, a COMMIT is issued and the number of table entries of the last
block, the total number of table entries that were copied so far, the duration of
November 2013
23
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
the last block, and the expected remaining runtime for the remaining blocks are
displayed. You can monitor the progress in the Comment field on the
Conversion Overview screen where the number of already copied table rows
is displayed.
When tables with content and with the option Data Transfer not Logged are
converted, the data is copied in one block. The corresponding SQL statement is
also written to the detailed conversion log.
In this case, you cannot monitor the conversion progress in the detailed
conversion log. However, the number of already copied table entries is displayed
in the Comment field on the Conversion Overview screen.
If the table has more than 20 MB and is to be compressed, at first 20 MB of data is
transferred by using means of sampling. Then, a compression dictionary is built
before the table is truncated and all table entries are transferred.
If the table is smaller than 20 MB, the complete table content is transferred to the
target table. Afterwards, the compression dictionary is built.
Finally compares the new number of table entries in table QCM8<TABLE> with the
number of table entries in table QCM<TABLE>. This number is written to the detailed
conversion log.
Step 6
Actions:
For real tables, the following steps are performed:
The dependent views are dropped again. (Skipped for DB2 V9.7 or higher.)
The view with the original name <TAB> is dropped.
The three triggers that were defined on the original table QCM<TAB> are
dropped.
The target table is renamed from QCM8<TAB> to <TAB>.
For deferred tables, the original view is dropped and re-created with the new target
tablespaces.
Step 7
Actions for DB2 versions lower than DB2 V9.7 FP4:
Re-creates all views using the converted table <TABLE> in accordance with step 1
Compares the number of re-created views to the number of views deleted in step 1
Actions for DB2 V9.7 FP4 or higher
Revalidates all views using the converted table <TABLE>
Step 8
Actions:
Changes the data class for the target table if you defined the conversion by specifying
a target data class. For deferred tables, this is the only action that is executed, the
rest of step 8 is skipped.
Deletes the original table QCM<TABLE> if you selected Delete Source Table After
Conversion when defining the conversion job
24
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
After the original table has been deleted, the indexes of the converted table are
renamed to their original names (that is, to the names they had before the conversion).
The database statistics for the target table are updated if you selected Update
Statistics After Conversion when defining the conversion. If a statistics profile existed
for the original table, the same statistics profile is created for the new target table.DB2
V9.1 or higher only:
Displays detailed information about the table size and compression again so that you
can compare these values.
Displays again the structure of the target table
An online conversion calls the following stored procedures for the online table
move depending on your database release:
For DB2 releases up to and including DB2 V9.5, report DB6CONV calls the
SAPTOOLS.ONLINE_TABLE_MOVE stored procedure.
As of DB2 V9.7, report DB6CONV calls the SYSTOOLS.ADMIN_MOVE_TABLE
stored procedure.
Since the steps performed by report DB6CONV for each of the stored
procedures are identical, they are only referred to as OTM in the following
(where OTM stands for online table move).
For more information about SAPTOOLS.ONLINE_TABLE_MOVE, see SAP
Note 1039544.
For more information about SYSTOOLS.ADMIN_MOVE_TABLE, see SAP Note
1543745.
Step 0
Identical to step 0 of an offline conversion
Step 1
Calls the OTM stored procedure for the table to be converted and the target
tablespaces with operation parameter INIT.
Creates all temporary objects needed for the online conversion, such as triggers, the
target table (if possible using the ABAP Dictionary), and the staging table.
Step 2
Calls the OTM stored procedure for the table to be converted and the target
tablespaces with operation parameter COPY.
Copies all data from the source table to the target table.
You cannot monitor the progress of the data transfer in the detailed conversion log but
in the Comment field on the Conversion Overview screen.
Step 3
Calls the OTM stored procedure for the table to be converted and the target
tablespaces with operation parameter REPLAY.
November 2013
25
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
Data that is modified after the start of the copy step is recorded in the staging table
and applied to the target table in subsequent REPLAY actions after the initial copy
step has finished.
If the conversion has been defined with the Stop Before Switch option, step 4 is
subsequently not executed and the status of the conversion job changes from
RUNNING to STOPPED.
Step 4
Calls the OTM stored procedure for the table to be converted and the target tablespaces
using operation parameter SWAP.
As a result, the source table is switched to the target table and the temporary objects that
were created during step 1 are deleted.
26
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
The fact that data is archived from a table does not necessarily mean that there
are empty extents after archiving. Often several criteria can be used to decide
which records should be archived. These criteria might not be based on the
creation time.
Based on the actual archiving session (see SAP transaction SARA
Statistics) in the
system, DB6CONV can create a list of tables that might be candidates for a conversion to
ITC tables. DB6CONV suggests tables that fullfill all of the following conditions:
The tables are part of an archiving object for which at least one completed archiving
session exists. A complete archiving session exists if data was archived and
afterwards deleted from several or all tables that belong to the archiving object.
The tables are not already ITC or MDC tables.
The tables are at least 1 GB in size.
In the Conversion Queue dialog box, the following information is displayed for the ITC
candidates:
The archiving object(s) to which the table belongs
If a table belongs to multiple archiving objetcs, all archiving objects are displayed.
The number of deleted archiving objects
This is an indication for the amount of data that was actually deleted in these tables.
The extent size (in KB) of the tablespace where the table resides.
Tablespaces in SAP installations usually come with an extent size of 32 KB (two 16 KB
pages). The higher the extent size, the less likely are completely empty extents after
deletions.
It is not guaranteed that deletions take place from all tables of an archiving
object. Therefore, the list of ITC table candidates can contain tables where
actually no deletions took place. These tables, however, are typically less than 1
GB in size.
November 2013
27
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
More Information
Multidimensional and insert time clustering extent management in the IBM DB2 10.1
Information Center at:
http://pic.dhe.ibm.com/infocenter/db2luw/v10r1/index.jsp?topic=%2Fcom.ibm.db2.luw.a
dmin.partition.doc%2Fdoc%2Fc0054692.html
SAP Note 1700631: DB6: Using DB2 10.1 with SAP Applications
SAP Note 975352: DB6: Reorganizations in DB2 / Using DB2 Auto REORG
28
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
Description
Status
Object Type
Object Name
Start Date
Start Time
November 2013
29
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
End Date
End Time
Duration
Size [KB]
Total runtime of the conversion job since its start (does not
include wait times)
For single table conversions:
Size of table to be converted in KB based on current
database statistics
The displayed value is based on the following formula:
(<value of syscat.tables-npages> times
<pagesize of the source tablespace>)
A value of 1- indicates that no statistics exist for the
corresponding table. Therefore, its size is unknown.
For mass conversions:
For status PLANNED: Total size of all tables of
the current conversion queue
For statuses other than PLANNED: Total size of
all tables of the conversion queue at the time the
mass conversion was started.
Jobs
30
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
Online
Comment
November 2013
31
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
The following information is displayed in the Tables from Mass Conversion area :
Column
Description
Status
Table Name
Start Date
Start Time
End Date
End Time
Duration
Size [KB]
Parent
Online
Comment
32
November 2013
Using Report DB6CONV Version 5.30 or Higher for SAP Systems on DB2 for LUW
Document History
The following table provides an overview of the most important changes to this document:
Document
Version
Date
Description
1.0
Initial version
2.0
2.1
3.0
4.0
November 2013
33