Excludable History Type tables from PD to PY Environment Copy (this time is urgent)

[Zoltan_Gyimesi]

Hi JDEList Community,

Prolog:
First of all excuse me, that I will post this onto the Application, CNC / Tech and Developers Forum
Currently I am totally out of CNC Tech and Application Consultant help and this time this issue is really URGENT & IMPORTANT.
Thanks in advance your appretiations & Please respect, I am just a developer.

Platform:
XE SP2, Oracle Database, Windows Enterprise Server with not a robust one resources

In the affected scenario I narrowed my suspection to 13 standard tables, based on description and/or record count. I will attach them to my post in an MS Excel file. Please, check it.
I suppose, these tables stores Change History entries, which not required in PY environment after an Environment Copy from PD.

The last PD to PY Environment Copy copied these tables and the duration time of the action almost exceeded the 20 hours.

Now we do not have so large time-frame and I would like dramatically decrease the duration time.

I am in doubt, because I am not sure which table exclusion will not cause SURELY any issue, problem in PY, and which can cause.

Please, let me know, which tables of these can I SURELY exclude from PD to PY Environment Copy?

As I mentioned, it is urgent and I need this info on this Saturday optimaly before 10:00 AM (UTC!), but hopefully (not sure) won’t be late up to 04:00 PM (UTC!)

Finally, I would like to mention, that the rquired Table Space also an issue as well.

Please, ask me, if I wasn’t clear enough.

Great Thanks in Advance & Regards,

Zoltán
…just a developer

 

[Zoltan_Gyimesi]

Re: Excludable History Type tables from PD to PY Environment Copy (this time is urgent)

Hi again,

I try to rephrase my issue:

What will be the conseqence, if I won’t copy these tables – by tables.

Regards,

Zoltán

 

[aidy]

Re: Excludable History Type tables from PD to PY Environment Copy (this time is urgent)

Zoltan

I am not aware of all of the tables that you attached, however F42019, F42119, F42199 I required in PY when we were testing aggressive purging. We wanted to ensure that if we purged relatively recent sales data, that a user could still see these in applications, and reports. (Some of which needed to be modded to include extra table joins, or report sections etc)

So I guess what I'm trying to say is, it depends on whether the testing in PY needs to see sales history or not.

My guess is that you could exclude F42019 and F42119, but include F42199.

Hope that helps a little!