PUBLIC

Document Version: 5.1 – 2023-05-09

Converting Tables Using Report DB6CONV

(Version 6.58 or Higher)
For SAP Systems on IBM Db2 for Linux, UNIX, and Windows
© 2023 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Requirements and Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

4 Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5 Performing a Conversion Using Report DB6CONV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5.1 Defining a Conversion Job in DB6CONV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Converting a Table or Tablespace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Performing a Database-Level Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Converting BW Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Converting SAP Convergent Invoicing Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

5.2 Using External Conversion Jobs for SAP BW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

5.3 Maintaining the Conversion Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

5.4 Maintaining the Conversion Queue of a Mass Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5.5 Specifying Conversion Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

5.6 Starting a Conversion Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5.7 Monitoring a Running Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5.8 Available Actions on the Conversion Overview Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

6 Conversion Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

7 Insert Time Clustering (ITC) Tables and Candidates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

8 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

8.1 Information on the Conversion Overview Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

8.2 SAP BW Tables Considered for BLU Acceleration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

8.3 References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

9 Disclaimer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

2 PUBLIC Content
1 Introduction

This documentation describes how you can convert a single table or multiple tables using report DB6CONV for
SAP systems on IBM Db2 for Linux, UNIX, and Windows.

Table conversion here 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.

 Note

This documentation only applies to DB6CONV Version 6.58 or higher. For information about the changes
applied to this document, see the Document History [page 5].

Where Can You Get the DB6CONV Report?

You always find the most current version of the DB6CONV report attached to SAP Note 1513862 .

What Are the Main Features?

• Single table conversions are executed in one process, mass conversions (conversion of multiple tables) are
executed in one or more parallel processes.
• You can define conversions using either target tablespaces or target data classes.
• Support of data compression
You can set the compression attribute for target tables. The compression rate is optimized by means of
sampling.
• Support of index compression
For target tables, you can set the compression attribute separately for data and indexes.
• As of Db2 10.1, DB6CONV supports:
• Adaptive compression for table data
• Hidden columns
• Insert time clustering (ITC) tables
• As of Db2 10.5 FP5SAP2, DB6CONV supports column-organized tables.
• Row-organized tables are online, that is, accessible for INSERT, UPDATE, or DELETE operations during the
conversion. Column-organized tables are read-only, that is, not accessible for INSERT, UPDATE, or DELETE
operations during the conversion.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Introduction PUBLIC 3
What Can You Do With the DB6CONV Report?

You use report DB6CONV, for example, if you want to:

• Circumvent the tablespace size limit

You can use DB6CONV to move tables that have reached the page size-dependent limit for tablespaces to
another tablespace that has a larger page size.
• Move tablespaces to new tablespaces using reclaimable storage
• Replace LONG VARCHAR columns with inline LOBs for all tables, which is referred to as LONGLOB
conversion throughout this document.
• Convert regular tables to ITC tables

 Note

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 BW objects, such as InfoCubes, DataStore objects, InfoObjects, or PSA tables, from using row-
organized tables to using column-organized tables and vice versa.

 Note

This feature is only available if your database is Db2 10.5 FP5SAP2 or higher and if the requirements
regarding component SAP_BASIS are fulfilled (see SAP Note 1513862 ).

• Convert SAP Convergent Invoicing tables from row-organized to column-organized and vice versa.

 Note

This feature is only available if your database is Db2 10.5 FP5SAP2 or higher and if you are using
SAP Contract Accounts Receivable and Payable (FI-CA) Release 617 or higher and have applied the
correction instructions according to SAP Note 2207508 ).

• Make use of tablespace pools

For more information about tablespace pools, see SAP Note 2267446 .
• Drop hidden columns for all tables

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

4 PUBLIC Introduction
2 Document History

The following table provides an overview of the most important changes to this document:

Document Ver­
sion Date Description

5.1 May 9, 2023 Small addition to section Performing a LONGLOB Conversion in chapter Performing
a Database-Level Conversion [page 14]

Note: Db2 9.7 and 10.1 are out of mainstream maintenance.

5.0 September 13, 2021 Document update due to new DB6CONV Version 6.58

Conversions of BW objects now take into account data classes and include a con­
sistency check between target data class and its target tablespaces. For more
information, see Converting BW Objects [page 18].

4.9 March 26, 2019 Document update due to new DB6CONV Version 6.56

Index layout for Db2 BLU Acceleration is now supported (see Converting BW Ob­
jects [page 18]).

4.8 July 31, 2018 Document update due to new DB6CONV Version 6.50

4.7 June 4, 2018 Document update due to new DB6CONV Version 6.40

Section Performing a Database-Level Conversion [page 14] was updated: new

option Correct Inline Length of LOB Columns)

Section Information on the Conversion Overview Screen [page 40] was updated:
As of Db2 11.1, progress details for copy & replay phase are displayed.

4.6 February 5, 2018 Document update due to new DB6CONV Version 6.39

Information about new option Upload from File added

4.5 March 9, 2017 Section about database-level conversions was updated (new option Drop Hidden
Columns)

4.4 August 4, 2016 Document update due to new DB6CONV Version 6.30

Section about BW conversions was updated (new Target: BLU Acceleration).

New section in Appendix (overview of SAP BW Tables Considered for BLU Accelera­
tion)

4.3 March 1, 2016 Document update due to new DB6CONV Version 6.24

DB6CONV now supports tablespace pools. For more information about tablespace
pools, see also SAP Note 2267446 .

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Document History PUBLIC 5
Document Ver­
sion Date Description

4.2 November 6, 2015 Document update due to new DB6CONV Version 6.20

New features include:

• Conversion of SAP Convergent Invoicing tables

• No read-only mode anymore

4.11 February 17, 2015 Document layout changed (new cover page and font style); content unchanged

4.1 December 9, 2014 Document update due to new DB6CONV Version 6.00; BW conversion is now possi­
ble

4.0 November 22, 2013 Document update due to new DB6CONV Version 5.30:

• Support of new Db2 release Db2 10.5

• Section 2.2 was changed (information about the use of external conversion
jobs for SAP NetWeaver BW was added).

3.0 July 20, 2012 Document update due to new DB6CONV Version 5.20

New features include:

• Support of new Db2 release (Db2 10.1)

• Separate data and index compression
• Replay pushbutton for paused online conversions

2.1 March 26, 2012 Document update due to new DB6CONV Version 5.15:

New online conversion step (chapter 3.2)

2.0 April 15, 2011 Document update due to new DB6CONV Version 5.07:

• New object type for conversion jobs (External)

• Section Defining a Conversion Job Outside DB6CONV was added

1.0 November 12, 2010 Initial version

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

6 PUBLIC Document History
3 Requirements and Restrictions

Usage Requirements

You must use the following Db2 and SAP releases:

• IBM Db2 for Linux, UNIX, and Windows Version 9.7 or higher
• SAP Basis Release 7.00 and higher

For conversions with Db2 releases lower than Db2 Version 9.7 and SAP systems lower than 7.00, you can only
use report DB6CONV version 5.36 (or higher) as described in SAP Note 2091519 .

Constraints

• Report DB6CONV is not part of the standard SAP delivery. The latest version is available as attachment to
SAP Note 1513862 .
The attached archive DB6CONV_V<version>_<timestamp>.SAR contains the data- and the co-file of the
corresponding DB6CONV transport that you have to import into the SAP system.
• Report DB6CONV can only move tables of the AS ABAP. Moving other kinds of tables, for example, of an
SAP Java system, is not supported by DB6CONV.
• Report DB6CONV cannot perform explicit structure changes when moving a table.
Implicit structure changes to tables, such as the conversion of LONG VARCHAR columns to VARCHAR
columns or LONG VARCHAR columns to columns of type LOB, are performed depending on the release
level of the ABAP Dictionary and the kernel database shared library dbdb6slib.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Requirements and Restrictions PUBLIC 7
4 Naming Conventions

