Client copy - journaling and asp usage

[Former Member]

I will be doing a client copy from our Production system to one of our

clients in development. Our current ASP usage is at 91%.

Should I stop journaling or should I just delete the files while the

client copy is running to avoid any problems.

Space at 91% percent should be OK, since the client copy is going to

delete the client first and then copy from production.

Or should I delete the client first, which I think is a waste of time

since the client copy is going to do the same.

Should I run a test run first.

Thanks

Joe

[dorothea_stein]

Hi Joe,

if you are short in disk space you might also want to consider using some special iSeries setting to reduce number of SQL packages during client copy.

Background: Normally, we try to distribute SQL statements as evenly as possible across SQL packages, and in many cases, the table name is a good hash criterium. But in case of a client copy, this leads to the problem that after the client copy, for every table in the system being touched by the copy, an SQL package will have been created if it didn't exist yet. - Not optimal in space and runtime.

Using a special iSeries hint, all critical statements will go into very few SQL packages in library R3<sid>Y0000. The how-to is described in SAP note 517589, basically, you need to set dbs/db4/use_hints=1.

If you are really, really short in space, you could in that case even delete older packages of that kind on the fly. The naming mechanism is described in SAP note 481868.

Best regards,

Dorothea

[Former Member]

Hi Joe,

PLEASE stop posting in 2 forums at the same time - that is not a good behaviour ...

You should set the *JRNRCVs for that time on *AUTODELETE ...that

would be the easiest.

turning off doesn't work, because SAP uses COMMIT.

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de -

http://www.easymarketplace.de