Rdisp/gui_auto_logout

I've had enough complaints that I beginning to think there is something wrong. I have the value of this parameter set to 14400.....SOX mandate. Users complainting they are well within the time value, but SAP is ending their sessions. SAPNET search shows nothing. Anyone else having this type problem?

Hi Jerry,
As Rich has pointed out, it should work as defined. We have exactly same setting for exactly same reason, and it has been working fine since 4.6C.
The only thing I can guess is that it is not correctly configured on all instances. Use Tcode RZ11 to reset this parameter dynamically and globally?
Good luck,
Victor Lin

Similar Messages

Rdisp/gui_auto_logout does not consider uploading

hi experts,
I set the rdisp/gui_auto_logout to 10 mins for testing. My problem is that it got me disconnected while in the middle of uploading. It seems it counts uploading as idle. Is there any way to drop idle sessions but not those in the middle of uploading data?
Thank you in advance!

Hi Karshbax,
Please go through the link. Here it says this parameter works upon idle time.
http://help.sap.com/saphelp_nw04/helpdata/en/22/41c43ac23cef2fe10000000a114084/content.htm
It says:
rdisp/gui_auto_logout:
Defines the maximum idle time for a user in seconds (applies only for SAP GUI connections).
Default value: 0 (no restriction); permissible values: any numerical value
Hope it clarifies. Let us know if it is helpful.
Regards,
Sujit.

Setting Profile parameter rdisp/gui_auto_logout value

Hi All,
The present value for the profile parameter value rdisp/gui_auto_logout is 1200 sec, now i would like to change the value from 1200 sec to 2400 sec.
can change the value directly in parameter value field (using T-code RZ10) or can i create a new parameter value?
Please any one give me the suggestions how to reset the value for this profile parameter
Regards,
Reddy V,

Hello reddy,
This rdisp/gui_auto_logout parameter can be changed dynamically too you can change the value via RZ11 if you dont want to restart your server now. but in this case whenever you will restart your server the parameter value will be set back to the original state
change it via RZ10 but in this case you have to start the server to activate this value
Select Change in instance profile via RZ10 and select extended maintainance then click on create parameter and enter the parameter name there and press enter, it will show you the current value then insert the new value and save and activate the profile.
Regards
Subhash

Configure rdisp/gui_auto_logout message

Hi,
Anybody knows if it is possible to configure the message that the system shows when it logs out a user due to long inactivity time (set with the parameter rdisp/gui_auto_logout )?
Thanks,
Best Regards,
Nahum.

Hi Karshbax,
Please go through the link. Here it says this parameter works upon idle time.
http://help.sap.com/saphelp_nw04/helpdata/en/22/41c43ac23cef2fe10000000a114084/content.htm
It says:
rdisp/gui_auto_logout:
Defines the maximum idle time for a user in seconds (applies only for SAP GUI connections).
Default value: 0 (no restriction); permissible values: any numerical value
Hope it clarifies. Let us know if it is helpful.
Regards,
Sujit.

SAP rdisp/gui_auto_logout

Hi All,
I would like to know about SAP gui auto logout time for example x amount of time. We have max gui session are 6 as default. If some user opens 6 sessions and works in 2 only and other 4 are idle. Does it terminate 4 those are idle after the x amount of time?.
It does not heppens in 4.7. Could you confirm that is possible in ECC5 or ECC6.
Thanks,
Harish

Hi,
Auto logout session is not session dependent, that is user id dependent.
That will not terminate all sessions if user is working with other session, means user is in active mode with one of the session.
Regards
Nick Loy

Disp/gui_auto_logout

Because our users number is very larger, the loading of primary machine(Instance: PRD) is very hight. So we install a DIA machine(Instance D01). and set rdisp/gui_auto_logout value to 1800 in the profile for each instance. Restart the machines, atfer logon to system from D01 and PRD 30 minutes, D01 gui can auto logout, but PRD gui can not logout . Our local conslutant reguest me add rdisp/gui_auto_logout parameter in the default profile and remove the parameter from PRD and D01 instance profiles. I do it follow the sugguestion, and restart the services, but the result is same: D01 gui can auto logout, PRD gui can not auto logout after logon 30 minutes. Why , what error I do? please help.
Thanks for your help

And also check the below mention parameter values also if this parameter values are grater then your value then you setting is not valid. and also check the profile has been activated.
rdisp/keepalive
rdisp/keepalive_timeout
rdisp/keepalive_old

SAP GUI710 Logon issue

Hi , all
Now , i am using SAP GUI710 , Patch level 3, i have an issue , if i leave the sec untouched for about 5 minutes , GUI will log off itself , and give me this information:
CD1: connection to partner " ..........: sapdp00" broken
WSAECONNRESET: connection reset by peer
though i can logon again , but this really boring me , every 5 minute , if no activity , then auto logoff and i need to logon again.
what is the problem , how to fix this ? thanks.

Hello,
If this happens for all the users , pl check the SAP instance parameter value rdisp/gui_auto_logout.
If it is 0 there wont be any auto log out.
set the value in seconds means if you set it at 300 it will log out automaticaly after 5 secs.
Pl try this . Dont forget to restart the server after making the changes.
Award if resolved.
Regards

Portal Session Timeout - ICM/Webdynpro/POWL

Hi Experts,
We are having SRM Portal which has POWL Webdynpro and other applications running.
SRM Portal is a seperate JAVA Instance and integrated to backend with SSO enabled.
We have Logon Ticket Timeout set as default 8 Hours and the Session Timeout in Portal set as 2 Hours (Server>services>webcontainer>properties>Session Timeout).
For the ABAP backend, we have rdisp/plugin_auto_logout-->7200 (2 Hours) and ICM timeout as remommeded by SAP as icm/server_port_0 = PROT=HTTP,PORT=8012,TIMEOUT=90,PROCTIMEOUT=600
Now the problem is:
1. Users connected to portal and work on any POWL Iviews has an idle time of two hours-->we get the ICM session timeout error page.
2. Sometimes Users get the Login screen of portal within the Navigation Frame which can be identified as the Ticket Expiration
Is there a possibility to control the behavior of portal to avoid these error pages to Users like if the timeout happened in backend, there should be auto refresh if the user clicks the application.
And if the ticket expired, the portal should refresh to the home screen on clicking any Iview.
We tried the IDLE timeout pop up and in Vain, you could see my another post on the same.
Portal Idle Pop Up
Regards,
Sethu

Hi,
Read SAP note 705013,
I think adjusting the kernel parameters, rdisp/gui_auto_logout and rdisp/plugin_auto_logout will help.
Try adding below parameters in the Instance profile.
icm/keep_alive_timeout 3600
icm/conn_timeout 5000
Regards,
Venkata S Pagolu