In this documentation, the following naming conventions apply:

Database Name Short Name

IBM Db2 Version 11.5 for Linux, UNIX, and Windows Db2 11.5

IBM Db2 Version 11.1 for Linux, UNIX, and Windows Db2 11.1

IBM Db2 Version 10.5 for Linux, UNIX, and Windows Db2 10.5

IBM Db2 Version 10.1 for Linux, UNIX, and Windows Db2 10.1 (out of mainstream maintenance)

IBM Db2 Version 9.7 for Linux, UNIX, and Windows Db2 V9.7 (out of mainstream maintenance)

The term mass conversion is used as a synonym for:

• Tablespace conversion
• Database-level conversion
• External conversion
• BW conversion
• Conversion of SAP Convergent Invoicing (SAP CI) tables

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

8 PUBLIC Naming Conventions
5 Performing a Conversion Using Report
DB6CONV

5.1 Defining a Conversion Job in DB6CONV

Procedure

1. To define a conversion job, call transaction SE38 in your SAP system.

2. In the Program field, enter DB6CONV and choose the Execute pushbutton. The Conversion Overview
screen appears providing information about the conversion jobs. For more information, see Information on
the Conversion Overview Screen [page 40].
3. On the Conversion Overview screen, choose the New Conversion pushbutton.
4. On the New Conversion screen, you can choose to do one of the following:
• Convert a single table
• Convert all or only some tables of a tablespace (in this procedure referred to as tablespace conversion)
• Perform a conversion on database level including one of the following options:
• LONGLOB conversion
• Conversion of ITC candidates to ITC tables (as of Db2 10.1)
• Reconversion of ITC tables to regular tables (as of Db2 10.1)
• Drop hidden columns
• Upload from file
• Correct inline length of LOB columns
• Convert all or single BW objects changing the table organization of the related tables from row-
organized to column-organized and vice versa, or keeping the table organization of the related tables
(as of Db2 10.5 FP5SAP2). This is referred to as BW conversion.
• Convert all SAP Convergent Invoicing tables from row-organized to column-organized and vice versa if
you are using SAP Contract Accounts Receivable and Payable (FI-CA) release 617 or higher (and as of
Db2 10.5 FP5SAP2). This is referred to as conversion of SAP Convergent Invoicing tables.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Performing a Conversion Using Report DB6CONV PUBLIC 9
5.1.1 Converting a Table or Tablespace

Context

The following procedure applies to the conversion of a single table as well as to tablespace conversion because
most parameters to be specified are identical on the Single Table and the Tablespace tab pages:

Procedure

1. In the field Table to Be Converted or Tablespace to Be Converted, enter a name or choose the table or
tablespace to be converted from the dropdown list. As of DB6CONV V6.24, you also find tablespace pools
in the list of available source tablespaces. You can recognize them by the curly brackets in the name. If
there are warning messages regarding a tablespace pool, the pushbutton Display Messages appears. Make
sure you click it and read the info.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

10 PUBLIC Performing a Conversion Using Report DB6CONV
 2. If you want to perform a conversion using target tablespaces, choose the radio button Use Target
Tablespaces and make further selections as follows:
a. In the field Target Data Tablespace, choose the appropriate target tablespace for the table or
tablespace to be converted from the dropdown list. As of DB6CONV V6.24, you also find tablespace
pools in the list of available target data tablespaces. You can recognize them by the curly brackets
in the name. If there are warning messages regarding a tablespace pool, the pushbutton Display
Messages appears. Make sure you click it and read the info.
b. In the field Target Index Tablespace, choose the appropriate target index tablespace of the table or
tablespace to be converted from the dropdown list. If you have chosen a data tablespace pool as
target in the previous step, this field is deactivated because DB6CONV determines the target index
tablespace pool automatically.
c. Optional: In the field Target Long Tablespace, choose the appropriate long tablespace for the table
or tablespace to be converted from the dropdown list. If you have chosen a data tablespace pool as
target in step a., this field is deactivated because DB6CONV determines the target long tablespace
pool automatically.

Note that with this conversion option, the data class of the table will remain the same and won't be
changed.
3. If you want to perform a conversion using a target data class, choose the radio button Use Target
Data Class, and in the field Target Data Class, choose the appropriate target data class for the table or
tablespace to be converted from the dropdown list. This dropdown list not only provides all existing data
classes, but also their respective data, index, and long tablespaces.

With this conversion option, the data class of the table is changed accordingly.
4. 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.
5. Only for tablespace conversions:
a. Always create the conversion queue first using the Create Queue pushbutton.
b. Then choose the Display/Edit Queue pushbutton to display and maintain the list of tables that are
part of the tablespace conversion, or choose the Save pushbutton to directly save the conversion. In
the Display/Edit 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 25].

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Performing a Conversion Using Report DB6CONV PUBLIC 11
6. Specify the following parameters for the conversion:

• Use COPY_WITH_INDEXES
With COPY_WITH_INDEXES, all indexes of the target table are created before the data transfer. By
default, this option is preselected in DB6CONV.
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. In addition, you might run into LOG_DIR full errors (SQL error SQL0964C). This
is particularly critical in HADR scenarios.
COPY_WITH_INDEXES is an option of the ADMIN_MOVE_TABLE procedure, which is called up by
DB6CONV for the online table move. As opposed to the ADMIN_MOVE_TABLE procedure, DB6CONV uses
COPY_WITH_INDEXES as its default to avoid LOG_DIR full errors.
• Use LOAD
If you select this option, the data transfer is done using the LOAD command.
• RECOVERABLE
The data transfer is logged. To use this option, you must specify the path for corresponding log
files for the conversion option COPY YES TO and for the profile LOAD (see Specifying Conversion
Options [page 29]).
• NON-RECOVERABLE

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

12 PUBLIC Performing a Conversion Using Report DB6CONV
 The data transfer is not logged. A backup after the conversion is required.
The NON-RECOVERABLE button is disabled if you're using HADR.
Note that the LOAD option will not be applied for tables with a size smaller than 2 MB, even if this
option has been selected, because there is no advantage using LOAD for such small tables.
• Use REDIRECT
If you select this option, the REPLAY phase of the ADMIN_MOVE_TABLE procedure will copy the delta
data directly to the target table instead of using the staging table.

 Note

The option REDIRECT is not available for BW conversions from row-organized to column-organized
(or vice versa) and for conversions of SAP Convergent Invoicing tables.

• Stop Before Switch

If you select this option, the 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.

 Note

The option Stop Before Switch is only available for the conversion of a single table.

• Delete Source Table after Conversion

Specify if you want the source table to be dropped after the conversion by selecting this checkbox.

 Note

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.

• Trace (Support Only)

If you select this option, the conversion for a single table is traced using the trace option of the
ADMIN_MOVE_TABLE procedure. The trace files are written to the db2dump directory of the underlying
database. This option should only be used in case of errors or problems with ADMIN_MOVE_TABLE.
7. 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.

 Note

For BW conversions from row-organized to column-organized (and vice versa) and for conversions of
SAP Convergent Invoicing tables, you cannot specify compression options.

By default, compression for tables and indexes is set to the value KEEP, that is, the compression after the
conversion will be the same as before the conversion.
8. 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.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Performing a Conversion Using Report DB6CONV PUBLIC 13
 The Conversion Overview screen appears and the new conversion job is displayed with status PLANNED in
the Conversion Jobs area.
9. Optionally, you can check and maintain the conversion parameters and the conversion queue as described
in Maintaining the Conversion Parameters [page 24] and Maintaining the Conversion Queue of a Mass
Conversion [page 25].
10. Start the conversion job (see Starting a Conversion Job [page 30]).

5.1.2 Performing a Database-Level Conversion

The different types of database-level conversions are described in the following. Depending on your database
version, the available scenarios vary.

Performing a Mass Conversion Based on an Uploaded File

