cancel
Showing results for 
Search instead for 
Did you mean: 

BO 4.2 SP3 DSL restart issue

Former Member
0 Kudos

We are running reports based on BW using BICS connection which makes use of DSL services.We have 8 DSL's with 32 GB memory allocated to each.

The issue once the DSL's reaches it's it maximum memory, the DSL service struck in starting sate in CMC and at the same time the corresponding BO service in the operating system(Java.exe) is not able to recycle of its own which in turn consuming almost 100% of CPU.Because of which other services has no CPU allocated and almost most of the reports failed with different generic errors.

Is there any thing to configure in BO/server which takes care of automatic recycling of the DSL service once it reaches it maximum?

Thanks in advance!!!

Accepted Solutions (0)

Answers (3)

Answers (3)

amitrathi239
Active Contributor
0 Kudos

check mentioned SAP note.

1968075 - WebI errors caused by BI Platform processes using an unusually high amount of virtual memory on some Linux platforms

Why you have 2 DSL's on each node?

Former Member
0 Kudos

Hi Dennis,

Version : BO 4.2 SP3 Patch 6

4 processing nodes of 104 GB memory each, in which each node is having 2 DSL's of 32 GB each.

All 24 core CPU's.

When the DSL's reaches it's maximum, the DSL service goes into starting state(PID of that service is removed) in the CMC->Servers but the corresponding service in Windows(java.exe) still holds the old PID which means the service is not recycled at the Windows level which takes the CPU to 100%.

Regards,

Manhoj

denis_konovalov
Active Contributor
0 Kudos

This means DSL service is crashed , that's why its not recycling properly.
So each node has 64gb dedicated to DSL out of 104, what else is running on those nodes ?
Are you sure there is enough left for all other services and you do not have memory contention ?
Why do you require 32gb for DSL - are you sure you're not using Webi as an ETL tool to export data from BW ?

denis_konovalov
Active Contributor
0 Kudos

Would be nice to have a version info as well as memory specs on each node.
Without those it looks to be a sizing and optimization issues in report design and/or on BW side.

However, you can also play with GC/other options of the DSL ASP's . They are Java processes, so you can use standard java tuning strategies.