Performance issue in ECC 6.0

HI Experts,
The client has upgraded to ECC 6.0 from 4.6c, everything works fine but the only problem is that the users complain that the server is slow. The client has done a memory upgrade from 8Gb to 16 Gb but the problem still pertains. The server is Up and running and there is no problem at all.
The ECC runs on this WIN NT server and the DB2 database is connected to it through the IBM server. They use DB2connect
They dont have any application servers.
After the upgrade their system performance declined,
Users are complaining that the response time of the system is very slow. Also while executing some transaction codes like GD13, the system just throws the user out after a while.
they have to execute the transaction in steps.The ST02 shows a lot of swaps in the program buffer and the EXport/ IMport buffer. Also in ST02,SAP memory section
we can see that the Max Use is 2 times that of the In Memory for the Page Area.
In ST03N, the DB time for the background work process type is much greater than the processing time.
Please let me know if i have missed out any details.
I am attaching the parameters here below for further information. Please let me know what are the parameters that have to be modified for solving this error. I am not a pro in performance tuning and that is the reason seeking help from the GURU's
Thank you in advance and please let me know if more details are required
SACHIN
03/06/2008                         Active parameters                        08:25:57
Parameter Name
Parameter value
|SAPDBHOST                                  sapgbeth
|j2ee/dbtype                                db2
|j2ee/dbname                                DB2P
|j2ee/dbhost                                SAPPRD
|SAPSYSTEMNAME                              PRD
|SAPGLOBALHOST                              sapap4
|rdisp/bufrefmode                           sendoff,exeauto
|rdisp/mshost                               sapap4
|rdisp/msserv                               sapmsPRD
|rdisp/msserv_internal                      3900
|j2ee/scs/host                              sapap4
|j2ee/scs/system                            31
|j2ee/ms/port                               3931
|SAPTRANSHOST                               sapap2
|login/system_client                        300
Instance parameters
                   Active parameters                        08:33:11
Parameter Name
Parameter value
|icm/server_port_1                          |PROT=SMTP,PORT=25
|zcsa/table_buffer_area                     |120000000
|rsau/selection_slots                       |5
|rsau/enable                                |1
|zcsa/presentation_buffer_area              |44000000
|rdisp/gui_auto_logout                      |7200
|rdisp/noptime                              |14400
|rdisp/wp_auto_restart                      |14400
|rsdb/ntab/entrycount                       |70000
|rsdb/esm/buffersize_kb                     |4096
|rsdb/esm/max_objects                       |2000
|rsdb/ntab/ftabsize                         |62500
|rsdb/ntab/irbdsize                         |30000
|rsdb/ntab/sntabsize                        |2500
|rsdb/obj/buffersize                        |32000
|rsdb/obj/max_objects                       |20000
|rsdb/otr/buffersize_kb                     |4096
|rtbb/buffer_length                         |30000
|rtbb/max_tables                            |500
|sap/bufdir_entries                         |4500
|zcsa/db_max_buftab                         |25000
|abap/buffersize                            |850000
|SAPSYSTEMNAME                              |PRD
|SAPGLOBALHOST                              |sapap4
|SAPSYSTEM                                  |00
|INSTANCE_NAME                              |DVEBMGS00
|DIR_CT_RUN                                 |$(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
|rsdb/cua/buffersize                        |12500
|DIR_EXECUTABLE                             |$(DIR_INSTANCE)\exe
|jstartup/trimming_properties               |off
|jstartup/protocol                          |on
|jstartup/vm/home                           |C:\j2sdk1.4.2_14-x64\
|login/fails_to_user_lock                   |4
|login/password_expiration_time             |30
|jstartup/max_caches                        |500
|jstartup/release                           |700
|jstartup/instance_properties               |$(jstartup/j2ee_properties);$(jstartup/sdm_properties)
|j2ee/dbdriver                              |C:/Program Files/IBM/SQLLIB/\java\/db2jcc.jar;C:/Program Files/IBM/SQLLIB/\java\/db2jcc_license_cisuz.jar
|rdisp/wp_no_dia                            |12
|rdisp/wp_no_btc                            |8
|rdisp/j2ee_start_control                   |1
|rdisp/j2ee_start                           |1
|rdisp/j2ee_libpath                         |$(DIR_EXECUTABLE)
|exe/j2ee                                   |$(DIR_EXECUTABLE)\jcontrol$(FT_EXE)
|rdisp/j2ee_timeout                         |600
|rdisp/frfc_fallback                        |on
|icm/HTTP/j2ee_0                            |PREFIX=/,HOST=localhost,CONN=0-500,PORT=5$$00
|icm/server_port_0                          |PROT=HTTP,PORT=80$$
|ms/server_port_0                           |PROT=HTTP,PORT=81$$
|rdisp/wp_no_enq                            |1
|rdisp/wp_no_vb                             |8
|rdisp/wp_no_vb2                            |1
|login/min_password_lng                     |4
|rdisp/wp_no_spo                            |2
|dbms/type                                  |db2
|dbs/db2/schema                             |SAPR3
|dbs/db2/use_drda                           |1
|dbs/db2/ssid                               |DB2P
|dbs/db2/hosttcp                            |sapprd
dbs/db2/user
PRDADM
|rsdb/max_blocking_factor                   |10
|rsdb/max_in_blocking_factor                |10
|rsdb/min_blocking_factor                   |3
|rsdb/min_in_blocking_factor                |3
|rsdb/prefer_fix_blocking                   |0
|rsdb/prefer_union_all                      |1
|rsdb/prefer_in_itab_opt                    |1
|j2ee/instance_id                           |ID0058933
                         Active parameters                        08:34:47
Parameter Name
Parameter value
SAPSYSTEMNAME
PRD
|SAPGLOBALHOST                              |sapap4
|SAPSYSTEM                                  |00
|INSTANCE_NAME                              |DVEBMGS00
|DIR_CT_RUN                                 |$(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
|DIR_EXECUTABLE                             |$(DIR_INSTANCE)\exe
|DIR_PROFILE                                |$(DIR_INSTALL)\profile
|_PF                                        |$(DIR_PROFILE)\PRD_DVEBMGS00_sapap4
|Start_Program_00                           |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF)
|_MS                                        |$(DIR_EXECUTABLE)\msg_server$(FT_EXE)
|Start_Program_01                           |local $(_MS) pf=$(_PF)
|_DW                                        |$(DIR_EXECUTABLE)\disp+work$(FT_EXE)
|Start_Program_02                           |local $(_DW) pf=$(_PF)
|_IG                                        |$(DIR_EXECUTABLE)\igswd$(FT_EXE)
|Start_Program_03                           |local $(_IG) -mode=profile pf=$(_PF)
|dbms/type                                  |db2
|dbs/db2/schema                             |SAPR3
|dbs/db2/use_drda                           |1
|dbs/db2/ssid                               |DB2P
|dbs/db2/hosttcp                            |sapprd
|dbs/db2/user                               |PRDADM
|rsdb/max_blocking_factor                   |10
|rsdb/max_in_blocking_factor                |10
|rsdb/min_blocking_factor                   |3
|rsdb/min_in_blocking_factor                |3
|rsdb/prefer_fix_blocking                   |0
|rsdb/prefer_union_all                      |1
|rsdb/prefer_in_itab_opt                    |1
ST02 details
System:                  sapap4_PRD_00             Tune summary
Date + Time of Snapshot: 03/06/2008    09:12:54    Startup:     02/28/2008 17:00:25
Buffer
HitRatio %
Alloc. KB
Freesp. KB
% Free Sp.
Dir. Size
FreeDirEnt
% Free Dir
Swaps
DB Accs
Nametab (NTAB)
0
Table definition
99.81
17,230
8,898
66.41
70,000
46,486
66.41
0
35,319
Field definition
99.82
67,969
1,093
1.75
70,000
50,465
72.09
3,122
23,024
Short NTAB
99.81
4,688
1,494
59.76
17,500
14,009
80.05
0
3,491
Initial records
77.19
32,188
25,367
84.56
17,500
204
1.17
0
17,333
0
program
99.86
850,000
2,503
0.31
212,500
187,621
88.29
16,688
133,368
CUA
99.89
12,500
1,687
15.43
6,250
4,841
77.46
0
1,440
Screen
99.92
42,969
4,178
9.78
4,500
2,539
56.42
0
2,025
Calendar
100.00
488
407
85.32
200
111
55.50
0
89
OTR
100.00
4,096
3,594
100.00
2,000
2,000
100.00
0
0
Tables
0
Generic Key
99.96
117,188
10,484
9.40
25,000
963
3.85
19
91,258
Single record
99.43
30,000
19,703
66.00
500
307
61.40
0
100,286
0
Export/import
87.05
32,000
345
1.28
20,000
7,881
39.41
20,674
Exp./ Imp. SHM
96.21
4,096
3,487
97.02
2,000
1,999
99.95
0
SAP Memory
Curr.Use %
CurUse[KB]
MaxUse[KB]
In Mem[KB]
OnDisk[KB]
SAPCurCach
HitRatio %
Roll area
6.99
18,328
24,152
262,144
0
IDs
88.76
Page area
11.15
29,222
262,136
131,072
131,072
Statement
86.00
Extended memory
13.28
2,228,224
4,182,016
16,773,120
0
0.00
Heap memory
0
0
1,953,199
0
0.00
Call Stati
HitRatio %
ABAP/4 Req
ABAP Fails
DBTotCalls
AvTime[ms]
DBRowsAff.
Select single
99.59
43,894,293
12,780,161
318,640
0
31,114,132
Select
91.37
83,904,537
0
1,381,069
0
10,468,946
Insert
0.00
27,752
11,469
28,873
0
48,575
Update
0.00
102,654
5,118
104,414
0
97,141
Delete
0.00
50,367
44,486
52,487
0
45,787
Total
95.48
127,979,603
12,841,234
1,885,483
0
41,774,581

Hi,
How is the database server operating system coping in terms of CPU load and memory? and what is the db data cache hit ratio in ST04?
I would look into the following things, network configuration between database and central instance, and the load on the DB server cpu load/memory and possibly the most important the DB2 memory and configuration instead of focusing on the SAP application server in case of high DB times.
Please be aware of the fact that tables in upgrade from 4.6C to ECC increase from about 30000 to 60-70000 and db tuning is the most likely explanation for your problems.
Regards
Sindri

SAP ECC 6.0 System Performance

Gentlemen,
Please advise me with the following scenario, which is Iu2019m facing a problem with system performance,
My system configuration is:      SAP ECC 6.0
Database System:          Oracle 10.2.0.2.0.
Server Configuration:     Power 6
Processor Type: PowerPC_POWER6
Processor Implementation Mode: POWER 6
Processor Version: PV_6_Compat
Number Of Processors: 6
Processor Clock Speed: 3503 MHz
CPU Type: 64-bit
Kernel Type: 64-bit
LPAR Info: 2 PRODUCTION
Memory Size: 47104 MB
Good Memory Size: 47104 MB
Platform Firmware level: EL340_039
Firmware Version: IBM,EL340_039
The following Information was generated from TCode: sm51:
SAP Release Information
Application Server SAPPRD_PRD_00
SAP Kernel Information
SAP Kernel : 700_REL
Database Client Library : OCI_101
created in : AIX 2 5 005DD9CD4C00
Support Level : 0
Kernel Patch number : 202
Source ID : 0.202
DBSL Patch No. : 046
ICU Version : 3.0 Unicode Version 4.0.1
libsapu16 Version : 1.0025 Apr 8 2009 16:21:08
Supported Environment
SAP Database Version
700
Database
ORACLE 9.2.0..
ORACLE 10.1.0..
ORACLE 10.2.0..
Operating System
aix 1 5
aix 2 5
aix 3 5
aix 1 6
My active parameter in Tcode : RZ10 as follow:
Parameter Name     Parameter value
login/accept_sso2_ticket     1
login/create_sso2_ticket     2
rsau/enable     1
login/failed_user_auto_unlock     0
login/fails_to_user_lock     5
gw/max_sys     2000
gw/max_overflow_size     25000000
rdisp/max_comm_entries     2000
rdisp/tm_max_no     2000
gw/max_conn     2000
rdisp/max_arq     2000
ES/SHM_SEG_COUNT     8192
ES/SHM_USER_COUNT     8192
ES/SHM_SEG_SIZE     2048
ES/TABLE     SHM_SEGS
ztta/short_area     4000000
em/global_area_MB     256
zcsa/db_max_buftab     10000
sap/bufdir_entries     10000
enque/table_size     60000
rsdb/obj/large_object_size     35000
rsdb/obj/max_objects     45000
rsdb/obj/buffersize     150000
rdisp/gui_auto_logout     0
login/password_expiration_time     0
rdisp/max_wprun_time     25000
login/multi_login_users     CICUSER,TALSAYED,ASALAM
login/disable_multi_gui_login     1
SAPSYSTEMNAME     PRD
SAPSYSTEM     0
INSTANCE_NAME     DVEBMGS00
DIR_CT_RUN     $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE     $(DIR_INSTANCE)/exe
PHYS_MEMSIZE     8000
exe/saposcol     $(DIR_CT_RUN)/saposcol
rdisp/wp_no_dia     70
rdisp/wp_no_btc     20
exe/icmbnd     $(DIR_CT_RUN)/icmbnd
icm/server_port_0     PROT=HTTP,PORT=80$$
ms/server_port_0     PROT=HTTP,PORT=81$$
rdisp/wp_no_enq     1
rdisp/wp_no_vb     2
rdisp/wp_no_vb2     2
rdisp/wp_no_spo     10
abap/buffersize     9900000
zcsa/table_buffer_area     108003328
rtbb/buffer_length     60000
rsdb/cua/buffersize     24000
zcsa/presentation_buffer_area     28166144
rdisp/appc_ca_blk_no     2000
rdisp/wp_ca_blk_no     1000
rsdb/ntab/entrycount     68500
rsdb/ntab/ftabsize     100000
rsdb/ntab/irbdsize     20000
rsdb/ntab/sntabsize     3995
DIR_ROLL     /usr/sap/PRD/DVEBMGS00/data
DIR_PAGING     /usr/sap/PRD/DVEBMGS00/data
DIR_DATA     /usr/sap/PRD/DVEBMGS00/data
DIR_REORG     /usr/sap/PRD/DVEBMGS00/data
DIR_TRANS     /usr/sap/trans
DIR_TEMP     /tmp
DIR_SORTTMP     /usr/sap/PRD/DVEBMGS00/data
zcsa/system_language     E
zcsa/installed_languages     AE
abap/use_paging     0
ztta/roll_first     1024
rdisp/keepalive_timeout     8000
ztta/roll_area     9000960
rdisp/ROLL_SHM     16384
rdisp/ROLL_MAXFS     32768
rdisp/PG_SHM     16384
rdisp/PG_MAXFS     200064
abap/heap_area_dia     2012217344
abap/heap_area_nondia     2012217344
abap/heap_area_total     2012217344
abap/heaplimit     40894464
abap/swap_reserve     20971520
ztta/roll_extension     2101346304
em/initial_size_MB     4092
em/blocksize_KB     4096
em/stat_log_size_MB     20
em/stat_log_timeout     0
login/no_automatic_user_sapstar     0
login/system_client     100
icm/server_port_1     PROT=SMTP,PORT=8025,TIMEOUT=180
rdisp/start_icman     TRUE
icm/host_name_full     SAPPRD.tmg.dom
install/codepage/appl_server     4102
ipc/shm_psize_10     500000000
ipc/shm_psize_14     0
ipc/shm_psize_18     0
ipc/shm_psize_19     0
ipc/shm_psize_30     -10
ipc/shm_psize_40     500000000
ipc/shm_psize_41     0
ipc/shm_psize_51     -10
ipc/shm_psize_52     -10
ipc/shm_psize_54     -10
ipc/shm_psize_55     -10
ipc/shm_psize_57     -10
ipc/shm_psize_58     -10
I already generated EWA report and I got the following result:
1. Performance Overview PRD
The performance of your system was analyzed with respect to average response times and total workload. We have detected some problems that may impair system performance.
To ensure adequate performance in your core business transactions, you should take corrective action as soon as possible. For further information, please SAP Support.
Rating     Check
     Performance Evaluation
The following table shows the average response times for various task types:
Task type     Dialog Steps     Avg. Resp. Time in ms     Avg. CPU Time in ms     Avg. Wait Time in ms     Avg. Load Time in ms     Avg. DB Time in ms     Avg. GUI Time in ms
DIALOG     212990     1595.2     257.7     31.0     5.0     622.2     136.8
RFC     2904     11876.4     192.1     33.1     1.4     10574.2     0.0
UPDATE     86257     116.1     28.4     2.1     2.9     58.1     0.0
UPDATE2     1100     84.6     16.9     1.3     1.4     48.2     0.0
BATCH     11600     189360.5     46218.1     5.5     3.7     132313.5     0.0
SPOOL     9989     1686.8     37.1     55.6     0.3     49.2     0.0
1.1. Current Workload
The following table lists the number of current users (measured from our workload analysis) in your system.
Users     Low Activity     Medium Activity     High Activity     Total Users
Measured in System     162     119     6     287
1.2. Performance Evaluation
The measured times are compared against reference times to provide a rating.
- If the number of dialog steps in an hour is less than 1000 this hour is not considered.
- If the total number of transaction steps is less than 24000, the rating for the task is not performed and a blue line is entered in the table.
The table below shows that a performance problem is expected for the task that is rated YELLOW.
Task     Steps     Application Server Performance     Database Server Performance
Dia     212987
Upd     86257
HTTP     0
Rating     Task     Time     Steps     Avg. Response Time (ms)     Avg. CPU Time (ms)     Avg. Database Time (ms)
     Dia     08-09     3726     1343     137     889
     Dia     09-10     19990     1003     174     620
     Dia     10-11     20603     1747     112     630
     Dia     11-12     27934     2437     239     612
     Dia     12-13     18921     2737     235     858
     Dia     13-14     21579     2163     349     549
     Dia     16-17     22529     1134     230     703
     Dia     17-18     12189     1709     561     991
     Dia     19-20     5840     1550     414     967
     Dia     20-21     4951     1294     176     454
The ratings in the table above are determined by comparisons against the reference table below.
If the dialog response times are very poor, it will cause a RED rating for the entire check.
Task     Reference for Avg. Response Time (ms)     Reference for Avg. DB time (ms)
Dia     1200     600
Upd     2400     1200
HTTP     1200     600
1.3. Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the highest workload in your system. NOTE: A business transaction normally consists of more than one dialog step. As a rough estimate, the actual number of business transactions that are executed in your system is approximately one third of the total dialog steps shown. (Transaction CPIC/RFC is not taken into account.)
1.3.1. Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload.
WORKLOAD BY TRANSACTION (DIALOG/UPDATE)
Transaction     Type     Dialog Steps     Total Resp. Time in %     Avg. Resp. Time in ms     Avg. CPU Time in ms     Avg. DB Time in ms     Avg. GUI Time in ms
Total          299247     100.0     1168.9     191.7     459.6     136.8
ZFIBB     DIA     8592     11.1     4522.4     2258.5     633.4     30.1
ZFIRP     DIA     6641     7.3     3858.0     1089.7     1162.6     50.0
RECN     DIA     11644     6.8     2047.9     129.1     1165.8     202.6
SESSION_MANAGER     DIA     8972     5.7     2226.9     80.2     244.2     458.2
ZFICCR     DIA     4834     5.2     3775.9     138.4     2535.9     195.6
ZRECPD     DIA     8895     4.6     1790.1     85.9     525.3     329.4
FBL3N     DIA     10414     4.1     1386.7     109.3     971.8     49.1
ZFIOBC2     DIA     852     3.4     13909.2     2675.7     9302.3     1028.7
ZREOR     DIA     2241     3.3     5216.1     2246.2     808.1     357.5
ZFIOB     DIA     1176     3.2     9503.7     51.3     8287.0     753.4
38.1% of the "Total Resp. Time" in the above table is caused by customer transactions.
WORKLOAD BY TRANSACTION (BATCH/SPOOL)
Transaction     Type     Dialog Steps     Total Resp. Time in %     Avg. Resp. Time in ms     Avg. CPU Time in ms     Avg. DB Time in ms
Total          21492     100.0     102913.8     24939.7     71399.3
SBIE0001     BTC     36     98.7     60613763.4     14848709.4     42408448.0
ZFIPR     SPO     448     0.2     7939.6     169.9     387.1
(BATCH)     BTC     7368     0.2     478.4     7.5     22.2
ZFIADCA     SPO     486     0.1     5733.7     168.6     177.9
RSAL_BATCH_TOOL_DISPATCHING     BTC     96     0.1     23895.0     1964.7     21770.3
ZFIJV     SPO     309     0.1     6092.5     107.7     89.5
SAPRSLOG     BTC     4     0.1     318475.8     69165.0     257824.5
ZRE_GENERATE_COND_RO     BTC     5     0.1     250075.0     3336.0     237287.8
ZRE_AUTO_REJECT_OFFER     BTC     20     0.1     57062.0     339.0     54977.8
ZRE_TRANSFER_TOCONT_UPL     BTC     346     0.0     3161.3     941.6     2327.7
0.6% of the "Total Resp. Time" in the above table is caused by customer transactions.
According to our analysis, the main system load is caused by background jobs.
The EarlyWatch Alert Service can only detect performance problems for dialog, update and RFC response times. This service does not evaluate performance problems for background jobs.
1.3.2. Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the database load, sorted by percentage of total database access times.
DATABASE LOAD BY TRANSACTIONS (DIALOG/UPDATE)
Transaction     Type     Dialog Steps     Total DB Time in %     Avg. DB Time in ms
Total          299247     100.0     459.6
RECN     DIA     11644     9.9     1165.8
ZFICCR     DIA     4834     8.9     2535.9
FBL3N     DIA     10414     7.4     971.8
ZFIOB     DIA     1176     7.1     8287.0
ZRECCR     DIA     1504     7.0     6368.3
ZFIOBC2     DIA     852     5.8     9302.3
ZFIRP     DIA     6641     5.6     1162.6
ZFIBB     DIA     8592     4.0     633.4
ZFIREMTCH     DIA     73     3.5     66443.6
ZRECPD     DIA     8895     3.4     525.3
45.3% of the "Total DB Time" in the above table is caused by customer transactions.
DATABASE LOAD BY TRANSACTIONS (BATCH/SPOOL)
Transaction     Type     Dialog Steps     Total DB Time in %     Avg. DB Time in ms
Total          21492     100.0     71399.3
SBIE0001     BTC     36     99.5     42408448.0
RSAL_BATCH_TOOL_DISPATCHING     BTC     96     0.1     21770.3
ZRE_GENERATE_COND_RO     BTC     5     0.1     237287.8
ZRE_AUTO_REJECT_OFFER     BTC     20     0.1     54977.8
SAPRSLOG     BTC     4     0.1     257824.5
ZRE_TRANSFER_TOCONT_UPL     BTC     346     0.1     2327.7
RSPO1043     BTC     4     0.0     143273.5
ZFIPR     SPO     448     0.0     387.1
(BATCH)     BTC     7368     0.0     22.2
ZFIADCA     SPO     486     0.0     177.9
0.3% of the "Total DB Time" in the above table is caused by customer transactions.
Please advice.
Regards,
Ahmed

Gentlemen,
Please advise me with the following scenario, which is Iu2019m facing a problem with system performance,
My system configuration is:
SAP ECC 6.0 , Oracle 10.2.0.2.0 , Kernel Patch number : 202 , DBSL Patch No. : 046
Server Configuration:
Power 6 , Processor Type: PowerPC_POWER6 , Processor Implementation Mode: POWER 6 , Processor Version: PV_6_Compat , Number Of Processors: 6 , Processor Clock Speed: 3503 MHz , CPU Type: 64-bit , Kernel Type: 64-bit , LPAR Info: 2 PRODUCTION , Memory Size: 47104 MB , Good Memory Size: 47104 MB , Platform Firmware level: EL340_039 , Firmware Version: IBM,EL340_039
My active parameter in Tcode : RZ10 as follow:
Parameter Name     Parameter value
rsau/enable                     1
login/failed_user_auto_unlock     0
login/fails_to_user_lock     5
gw/max_sys                     2000
gw/max_overflow_size     25000000
rdisp/max_comm_entries     2000
rdisp/tm_max_no                     2000
gw/max_conn                     2000
rdisp/max_arq                        2000
ES/SHM_SEG_COUNT     8192
ES/SHM_USER_COUNT     8192
ES/SHM_SEG_SIZE                     2048
ES/TABLE     SHM_SEGS
ztta/short_area                     4000000
em/global_area_MB                     256
zcsa/db_max_buftab                     10000
sap/bufdir_entries                     10000
enque/table_size                     60000
rsdb/obj/large_object_size     35000
rsdb/obj/max_objects                     45000
rsdb/obj/buffersize                     150000
rdisp/max_wprun_time     25000
DIR_CT_RUN                     $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE                  $(DIR_INSTANCE)/exe
PHYS_MEMSIZE                   8000
exe/saposco                        $(DIR_CT_RUN)/saposcol
rdisp/wp_no_dia                         70
rdisp/wp_no_btc                  20
exe/icmbnd                        $(DIR_CT_RUN)/icmbnd
rdisp/wp_no_enq                1
rdisp/wp_no_vb                      2
rdisp/wp_no_vb2              2
rdisp/wp_no_spo                10
abap/buffersize                      9900000
zcsa/table_buffer_area     108003328
rtbb/buffer_length                    60000
rsdb/cua/buffersize              24000
zcsa/presentation_buffer_area     28166144
rdisp/appc_ca_blk_no                     2000
rdisp/wp_ca_blk_no               1000
rsdb/ntab/entrycount               68500
rsdb/ntab/ftabsize              100000
rsdb/ntab/irbdsize             20000
rsdb/ntab/sntabsize              3995
abap/use_paging                    0
ztta/roll_first                      1024
rdisp/keepalive_timeout                   8000
ztta/roll_area                        9000960
rdisp/ROLL_SHM                   16384
rdisp/ROLL_MAXFS                 32768
rdisp/PG_SHM                16384
rdisp/PG_MAXFS                 200064
abap/heap_area_dia             2012217344
abap/heap_area_nondia     2012217344
abap/heap_area_total      2012217344
abap/heaplimit                40894464
abap/swap_reserve                  20971520
ztta/roll_extension                  2101346304
em/initial_size_MB              4092
em/blocksize_KB                  4096
em/stat_log_size_MB                     20
em/stat_log_timeout                       0
install/codepage/appl_server     4102
ipc/shm_psize_10               500000000
ipc/shm_psize_14              0
ipc/shm_psize_18             0
ipc/shm_psize_19             0
ipc/shm_psize_30             -10
ipc/shm_psize_40            500000000
ipc/shm_psize_41                 0
ipc/shm_psize_51               -10
ipc/shm_psize_52            -10
ipc/shm_psize_54             -10
ipc/shm_psize_55             -10
ipc/shm_psize_57             -10
ipc/shm_psize_58                   -10
I already generated EWA report and I got the following result:
Performance Evaluation
The following table shows the average response times for various task types:
Task type     Dialog      Avg. Resp.      Avg. CPU      Avg. Wait      Avg. Load      Avg. DB      Avg. GUI
DIALOG     212990     1595.2                      257.7     31.0     5.0     622.2     136.8
RFC     2904     11876.4                      192.1     33.1     1.4     10574.2     0.0
UPDATE     86257     116.1                       28.4     2.1     2.9     58.1     0.0
UPDATE2     1100     84.6                      16.9     1.3     1.4     48.2     0.0
BATCH     11600     189360.5                46218.1     5.5     3.7     132313.5     0.0
SPOOL     9989     1686.8              37.1     55.6     0.3     49.2     0.0
1.1. Current Workload
The following table lists the number of current users (measured from our workload analysis) in your system.
Low Activity     Medium Activity     High Activity     Total Users
162                  119                                    6     287
1.2. Performance Evaluation
Task     Time     Steps     Avg. Response      Avg. CPU      Avg. Database
Dia     08-09     3726     1343              137     889
Dia     09-10     19990     1003                174     620
Dia     10-11     20603     1747              112     630
Dia     11-12     27934     2437                    239     612
Dia     12-13     18921     2737              235     858
Dia     13-14     21579     2163                  349     549
Dia     16-17     22529     1134               230     703
Dia     17-18     12189     1709                   561     991
Dia     19-20     5840     1550              414     967
Dia     20-21     4951     1294              176     454
Task     Reference for Avg. Response Time (ms)     Reference for Avg. DB time (ms)
Dia     1200                                                     600
Upd     2400                                               1200
HTTP     1200                                                  600
Please advice.
Regards,
Ahmed

RFC error when sending logon data

Hi;
We cannot configure the STMS of our development system. When we try to
configure it, system gives an error message: Errors during distribution
of tp configuration; TMS Alert Viewers tells us
RFC_COMMUNICATION_FAILURE: RFC communications error with
system/destination TMSADM-FKT.DOMAIN_FKT RFC error when sending logon
data and READ_PROFILE_FAILED:File
erptest\sapmnt\trans\bin\TPPARAM
could not be opened for reading (No such file or directory).
Is there any advise for solution?
Best regards
Noyan
PS: Please find the profiles below:
START:
#.*       Start profile START_DVEBMGS00_erptest                                                                                *
#.*       Version                 = 000006                                                                                *
#.*       Generated by user = BASIS                                                                                *
#.*       Generated on = 30.12.2010 , 15:40:55                                                                                *
generated by R3SETUP
SAPSYSTEMNAME = FKT
INSTANCE_NAME = DVEBMGS00
SAPSYSTEM = 00
SAPGLOBALHOST = erptest
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
start database
#_DB = strdbs.cmd
#Start_Program_02 = immediate $(DIR_EXECUTABLE)\$(_DB) FKT
start message server
#_MS = msg_server.exe
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
Start IGS
Start_Program_05 = local $(DIR_EXECUTABLE)$(DIR_SEP)igswd$(FT_EXE) -mode=profile pf=$(DIR_PROFILE)$(DIR_SEP)FKT_DVEBMGS00_erptest
start application server
#_DW = disp+work.exe
#Start_Program_04 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\FKT_DVEBMGS
General parameters for starting the system
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPSYSTEM = 00
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPSYSTEMNAME = FKT
#parameter created                          by: BASIS        24.12.2007 23:53:27
#INSTANCE_NAME = DVEBMGS00
#parameter created                          by: BASIS        24.12.2007 23:53:27
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
#parameter created                          by: BASIS        24.12.2007 23:53:27
#SAPGLOBALHOST = erptest
Start database
#parameter created                          by: BASIS        24.12.2007 23:53:27
_DB = strdbs.cmd
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_01 = immediate $(DIR_EXECUTABLE)\$(_DB) $(SAPSYSTEMNAME)
Start message server
#parameter created                          by: BASIS        24.12.2007 23:53:27
MS = msgserver.exe
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_02 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
Start applications server
#parameter created                          by: BASIS        24.12.2007 23:53:27
_DW = disp+work.exe
#parameter created                          by: BASIS        24.12.2007 23:53:27
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
DEFAULT:
SAPDBHOST = ERPTEST
dbms/type = mss
dbs/mss/server = ERPTEST
dbs/mss/dbname = FKT
dbs/mss/schema = fkt
SAPSYSTEMNAME = FKT
SAPGLOBALHOST = erptest
SAPFQDN = tr.delta.is
SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(SAPFQDN)
SAPDBHOST = erptest
SAPTRANSHOST = erptest
DIR_TRANS =
$(SAPTRANSHOST)\sapmnt\trans
#DIR_TRANS = D:\usr\sap\trans
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
SAP Message Server for ABAP
rdisp/mshost = erptest
rdisp/sna_gateway = erptest
rdisp/sna_gw_service = sapgw00
rdisp/vbname = erptest_FKT_00
rdisp/enqname = erptest_FKT_00
rdisp/btcname = erptest_FKT_00
rdisp/msserv = sapmsFKT
rdisp/msserv_internal = 3900
rdisp/bufrefmode = sendoff,exeauto
login/system_client = 200
#GUVENLIK PARAMETRELERI
login/password_expiration_time = 90
login/min_password_lng = 6
#parameter created                          by: BASIS        25.03.2004 08:41:25
rdisp/gui_auto_logout = 10800
#parameter created                          by: BASIS        25.03.2004 08:37:47
#old_value: 3                                 changed: BASIS 25.03.2004 08:42:38
login/fails_to_user_lock = 6
#validasyon geregi, g#venligi artirma ama#i - check active but no check for SRF
#parameter created                          by: BASIS        16.06.2007 17:35:41
#old_value: 2
#changed: BASIS         14.05.2008 15:24:55
auth/rfc_authority_check = 1
#otomatik unlocki iptal eder
#parameter created                          by: BASIS        10.11.2006 17:47:15
login/failed_user_auto_unlock = 0
#AUDIT PARAMETRELER?
#old_value:                                   changed: BASIS 20.04.2005 17:13:37
rsau/max_diskspace/per_day = 1996800000
#old_value: 1000000000                        changed: BASIS 20.04.2005 17:17:01
#old_value: 0                                 changed: BASIS 20.04.2005 17:19:12
rsau/max_diskspace/local = 2048000000
#old_value: 2000000000                        changed: BASIS 28.03.2005 23:17:11
#old_value: 2                                 changed: BASIS 29.03.2005 12:09:14
#old_value: 0                                 changed: BASIS 20.04.2005 17:13:37
rsau/max_diskspace/per_file = 665600000
rsau/enable = 1
rsau/local/file = D:\usr\sap\FKT\DVEBMGS00\log\++++++++######..AUD
rsau/selection_slots = 12
#rec/client = ALL
DIR_AUDIT = D:\usr\sap\FKT\DVEBMGS00\log
FN_AUDIT = ++++++++######..AUD
#DIL PARAMETRELERI
#Turkish codepage settings
abap/import_char_conversion = 0
install/codepage/db/non_transp = 1610
install/codepage/db/transp = 1610
zcsa/installed_languages = DET
#zcsa/system_language = E
zcsa/system_language = T
zcsa/second_language = E
install/codepage/appl_server = 1610
#OS dependent
abap/locale_ctype = Turkish_turkey.28599
#DIR_PUT = D:\usr\sap\FKQ\upg\abap
   *** UPGRADE EXTENSIONS (RELEASE "701") ***
#rdisp/msserv_internal = 3900
#system/type = ABAP
INSTANCE:
SAPSYSTEMNAME = FKT
SAPGLOBALHOST = erptest
SAPSYSTEM = 00
INSTANCE_NAME = DVEBMGS00
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
icm/server_port_0 = PROT=HTTP,PORT=80$$
SAP Message Server parameters are set in the DEFAULT.PFL
ms/server_port_0 = PROT=HTTP,PORT=81$$
#rdisp/wp_no_dia = 10
#rdisp/wp_no_btc = 3
#rdisp/wp_no_enq = 1
#rdisp/wp_no_vb = 1
#rdisp/wp_no_vb2 = 1
#disp/wp_no_spo = 1
rdisp/wp_no_dia = 12
rdisp/wp_no_vb = 3
rdisp/wp_no_vb2 = 0
rdisp/wp_no_enq = 1
rdisp/wp_no_btc = 3
rdisp/wp_no_spo = 1
#PERFORMANS PARAMETRELERI
#parameter created                          by: SAP*         08.08.2001 10:30:18
abap/fieldexit = yes
#parameter created                          by: ALPER        13.10.2000 18:24:16
install/collate/active = 1
rdisp/max_wprun_time = 25000
MEMORY_NO_MORE_PAGING dump nedeniyle
#parameter created                          by: BASIS        27.12.2006 17:00:22
rdisp/PG_MAXFS = 262144
abap/heap_area_nondia = 2000000000
rdisp/PG_SHM = 16384
rdisp/ROLL_SHM = 32768
#'STORAGE_PARAMETERS_WRONG_SET' or 'TSV_TNEW_PAGE_ALLOC_FAILED'
#Note 552209 - Maximum memory utilization for processes on NT/Win2000
#parameter created                          by: BASIS        30.10.2007 10:57:24
#abap/heap_area_nondia = 50000
#parameter created                          by: BASIS        30.10.2007 10:58:54
#rdisp/PG_SHM = 0
#parameter created                          by: BASIS        30.10.2007 10:58:27
#rdisp/ROLL_SHM = 625
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:49:57
dbs/mss/stats_on = 1
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:49:33
dbs/oledb/stats_on = 1
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:48:23
dbs/oledb/add_procs = 8
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:47:29
rsdb/esm/max_objects = 2000
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:47:03
rsdb/otr/buffersize_kb = 4096
#EWA report 12.2007
#parameter created                          by: BASIS        03.01.2008 19:46:21
rsdb/esm/buffersize_kb = 4096
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:18:14
ztta/parameter_area = 16000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:43
enque/table_size = 10000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:20
gw/max_sys = 2000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:16:01
gw/max_overflow_size = 25000000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:15:19
rdisp/max_comm_entries = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:14:48
rdisp/tm_max_no = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:14:20
gw/max_conn = 2000
Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:13:42
rdisp/max_arq = 2000
#Eyl#l 2006 EWA raporu
#parameter created                          by: BASIS        24.11.2006 13:12:57
ztta/roll_area = 3500000
#parameter created                          by: BASIS        18.05.2005 09:20:25
#old_value: 90                                changed: BASIS 18.05.2005 09:22:25
rdisp/max_hold_time = 300
#parameter created                          by: BASIS        20.08.2003 12:10:20
#old_value: 6144
#changed: BASIS         03.01.2008 19:42:10
rsdb/obj/buffersize = 20000
#parameter created                          by: BASIS        20.08.2003 12:09:48
#old_value: 6000
#changed: BASIS         03.01.2008 19:42:59
rsdb/obj/max_objects = 20000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:42:11
#old_value: 250000
#changed: BASIS         30.10.2007 10:56:17
#abap/buffersize = 100000
#changed: BASIS         03.01.2008 19:40:36
#abap/buffersize = 300000
#by: BASIS 12.06.2008
abap/buffersize = 400000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:41:32
#zcsa/presentation_buffer_area = 20000000
#64 bite gectikten sonra   by: BASIS 10.06.2008
zcsa/presentation_buffer_area = 30000768
note 103747
#parameter created                          by: BASIS        08.07.2003 20:40:55
rsdb/ntab/ftabsize = 30000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:40:12
rtbb/max_tables = 500
note 103747
#parameter created                          by: BASIS        08.07.2003 20:39:15
#old_value: 20000
#changed: BASIS         03.01.2008 19:41:29
#rtbb/buffer_length = 30000
#64 bite gectikten sonra by: BASIS 10.06.2008
rtbb/buffer_length = 50000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:38:26
zcsa/db_max_buftab = 10000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:37:37
#zcsa/table_buffer_area = 50000000
#64 bite gectikten sonra   by: BASIS 10.06.2008
#zcsa/table_buffer_area = 89000000
by: BASIS 12.06.08
zcsa/table_buffer_area = 99000000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:36:54
sap/bufdir_entries = 10000
note 103747
#parameter created                          by: BASIS        08.07.2003 20:36:12
rsdb/cua/buffersize = 8000
#note 103747
#parameter created                          by: BASIS        08.07.2003 20:34:46
#old_value: 5000                              changed: BASIS 08.07.2003 20:35:39
rsdb/ntab/sntabsize = 5500
#parameter created                          by: BASIS        08.07.2003 20:33:56
#note 103747
#old_value: 10607                             changed: BASIS 08.07.2003 20:34:58
#old_value: 10000                             changed: BASIS 08.07.2003 20:35:39
rsdb/ntab/irbdsize = 11000
#note 103747
#parameter created                          by: BASIS        08.07.2003 20:32:18
rsdb/ntab/entrycount = 40000
#old_value: 2076                              changed: BASIS 28.06.2005 19:36:21
#old_value: 5735                              changed: BASIS 28.06.2005 19:40:01
PHYS_MEMSIZE = 4096
#64 bite gectikten sonra   by: BASIS 10.06.2008
abap/heaplimit = 40894464
abap/heap_area_total = 2000683008
ztta/roll_extension = 2000683008
em/blocksize_KB = 4096
   *** UPGRADE EXTENSIONS (RELEASE "701") ***
#rdisp/elem_per_queue = 2000
#auth/auth_number_in_userbuffer = 9000
#snc/enable = 0

Hi Srikishan;
You are right. The problem was releated with secstore. I found a SAP note ( Note 1532825 - Deleting SECSTORE entries during system export/system copy). I created the program which ise mentioned in the note and than run it. After that everything seems ok now.
Thanks for your help and interest
Best regards
Noyan

How to config the logout time in BW

If the user do'nt refresh the Bex report for a longtime how to set the logout time in BW. Could someone give me some hits. Thanks.

If you want to logout the user session automatically if the user has not worked or does any activity in the system then for that you need to change the parameter settings using the RZ11 transaction
parameter :rdisp/gui_auto_logout
Enter the required number of seconds of inactivity before the user is logged off automatically.
To deactivate automatic log off, delete the parameter from the profile(s) or set the value '0'.

"Page not found" error after 5 minutes of see "processing" on the screen

We are using WebLogic 8.1 server and also the WebLogic proxy as our front end. When a user runs a process that takes over 5 minutes using the Proxy URL they receive an IE "Page not found" error after 5 minutes of seeing "processing" on the screen. If they run it on none Proxy URL (directly on WebLogic server) it works fine.
We have looked into the WLIOTimeoutSecs parameter and set in the web.xml for both the HttpClusterServlet and HttpProxyServlet, but this had no affect.
Is there another timeout that controls this 5 minute timeout? It seems if one uses Apache and sets the WLIOTimeoutSecs parameter to a higher number than 300 seconds there is not an issue.
Did this parameter get omitted for the WebLogic Proxy and if so, what does one use?
Thanks,
Jim

Hello George,
Thank you for the quick reply. I will surely try the option suggested by you.
But what i was thinking is that as this is not a Connection Time Out (500) error, instead its a Page Not Found error, it would be Session-Timeout and not Connection Time-Out.
Maybe I should be looking at:
SESSION-TIMEOUT due to kernel:
Kernel parameter: rdisp/gui_auto_logout
Kernel parameter: rdisp/plugin_auto_logout
as per the SAP OSS Note: 705013
But again, I think this Note is pointing to the SICF service and IAC type of iView and not SAP Transaction type iView. Please advice.
Thanks,
Gaurav
Edited by: Gaurav Shah on Dec 4, 2008 9:37 PM
Edited by: Gaurav Shah on Dec 4, 2008 9:42 PM

Auto Logout when idle not working for transaction iview

Hi,
When we open an SAP system using transaction iview and if the screen is idle for 30 mins, auto logout doesn't seem to be work.
We have verified that rdisp/gui_auto_logout parameter is set to 1800 i.e., 30 min. which a default value. Do we have to activate this service or its activated by default? Let me know if any other parameter needs to be configured.
Also, is there a way to detect multiple sessions when SAP transaction is executed like the way SAP Logon pad detects when user has logged in into SAP system on different PC?
We are using NW portal 7.01 and IE 7.
Regards,
Vaibhav

Hi
the param icm/keep_alive_timeout does only that if within this time interval new data arrives over the network from the partner, the ICM attempts to keep the connection open once it has been established. If, for the existing connection, there is no further communication within the specified time period, the ICM terminates the connection. and this is a static param so if u change this it needs a sys restart and the param rdisp/plugin_auto_logout is also dependent on the above param as then it delets only the user context after the time period is reached not the work process context and the param login/disable_multi_gui_login works only for dialog log ins not for prta and as far as my knowledge there is no other way to detect this but i heard like by doing some code changes u can know something regarding that.
Thanks & Regards
Pradeep Srimanthula

UWL Iview getting 500 Internal Server Error

Hi All,
We have Uwl iview which is connected to R/3 system and its works fine. But if the user leaves the UWL session for more than 30 mins its get an message:
" Web dynproapplicatie 'UWL' past. Start application again. Launch iView again via "Refresh" in iview vak or knowp browser 'Refresh' "
Portal cookie is still active, User can navigate to other applications easily, I want to know why this message is appearing and how can we increase the duraction.?
Cache Value parameters under UWL service are:
Default Cache Validity Period, in Minutes:5
Timeout Value for the Connected Systems, in Seconds: * 30
Regards
Parth

Hey Parth,
check the note recommended by Ladislav i.e. 842635 and also check note 842878.
I would suggest you to check the backend system parameters about the session timeout related things through RZ10/RZ11.
The param is "rdisp/gui_auto_logout".
You can configure the HTTP session timeout using the web.xml descriptor. Session configuration u2013 Session timeout field.
You can get this file from the following location:
\usr\sap\<EP_SID>\j2ee\j2ee_01\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\web.xml
You have to restart your portal to ttake this effect.
Hope it helps.
Regards
Puneet

Rdisp/gui_auto_logout

Similar Messages

Maybe you are looking for