To simplify the task of converting a set of tables that even may reside in different tablespaces, you can write
their names to a file and upload the file into DB6CONV.

Note the following:

• Only plain text files are allowed for upload.

• The file must consist of a list of tables to be converted, one table name per line.
• Table names must comply with the naming conventions as described at https://www.ibm.com/support/
knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.admin.dbobj.doc/doc/c0007245.html. .
• You may use wildcards: '*' representing an arbitrary number of characters, and '+' representing exactly one
character.

Performing a LONGLOB Conversion

As of Db2 9.7, inline LOBs were introduced providing faster access to data than LONG VARCHAR columns.
During a LONGLOB conversion with report DB6CONV, new tables are created with inline LOB columns instead
of LONG VARCHAR columns. During the LONGLOB conversion, all tables with LONG VARCHAR columns are
collected in the conversion queue and converted.

Note that virtual tables with LONG VARCHAR columns are not part of the conversion queue because their
LONG VARCHAR columns are implicitly replaced by inline LOB columns when these tables are materialized.

To perform a LONGLOB conversion, go the Database-Level tab page and choose the radio button Replace LONG
VARCHAR Columns by LOB Columns (LONGLOB Conversion). Then proceed as described in step 6 to 13 in
Converting a Table or Tablespace [page 10].

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

14 PUBLIC Performing a Conversion Using Report DB6CONV
Converting ITC Candidates to ITC Tables

 Note

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 38].

To convert ITC candidates to ITC tables, go to the Database-Level tab page and choose the relevant radio
button. Then proceed as described in step 6 to 13 in Converting a Table or Tablespace [page 10].

Reconverting ITC Tables to Regular Tables

 Note

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, go to the Database-Level tab page and choose the relevant radio
button.

Dropping Hidden Columns

 Note

This option is only available as of Db2 10.1.

In some scenarios, it might be necessary to work with hidden columns in a table that need to be dropped
later. This is the case, for example, when an SAP system upgrade with the zero-downtime option (ZDO) in
the software update manager (SUM) is reverted. Instead of directly dropping one or more columns of a table
(which will put the table in a "reorg pending" state), these columns are altered to “implicitly hidden”. This
has the advantage that the columns are invisible and the table is still available. To get rid of the hidden fields
eventually, the table needs to be reorganized. Alternatively, to avoid the downtime for a reorganization, you can
convert the tables using DB6CONV with the conversion type Drop Hidden Columns.

During such a conversion, all tables with hidden columns are collected in the conversion queue and converted,
which implicitly recreates each table without the hidden columns.

 Note

If you don't want to drop all hidden columns, make sure that you choose the Display/Edit Queue button and
delete the relevant tables from the conversion queue.

To perform this kind of conversion, go to the Database-Level tab page and choose the radio button Drop Hidden
Columns. Then proceed as described in steps 6 to 13 in Converting a Table or Tablespace [page 10].

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Performing a Conversion Using Report DB6CONV PUBLIC 15
Correcting the Inline Length of LOB Columns

For Db2 9.7 or higher and SAP Kernel 7.00 or higher, BLOB and CLOB columns are created with a default
INLINE LENGTH clause as described in SAP Note 29824 . If the existing inline length of a BLOB or CLOB
column is less than its default value, it may lead to bad performance when this data is accessed.

During a conversion with option Correct Inline Length of LOB Columns, all tables of this kind are collected in the
conversion queue and converted, which implicitly corrects the inline length of their BLOB and CLOB columns to
the default value.

To perform this kind of conversion, go the Database-Level tab page and choose the radio button Correct Inline
Length of LOB Columns. Then proceed as described in step 6 to 13 in Converting a Table or Tablespace [page
10].

Procedure

1. On the New Conversion screen, go to the Database Level tab page and choose one of the above-mentioned
options.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

16 PUBLIC Performing a Conversion Using Report DB6CONV
 2. Create the conversion queue using the Create Queue pushbutton.
3. Then choose the Display/Edit Queue pushbutton to display and maintain the list of tables that are part of
the tablespace conversion, or choose the Save pushbutton to directly save the conversion.
In the Display/Edit 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 25].
4. By default, all tables of a database-level conversion are converted within their own tablespaces. Using
the Target Tablespaces button on the New Conversion screen, you can specify a different set of target
tablespaces. The Choose Target Tablespaces screen displays all tablespaces that contain tables of the
conversion queue in the Source Data Tablespace column. If you choose a tablespace from the dropdown
list in the Target Data Tablespace, Target Index Tablespace, and Target Long Tablespace columns, all tables
currently residing in the source tablespace will be moved to the newly selected set of target tablespaces
during the conversion.

 Note

Selecting a target long tablespace is optional whereas the selection of a target index tablespace is
mandatory unless you have chosen a tablespace pool as target data tablespace. If you have chosen
a tablespace pool as target data tablespace, leave the Target Index Tablespace and Target Long
Tablespace columns empty because they are automatically determined and any manual selections
would be overwritten.

5. Then proceed as described in step 6 to 13 in Converting a Table or Tablespace [page 10].

Naming Convention for Database-Level Conversions

After saving, the database-level conversions are named as follows:

Naming Selected Conversion Type

<FILE>_<6-digit number> Upload from File

<LONGLOB> LONGLOB Conversion

<CONVERT_TO_ITC> ITC Conversion

<RECONVERT_ITC> Reconversion of ITC Tables

<DROP_HIDDEN> Drop Hidden Columns

<LOB_INLINE> Correct Inline Length of LOB Columns

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Performing a Conversion Using Report DB6CONV PUBLIC 17
5.1.3 Converting BW Objects

Context

As of DB6CONV Version 6.20 with Db2 10.5 FP5SAP2 and if the SAP Business Warehouse (SAP BW)
requirements are fulfilled (see SAP Note 1513862 ), you can perform BW conversions using the Business
Warehouse tab page.

You can convert SAP BW object tables from row-organized to column-organized and vice versa, or without
changing the table organization. You can also combine BW conversions with a move of the affected tables to
new tablespaces. If BW object tables are converted, the additional task of BW post-processing is executed per
BW object.

During BW post-processing , the following actions are performed:

• Aggregates for InfoCubes that are being converted from row-organized to column-organized are disabled.
• BW metadata for the converted BW objects is updated.
• Write-programs are re-created for InfoCubes.

To check the consistency of BW objects or to repeat the post-processing for BW objects, you can also execute
BW Post-Processing Only without converting the related SAP BW object tables.

 Note

When the RSADMIN parameter DB6_ALLOW_CDE is set to NO, the creation of new objects for BLU
Acceleration is blocked in the system. In this case, the DB6CONV report informs you that conversion to
BLU Acceleration is not allowed, and the target BLU Acceleration is grayed out on the Business Warehouse
tab page.

For more information, see the guide SAP Business Warehouse on IBM Db2 10.5 and Higher for Linux, UNIX, and
Windows: Administration Tasks at https://help.sap.com/viewer/db6_bw.

Procedure

1. On the New Conversion screen, choose the Business Warehouse tab page and select/deselect the BW
object types that you want to convert, that is, InfoCubes, DataStore objects (DSO), InfoObjects, or
Persistent Staging Area (PSA) tables. By default, all types are selected.
2. Select the BW objects to be converted by name in one of the following ways:

• Choose a BW object name

The asterisk symbol (*), which is the default value, stands for "all BW objects". You can narrow down
the number of BW objects by entering a BW object name that may include wildcards: '*' representing
an arbitrary number of characters, and '+' representing exactly one character.
• Choose the Upload from File option
To simplify the task of converting a set of BW objects, you can write their names to a file and upload the
file into DB6CONV.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

18 PUBLIC Performing a Conversion Using Report DB6CONV
 Note the following:
• Only plain text files are allowed for upload.
• The file must consist of a list of BW objects to be converted, one object name per line.
• You may use wildcards: '*' representing an arbitrary number of characters, and '+' representing
exactly one character.

