For most of the menu options, you must know whether or not your database has a server running. You are prompted to connect to the database as shown in the following procedure.
2. Enter your connection type (0, 1, or #threads).
If a database broker is not running, you must select zero (0). If a database broker is running, you can run the report using one or more threads. If you enter a connection type that does not match the state of the database, DBTOOL returns this error:
dsmUserConnect failed rc = -1
After you enter a valid connection code, the prompts specific to the functionality of your selection appear.
3. Continue through the remaining prompts for your option.
Common prompts include the following:
Table — Enter the table number at the following prompt:
<table>: (Table number or all)?
You may be prompted to further refine your selection:
If the table you select is a multi-tenant table, you will be prompted with the following sub-prompt:
<multi-tenant>:(tenant tname | group gname | shared | all)?
If you specify tenant or group, dbtool only evaluates the partition owned by the named tenant or group. If you specify shared, the shared partition is evaluated. Specifying all evaluates the entire table.
If the table you select is a table partitioned by table-partitioning, you will be prompted with the following sub-prompt:
<Partition Name>: (Partition name or all)?
If you specify a partition name, dbtool only evaluates the named table partition. Specifying all evaluates the entire table.
Area — Enter the area number at the following prompt:
<area>: (Area number or all)?
If the area you select contains multi-tenant tables or indexes, you will be prompted with the following sub-prompt:
<tenant/group>:(tenant tname | group gname | shared | all)?
Refine the data that dbtool evaluates. If you specify tenant or group, dbtool only evaluates the partitions owned by the named tenant or group. If you specify shared, the shared partition is evaluated. Specifying all evaluates the entire area.
Display — Enter the verbose level. The verbose level defines the amount of output displayed, with zero being the least verbose. The following prompt appears for display:
<display>: (verbose level 0-4)?
The SQL Width Scan options are used to display or set the width of columns based on the size of the actual data in the fields. These calculations are sized in the same way for OpenEdge SQL and OpenEdge DataServers except in the case of CHARACTER, RAW, and DECIMAL extent columns in OpenEdge DataServers. For information on the SQL Width & Date Scan w/Report Option, see DBTOOL utility.
When the SQL Width Scan options are applied to OpenEdge SQL, use verbose levels 0-3 to display information about column width calculations made by the tool. For OpenEdge SQL, the "_Width" value for the extent fields is the total of the data size of each individual element of the extent added together. The verbose levels report varying levels of detail, depending on the option selected, but generally follow the model:
Level 0 — Report summary information
Level 1 — Report errors for each record
Level 2 — Report record size and the number of fragments, errors etc
Level 3 — Report on binary data in the records
Level 4 — Report details for OpenEdge DataServer only
When the SQL Width Scan options are applied to OpenEdge DataServers, use verbose level 4 to display information about column width calculations along with the Array Width and Max ArrayWidth information. These additional display fields (Array Width and Max ArrayWidth) show column widths that are adjusted differently for CHARACTER, RAW, and DECIMAL extent fields as needed to support DataServers and foreign data sources. The "_Width" schema field is not changed directly. Therefore, OpenEdge SQL users are not affected by the alternative calculations for DataServer extent fields.
The SQL Width Scan w/Fix Option stores a hidden schema field containing the width value required by the OpenEdge DataServers. The calculated extent width identifies the largest single data element in the array and multiplies its length with the number of elements in the extent. This calculation ensures that an adequate column width is derived for the columns migrating to a foreign data source. At the time of migration, the hidden schema field is compared to the current width value in the schema, and the foreign database column size is based on the larger of the two. The width value derived for the extent field when the file was originally added to the schema is based on the field format.
The hidden schema field for the OpenEdge DataServers is set irrespective of the verbose level selected.
Table — Enter the table number at the following prompt: