cancel
Showing results for 
Search instead for 
Did you mean: 

Performance issue after applying patch 19

Former Member
0 Kudos

Hello,

We recently applied Patch 19 (SAP BW 70) to our BI systems.

Since then, we are experiencing severe performance problems, in load time, DSO activation and query execution. After testing queries in RSRT, we realized the problem is limited to the back end (Variable exit takes long time). For some reason, the problem is in Prod and QA but not in DEV, although we applied the patches to all 3 systems.

Anyone experienced that issue?

Thanks,

JLT

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hello,

We saw similar table scan on the /BIC/Q* tables (and some other ones) after we recently upgraded our backend and ended up tracing the processes and then adding indexes to the tables being scanned.

The note mentioned doesn't apply to us because we're going to SP20 which the note is in.

One thing we found was that the Global setting for Parallism in DSO activation was set to 1 (serial). Even though, individual DSOs had a different setting, it used the global setting and everything ran badly. We switched the global setting back to 3 for parallelism and are seeing normal performance.

We also tried switching the parallel processes on the DSO Activation to use Dialog processes instead of Background processes and saw a 3X performance improvement in DSO Activation.

We're still playing around in RSBATCH and our Operation Mode settings to determine the optimal configuration.

More investigation is required.

Peace,

Dan Glick

Former Member
0 Kudos

Dear,

We've recently faced the same issue, and it seems it had something to do with our patch level of Oracle (cfr. note 981875).

Or did you find another solution for this problem?

Thanks!

Best regards.

Former Member
0 Kudos

Hi,

We recently applied SAP_ABA 18, SAP_BASIS 18 and SAP_BW 20 and are experiencing similar issues primarily with a much longer DSO Activation time. However, when we activate the DSO manually it runs without delay. It's only when run in a process chain that we see the greatly increased runtime.

We'll be cutting a customer message with SAP.

Thanks,

Dan Glick

Former Member
0 Kudos

No. We applied SAP_BW 019, SAP_BASIS 017, SAP_ABAP 017 and Java Stack SP17.

JLT

Former Member
0 Kudos

We are also getting several locking issues for process chain runs after this support pack.

SAP_BASIS 700 0017 SAPKB70017

SAP_BW 700 0019 SAPKW70019

We changed number of parallel processes to one for most of the DTPs, as some data packet loads are waiting forever for a free process. Some times the the table RSMONMESS is locked for a long time. Getting SID missing/inconsistencies some times (RSRV checks). NRIV locks while loading (Seems some problem with Number range buffering of DIMIDs and SIDs)

Also the Master data reorganization didnt work after this SP. After we applied advanced correction SAP note 1234411 it worked for some of the Master data objects. But it is taking too long (2 days +) for Master data reorg for 11 Million records Master data object (It is stuck at big SQL statement for 2 days, full table scan on /BIC/Q* ). Is there any know issue or a SAP note for this?

Former Member
0 Kudos

Do you mean you applied service-pack 19, without the ABA and BASIS packs that go with this? The service-stack is due in june I believe.