If you want to include InfoObjects in the conversion queue that are referenced in the InfoCubes and
DataStore Objects to be converted, select the Include Dependent InfoObjects checkbox. By default, this
option is preselected because the reporting performance usually improves if the InfoObject tables that are
referenced in the queries have the same layout as the InfoCube or DSO tables. If you do not want to convert
InfoObjects, deselect this option.

Note that you cannot change the table organization of flat InfoCubes (Flat ICubes) as flat InfoCubes
are always column-organized. However, if you select dependent InfoObjects of a flat InfoCube, these
dependent InfoObjects can be converted (to BLU Acceleration or to row-organization).

3. Choose the conversion mode depending on how you want to convert your selected BW object tables:

• If you want to convert from row-organized to column-organized, choose the Target: BLU Acceleration
radio button in the Conversion section.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Performing a Conversion Using Report DB6CONV PUBLIC 19
 • If you want to convert from column-organized to row-organized, choose the Target: Row-Organized
radio button in the Conversion section.
• If you want to convert the selected BW object tables without changing the table organization, choose
Keep Table Organization.

• If you want to check the consistency of the BW metadata of your BW objects or if a former BW
post-processing entry with status ERROR exists, choose the BW Post-Processing Only radio button. In
this conversion mode, no tables are actually converted.
Note that changing the conversion mode automatically invalidates/deletes all entries from the current
conversion queue because the BW objects and the related SAP BW tables might vary depending on the
the chosen conversion mode. Therefore, after changing the conversion mode, you must create a new
conversion queue (see the following step).
• If you converted BW objects to BLU Acceleration with Db2 versions lower than Db2 11.1 Mod 3 FP 3,
the tables belonging to these BW objects were created as column-organized, but without indexes. If
you are on Db2 11.1 Mod 3 FP 3 or higher and only want to create indexes on your column-organized
tables ('index layout') without converting the tables again, choose the Migrate BLU to Index Layout
radio button. (This option isn't shown if you're on Mod Pack 2 or lower.)
• If you are using column-organized tables with the index layout on Db2 11.1 Mod 3 FP 3 or higher and
want to go back to the setup before Mod Pack 3, that is, if you want to get rid of the indexes without
converting the tables again, choose the Migrate BLU to Non-Index Layout radio button. (This option
isn't shown if you're on Mod Pack 2 or lower.)
4. Choose the Create Queue button. Keep in mind that this irretrievably deletes an existing conversion
queue. As of version 6.58, the DB6CONV tool runs a consistency check for each table that belongs to the
conversion queue and shows whether its target data class and target tablespaces match:

• If all tables in a conversion queue that belong to the same BW object are consistent, that is, their target
data class and target tablespaces match, the corresponding BW object is consistent. Subsequently, if
all BW objects in a conversion queue are consistent, the whole conversion queue is consistent.

 Note

A consistent queue is mandatory for the successful update of BW metadata in the post-processing
step of a BW conversion.

• If one or more tables in a conversion queue that belong to the same BW object are inconsistent,
that is, their target data class does not match their target tablespaces, the corresponding BW object
is marked as inconsistent. Subsequently, if one or more BW objects in a conversion queue are
inconsistent, the whole conversion queue is inconsistent and you get the corresponding notification on
the New Conversion screen.
5. If you want to check your selection or delete one or more BW objects from the selection, choose the
Display/Edit Queue button. The Conversion Queue dialog window opens displaying all BW objects related
to the selected BW object types and their consistency as to target data class and matching target
tablespaces. Inconsistent BW objects are displayed in red and marked as error.

If necessary, you can now modify the queue by explicitly deleting one or more BW objects before saving the
conversion.

By double-clicking a BW object, you can display a list of all tables belonging to this object that will be
converted. This list tells you the current (that is, source) table organization, the calculated target table
organization as well as what kind of conversion will be performed. As of DB6CONV version 6.58, the target
data class, target tablespaces, and the outcome of their consistency check are shown for each table as

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

20 PUBLIC Performing a Conversion Using Report DB6CONV
 well. Inconsistent tables where the target data class does not match the target tablespaces are displayed in
red and marked as error.

 Note

Note that the target state BLU Acceleration of a BW object might consist of a mix of row- and column-
organized tables because not all tables of a SAP BW object can be converted to column-organized. To
find out which tables can be column-organized, see SAP BW Tables Considered for BLU Acceleration
[page 45] in the appendix.

Therefore, as of DB6CONV 6.30, if you have tables that are not eligible to BLU Acceleration, but are
nevertheless column-organized (“C “), a BW conversion with Target: BLU Acceleration will convert them
back to row-organized (“R “).

6. To specify a different set of target data classes, use the Target Data Classes button on the New
Conversion screen. By default, the tables of a BW conversion are converted within their own tablespaces
without changing their data class. The Choose Data Classes screen displays all data class-tablespace
combinations, which contain tables of the conversion queue, together with their consistency status in
the Source Data Class column. Inconsistent entries are marked as error in red. If you choose a data
class-tablespace combination from the dropdown list in the Target Data Class column, all tables with the
relevant source data class and currently residing in the corresponding set of source tablespaces will be
moved to the newly selected set of target tablespaces during the conversion and their data class will be
changed to the newly selected target data class.

 Note

A newly defined BW conversion can only be saved if its conversion queue is consistent. Therefore, for
every inconsistent source data class, make sure you choose a new target data class.

If you choose a target data class corresponding to new tablespaces, all tables belonging to the BW
object are converted, even if their table organization does not change. If you don’t choose a new data class-
tablespace combination, only those tables are converted where the table organization changes during the
conversion.
7. Then proceed as described in steps 6 to 13 in Converting a Table or Tablespace [page 10].

Naming Convention for BW Conversions:

After saving, all BW conversions are named <BW>_#, where # is a 6-digit ascending number starting with
<BW>_000001 for the first BW conversion.

5.1.4 Converting SAP Convergent Invoicing Tables

Prerequisites

You are using SAP Contract Accounts Receivable and Payable (FI-CA) Release 617 or higher running on Db2
10.5 FP5SAP2 or higher.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Performing a Conversion Using Report DB6CONV PUBLIC 21
Before the conversion, you must do the following:

1. Check and implement the prerequisites for column-based storage (BLU Acceleration) from SAP Note
1819734 .
2. Apply SAP Note 2207508 .

Context

As of version 10.5, IBM Db2 for Linux, UNIX, and Windows supports column-based storage for the analysis of
unbilled items in SAP Convergent Invoicing. If you want to use column-based storage, you need to convert the
relevant database tables from a row-based to a column-based table layout. For more information, see SAP Note
2136479 .

On the Convergent Invoicing tab page, you can convert SAP Convergent Invoicing tables from row-organized to
colum-organized and vice versa. You can also combine these conversions with the move of the affected tables
to new tablespaces.

After you have converted tables to column-based, new tables that are created for a billing class will
automatically be created in column-based storage.

Procedure

1. On the New Conversion screen, choose the Convergent Invoicing tab page.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

22 PUBLIC Performing a Conversion Using Report DB6CONV
 2. Choose the conversion mode: Depending on how you want to convert your selected SAP Convergent
Invoicing (SAP CI) tables, choose the From Row- to Column-Organized radio button or the From Column- to
Row-Organized radio button in the Conversion of Convergent Invoicing Tables section.
3. Choose the Create Queue button.
4. If you want to check your selection, choose the Display Queue button. The Conversion Queue dialog
window opens displaying all SAP Convergent Invoicing objects to be converted.
5. By default, all tables of a SAP CI conversion are converted within their own tablespaces. Using the Target
Tablespaces button on the New Conversion screen, you can specify a different set of target tablespaces.
The Choose Target Tablespaces screen displays all tablespaces that contain tables of the conversion queue
in the Source Data Tablespace column. If you choose a tablespace from the dropdown list in the Target Data
Tablespace, Target Index Tablespace, and Target Long Tablespace columns, all tables currently residing in
the source tablespace will be moved to the newly selected set of target tablespaces during the conversion.

 Note

Selecting a target long tablespace is optional whereas the selection of a target index tablespace is
mandatory unless you have chosen a tablespace pool as target data tablespace. If you have chosen
a tablespace pool as target data tablespace, leave the Target Index Tablespace and Target Long

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Performing a Conversion Using Report DB6CONV PUBLIC 23
 Tablespace columns empty because they are automatically determined and any manual selections
would be overwritten.

6. Then proceed as described in steps 6 to 13 in Converting a Table or Tablespace [page 10].

Naming Convention for the Conversion of SAP Convergent Invoicing Tables:

After saving, all mass conversions of SAP Convergent Invoicing tables are named <CI>_#, where # is a
6-digit ascending number starting with <CI>_000001 for the first mass conversion.

5.2 Using External Conversion Jobs for SAP BW

In DB6CONV, you can also run conversion jobs for SAP BW that repair distribution keys.

These conversion jobs are generated by tools outside the DB6CONV report and are then listed in DB6CONV as
object type External. The object name of the corresponding conversion job starts with <EXT>_.

The following conversion jobs and tools are available:

Tool to Generate the Con­

Conversion Task Name of Conversion Job version Job Relevant SAP Notes

Repair distribution keys for <EXT>_REP_PK_IC Function module 1574965 , 648432

fact tables RSDU_CHKREP_PKEY_ALL_C
UBES_DB6

Repair distribution keys for <EXT>_REP_PK_ODS Function module 1574965 , 648432

ODS tables RSDU_CHKREP_PKEY_ALL_O
DS_DB6

Repair distribution keys for <EXT>_REP_PK_PSA Function module 1574965 , 648432

PSA tables RSDU_CHKREP_PKEY_ALL_P
SA_DB6

For more information, see the database administration guide SAP Business Warehouse on IBM Db2 10.5 and
Higher for Linux, UNIX, and Windows: Administration Tasks at https://help.sap.com/viewer/db6_bw.

5.3 Maintaining the Conversion Parameters

For any conversion job, you can display or maintain the conversion parameters as follows:

• For a new conversion, you can specify the parameters for the conversion job on the New Conversion screen
(not applicable for external conversions).
• For conversions with status PLANNED, you can display or maintain the current conversion parameters by
selecting an entry on the Conversion Overview screen and choosing the Details pushbutton.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

24 PUBLIC Performing a Conversion Using Report DB6CONV
 Exception: For tablespace conversions, you cannot change the option that you have chosen in the Insert
Time Clustering field anymore.
• For conversions with any other status than PLANNED, you can only display the conversion parameters by
choosing the Details pushbutton on the Conversion Overview screen.
• Although the conversion parameters can only be displayed if the conversion status is other than PLANNED,
there is one exception: If, in a support case, you have to switch on the trace for an aborted conversion, you
can do so by selecting the affected single table conversion and entering AMT1 into the transaction field of
the SAP GUI. By entering AMT0, you can switch off the trace for conversions.

5.4 Maintaining the Conversion Queue of a Mass

Conversion

For a mass conversion, you can display or maintain the current queue of tables to be converted as follows:

• For a new conversion, you can display or maintain the initial conversion queue while specifying the
parameters for the conversion job by choosing the Conversion Queue pushbutton on the New Conversion
screen.
• For conversions other than Convergent Invoicing conversions with status PLANNED, you can display or
maintain the current conversion queue by choosing the Details pushbutton on the Conversion Overview
screen and then the Conversion Queue pushbutton on the Details for <object name> screen.
• For Convergent Invoicing conversions or conversions with any other status than PLANNED, you can only
display the conversion queue by choosing the Details pushbutton on the Conversion Overview screen and
then the Conversion Queue pushbutton on the Details for <object name> screen.

For tablespace conversions, all tables that reside in the specified tablespace and that have the table schema of
the AS ABAP system are initially displayed in the conversion queue in alphabetical order. A message window is
displayed if the tablespace contains tables with a table schema other than the table schema of the AS ABAP
system.

For LONGLOB conversions, all tables that have the table schema of the AS ABAP system with at least one
LONG VARCHAR field are initially displayed in the conversion queue in alphabetical order independently of their
tablespace location.

For ITC conversions, all ITC candidate tables are initially displayed in the conversion queue in alphabetical order
independently of their tablespace location.

Similarly, for the reconversion of ITC tables to regular tables, all ITC tables are initially displayed in the
conversion queue in alphabetical order independently of their tablespace location.

For BW conversions, all BW objects of the selected object types of which at least one table is not in the target
table organization are initially displayed in the conversion queue.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Performing a Conversion Using Report DB6CONV PUBLIC 25
The following information is displayed in the Conversion Queue dialog box (not for BW conversions; see the end
of this chapter for information about what is listed in the conversion queue for BW conversions):

Column Description

Table Name Name of the table

Size [KB] Size of the 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>)

Note that this value only includes inlined LOB data.

A value of 1- indicates that no statistics exist for the corre­

sponding table. Therefore, its size is unknown.

 Note
Without current statistics, the real size of a table can
deviate from the size specified here.

Status For conversions currently being defined or with status

PLANNED, the status for each table of the conversion queue
is set to NEW. Once a conversion job has started, the status
for the tables in the queue changes accordingly, for example,
to RUNNING or ABORTED.

For Db2 10.1 or higher and if the database is not using the Db2 pureScale Feature:

Column Description

Clustering Indicates whether the table is clustered before the conver­

sion.

Possible values:

NO: Table is not clustered

MDC: Table is clustered by dimensions

ITC: Table is clustered by insert time

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

26 PUBLIC Performing a Conversion Using Report DB6CONV
 Column Description

ITC Conversion strategy using insert time clustering. You can

choose between the following values and, if necessary, over­
write your previous selection for the mass conversion:

YES:

Table will be clustered by insert time after the conversion

(independent of the status before). This is the default value
for ITC candidates in the following scenarios:

• Tablespace conversions where the ITC setting is Yes for

Candidates
• ITC conversions

NO:

Table will not be clustered by insert time after the conversion

(independent of the status before). This is the default value
for:

• Tablespace conversions where the ITC setting is No

• ITC reconversions

KEEP:

Status of insert time clustering will not change during the

conversion. This is the default value for:

• Tablespace conversions where the ITC setting is KEEP

• Tables that are no ITC candidates in tablespace conver­
sions where the ITC setting is Yes for Candidates
• LONGLOB conversions

If you need detailed information about ITC candidates, you can display the following columns by choosing the
ITC Status pushbutton:

Column Description

Deleted Objects Number of deleted archiving objects for the table

This field is empty if the table is not considered an ITC candi­

date by DB6CONV.

Archiving Object Archiving object(s) for this table

Extent Size Extent size (in KB) of the table

For more information, see Insert Time Clustering (ITC) Tables and Candidates [page 38].

The following information is displayed in the Conversion Queue dialog window for BW conversions only:

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Performing a Conversion Using Report DB6CONV PUBLIC 27
Column Description

BW Type Type of BW object: InfoCube, InfoObject, DataStore object

(DSO), or Persistent Staging Area (PSA) tables

BW Object Name of the BW objects

If you click on a BW object in the list, a dialog window opens displaying the following information for the tables
related to the BW object:

Column Description

Table Name Name of the table

Size [KB] Size of the table to be converted based on current database

statistics (in KB)

The displayed value is based on the following formula:

(<value of syscat.tables-npages> times <pagesize of the

source tablespace>)

Note that this value only includes inlined LOB data.

A value of 1- indicates that no statistics exist for the corre­

sponding table. Therefore, its size is unknown.

 Note
