V8.2 SQLite database – columns with FLOAT / DOUBLE data type

Content

We have found an issue with the GA version of IZSAM 8.2 SQLite database. Db2 users are not affected.

When importing Usage records, SQLite incorrectly handles columns defined as FLOAT/DOUBLE.

As a result, Usage counts for products are calculated incorrectly and also displayed incorrectly.

Depending on the status of your setup, follow the steps listed below to fix the data.

1. New V8.2 Repository

a. All outstanding PTFs required for V8.2 MUST be applied since IZSAM V8.2 was GA (dated 2020-12-11). 

    PTF UJ06863/OA62189 dated 2021-10-14 provided a fix for columns with FLOAT / DOUBLE data type.

b. Follow instructions from the manual to customize and create a new repository.

2. TADz V8.1 Repository

If you are still at V8.1 version, and wish to migrate to IZSAM V8.2:

a. Read the migration instructions

b. Apply all outstanding V8.2 PTFs.  PTF UJ06863/OA62189 dated 2021-10-14 provided a fix for columns with FLOAT / DOUBLE data type.

c. Run the migration jobs to bring you to V8.2.

d. Once you have migrated, continue to run operational jobs.

3. IZSAM V8.2 Repository

If you have migrated from V8.1 and have run Usage Import job, HSISUIMP before PTF UJ06863/OA62189 was applied, then data for FLOAT / DOUBLE columns have been imported incorrectly.  To fix the problem, you need to delete all Usage records and re-import again.   

a. To delete all Usage and Aggregator records, use the following SQL statements:

(Replace all &REPZSCHM with your Repository schema name)

    DELETE FROM &REPZSCHM.TUSEMTD ;             

    DELETE FROM &REPZSCHM.PRODUCT_USE;

    DELETE FROM &REPZSCHM.PRODUCT_USE_DETAIL ;

    DELETE FROM &REPZSCHM.TUSEPOV ;

    DELETE FROM &REPZSCHM.TUSEPOVLIB ;

b. Ensure all outstanding V8.2 PTFs have been applied.  

   PTF UJ06863/OA62189 dated 2021-10-14 provided a fix for columns with FLOAT / DOUBLE data type.