Unicode conversion: Number of rows of table clusters changed

[] [] [] [] [] [] [] [] [] []

Related:

  1. Reducing data volume before Unicode ConversionSymptom You want to reduce large data volume in particular...
  2. Efficient Table Splitting for Oracle DatabasesSymptom R3ta calculation of ranges for packages for large Oracle...
  3. Distribution MonitorSymptom You want to use the Distribution Monitor for your...
  4. Unicode Conversion: TroubleshootingSymptom Problems or errors occur during conversion from non-Unicode SAP...
  5. DB2 z/OS: Overview of transports and correctionsSymptom This note contains an overview of all transports and...
  6. Conversion to UnicodeSymptom *********************************************************************** * Conversion from non-Unicode to Unicode / *...
  7. Unicode conversion preparation: Container table T5GEFDATASymptom You have recently done a Unicode conversion of a...

Symptom

You are executing a Unicode conversion. After the Unicode conversion you notice, that the number of rows in table clusters (e.g. CDCLS) has changed.
Other terms

Unicode conversion, table clusters, CDCLS, EDID4, DOKLU
Reason and Prerequisites

In table clusters the mapping between logical and physical records is not one-to-one. A physical cluster item consists of many logical cluster records (belonging to different logical tables). The number of physical table rows needed to store the physical cluster item in the database depends on the number of logical records that belong to the item and their size. During a Unicode conversion the data volume of the logical records changes and therefore the number of physical table rows needed to represent the physical cluster item may change as well.
Solution

For table clusters, changes in number of physical table rows do not indicate a problem during the Unicode conversion.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment