ECC 6.0 SR3 Installation very slow

[steven_bier]

Hello,

the Installation of ECC 6.0 SR3 takes 24 Hours. (Step Import Abap)

Normaly the Installation was finsihed in about 7 Hours !

The Server is a:

PRIMERGY TX300 S4

8 CPU´s

32 GB Ram

1200 GB HDD Raid

Operating System:

SLES 10 SP1

Do anybody know the Problem?

Thanks

Steven

[steven_bier]

Hi,

today i install a ECC 6 SR2 on the same server.

Installation time was under 3 hour !!

So the Problem is in the ECC 6 SR3 not on the Server Hardware.

greets

Steven

[hannes_kuehnemund]

Hi Steven,

then this is definately a bug in the SR3 installation (either SAPINST, SAP Kernel [R3load], MaxDB or the export).

In case you don't have to install hundreds of SR3 systems, you may have to wait the day until the installation finishes. In case you have to install several SR3 systems, you either can "downgrade" the installation package of SR3 with the SAP Kernel [R3load] and MaxDB from SR2.

Nevertheless, you should definately open a OSS call at SAP !

Thanks,

Hannes

[steven_bier]

Hi Markus,

the Database does nothing.

SERVERDB: SID

i writen in console by executing x_cons SID sh ac 1

thanks

steven

[steven_bier]

Hi,

i set the parallel Import Jobs to 16 bit no bettering the installation run 25 hours.

Now i change R3load and libdbsl durning Step create Database, i think its working faster.

What is a normal Installation time of a new ECC 6 SR3 ?

Thanks

Steven

[markus_doehr2]

Please check after let´s say 6 hours as user sqd using the command

x_cons <SID> sh ac 1

what the database is doing.

Markus

[steven_bier]

Hi,

@ Markus thanks a lot for the hint but the note 1267841 is not available on sap

@ Hannes thanks i test it now

greets

Steven

[markus_doehr2]

> @ Markus thanks a lot for the hint but the note 1267841 is not available on sap

Yes - it has been withdrawn - but the patch helped us

Markus

[steven_bier]

Hi,

64bit

Maxdb

greets

Steven

[hannes_kuehnemund]

Hi Steven,

just set parallel jobs to 16 (double amount of CPU's) and then it should be as fast as before. Having only 3 parallel jobs is just not enough to utilize the machine to a reasonable level. Maybe a bug in SAPINST ...

Please post the result when setting it to 16.

Thanks,

Hannes

[markus_doehr2]

The problem can also be the "create index serial" thing. SAPINST for MaxDB creates first all tables, loads all the data an later creates all the indexes sequentially. There was a problem in the corresponding libdbsdb.so (see note 1267841).

Install the latest R3load + libsdbsl during the time the database is created, it may run a lot faster after that.

Markus

[steven_bier]

Hello,

thanks for the fast answer,

parallel job is set to 3,

No warings in the Database log.

dmesg and Messages OK !

iostat / vmstat / sar OK !

Now I start a new installation and increase the paralel imports to 8.

I would post the outcome

greets

Steven

[markus_doehr2]

Is this Oracle? Is this 64bit?

Markus

[hannes_kuehnemund]

Hi Steven,

how many parallel imports do you have configured. Normally the it is either the number of CPUs +1 or *2, which means 9 or 16 in your case (having 8 CPUs). Maybe the SAPINST set it to 1, which would only utilize 1 CPU? If it is set to 9 or 16, please check database during import (x_cons for MaxDB for example) to see if there are any warnings or curious things happening. Also, check OS with iostat/vmstat/sar during import, maybe there is an I/O bottleneck (high %wait times). Also check dmesg and /var/log/messages

Thanks,

Hannes