Size of DB during import but the only the half

[janlars_goedtke]

Hello,

we had this problem several times during the import of several databases while unicode migrations, 'normal' migrations etc.

During the load/import of the database the size increases more and more, sometimes the DB runs full and stands still.

After adding volumes, it takes some time, the loading continues, and than all of the sudden, the database size is back to normal, which can be half the size as some moments before. The new size fits to the size before the export.

We use MAX Db 7.7 (dif. releases) on AIX 6.1 .

It is not reproducebable, we decreased the size of processes, it happens, we increase them, it doesn't happen.

It's not an problem during index creation as they are not created at that moment.

So why does it get so big?

Ideas?

Thanks

Jan

Edited by: Jan Lars Goedtke on Jun 22, 2010 2:03 PM

[markus_doehr2 · Accepted solution]

> We use MAX Db 7.7 (dif. releases) on AIX 6.1 .

> It is not reproducebable, we decreased the size of processes, it happens, we increase them, it doesn't happen.

> It's not an problem during index creation as they are not created at that moment.

We saw the same issue with a test system on MaxDB 7.8. The problem is known and is solved with the newest patches (I'd have to search the exact PTS numbers).

Markus

[janlars_goedtke]

Hi,

we only used loadprocedure fast and later -force_repeat (which led to the same error)...

Jan

[franz_hiltscher]

Hi Jan,

do you use the r3load option -c commit count?

If not the commit will be send on the end of the load. If you dont set an commit count all data will be stored parallel in the historie during the complete load.

Iam not sure but this could be the reason.

Take a look on [Note 1464560|https://websmp130.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1464560]

Kind Regards.

Franz

Edited by: Franz Hiltscher on Jun 22, 2010 2:29 PM