ASM timeout parameters?

Oracle: 11.2.0.3 non-RAC (Oracle Restart grid home)
OS: RHEL Server 5.8
Can timeout parameters be set for an ASM instance or for any downstream database instances dependent on an ASM instance? Our storage and sysadmins ran a test (failing over a controller). The Oracle database instance detected a problem reaching +FLASHREC on the NetApp device (it was trying to access a control file evidently). Approximately one second later the database instance decided to terminate itself. The ASM instance remained up. But subsequent checking with ASMCD showed no ASM Diskgroup available using an LS command. After bouncing the ASM instance all was well--the diskgroups reappeared and we were able to restart our database instance. A second seems a bit unforgiving. Can any timeout-related parameters be set on the ASM or ASM-client instance to provide more wiggle room during a controller failover?
Some errors we encountered from the database instance alert log. Further below are errors from the ASM instance's alert log
Wed Mar 14 04:00:55 2012
Archived Log entry 89 added for thread 1 sequence 142 ID 0xbb0a69f4 dest 1:
Wed Mar 14 17:51:06 2012
Errors in file /u01/app/oracle/diag/rdbms/<instance name here>/<instance name here>/trace/<instance name here>ckpt310.trc:
ORA-27072: File I/O error
Linux-x86_64 Error: 5: Input/output error
Additional information: 4
Additional information: 120864
Additional information: -1
WARNING: Read Failed. group:2 disk:0 AU:59 offset:16384 size:16384
Wed Mar 14 17:51:06 2012
Errors in file /u01/app/oracle/diag/rdbms/<instance name here>/<instance name here>/trace/<instance name here>arc2399.trc:
ORA-27072: File I/O error
Linux-x86_64 Error: 5: Input/output error
Additional information: 4
Additional information: 120864
Additional information: -1
WARNING: failed to read mirror side 1 of virtual extent 0 logical extent 0 of file 256 in group [2.2142222202] from disk FLASHREC_0000 allocation unit 59 reason error; if possible, will try another mirror side
WARNING: Read Failed. group:2 disk:0 AU:59 offset:16384 size:16384
WARNING: failed to read mirror side 1 of virtual extent 0 logical extent 0 of file 256 in group [2.2142222202] from disk FLASHREC_0000 allocation unit 59 reason error; if possible, will try another mirror side
Errors in file /u01/app/oracle/diag/rdbms/<instance name here>/<instance name here>/trace/<instance name here>ckpt310.trc:
ORA-00202: control file: '+FLASHREC/<instance name here>/controlfile/current.256.776099703'
ORA-15081: failed to submit an I/O operation to a disk
Errors in file /u01/app/oracle/diag/rdbms/<instance name here>/<instance name here>/trace/<instance name here>arc2399.trc:
ORA-00202: control file: '+FLASHREC/<instance name here>/controlfile/current.256.776099703'
ORA-15081: failed to submit an I/O operation to a disk
Errors in file /u01/app/oracle/diag/rdbms/<instance name here>/<instance name here>/trace/<instance name here>ckpt310.trc:
ORA-27061: waiting for async I/Os failed
Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 16384
WARNING: Write Failed. group:2 disk:0 AU:59 offset:49152 size:16384
Errors in file /u01/app/oracle/diag/rdbms/<instance name here>/<instance name here>/trace/<instance name here>ckpt310.trc:
ORA-15080: synchronous I/O operation to a disk failed
WARNING: failed to write mirror side 1 of virtual extent 0 logical extent 0 of file 256 in group 2 on disk 0 allocation unit 59
Wed Mar 14 17:51:06 2012
Errors in file /u01/app/oracle/diag/rdbms/<instance name here>/<instance name here>/trace/<instance name here>m00023737.trc:
ORA-27072: File I/O error
Linux-x86_64 Error: 5: Input/output error
Additional information: 4
Additional information: 120864
Additional information: -1
WARNING: Read Failed. group:2 disk:0 AU:59 offset:16384 size:16384
WARNING: failed to read mirror side 1 of virtual extent 0 logical extent 0 of file 256 in group [2.2142222202] from disk FLASHREC_0000 allocation unit 59 reason error; if possible, will try another mirror side
Errors in file /u01/app/oracle/diag/rdbms/<instance name here>/<instance name here>/trace/<instance name here>m00023737.trc:
ORA-00202: control file: '+FLASHREC/<instance name here>/controlfile/current.256.776099703'
ORA-15081: failed to submit an I/O operation to a disk
Errors in file /u01/app/oracle/diag/rdbms/<instance name here>/<instance name here>/trace/<instance name here>ckpt310.trc:
ORA-00206: error in writing (block 3, # blocks 1) of control file
ORA-00202: control file: '+FLASHREC/<instance name here>/controlfile/current.256.776099703'
ORA-15081: failed to submit an I/O operation to a disk
ORA-15081: failed to submit an I/O operation to a disk
Errors in file /u01/app/oracle/diag/rdbms/<instance name here>/<instance name here>/trace/<instance name here>ckpt310.trc:
ORA-00221: error on write to control file
ORA-00206: error in writing (block 3, # blocks 1) of control file
ORA-00202: control file: '+FLASHREC/<instance name here>/controlfile/current.256.776099703'
ORA-15081: failed to submit an I/O operation to a disk
ORA-15081: failed to submit an I/O operation to a disk
CKPT (ospid: 310): terminating the instance due to error 221
Errors in file /u01/app/oracle/diag/rdbms/<instance name here>/<instance name here>/trace/<instance name here>m00023737.trc:
ORA-00204: error in reading (block 1, # blocks 1) of control file
ORA-00202: control file: '+FLASHREC/<instance name here>/controlfile/current.256.776099703'
ORA-15081: failed to submit an I/O operation to a disk
Wed Mar 14 17:51:07 2012
License high water mark = 8
Instance terminated by CKPT, pid = 310
USER (ospid: 24054): terminating the instance
Instance terminated by USER, pid = 24054
Some errors we encountered from the ASM instance alert log
Mon Mar 12 14:56:18 2012
NOTE: ASMB process exiting due to lack of ASM file activity for 305 seconds
Wed Mar 14 17:51:06 2012
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM/trace/+ASM_gmon_27396.trc:
ORA-27072: File I/O error
Linux-x86_64 Error: 5: Input/output error
Additional information: 4
Additional information: 4088
Additional information: -1
WARNING: Write Failed. group:1 disk:0 AU:1 offset:1044480 size:4096
WARNING: Hbeat write to PST disk 0.3916384140 (DATAFILE_0000) in group 1 failed.
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM/trace/+ASM_gmon_27396.trc:
ORA-27072: File I/O error
Linux-x86_64 Error: 5: Input/output error
Additional information: 4
Additional information: 4088
Additional information: -1
WARNING: Write Failed. group:2 disk:0 AU:1 offset:1044480 size:4096
WARNING: Hbeat write to PST disk 0.3916384141 (FLASHREC_0000) in group 2 failed.
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM/trace/+ASM_gmon_27396.trc:
ORA-27072: File I/O error
Linux-x86_64 Error: 5: Input/output error
Additional information: 4
Additional information: 4088
Additional information: -1
WARNING: Write Failed. group:3 disk:0 AU:1 offset:1044480 size:4096
WARNING: Hbeat write to PST disk 0.3916384142 (TEMPFILE_0000) in group 3 failed.
Wed Mar 14 17:51:06 2012
NOTE: process b000+asm (23739) initiating offline of disk 0.3916384140 (DATAFILE_0000) with mask 0x7e in group 1
WARNING: Disk 0 (DATAFILE_0000) in group 1 in mode 0x7f is now being taken offline on ASM inst 1
NOTE: initiating PST update: grp = 1, dsk = 0/0xe96f478c, mask = 0x6a, op = clear
Wed Mar 14 17:51:06 2012
NOTE: process b001+asm (23753) initiating offline of disk 0.3916384141 (FLASHREC_0000) with mask 0x7e in group 2
WARNING: Disk 0 (FLASHREC_0000) in group 2 in mode 0x7f is now being taken offline on ASM inst 1
NOTE: initiating PST update: grp = 2, dsk = 0/0xe96f478d, mask = 0x6a, op = clear
GMON updating disk modes for group 1 at 13 for pid 20, osid 23739
ERROR: no read quorum in group: required 1, found 0 disks
Wed Mar 14 17:51:06 2012
NOTE: process b002+asm (23791) initiating offline of disk 0.3916384142 (TEMPFILE_0000) with mask 0x7e in group 3
WARNING: Disk 0 (TEMPFILE_0000) in group 3 in mode 0x7f is now being taken offline on ASM inst 1
NOTE: initiating PST update: grp = 3, dsk = 0/0xe96f478e, mask = 0x6a, op = clear
GMON updating disk modes for group 2 at 14 for pid 23, osid 23753
ERROR: no read quorum in group: required 1, found 0 disks
Wed Mar 14 17:51:06 2012
NOTE: cache dismounting (not clean) group 1/0x7FAFB779 (DATAFILE)
NOTE: messaging CKPT to quiesce pins Unix process pid: 23826, image: oracle@dot-oraprd04 (B003)
Wed Mar 14 17:51:06 2012
NOTE: halting all I/Os to diskgroup 1 (DATAFILE)
Wed Mar 14 17:51:06 2012
NOTE: LGWR doing non-clean dismount of group 1 (DATAFILE)
NOTE: LGWR sync ABA=6.6196 last written ABA 6.6196
NOTE: cache dismounted group 1/0x7FAFB779 (DATAFILE)
SQL> alter diskgroup DATAFILE dismount force /* ASM SERVER */
Wed Mar 14 17:51:06 2012
NOTE: cache dismounting (not clean) group 2/0x7FAFB77A (FLASHREC)
NOTE: messaging CKPT to quiesce pins Unix process pid: 23836, image: oracle@dot-oraprd04 (B004)
NOTE: halting all I/Os to diskgroup 2 (FLASHREC)
NOTE: LGWR doing non-clean dismount of group 2 (FLASHREC)
NOTE: LGWR sync ABA=5.1120 last written ABA 5.1120
GMON updating disk modes for group 3 at 15 for pid 25, osid 23791
ERROR: no read quorum in group: required 1, found 0 disks
NOTE: cache dismounted group 2/0x7FAFB77A (FLASHREC)
SQL> alter diskgroup FLASHREC dismount force /* ASM SERVER */
Wed Mar 14 17:51:06 2012
NOTE: cache dismounting (not clean) group 3/0x7FAFB77B (TEMPFILE)
NOTE: messaging CKPT to quiesce pins Unix process pid: 23838, image: oracle@dot-oraprd04 (B005)
NOTE: halting all I/Os to diskgroup 3 (TEMPFILE)
NOTE: LGWR doing non-clean dismount of group 3 (TEMPFILE)
NOTE: LGWR sync ABA=6.11 last written ABA 6.11
NOTE: cache dismounted group 3/0x7FAFB77B (TEMPFILE)
SQL> alter diskgroup TEMPFILE dismount force /* ASM SERVER */
WARNING: Offline of disk 0 (TEMPFILE_0000) in group 3 and mode 0x7f failed on ASM inst 1
WARNING: Offline of disk 0 (DATAFILE_0000) in group 1 and mode 0x7f failed on ASM inst 1
WARNING: Offline of disk 0 (FLASHREC_0000) in group 2 and mode 0x7f failed on ASM inst 1
Wed Mar 14 17:51:07 2012
ERROR: -9(Error 27061, OS Error (Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 512)
ERROR: -9(Error 27061, OS Error (Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 512)
ERROR: -9(Error 27061, OS Error (Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 512)
Wed Mar 14 17:51:07 2012
ERROR: -9(Error 27061, OS Error (Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 512)
ERROR: -9(Error 27061, OS Error (Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 512)
ERROR: -9(Error 27061, OS Error (Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 512)
Wed Mar 14 17:51:07 2012
ERROR: -9(Error 27061, OS Error (Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 512)
ERROR: -9(Error 27061, OS Error (Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 512)
ERROR: -9(Error 27061, OS Error (Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 512)
ASM Health Checker found 1 new failures
ASM Health Checker found 1 new failures
ASM Health Checker found 1 new failures
Wed Mar 14 17:51:07 2012
NOTE: ASM client <instance name here>:<instance name here> disconnected unexpectedly.
NOTE: check client alert log.
NOTE: Trace records dumped in trace file /u01/app/oracle/diag/asm/+asm/+ASM/trace/+ASM_ora_322.trc
Wed Mar 14 17:51:07 2012
NOTE: cache deleting context for group FLASHREC 2/0x7fafb77a
NOTE: cache deleting context for group TEMPFILE 3/0x7fafb77b
NOTE: cache deleting context for group DATAFILE 1/0x7fafb779
GMON dismounting group 2 at 16 for pid 27, osid 23836
GMON dismounting group 1 at 17 for pid 26, osid 23826
NOTE: Disk in mode 0x8 marked for de-assignment
GMON dismounting group 3 at 18 for pid 28, osid 23838
NOTE: Disk in mode 0x8 marked for de-assignment
NOTE: Disk in mode 0x8 marked for de-assignment
SUCCESS: diskgroup FLASHREC was dismounted
SUCCESS: alter diskgroup FLASHREC dismount force /* ASM SERVER */
SUCCESS: diskgroup DATAFILE was dismounted
SUCCESS: alter diskgroup DATAFILE dismount force /* ASM SERVER */
SUCCESS: diskgroup TEMPFILE was dismounted
SUCCESS: alter diskgroup TEMPFILE dismount force /* ASM SERVER */
ERROR: PST-initiated MANDATORY DISMOUNT of group TEMPFILE
ERROR: PST-initiated MANDATORY DISMOUNT of group FLASHREC
ERROR: PST-initiated MANDATORY DISMOUNT of group DATAFILE
Wed Mar 14 17:51:07 2012
NOTE: diskgroup resource ora.FLASHREC.dg is offline
NOTE: diskgroup resource ora.DATAFILE.dg is offline
NOTE: diskgroup resource ora.TEMPFILE.dg is offline
Wed Mar 14 17:51:08 2012
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM/trace/+ASM_ora_24250.trc:
ORA-17503: ksfdopn:2 Failed to open file +DATAFILE/<instance name here>/spfile<instance name here>.ora
ORA-15001: diskgroup "DATAFILE" does not exist or is not mounted
Wed Mar 14 17:51:08 2012
SQL> ALTER DISKGROUP FLASHREC MOUNT /* asm agent *//* {0:5:72} */
NOTE: cache registered group FLASHREC number=1 incarn=0xfa7fb7ea
SQL> ALTER DISKGROUP FLASHREC MOUNT /* asm agent *//* {0:5:72} */
NOTE: cache registered group FLASHREC number=1 incarn=0xfa7fb7ea
NOTE: cache began mount (first) of group FLASHREC number=1 incarn=0xfa7fb7ea
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM/trace/+ASM_ora_27411.trc:
ORA-27061: waiting for async I/Os failed
Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 4096
WARNING: Read Failed. group:0 disk:1 AU:0 offset:0 size:4096
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM/trace/+ASM_ora_27411.trc:
ORA-27061: waiting for async I/Os failed
Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 4096
WARNING: Read Failed. group:0 disk:0 AU:0 offset:0 size:4096
Errors in file /u01/app/oracle/diag/asm/+asm/+ASM/trace/+ASM_ora_27411.trc:
ORA-27061: waiting for async I/Os failed
Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 4096
WARNING: Read Failed. group:0 disk:2 AU:0 offset:0 size:4096
ERROR: no read quorum in group: required 2, found 0 disks
NOTE: cache dismounting (clean) group 1/0xFA7FB7EA (FLASHREC)
NOTE: messaging CKPT to quiesce pins Unix process pid: 27411, image: oracle@dot-oraprd04 (TNS V1-V3)
NOTE: dbwr not being msg'd to dismount
NOTE: lgwr not being msg'd to dismount
NOTE: cache dismounted group 1/0xFA7FB7EA (FLASHREC)
NOTE: cache ending mount (fail) of group FLASHREC number=1 incarn=0xfa7fb7ea
NOTE: cache deleting context for group FLASHREC 1/0xfa7fb7ea
Wed Mar 14 17:51:08 2012
ERROR: -9(Error 27061, OS Error (Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 512)
ERROR: -9(Error 27061, OS Error (Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 512)
ERROR: -9(Error 27061, OS Error (Linux-x86_64 Error: 5: Input/output error
Additional information: -1
Additional information: 512)
GMON dismounting group 1 at 20 for pid 18, osid 27411
ERROR: diskgroup FLASHREC was not mounted
ORA-15032: not all alterations performed
ORA-15017: diskgroup "FLASHREC" cannot be mounted
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "FLASHREC"
ORA-15080: synchronous I/O operation to a disk failed
ORA-15080: synchronous I/O operation to a disk failed
ORA-15080: synchronous I/O operation to a disk failed
ERROR: ALTER DISKGROUP FLASHREC MOUNT /* asm agent *//* {0:5:72} */
ASM Health Checker found 1 new failures

Thanks Dan. The server had been built recently but not yet released. Testing was uncoordinated but no permanent harm was done. Great group of people and NetApp is new to them. Glad they are testing things like controller failover. But it sounds like ASM may be a victim and not the culprit. If ASM remains suspect during continued failover testing I'll consider opening an SR like you suggested.

Similar Messages

Comprehensive list of EP timeout parameters?

I'm looking to document and comparing timeout parameters across our landscape of 7.3 enterprise portals. However I cant find a list of relevant parameters to look for. Other than the "session.invalidation.timeout" parameter, what other timeout controls come into play? Any pointers/suggestions would be appreciated. -Thanks in advance.

Just wanted to update this.
Because I use Business Objects OEM, I didn't have direct support with SAP/Business Objects. However, because of this issue (and other issues) we purchased Business Objects Edge 3.0.
After getting BOE 3 installed/configured, I migrated those reports and underlying Business Views over.
And guess what? The problem still occurred on the new platform.
I then created a support incident and the person that initially tried to help me couldn't figure out what was going on.
However, during that time, I did try re-creating the report using a newer version of Crystal (Crystal 2008) and the problem went away. (note, I didn't recreate the business views.. just the reports).
So bottom line:
I created all reports from scratch instead of using the reports that I migrated from BO XI R2/CR XI and no longer had the problem.
The techs never figured out the exact cause of the issue.
So far, my experience with their support has been the same on all incidents. They don't seem to be trained (at least at the 1st level) for actually using the debug/logs/etc to help quickly pinpoint/analyze issues. They do basically like I do (the end user) and smartly poke around and do trail/error. I have yet to get a support tech that knew the exact nature of my issue and could solve it without this kind of trial/error approach.

ICM - Timeout Parameters

Hi All,
We are facing issues with ICM only in one of the app servers. It is taking more load and going to emergency mode only in one app. I looked at ICM services in both instances
No. Protocol           Service Name/Port    Host Name            Keep Alive          Proc.Timeo Actv External Bind
1 HTTP               8000                                  Host2               9,999,999                  1-
2 SMTP               0                                        Host2               30                        9,999,999
icm/server_port_0     = PROT=HTTP,PORT=8000,PROCTIMEOUT=-1
No. Protocol           Service Name/Port    Host Name         Keep Alive             Proc.Timeo Actv External Bind
1 HTTP               8001                                 Host1               30                                              9,999,999
2 SMTP               0                                      Host1               30                                                9,999,999
icm/server_port_0     = PROT=HTTP,PORT=8001
Problem is with Host2. I see differences here. Please help fixing the issue. Which timeout parameter should I modify? If I just remove Proctimeout=-1, will it fix issue. Production is getting affected. PLs advise ASAP.
Thanks,
Kavitha Rajan.

Great - sorry I misunderstood you at first.
So the users come into the webdispatcher on the address -> http://host1/sap/bc/bsp/sap/crm_ui_frame/default.htm -> this represents the address of the Web Dispatcher. The dispatcher however, seems to be over loading one of the application servers on the ABAP backend.
A few items I'd check then:
1) Logon to the admin console for the Web Dispatcher itself. Check to ensure that it is indeed seeing all of the logon groups configured in the ABAP backend.
2) Check the configurations of the ABAP logon groups for any issues - i.e. they are excluding servers.
3) Check the configuration of the ICM parameters in each of the ABAP servers - they should all be identicial unless you have exceptions noted.
4) For the Web Dispatcher itself, you may wish to set it up for a 'large system' scenerio with values like this:
icm/max_conn
icm/max_sockets
icm/req_queue_len
icm/min_threads
icm/max_threads
mpi/total_size_MB
mpi/max_pipes
16384
16384
6000
100
250
500
21000
The Web Dispatcher uses the configuration under "Accesssability of Message Server" to determine the location of a ABAP / J2EE message server and in turn read back the available logon groups. If the Web Dispatcher is seeing the logon groups correctly, then it's something to do with either the ICM settings on each app server or the logon group configurations itself.
The only thing I see odd here is that the servername for the Web Dispatcher is "HOST 1" but under the instance profile you have:
# Accesssability of Message Server
rdisp/mshost = Host1
ms/http_port = 8101
So unless that's a typo, are the WD and ABAP stack on the same server? "rdisp/mshost" should be pointing to the servername where the message server service (CI typically) is running for the ABAP stack.
Hope this helps.
Tim

Changing timeout parameters

In this blog:
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
mr Michal Krawczyk says changing parameters like xiadapter.inbound.timeout.default should be avoided. However our current problem is really the 180000 millisecond (=3minutes) limit that derives from this setting. Some RFC calls just take more time in the backend system.
Can this particular parameter be changed or not?
The parameter name "...default" sounds like it is just a default and you could override it with some other parameter. But this is just my imagination? I know that there exists parameter syncMessageDeliveryTimeoutMsec as a property of the RfcAdapter J2EE Service (Michal has also mentioned this), but the value of it is already much larger than xiadapter.inbound.timeout.default.
br: Kimmo
PS. I will not reward with points for answers like "optimize you backend RFC function modules and no timeout will occur".

No, I did not changed syncMessageDeliveryTimeoutMsec because it is sufficient already ( 300000 msec ). And the error message MessageExpiredException ( full error message is "com.sap.aii.af.ra.ms.api.MessageExpiredException: Message 433f56a0-2e99-11db-b6e6-00112540039c(INBOUND)" comes exactly after 3minutes (=180000 msec), that's why I believe the limitation comes from the parameter xiadapter.inbound.timeout.default whose value is 180000.
To be honest, I have some doubts, that execution of RFC-function module does NOT take 3mins. I have tested the rfc fm with same parameters as timeouted messages with SE37 in the backend system and they run quickly. I have been thinking if the RFC-adapter have trouble receiving the call due to sudden system overload and therefore gives MessageExpiredException.
But why I cannot change the parameter xiadapter.inbound.timeout.default?
In your blog Michal you say it's denied in note 791379 but I don't find a word there that denies the change.
br: Kimmo

SSRS Integrated mode failes (timeout) when executing lengthy reports.

Hi All,
I have SSRS 2008 R2 running in integrated mode with SharePoint 2010 foundation. The SharePoint farm and SSRS are both configured for Kerberos authentication. Both SSRS and SharePoint are working well. The vast majority of reports
compile in less than 30 seconds, users are generally happy.
Except, I have a couple of reports which take a long time to execute on the SQL side, I cant change this, that's just how it has to be. The simplest of the reports to explain is a report, with 1 parameter with four values, which performs
up to four actions on the SQL Server and then returns around two dozen rows of the result, typically the entire process completes in around 10 minutes. If I run this report via the ssrs /reportserver WFE the report always completes, results are presented
on screen, no issues whatsoever. When I run the same report from within SharePoint, its a different story, the report will complete only if I select just one of the four parameter actions, resulting in the total report execution time of
around 4 minutes, However when running the report with all four parameters selected, the loading spinner appears, then after 6 minutes, disappears entirely. The page returns to the parameter selection, no results are presented.
Having checked all the SSRS log files and ExecutionLogStorage table, they suggest that the report carries on building in the background, and then completed roughly 10 minutes after starting.
So my conclusion is that something in SharePoint does not like the extended duration of the report execution. But what is it, What triggers the 6 minute timeout?
Any help much appreciated.
Regards
Dan

Hi danbridgland,
According to your description, there are a couple of reports in SSRS Sharepoint integrated mode. The query takes a long time to execute in SQL Server. When you run the report via Sharepoint WFE, the report works fine. When you run the report in Sharepoint
Application, the report will be displayed if you select one parameter value, if four values of the parameters are selected, the report disappears after 6 minutes’ loading.
In Native mode, SSRS uses a default timeout of 9000 seconds. In SharePoint integrated mode the timeout is reduced to 120 seconds. The timeout in SharePoint is actually related to the fact that reports are rendered using the http runtime. Any operation that
is launched from within SharePoint using the httpRuntime object has to complete within the timeout parameters. In this case, we can directly editing timeout in web.config by following steps:
Locate web.config for the SharePoint site you have configured for SSRS integration (default location: C:\inetpub\wwwroot\wss\VirtualDirectories\80).
Open the file in an XML or text editor.
Navigate to httpRuntime element, inside the tag, add executionTimeout="9000".
In addition, in SharePoint integrated mode, reports typically run slower than when the same reports run in native mode. One main cause of this latency can be attributed to SharePoint object model calls that are made. For detail information, please refer
to the following document:
http://support.microsoft.com/kb/2216504
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu

Apex Version 4.2: Why doesn't the session timeout parameter settings work?

Prior to an upgrade to Apex Version 4.2.0.00.27, we ran Apex Version 4.1 in our environment. This is on a platform using Oracle Database Enterprise Edition 11g R2 on Windows Server 2008. The session timeout parameters (set for a single application using "Shared Components" -> "Security Attributes") were set to the following:
Maximum Session Time: 1 day
Maximum Session Idle Time: 8 hours
This worked with no problems in Apex 4.1; our user would leave a data entry form open for several hours, complete the data entry then submit the page. Now, with the upgrade to Apex 4.2, doing the same thing causes the system to redirect to the login page and aborting any edits or new data entered into the form previously.
I have tried to set both session parameters to ZERO (0) which is what the documentation explains is the equivallent to "no timeout" but that didn't work as well.
I have reset the session control parameters to what they were before the upgrade and my session times out before the time values I set. (on the version 4.2 upgraded instance).
Why was the session timeout parameters I set ignored by the system? Can anyone else out there confirm/repeat the problem I observed?

Hi Richard,
You probable have it ok, but the time should be in seconds.
Kees

Need to warn user of session timeout in BSP app hap_document......

Hi,
We're using the hap_document app to allow employees to change appraisal documents in ESS and for managers to create them thru MSS....
When employees have their documents open for more than 1 hour, the next time they click on save, it takes them to the session timeout (ICM, version 6040, module icxxthr_mt.c)....
Is there a way to add a timer to the document.htm or body.htm pages in the application to start a timer, reset it each time user clicks on save, and warn him with a popup when we're within 5 minutes to a timeout...
I've read messages on the BSP thread that say...
"Document.htm is split in two frames. One hidden to enable session handling, the second one visible which contains the document.
So the document.htm is not refreshed, the second frame is refreshed. I tried your approach as well and was not able to tie the script to the second frame.
Regards and Groetjes,
Maurice"
I've also read Thomas's stateful/stateless timeout parameters article...
Can anyone help me with where I would put the timer javascript code (if not in document.htm or body.htm) and which timeout parameter to check...
Thanks for all your help,
Venkatesh

Look at the sample code..Will solve your problem..
<%@page language="abap" %>
<%@extension name="htmlb" prefix="htmlb" %>
<script type="text/javascript">
function remind() {
var msg = "Your Session will be timed out in 10 Secs";
alert(msg);
</script>
<htmlb:content design="design2003" >
<%
data: v_rem type string.
DATA: port TYPE STRING.
port = request->get_header_field( if_http_header_fields_sap=>server_port ).
DATA: services TYPE TABLE OF ICM_SINFO.
CALL FUNCTION 'ICM_GET_INFO' TABLES SERVLIST = services.
FIELD-SYMBOLS: <service> TYPE ICM_SINFO.
DATA: wait TYPE STRING.
READ TABLE services ASSIGNING <service> WITH KEY service = port.
wait = <service>-KEEPALIVE - 10.
CONDENSE wait.
concatenate `'remind(` wait `)',2000` into v_rem.
%>
<htmlb:page onLoad = "setTimeout(<%= v_rem %>)"
              title = " " >
    <htmlb:form>
      <htmlb:textView text   = "Hello World!"
                      design = "EMPHASIZED" />
      <htmlb:button text    = "Press Me"
                    onClick = "myClickHandler" />
    </htmlb:form>
</htmlb:page>
</htmlb:content>
<i>* Reward each useful answer</i>
Raja T

Report of DeskI on web goes on timeout

Post Author: Roberto Cassoni
CA Forum: Desktop Intelligence Reporting
Hi,
I'm using BO XI R2 Sp2. When I launch my report from Infoview my report goes on timeout ( but i'm not sure that depends from several parameters timeout ) and Infoview is blocked. Launching the same report from Full Client I doesn't have any problem: in 10 seconds I have my good report.
I followed all support KB, putting all interested timeout parameters to 20 minutes ( Support Advised )
Who has the same problem?
Tks

Post Author: Roberto Cassoni
CA Forum: Desktop Intelligence Reporting
Yes I checked the control parameters of the universe. I also applied the KB article 6285653, and i had a better result: the report are created without data.
With Full client i haven't got problems

XI adapter polling issue & JDBC / DB2 driver connection timeout properties

Hello Group,
We have a long running issue with our XI 7.0 system running on iseries. (V5R3) The issue occuring is that our XI adapters stop polling and the only resolution is to restart the J2EE engine or to resart the adapter framework services.
We have had several OSS messages open on this subject for over a year and are going round in circles with the a number of different SAP consultants.
The one topic that we keep coming back to is that we are being asked to set DB2 driver connection timeout properties. We are using the toolbox driver and have upated to the latest JTopen driver, but have not managed to find any inofrmation on how to set the timeout parameter. Does anyone know where the timeout parameter set?
Has anyone experienced polling issue like this before and how did you resolve?
SAP referred to the SAP note 1078420 - XI/PI JDBC Adapter: Setting JDBC driver properties for DB which is for Oracle, but this will give an idea of what timeout parameters SAP are asking about.
Extract of the note is below:-
Symptom
This note gives an option to set JDBC driver properties while acquiring a DB connection. When connecting to DB using JDBC adapter there are instances
where DB connection take a long time to establish connection. Some times call made to Driver will hang permanently. Setting driver properties would resolve this problem.
More Terms
Connection timeout, time out, query timeout
Cause and Prerequisites
Solution
In the advanced mode table section of sender channel and receiver channel configurations, we can set driver properties for each DB connection. Any
such property would have to contain prefix 'driver:'(with out quotes) For example, for Oracle Database JDBC thin driver 10.2.0.3 version, the
property oracle.jdbc.ReadTimeout helps to set read timeout while reading from the socket. Also for setting login time out in Oracle, we use
oracle.net.CONNECT_TIMEOUT. To set these two properties use as follows:
driver:oracle.jdbc.ReadTimeout 1000
driver:oracle.net.CONNECT_TIMEOUT 1000
(The TimeOut Driver properties like ReadTimeout and CONNECT_TIMEOUT are in milliseconds)
Refer to your DB documentation/ JDBC driver documentation on this. Please note that properties can vary from each driver version. For instance, some
of properties of Oracle JDBC thin Driver 10.2.0.3 properties may not be present in older version drivers. Please contact DB vendor for the complete
list of driver properties. In addition to above, we also provide another parameter for query time out.
sqlquerytimeout (prefix 'driver:' is not required) is the parameter that is to be used for SQL query time out. This is case-sensitive and should be
configured as positive integer value in seconds(greater than 0).
Any help on this would be much appreciated.
With regards,
Steven

Hello,
I am not talking about the XI timeouts. But the timeouts which can be used to get the connection timeouts for DB2/AS400 databases.
So please provide that information.
THanks,
soorya

HTTP_RESP_STATUS_CODE_NOT_OK -- 500 -- Timeout

Hi Guys,
There is 1 msg gone to error status with below error .
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Timeout</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 500 with the description Timeout Error when sending by HTTP (error code: 500, error text: Timeout)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
This error happened only once and again all the msgs for the same interface processing successfully.
Scenario is: proxy --> XI --> IDoc(Asynchronous)
Could any one plz let me know wht could be the problem that time?
Thanx,
Kumar

Hi Kumar,
as far as I understood your problem, the Timeout error occurs when sending from
ABAP Proxy (?) to the Integratin Server, correct?
Please check with transaction SMICM on both sides the trace file and the parameter settings for the http protocol.
It could be that your message is quite large, and therefore the default values of 60 seconds are to small defined.
In general for Timeout settings, there is a nice unit called "Timeouts in XI" in the XI3.0/XI7.0 Troubleshooting Guide available at
<a href="http://service.sap.com/instguidesNW70">http://service.sap.com/instguidesNW70</a> > Operations
- Process Integration: <a href="http://Troubleshooting Guide - SAP XI 3.0/SAP NW 7.0">http://service.sap.com/~sapidb/011000358700005909032005E.PDF</a>
Extract from the guide, which should be also valid for your case:
ICM 402 timeout for http client calls (IS -> AF): ICM_HTTP_TIMEOUT
Value for all ports: icm/keep_alive_timeout (Default: 60 seconds)
Value for specific ports:
icm/server_port_0 = PROT=HTTP,PORT=<icmhttpport>, TIMEOUT=30, PROCTIMEOUT=900
PROCTIMEOUT not set > TIMEOUT is used > TIMEOUT not set > icm/keep_alive_timeout is used
Default: TIMEOUT and PROCTIMEOUT not set >icm/keep_alive_timeout is used
In the event of errors, increase the PROCTIMEOUT value for the HTTP/HTTPS ports used.
Do not increase icm/keep_alive_timeout or the TIMEOUT value as this would lead to a higher resource consumption.
For more information, see SAP Note 824554 - ICM timeout parameters.
Best regards,
Silvia

Solution Manager 7.1 SP4: Session Timeout during SOLMAN_SETUP

Hello Experts,
We recently installed Solution Manager 7.1 SP4 on Linux/Oracle. We also completed the System Preparation and Basic Configuration part of the SOLMAN_SETUP wizard as well (which includes applying the Central Correction Note and other steps).
During the Managed System Setup Part, as soon as we click on the Configure System for a managed system - a new window opens up and immediately we get the below timeout messages:
This session will terminate due to inactivity in 0:00 minutes
To continue working in this session, choose 'Continue Session'
The above is immediately followed by the actual session timeout message:
This session terminated due to inactivity.
Click Close Popup
or to start new session, press F5.
Now even if we press F5/Refresh, the same cycle repeats.
I already checked the ICM timeout parameters as mentioned in the Guide and further findings with regards to ITS update as in thread WEBGUI Timeout immediately after logging in
Applying the latest kernel patch also did not help. The strange issue is that the session timeout occurs only the LMDB related services, wherease normal services like WEBGUI etc work fine.
Please suggest if anyone came across this issue, especially after update to SP04.
Thanks and Regards,
Srikishan

Hi,
Thanks, I will check the note steps and close this thread accordingly.
Perhaps I need to hone my notes searching skills !
Regards,
Srikishan

Changeing Transaction timeouts

Hi..
While trying to tune the WLI ejbs, I came across the following documentation
on edocs.bea.com. It mentions to change the trans-timeout-seconds attribute
for the wlpi-ejb.jar file.
But when I accessed the ejb descriptor using weblogic console, I could not
find the trans-timeout-seconds attribute in the ejb-jar.xml. Can anyone
please inform me where to find it ?
Configuring EJB Transactions
If your system returns an exception indicating that a transaction timed out
while a message was being processed, we recommend that you tune the
transaction timeout parameters in the following BPM resources:
a.. WLI-BPM Server (wlpi-ejb.jar)
b.. WLI-BPM Event Processor EJB (wlpi-mdb-ejb.jar)
Note: Transaction timeouts are more likely to occur when large messages,
rather than small messages, are being processed.
To tune the transaction timeout parameters, we recommend that you change the
trans-timeout-seconds attribute in the wlpi-ejb.jar and wlpi-mdb-ejb.jar
files from 90 seconds to 1090 seconds. To access the JAR files:
1.. In the Administration Console navigation tree, select
Deployments->EJB.
2.. Select WLI-BPM Server EJB or WLI-BPM Event Processor EJB.
3.. Click Edit EJB Descriptor to display a new window in which you can
edit the EJB descriptor.
Thanks..
Mandar

Hi,
The trans time out value is set in "weblogic-ejb-jar.xml" Choose edit EJB descriptor
for BPM server,In wlpi-ejb.jar, there are three jars, choose weblogic EJB jar.
You can find the Transaction descriptor in Weblogic Enterprise beans.
Regards,
Anandhi
"Mandar Gandhe" <[email protected]> wrote:
Hi..
While trying to tune the WLI ejbs, I came across the following documentation
on edocs.bea.com. It mentions to change the trans-timeout-seconds attribute
for the wlpi-ejb.jar file.
But when I accessed the ejb descriptor using weblogic console, I could
not
find the trans-timeout-seconds attribute in the ejb-jar.xml. Can anyone
please inform me where to find it ?
Configuring EJB Transactions
If your system returns an exception indicating that a transaction timed
out
while a message was being processed, we recommend that you tune the
transaction timeout parameters in the following BPM resources:
a.. WLI-BPM Server (wlpi-ejb.jar)
b.. WLI-BPM Event Processor EJB (wlpi-mdb-ejb.jar)
Note: Transaction timeouts are more likely to occur when large messages,
rather than small messages, are being processed.
To tune the transaction timeout parameters, we recommend that you change
the
trans-timeout-seconds attribute in the wlpi-ejb.jar and wlpi-mdb-ejb.jar
files from 90 seconds to 1090 seconds. To access the JAR files:
1.. In the Administration Console navigation tree, select
Deployments->EJB.
2.. Select WLI-BPM Server EJB or WLI-BPM Event Processor EJB.
3.. Click Edit EJB Descriptor to display a new window in which you
can
edit the EJB descriptor.
Thanks..
Mandar

Timeout on Client Proxy

Hi
When running an ABAP client proxy in an ECC system I get the following error message:
HTTP Response Contains status code 500 with the description of Timeout.
I have increased the HTTP timeout parameters to according to the blog (Points 1 & 2):
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
but with no success. Can anyone please advise further ?.
A point to note that this does not happen with all messages only larger ones.
Thanks in advance ...

hi,
>>the timeouts were increased by basis team on the R/3 backend and there was a restart following this.
I'd stay with my initial answer - it's http timeout parameter
maybe it was not done in a proper way by your basis
HTTP timeout is HTTP timeout - unless there is some more errors
which you did not see
BTW - about packages
I've never heard about anything like abap proxy packages
I don't think he meant any XI functionality
Regards,
Michal Krawczyk

SMQS transaction and Vertex calls timeout

Hi,
    We just went live with one our SD projects. Before we went live we never had Vertex timeout issue, but after we went live we started getting 0 or 2 or sometimes 4 dumps in a day "CALL_FUNCTION_REMOTE_ERROR" The function where it dumps is RFC_CALCULATE_TAXES_DOC destination VERTEX. The description says "timeout during allocate" no connect of TP /usr/lpp/vertex/translink/verrfc from
host ansapap7 after 122 sec" .
RFC status: "CODE=CM_PRODUCT_SPECIFIC_ERROR CM_NO_STATUS_RECEIVED
CM_NO_DATA_RECEIVED SAPCODE=456 CONV=06153020"
RFC error text: "RFC_IO27"
CPI-C error text: "CPIC-CALL: 'ThSAPCMRCV'#Timeout during connection setup
(check that partner exists) "
Wierd thing is that it does not happen all the times. It happens 3 to 4 times in a day, sometimes it happens only once and sometimes does not happen at all.
I checked the SMQS transaction, it shows destination Vertex, max connection 1, max timeout 60. With this setting since last 3 + years we never had timeout issue, then why now when we have some 500 more orders being processed per day. These settings are still working for majority of orders, only some orders could pass through and get this dump.
Can someone guide me what this problem can be. Also can someone tell me is it safe to change the max connections and max timeout parameters in SMQS transactions and will changing those settings help in solving this.
Thanks in advance
Pulin

I had checked 645527 note also. We have not upgraded SAP since last 3 yrs. Its still 4.7, we have not applied any upgrade patches. It started happening after we went live on November 4th 06.
I think, this is some load distribution issue. Should I change the settings in SMQS transaction. Is that safe ?
If any one of you are using Vertex with SAP 4.7 or higher, then can you tell me what is present in table TTXC. Does this table contain old RFC calls(RFC_CALCULATE_TAXES1) or new RFC names(RFC_CALCULATE_TAXES_DOC).?

Processing timeout VS. keepalive timeout

Hi,
According to note 824554 there are two timeouts parameters:
icm/server_port_ < n > = ...,PROCTIMEOUT=< s > that sets the process timeout
and
icm/server_port_ < n > = ...,TIMEOUT=< s > that sets the timeout of a live process after it is complete.
If I get "Pipeline timeout condition satisfied" error in my XI system, how can I
determine what parameter between the two above, I need to increase ?
and ... why HTTP_TIMEOUT parameter in sxmb_adm referenced to TIMEOUT parameter and not to PROCTIMEOUT ?
Please advice,
Dimitry Haritonov

I can give you a way out for session timeout.
Lets say you have a session variable say username which you are rendering in every page after storing in the session for the first time. Now in the action you can check for the session variable, username not null. If it is null, you can forward it to the different jsp page.
Hope you get this and it works for you

ASM timeout parameters?

Similar Messages

Maybe you are looking for