Without current statistics, the real size of a table can
deviate from the size specified here.

Available Actions in the Conversion Queue Dialog Box

In the Conversion Queue dialog box, you can perform one of the following actions by choosing the appropriate
pushbutton:

• Delete tables from the conversion queue

You can delete a table from the conversion queue by selecting it from the list and choosing the Delete
pushbutton. These tables are no longer part of the upcoming mass conversion.
The Delete pushbutton is disabled when the conversion is started.
• For Db2 10.1 only, if the database is not using the Db2 pureScale Feature, and not for BW conversions:
• Display additional ITC-related columns (see table above).
• Change the displayed ITC option for individual tables by selecting the appropriate value from the
dropdown list.
• Refresh the conversion queue
The Refresh pushbutton is disabled until the conversion is started.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

28 PUBLIC Performing a Conversion Using Report DB6CONV
5.5 Specifying Conversion Options

You can display and maintain conversion options on the Conversion Overview screen. The conversion options
will apply to all conversions that you create and that use the LOAD command from IBM Db2.

Context

DB6CONV uses the Db2 command LOAD to load data into tables. With the conversion options, you can define
additional options for the LOAD command.

Procedure

1. On the Conversion Overview screen, choose Conversion Options.

2. In the List of Conversion Options dialog window, you can select the following options for the Load profile
from the dropdown list:

LOAD Option Description

COPY YES With the COPY YES option, you define the target location
where data is stored during a recoverable load. The values
that you can enter are:

• USE TSM
• TO <device/directory>
• LOAD <lib-name (including full
path)>

For conversions defined with Use Recoverable LOAD, you

must select and specify this option.

 Note
In an HADR scenario, make sure that the standby can
access the files at the location that you have speci­
fied.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Performing a Conversion Using Report DB6CONV PUBLIC 29
 LOAD Option Description

CPU_PARALLELISM For conversions defined with Use LOAD, you can select
and specify one or more of these options to finetune the
DATA_BUFFER
DB2 LOAD command.
DISK_PARALLELISM

FETCH_PARALLELISM

SORT BUFFER

More Information

For more information about the DB2 LOAD command, see the IBM Db2 documentation .

5.6 Starting a Conversion Job

Procedure

1. On the Conversion Overview screen, start the conversion job by selecting the planned job from the list and
choosing the Start pushbutton.
2. In the Start Conversion dialog box, specify the following parameters:

• The number of parallel jobs used during the conversion (only available for mass conversions)
The value can range from 1 up to the number of batch jobs configured in the system.
• 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.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

30 PUBLIC Performing a Conversion Using Report DB6CONV
5.7 Monitoring a Running Conversion

You can monitor the progress of a running conversion using the information displayed in the Comment field on
the Conversion Overview screen.

 Note

Since there is no automatic refresh, make sure that you manually refresh the information to always have
the most current information displayed.

Single Table Conversion

The Comment field contains the number of the conversion step that is currently being executed. For the data
transfer step, the number and percentage of currently transferred table rows is also displayed.

Tablespace and Database-Level Conversion

The Comment field displays information based on the following formula:

<x>/<y> tables (<z> KB)

where

<x> stands for the number of tables that were already successfully converted

<y> stands for the total number of tables in the conversion queue at the start of the mass conversion

<z> stands for the size of data in KB that was successfully moved

BW Conversion

The Comment field displays information based on the following formula:

<x1>/<y1> tables (<z> KB)- <x2>/<y2> BW objects

where

<x1> stands for the number of tables that were already successfully converted

<y1> stands for the total number of tables in the conversion queue at the start of the mass conversion

<z> stands for the size of data in KB that was successfully moved

<x2> stands for the number of BW objects that were already successfully converted, that is, all tables
belonging to this BW object have been successfully converted

<y2> stands for the total number of BW objects in the conversion queue at the start of the mass conversions

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Performing a Conversion Using Report DB6CONV PUBLIC 31
The tables that are implicitly converted during a mass conversion are displayed in the Tables from Mass
Conversions area including their status.

For a BW conversion, an additional entry with the name of the BW object and the comment BW Post Processing
is displayed in the Tables from Mass Conversions area after the last table belonging to this BW object was
successfully converted.

If you doubleclick such an entry (or select it and choose the Conversion Log button), the detailed results of
the BW post-processing for the selected BW object is displayed. If the status is ERROR, check the results and
contact SAP support, if necessary.

If a subsequent BW post-processing step for the same BW object succeeds, the status of older erroneous
entries changes to ERROR (RESOLVED) and those entries can be deleted from the Tables from Mass
Conversions list.

Progress Details for the Copy & Replay Phase of a Conversion (only as of Db2
11.1)

As of Db2 11.1, you can use the Conversion Overview Screen also to get detailed information about the copy &
replay phase of a conversion.

Related Information

Information on the Conversion Overview Screen [page 40]

5.8 Available Actions on the Conversion Overview Screen

Once you have planned and started a conversion job, you can perform the following actions:

• Pause, continue, replay, abort, or reset a conversion

• Display and delete the conversion log
• Change the number of parallel jobs
• Switch tracing on and off

Pausing a Conversion

 Note

This pushbutton is only available for mass conversions with status RUNNING.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

32 PUBLIC Performing a Conversion Using Report DB6CONV
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

 Note

This pushbutton is only available for aborted single table conversions or aborted or paused mass
conversions.

To continue an aborted single table conversion or an aborted or paused mass conversion, select the
appropriate batch job and choose the Continue pushbutton in the Conversion Jobs area.

For a mass conversion, you have to consider the following:

An aborted single table conversion that was started by a batch job of a parent mass conversion is automatically
continued unless you reset or continue the conversion on table level earlier by selecting the appropriate table
from the list in the Tables from Mass Conversion area and choosing the appropriate pushbutton.

When you continue a mass conversion, you can also change the number of parallel jobs that you specified
when starting the conversion.

Replaying a Conversion

 Note

This pushbutton is only available for conversions of single tables with status PAUSED.

For 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 a conversion.

Aborting a Conversion

 Note

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.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Performing a Conversion Using Report DB6CONV PUBLIC 33
We recommend that you only use this option in emergency cases, for example, if a conversion is running too
long.

Resetting a Conversion

 Note

This pushbutton is only available for aborted single table conversions or aborted or paused mass
conversions.

 Note

You can reset an aborted single table conversion or a mass conversion by selecting the appropriate job
from the list and choosing the Reset pushbutton in the Job Conversion area.

For a single table conversion, resetting a table restores the state of the table from before the conversion if the
table has not yet been renamed.

For a mass conversion, you have to consider the following:

Resetting a mass conversion simply empties the queue of the marked mass conversion and resets table
conversions with status ABORTED that belong to this mass conversion. Then, all tables that have already been
successfully converted reside in the target tablespace. All tables that have not yet been converted remain in the
source tablespace.

 Note

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.

Changing the Number of Parallel Jobs

 Note

This pushbutton is only available for currently running mass conversions.

You can change the number of parallel jobs of a running mass conversion dynamically without stopping it by
selecting the appropriate conversion job from the list and choosing the +/- Jobs pushbutton.

You might want to change the number of parallel jobs, for example, in the following situations:

• You accidentally defined not enough or too many parallel processes.

• Another important process requires more batch processes than the currently running conversion.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

34 PUBLIC Performing a Conversion Using Report DB6CONV
Displaying the Conversion Log

You can display log information about any conversion job independently of whether it is running or whether
it has finished. To do so, select the appropriate entry on theConversion Overview screen and choose the
Conversion Log pushbutton. Alternatively, you can double-click the appropriate entry:

