CU&UC DURATION in Productionu00BF?

[Former Member]

Hello!:

We are doing a CU&UC (we are doing the first cicle, but we want to see the aprox duration in our Productive System).

The steps are the next:

- homogeneous copy to an additional system (8hours).

- upgrade the additional system from 46C to 620 (40 hours).

- do the additional system steps preparation (8 hours).

- in the source system 46C MDMP:

... Preparation (4 hours)

... Prepare Upgrade (8 hours)

... Prepare Unicode (all the SCANsss)

We have two CPU's in our Productive Server (Server that has the DB Server)....so we can only launch 2 jobs simultaneously.

May be 2-3 days¿?¿?

can give problems of performance in the system???

... With Download:

Upgrade (40 hours¿?)

Unicode Conversion (export import) (DB with 600GB 24horus¿?¿?)

Completion Unicode Phase (8 hours¿?)

What do you think about these hours¿? From Friday 15h to Monday 15h it's possible to do all the steps neccesary with download¿?

Thanks and regards.

Alfredo.

[Former Member · Accepted solution]

Hi,

I guess all these times that you have mentioned are basically based on the times you have taken from DEV and TEST systems. Then the time should be good enough to move ahead.

If you are doing these activities for the first time and that too on production server then i wont recommend you to go ahead as you should do a proper rehearsal before starting any activity on Production.

Regards,

Suhas

[Former Member · Accepted solution]

Yes, i know it, but i would like other references....

[Former Member · Accepted solution]

Hi,

Buddy its very difficult to judge the timings, but any ways i am going to share the timings and the DB size i had come across during upgrade and export/import.

For an upgrade of around 1TB i required around 2 full days including testing and all.

For an export import of arounf 1TB of data i required around 24 hrs for export and 15-16 hours for import. Testing another 3-4 hrs.

This is max what i can share with you.

Also i important thing , just check with SAP if they recommend performing an unicode conversion immediately after an upgrade.

Regards,

Suhas

[Former Member · Accepted solution]

Yes, it's mandatory for us do the CU&UC (Upgrade+Unicode)

Alfredo.

[Former Member · Accepted solution]

BD 610GB

Export normal 45hours.

Export with split 32 hours.

with 3 R3load and 2CPU's 100%

Do you think normal?

Thanks.

[Former Member · Accepted solution]

Hi,

I guess you can still get better results by splitting the files properly.....If using only split you take around 32 hrs then its more... as i had taken only 24 hrs for export for data arnd 1 TB. This is what you can do...

First you need to find out what is the size for each in terms of GB.

Then take top 50 tables with high db size.

Sort it as descending order.

Check in which cmd or tsk file the particular table exists.

Once you do that, assign that file as AA<filename>

in similar manner the next file and the next and the next.But with this combi you will last till AZ<filename>. So now you can start with BA<filename> and so on. This will help you to to load the table with maximum data first.

This will help you, because if say for example a table exists with name as ZABCDEFG. This table as per naming convention will load last as its name starts with Z and will take maximum time. So basically you will have to assign AA in front of the filename so that it loads first.

This is a tideous process, so you will have to pay utmost attention. I hope you unterstood what i am trying to say. )

Regards,

Suhas

[Former Member · Accepted solution]

Suhas,

the export with split (32 hours) is very less that export without split (45 hours), and i've seen that the 2CPU's are 100% during 30 hours and only are 70% during the other two hours.......

So it's difficult to take less time in the export¿?

Regards,

Alfredo.

[Former Member · Accepted solution]

Hi,

Well if you have figured out the best possible combination than it is good enough. I was suggesting if you could arrange the priority of the tables being loaded. Anyways looks you are also not having enuf CPU as it is 100% for the first 30 hrs.

Also just check if you have removed data from APQD table and all the log tables. Because this data is of no use and not necessary to migrate.

Please check the migration guide for these details.

Regards,

Suhas

[Former Member · Accepted solution]

Th problem is that tables like MSEG and BSIS has 80GB...........

[Former Member · Accepted solution]

Hi,

These tables are normally of this size only....so no need to worry.... Only make sure you have enough space in PSAPTEMP and also thet these tables are exported first.

regards,

Suhas

[Former Member · Accepted solution]

Perfect, but i think that i need more CPU...

[Former Member · Accepted solution]

hi,

Well yes i also think you need more CPU....but have you checked with more no of R3load processes ??? If not check with that also... Coz work will be properly distributed...and would also reduce some more time...

Regards,

Suhas

[Former Member · Accepted solution]

I've think to do the export in one server and in the same moment the import in other server, but we need two servers.

Otherwise, in the export you select the number of R3load, but there is not options to select more than one server¿?

Thanks

[Former Member · Accepted solution]

Hi,

Just check whether you can add more CPU and then increase the R3load processes.

Regards,

Suhas

[Former Member · Accepted solution]

I want to do it.....but before do it i have to see how many CPU's i need

[Former Member · Accepted solution]

With SPLIT, Load Fast Procedure and DB with statistics, in a 610GB of DB: EXPORT 35h, and IMPORT 30h.

It's a lo of time, the server has 2CPU's (3-4 R3load in the same moment), so we are looking for other server......

So, if we add the time of the downtime of the upgrade and the time of the downtime of the export/import, the total downtime is more than 5 days in this server.

Can you say your times in the CU&UC????? (please the info of the machine, the DB GB).

Thanks and regards,

Alfredo.