Solved: Speed up SDM deployment?

Former Member · ‎03-14-2007

Hi,

We're currently investigating methods for optimizing the SDM deployment, so that it takes shorter time and wondered if anyone have discovered some methods.

We've got an EP Nw04s SP09 system which we want to patch to the newest patch level (still on SP09) for these components:

*EPSERV

*EPBC

*EPBC2

*SAPJEE

*SAPJEECORE

*SAPJTECHS

*SAPJTECHF

In total about 290 MB.

On my dev workplace installation with MaxDB the actual SDM deployment took about 110 minutes, but on our sandbox system on HP-UX with Oracle it took 440 minutes. Because of this we have problems fitting the patching in outside our major upgrade windows.

What could be the bottleneck and explain the difference ?

*Database access?

*Files under SDM\root?

*HP-UX JVM parameters (I've seen note 796560)

Is there anything we can do to speed up the deployment, for example:

Move a database table into memory
Delete files on the files system (for example under SDM\root)
Update JVM parameters
Press F12 five times while sitting on the desk

Anyone with some positive experiences?

Regards

Dagfinn

Former Member · ‎03-16-2007

check the cpu usage and the io

(you can see this information in the task manager)

if it is a ORACLE than you would see high io in the DB process,

you may create an oracle trace with the standard gui tools of ORACLE

(you don't necceserly have to use TOAD)

if it is j2ee error you would see high io/cpu in the j2ee process.

Former Member · ‎01-24-2008

No real solution, but can live with it and test again for newer support packages.

Former Member · ‎03-27-2007

On HP-UX there is an issue with the JIT which was causing some stability issues with SDM. As such, the JIT compiler has been disabled for the SDM process. Please see SAP note 991283.

Disabling the JIT compiler for SDM on HP-UX was hard-coded in the JLaunch program. The HP Java VM does not provide a means to "undo" the effects of the critical "-Djava.compiler=NONE" parameter.

That code sequence has been removed in SPS10.

That change is incorporated in the database-independent part of SPS10, a downport/patch is not possible.

You can, however, install the Kernel binaries from SP10 SAPEXE.SAR without upgrading the Java part of the system.

Cheers, Ventsi

Former Member · ‎03-15-2007

everying can be the bottleneck:

*Database access

*Files under SDM\root

*HP-UX JVM parameters (I've seen note 796560)

my guess is the database access.

in order to check every one of them do the following:

DB - create a db trace via SAP or via the DB,

to do a sql trace via SAP, enter to the server of the j2ee, under: http://<server>:50000, and create a "SQL Trace" in the MaxDB and

do the same thing in the ORACLE.

(alternately you can do an sql trace via the DB, in order to do this use each DB tools)

You probebly would find a statment that takes a lot of time,

and creating an index/updating the statistics would solve the problem.

to check files under SDM\root you can use perfmon and monitor the disk response time or just go to http://www.microsoft.com/technet/sysinternals/default.mspx and download "file and disk utilities" (however, filesystem is not likely the problem)

if the jvm parameters are set incorrectly,

you might see high cpu usage while deploying at the HP.

Speed up SDM deployment?

Accepted Solutions (1)

Accepted Solutions (1)

Answers (3)

Answers (3)

Lumira document dependency

Where did XVBPA get populated in program MV45AFZZ

Re: Getting error while configuring SAP system in ...

sapui5 planning calendar special dates but interva...

Re: BusinessObjects 4.2 SP9 to 4.3 latest version