Currently if we restore a database backup that was taken on a higher edition of Db2 into Developer-C, it fails with SQL1139N, even if it is fully less than 100GB. There are two workarounds for this:
DB2 should just force the max settings on restore without a user having to go in and change them.
Why is it useful?
|Who would benefit from this IDEA?||Anyone who wants to build a sandbox or development environment based on another environment.|
How should it work?
On restore, Db2 should set a max size for each table space of 100 GB. If any table space exceeds this, then the restore should fail. Alternately, a utility should be available to run against the backup to set the max size for each table space in the backup image.
I understand that IBM needs to enforce their licensing requirements, but making it harder to use the entry level edition is not the best way to do it.
|Priority Justification||It is strange that this does not work already. I understand that IBM needs to enforce their licensing requirements, but making it harder to use the entry level edition is not the best way to do it.|