Dump Reload Level I to II

[JLovegren]

I hate to ask an unsmart question but...
Windows

I did a dump of data and sequences of a v9.1 workgroup database with Level I storage and a load into a v12.8 workgroup database with Level II storage.

I noticed that it appears that all of the data went into my schema area.
I may not know how to read it properly but from a file size standpoint it seems to be that.

The dump was straight forward and so was the load.
To be clear, I had previously created the v12.8 database and was running it in "test environment". I am refreshing the data with backed up data from v9. This is a go live simulation.

Before doing this I did not note the size of schema extent but it is now the size of my whole database which is odd and indicates that I may have missed a step.


I will share my set file and the screenshot of the data folder.


my set file:
____________________________________
#
b E:\AriesBI\Aries.b1 f 819200
b E:\AriesBI\Aries.b2
#
d "Schema Area":6,64;1 D:\AriesDB\Aries.d1
#
a F:\AriesAI\Aries.a1
#
a F:\AriesAI\Aries.a2
#
a F:\AriesAI\Aries.a3
#
d "DataArea":10,128;64 D:\AriesDB\Aries_10.d1 f 1024000
d "DataArea":10,128;64 D:\AriesDB\Aries_10.d2 f 1024000
d "DataArea":10,128;64 D:\AriesDB\Aries_10.d3 f 1024000
d "DataArea":10,128;64 D:\AriesDB\Aries_10.d4 f 1024000
d "DataArea":10,128;64 D:\AriesDB\Aries_10.d5 f 1024000
d "DataArea":10,128;64 D:\AriesDB\Aries_10.d6
#
a F:\AriesAI\Aries.a4
#
a F:\AriesAI\Aries.a5
#
a F:\AriesAI\Aries.a6
#
a F:\AriesAI\Aries.a7
#
a F:\AriesAI\Aries.a8
#
a F:\AriesAI\Aries.a9
#
a F:\AriesAI\Aries.a10
#
d "IndexArea":20,128;64 D:\AriesDB\Aries_20.d1 f 1024000
d "IndexArea":20,128;64 D:\AriesDB\Aries_20.d2 f 1024000
d "IndexArea":20,128;64 D:\AriesDB\Aries_20.d3

______________________________________________________

 

[Rob Fitzpatrick]

I did a dump of data and sequences of a v9.1 workgroup database

I assume you mean a dump of data, sequence values, and schema.

It is the schema that contains the mapping of schema objects (tables, indexes, and LOBs) into storage areas. If you loaded the same schema into your target database that you dumped from your source, then the area assignments would be unchanged. For example, if all objects in your v9 database are in the schema area, then loading that same schema into 12.8, followed by a data load, would put those objects into the new schema area.

What seems to be missing from your process is a change to the mapping of objects to areas. You can do this in a few ways. You can dump the .df and then manually modify the " AREA " line items, save the .df file, and load it into the target; or you can load the .df into a temporary schema holder database, move the objects to the desired locations, and then dump a new .df to be loaded into your target; or you can load the .df into your target database, move the empty objects to their desired areas via proutil -C tablemove/idxmove commands, and then load your data.

 

[TomBascom]

Note: if you are doing “tablemove”… that step should be with a database that has the schema but NO data yet. Technically you can move populated tables but it is EXTREMELY slow and EXCRUTIATINGLY painful for non trivial amounts of data. Like in days or weeks…