cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

BPC web login taking time

Former Member
0 Likes
530

Hi experts,

BPC login is taking too much time to take to ADMIN page. Please tell me what can be issue cause and how to correct it. Compatibiltiy Settings are fine.

I am working on BPC 10.1 NW

Regards

Praveen

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Likes

The issue is solved now.

Thanks to Gersh and andy, SM50 analysis helped me to move ahead. The original problem with this issue is UI5 interface. frequently the cache memory of this UI5 application, gets deleted and during login it gets struck at checking all the entires in O2PAGCON table. To overcome this schedule report /UI5/UPDATE_CACHEBUSTER in SM36.

SAP Note: 1942086 solved this issue.

Summary of this note from SAP is as below

As understood you observe a performance problem from time to time and not with a repeated startup of the application. The problem is reproducable when you start the report /UI5/RESET_CACHEBUSTER.
Is this correct?
Then I want you to point to the SAP note:
1942086 - SAPUI5 Cache Buster for Applications - Update via scheduled Report
Please use transaction sm36 schedule the report /UI5/UPDATE_CACHEBUSTER as described there.
This might solve the problem.


Regards

Praveen

Answers (1)

Answers (1)

Former Member
0 Likes

Hi Praveen,

is the issue only for you or other users as well?

you can try clean the cache on your internet browser.

you don't need to add in compatibility settings for BPC 10.1

Andy

Former Member
0 Likes

Hi Andy This issue is for all users. Tried in different systems using different login ids. This problem is in production system only, while the development works fine.

Regards

Praveen

Former Member
0 Likes

Hi Praveen,

compare the SMICM settings between all 3 landscapes, test RFC connections in SM59.

ask your basis to have a look with the connection settings.

Andy

Former Member
0 Likes

Hi Praveen,

This type of analysis is better to start form running a Fiddler trace so see where most of the time is taken. If you find out that it's on App server, then run ST12 to see what program is taken the longest.

If you can see that in SM50 some program name is not changing for a long time then it can be the program to analyze.

Regards,

Gersh

Former Member
0 Likes

Hi andy and Gresh,

My observations, are Once i login it is generating some background jobs, i can see that in SM50. Also if i terminate this background job, login is happening quickly.

SAP Observed that, Some table name O2PAGCON (INDX File for Oxygen Pages) is taking longer time, but have got no solution yet.

Any suggestion on how to bypass this background activities?

Regards

Praveen

Former Member
0 Likes

Hi Praveen,

You need to speak to your DB consultant, maybe fine tune the index cache settings of your DB?

Andy