After a binary load a table doubled in size both tabanalys and the extent size

After a binary load a table doubled in size
Both tabanalys metrics and the extent size are doubled compared to the original database.
The table has undergone schema additions of fields over time.

 

Database analysis prior to dump shows min record size much smaller than database analysis after loading table into new database.
Database analysis prior to dump shows max record size much smaller than database analysis after loading table into new database.
Database analysis prior to dump shows mean record size much smaller than database analysis after loading table into new database.

This is expected behavior.

Not all records had been updated since schema modifications were made in the original database.

Existing records of a table that have new fields added, may not allocate new space for the records until the records are next updated when the new fields meet the criteria for Fast Schema Update.

When the table is loaded into a new database all fields are instantiated for each record, which can radically change the amount of space that is need for the records compared to what was needed for the records that previously did not have all fields instantiated.

The increased size of the table is a result of the current table schema definition which is instantiated in its entirety for each record that is loaded into the new database.

For further clarification refer to Article  How does Fast Schema Update work?