• If you doubleclick an entry in the Tables from Mass Conversion area or an entry with object type Table in the
Conversion Jobs area, the conversion log for the conversion of this particular table is displayed.
• If you doubleclick an entry of object type Tablespace or LONGLOB in the Conversion Jobs area, a summary
log is displayed for this mass conversion containing information about the conversion queue and the batch
jobs.
• If you doubleclick a line containing Conversion Job <batch job name> in the summary log for this mass
conversion, you switch to the summary log of that batch job that contains information about the single
table conversions started by this batch job (parent). If you doubleclick a line containing Conversion of
table <table name> in the summary log of that batch job, the conversion log of that specific table is finally
displayed.

Deleting the Conversion Log

 Note

This pushbutton is only available for conversions with status FINISHED, RESET, or PLANNED.

By choosing the Delete pushbutton, you can delete the detailed conversion logs of a single or multiple selected
conversions.

Switching Tracing On and Off

If a single table conversion (either listed in the Conversion Jobs section or in the Tables from Mass Conversions
section) aborts and you want to reproduce the error using the trace option of the ADMIN_MOVE_TABLE
procedure, you can do so by selecting the single table conversion and entering AMT1 into the transaction field
of the SAP GUI. A message window appears to confirm that the trace has been switched on. If you continue
with the selected table conversion, trace files are now written to the Db2 dump directory.

By entering AMT0, you can switch off the ADMIN_MOVE_TABLE trace.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Performing a Conversion Using Report DB6CONV PUBLIC 35
6 Conversion Steps

In the following, the steps and relevant actions of a table conversion are described.

Starting with DB6CONV V6.20, all conversions are performed using the SYSTOOLS.ADMIN_MOVE_TABLE
stored procedure (in the following referred to as AMT). For more information, see SAP Note 1543745 .

Step 0

• Checks whether the conversion is possible.

• Writes the following information to the conversion log:
• Header section containing the conversion parameters
For example, the target tablespaces are listed together with their database partition group and
database partition number.
• Data class and data, index, and long tablespaces of the source table together with their database
partition group and the data partition number
• Page sizes of the source and target tablespaces
• Actual table size and compression status
• Structure (DESCRIBE TABLE) of the source table (only when a conversion is started)
• Table type of the source table
Possible values are TRANSP, POOL, or CLUSTER.
• All indexes of the table with index name, uniqueness, index type, and index fields
• Definition of all triggers defined on the table
• SAP Basis and SAP BW version, kernel release, and database release

Step 1

• Creates the target table QCM8<TABLE> as follows:

• For tables known to the ABAP Dictionary:
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.
• For tables not known to the ABAP Dictionary:
Creates the target table QCM8<TABLE> using the CREATE TABLE statement retrieved from db2look.
DDSTORAGE is not considered in this case.
• Writes the CREATE TABLE statement to the conversion log.
• Calls AMT for the table to be converted specifying the target table with operation parameter INIT. This
implicitly creates all temporary objects needed for the conversion, such as triggers and the staging table.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

36 PUBLIC Conversion Steps
Step 2

• Calls the AMT 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 AMT stored procedure for the table to be converted and the target tablespaces with operation
parameter REPLAY.

 Note

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.

• Updates the statistics for the table to be converted if necessary, that is, if SYSCAT.TABLES-CARD is less or
equal zero.

Step 4

• Calls the AMT 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.
• Changes the data class for the target table if you have specified a target data class. For virtual tables, this is
the only action that is executed, the rest of step 4 is skipped.
• Deletes the original table if you selected Delete Source Table After Conversion when defining the conversion
job.
• Displays again detailed information about the table size and compression.
• Displays again the structure of the target table.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Conversion Steps PUBLIC 37
7 Insert Time Clustering (ITC) Tables and
Candidates

As of Db2 10.1, you can create insert time clustering (ITC) tables. ITC tables are based on the infrastructure
for MDC tables and allow you to reclaim free space without reorganization using the REORG command with the
RECLAIM EXTENTS ONLY clause. In an ITC table, records are clustered based on their insert time.

For an effective reclamation of free space for ITC tables, complete extents of the table must be empty.
Therefore, a regular table should only be considered an ITC candidate if records that are inserted together
are also deleted together. In an SAP system, this access pattern is typical for tables from which data
is archived. For example, a business object contract has an associated archiving object. During archiving,
usually all contracts up to a specific creation date are written to the archive and afterwards deleted from the
corresponding tables.

 Note

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 fulfill 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.

 Note

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.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

38 PUBLIC Insert Time Clustering (ITC) Tables and Candidates
Related Links

Multidimensional and insert time clustering extent management in the IBM Db2 documentation

SAP Note 1700631

SAP Note 975352

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Insert Time Clustering (ITC) Tables and Candidates PUBLIC 39
8 Appendix

8.1 Information on the Conversion Overview Screen

On the Conversion Overview screen, you can find information about:

• Conversion jobs
• Tables from mass conversions
• Progress details for copy & replay (as of Db2 11.1 and higher)

Information Displayed in the Conversion Jobs Area

Here you can see all the conversion jobs that are known to DB6CONV. A conversion job is a conversion that
you have explicitly defined using DB6CONV or that has been defined outside DB6CONV using a BW function
module.

For each conversion job, the following information is displayed:

Column Description

Status Status of the conversion job

Possible values:

• PLANNED
• SCHEDULED
• PAUSED
• RUNNING
• ABORTED
• FINISHED
• RESET
• NEW
• PRELIMINARY

The conversion job statuses NEW and PRELIMINARY reflect the job status of the correspond­
ing batch job as shown in SM37. They may occur if a batch job was planned, but could not be
started. Conversions with this status cannot directly be continued or reset. In these cases, you
have to delete the corresponding batch job in SM37. After refreshing the conversion overview,
the status of the conversion job should have switched to ABORTED.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

40 PUBLIC Appendix
 Column Description

Object Type Type of object to be converted

Possible values:

• Table
• Tablespace
• DLCONV
• External
• BW
• CI

Object Name Name of the object to be converted

Start Date Start date of the conversion

Start Time Start time of the conversion

End Date Date and time when the status of a running conversion job changed to one of the following
statuses:
End Time
• PAUSED
• ABORTED
• RESET
• FINISHED

Duration Total runtime of the conversion job since its start (does not include wait times)

Size [KB] For single table conversions with status PLANNED:

Size of the 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>)

Note that this value only includes inlined LOB data.

A value of 1- indicates that no statistics exist for the corresponding table. Therefore, its size is
unknown.

Once the conversion is running, the displayed value is replaced by the actual table size, now
including LOB data that are not inlined.

For mass conversions:

• For status PLANNED: Total size of all tables of the current conversion queue based on the
formula mentioned above for single table conversions with status PLANNED.
• Once the conversion is running, the displayed value keeps changing as it's constantly
being updated with the actual table size for each table in the conversion queue.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Appendix PUBLIC 41
Column Description

Jobs Number of currently defined parallel processes for the conversion job

A value of 1 is displayed for single table conversions and for mass conversions with status
PLANNED.

For mass conversions with status PLANNED, you can specify the number of parallel jobs in the
Start Conversion dialog box.

For mass conversions with a status other than PLANNED, the number of parallel jobs can be
changed as follows:

• Manually when you continue an aborted or paused mass conversion (in the Continue
Conversion dialog box)
• Dynamically while the mass conversion is running using the +/- Jobs pushbutton on the
Conversion Overview screen

For more information, see Available Actions on the Conversion Overview Screen [page 32].

Comment Information that is related to the conversion as such or to a specific conversion step

For single table conversions with status RUNNING, the current conversion step is displayed.
While data is being transferred, the progress of the data transfer is also displayed.

For tablespace and database-level conversions, the progress of the conversion is displayed
as follows:

<x> /<y> tables (<z>KB)

where

<x> stands for the number of tables that have already been successfully converted

<y> stands for the total number of tables in the conversion queue at the start of the mass
conversion

<z> stands for the size of data in KB that was successfully moved

For BW conversions, the Comment field displays information based on the following formula:

<x1>/<y1> tables (<z> KB)- <x2>/<y2> BW objects

where

<x1> stands for the number of tables that were already successfully converted

<y1> stands for the total number of tables in the conversion queue at the start of the mass
conversion

<z> stands for the size of data in KB that was successfully moved

<x2> stands for the number of BW objects that were already successfully converted, that is,
all tables belonging to this BW object have been successfully converted

<y2> stands for the total number of BW objects in the conversion queue at the start of the
mass conversions

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

42 PUBLIC Appendix
Information Displayed in the Tables from Mass Conversions Area

All table conversions are listed that have implicitly been started by the batch process that you defined for the
parent mass conversion job. The mass conversion job itself is displayed in the Conversion Jobs area.

The following information is displayed in the Tables from Mass Conversions area:

Column Description

Status Status of the conversion job

Possible values:

• PLANNED
• SCHEDULED
• PAUSED
• RUNNING
• ABORTED
• FINISHED
• RESET
• ERROR (only for BW post processing)
• ERROR (RESOLVED) (only for BW post processing)
• NEW
• PRELIMINARY

The conversion job statuses NEW and PRELIMINARY reflect the job status of the corre­
sponding batch job as shown in SM37. They may occur if a batch job was planned, but
could not be started. Conversions with this status cannot directly be continued or reset. In
these cases, you have to delete the corresponding batch job in SM37. After refreshing the
conversion overview, the status of the conversion job should have switched to ABORTED.

Table Name Name of the table that is converted

Start Date Start and end date of the conversion

End Date

Start Time Start and end time of the conversion

End Time

Duration Total runtime required for a conversion job with status RUNNING (does not include wait
times)

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Appendix PUBLIC 43
Column Description

Size [KB] Initially, the size of the table to be converted in KB based on current database statistics is
shown. The displayed value is based on the following formula:

(<syscat.tables-npages> times <pagesize of the source

tablespace>)

Note that this value only includes inlined LOB data.

A value of 1- indicates that no statistics exist for the corresponding table. Therefore, its size
is unknown.

Once the conversion is running, the displayed value is replaced by the actual table size
including LOB data that are not inlined.

Parent Name of the batch process of the mass conversion job that implicitly performed the conver­
sion of a single table

Comment Information that is related to the conversion as such or to a specific conversion step

For single table conversions with status RUNNING, the current conversion step is displayed
as well as the progress of the data transfer.

For BW conversions, BW Post Processing is indicated.

Information Displayed in the Progress Details for Copy & Replay Area (Db2
11.1 or higher)

All table conversions are listed with AMT Status Copy or Replay. Especially for large tables where the related
Conversion Steps [page 36] no. 2 and 3 may take a long time, detailed information about the copy or
replay performance can be helpful. For more information about the displayed data see ADMIN_MOVE_TABLE
procedure - Move tables online in the IBM Db2 documentation .

The following information is displayed in the Progress Details for Copy & Replay area:

Column Description

Table Name Name of the table that is converted

Action Indicates if the conversion job is in COPY or REPLAY mode

Throughput [rows/s] Indicates the copy performance based on the following formula:

COPY_TOTAL_ROWS/(MIN(CURRENT_TIMESTAMP, COPY_END)-COPY_START)

If the conversion has the status PAUSED or ABORTED, 0 (null) is returned.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

44 PUBLIC Appendix
 Column Description

Rows Staging Number of rows in the staging table

It's calculated using the MON_GET_TABLE values rows_inserted -

rows_deleted.

Inflow Staging [rows/s] Number of rows per second that are inserted into the staging table

Outflow Staging [rows/s] Number of rows per second that are removed from the staging table

If the conversion has the status PAUSED or ABORTED, 0 (null) is returned.

Time Remaining Estimated time until completion of the current action.

If the conversion has the status PAUSED or ABORTED, n.a. (not available) is returned.

8.2 SAP BW Tables Considered for BLU Acceleration

The table provides you with an overview which tables of SAP BW objects can be converted to column-organized
table layout or not.

The table lists the most relevant tables of each SAP BW object and whether they can be column-organized. For
some SAP BW objects such as InfoObjects, only some of their tables can be converted to column-organized
while the rest of the tables remain row-organized. For other SAP BW objects, you can control with RSADMIN
parameters whether tables are converted to row-organized or to column-organized. Note that this is intended,
as not every table conversion to column-organized really results in a performance benefit. The defaults and
possible settings listed here are considered by report DB6CONV as of version 6.30 when you convert tables
from row-organized to column-organized and vice versa.

List of Tables of SAP BW Objects: Candidates for BLU Acceleration

Can Be Column-Or­
SAP BW Object Object Type Table Name ganized Comments

DataStore object Standard Only if no secondary indexes exist

/.../A...00 Yes

/.../B... No

/.../A...40 No

Write-optimized /.../A...00 Yes Only if no secondary indexes exist

Direct Update /.../A...00 No

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Appendix PUBLIC 45
 Can Be Column-Or­
SAP BW Object Object Type Table Name ganized Comments

InfoCube Standard or real- /.../F... Yes F fact table

time
/.../E... Yes E fact table

/.../D... Yes Dimension tables

InfoCube for SAP /.../9F... No

APO
/.../9E... No

/.../9D... No

Flat /.../F... Yes F fact table

Flat InfoCubes are always column-

organized.

/.../D... Yes Package dimension table

InfoObject To enable BLU Acceleration for In­

foObjects, set RSADMIN parameter
DB6_IOBJ_USE_CDE = YES.

/.../S... Yes

/.../P... Yes As of Db2 10.5 FP5SAP2, the table

is column-organized per default.

You can switch to row-organized

by setting the RSADMIN parameter
DB6_IOBJ_PQT_USE_CDE to NO.

/.../Q... Yes As of Db2 10.5 FP5SAP2, the table

is column-organized per default.

You can switch to row-organized

by setting the RSADMIN parameter
DB6_IOBJ_PQT_USE_CDE to NO.

/.../X... Yes

/.../Y... Yes

/.../T... Yes As of Db2 10.5 FP5SAP2, the table

is column-organized per default.

You can switch to row-organized

by setting the RSADMIN parameter
DB6_IOBJ_PQT_USE_CDE to NO.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

46 PUBLIC Appendix
 Can Be Column-Or­
SAP BW Object Object Type Table Name ganized Comments

Other No

PSA To enable BLU Acceleration for

PSA tables, set RSADMIN parame­
ter DB6_PSA_USE_CDE = YES.

/BIC/B... Yes

Other No

8.3 References

Are you looking for more documentation? Here's an overview of information sources that are available for SAP
systems on IBM Db2 for Linux, UNIX, and Windows.

Documentation by SAP

For central access to all our documentation, use our SAP on IBM Db2 page on SAP Help Portal at https://
help.sap.com/viewer/p/DB6.

SAP on Db2 for Linux, UNIX, and Windows Community

Check out and participate in our SAP community for IBM Db2 at https://www.sap.com/community/topic/
db2-for-linux-unix-and-windows.html . Here you'll find blogs, Q&As, whitepapers, videos, and guides. You can
also write blogposts yourself and publish them here.

Documentation by IBM

You can find product documentation on your Db2 version in the IBM Db2 Documentation at https://
www.ibm.com/docs/en/db2 .

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Appendix PUBLIC 47
9 Disclaimer

By following links to IBM Documentation you are leaving the SAP product documentation and entering a
site that is not hosted by SAP. By using the link, YOU AGREE that unless expressly stated otherwise in your
agreements with SAP you are about to access an external webpage which is not part of SAP’s offering:

(i) the content of the linked-to site and any further external site is not product documentation and you may not
infer any product documentation claims against SAP based on this information;

(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.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

48 PUBLIC Disclaimer
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

Converting Tables Using Report DB6CONV (Version 6.58 or Higher)

Important Disclaimers and Legal Information PUBLIC 49
www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN