Which timeout is killing me?

I hava one process loading 30,000 entries into NamedCache and then launching a remote task via InvocationService.execute call
this task on the remote node loads the entries from the cache one by one until about 30 seconds later it is interrupted:
(Wrapped) java.lang.InterruptedException
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:59)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:11)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.get(DistributedCache.CDB:24)
at com.tangosol.util.ConverterCollections$ConverterMap.get(ConverterCollections.java:1522)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$ViewMap.get(DistributedCache.CDB:1)
at com.tangosol.coherence.component.util.SafeNamedCache.get(SafeNamedCache.CDB:1)
at com.my.coherence.CoherenceMember.initData(CoherenceMember.java:85)
at com.my.coherence.CoherenceTask.run(CoherenceTask.java:61)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.InvocationService.onInvocationRequest(InvocationService.CDB:10)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.InvocationService$InvocationRequest.onReceived(InvocationService.CDB:40)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onMessage(Grid.CDB:9)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:136)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:485)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:31)
... 13 more
and I get memberFailed in the master node. I run with default development mode config and wonder which of the timeout settings should I adjust to give my task more time?
I've also tried adding
<request-timeout>310000</request-timeout>
<task-timeout>310000</task-timeout>
<task-hung-threshold>310000</task-hung-threshold>
into <distributed-scheme> but this does not help :(

This is likely the Service Guardian killing a long running invocation.
Use the following property override to set it to an arbitrary new timeout in milliseconds:
-Dtangosol.coherence.guard.timeout=60000 // sets it to 60 seconds
Setting it to 0 turns it off.
More about the Service Guardian in Patrick Peralta's blog post here:
http://blackbeanbag.net/wp/2009/07/20/coherence-3-5-service-guardian-deadlock-detection/
And more about the configuration for the guardian here:
http://wiki.tangosol.com/display/COH35UG/service-guardian
/Christer

Similar Messages

Timeout: Tuxedo kills the service but not the database connection

Hi all,
I am experiencing some performance problems on my system due an efficient SQL and a Tuxedo improper timeout handling.
A service is using a "problematic" SQL (we will tune it but it's not the main problem). After 60 seconds from the execution, Tuxido kills the services for a timeout.
At this point I would like Tuxedo to notify DB2 database as well in order to stop processing the SQL. Instead the SQL continues running on the database (also if the service is killed) and this produce a gradual slow down of the performances.
In the UBBCONFIG, we are using a service configuration like the following timeout configuration:
.RESOURCES
SCANUINIT 5
SANITYSCAN 6
BLOCKTIME 12
.SERVICES
DEFAULT: SVCTIMEOUT=45
service1 SVCTIMEOUT=60 TRANTIME=60
service2 SVCTIMEOUT=60 TRANTIME=60
Note: not all the services are listed in the .SERVICES section and we are using the default NOTIFY as well as an OPENINFO.
Can you please help me in finding a configuration to kill both the services and the database?
Thanks in advance,
Benedetto

Hi Benedetto.
First of all, Tuxedo doesn't kill services, it kills servers. Your UBBCONFIG file specifies three timeouts, BLOCKTIME, SVCTIMEOUT, and TRANTIME.
BLOCKTIME specifies how long a Tuxedo API that needs a response will wait for that response. If the response isn't received in that period of time, Tuxedo will return TPETIME to the caller. As with any failure, if the request was part of a transaction, the transaction is marked rollback only. Note, this timeout does not affect the request, whether sitting in a server's IPC queue or currently executing in a server.
SVCTIMEOUT is a much more severe timeout and determines how long Tuxedo will allow a service implementation to execute. If a service implementation doesn't reply within the SVCTIMEOUT period, Tuxedo will issue an OS level KILL request to kill the process. If the server is marked restartable, Tuxedo will then try to restart the server assuming none of the restart limits have been reached. Killing the server causes the request to be lost within the server so the caller will stay blocked until BLOCKTIME is reached at which point the above actions will take place.
TRANTIME is the amount of time Tuxedo allows a transaction to remain active and viable. When this period expires, Tuxedo will mark the transaction as timed out with the only option being rollback. As well, Tuxedo aborts any API requests that would normally cause messaging to occur, i.e., making a tpcall() within a timed out transaction will fail without any attempt to call the service.
So in your case, the issue is partially that you have the values of your timeouts in somewhat reverse order. Typically we see BLOCKTIME being the smallest value, with TRANTIME typically larger than BLOCKTIME, and SVCTIMEOUT larger even still, although there are good reasons for exceptions to this guideline. Part of the reasoning behind this is that killing a server is a significant thing and its usually best to try and let the server complete whatever its doing, if if the work has been timed out either due to BLOCKTIME or TRANTIME, since the cost of killing and restarting a server is significant.
Tuxedo will notify the database of the transaction status when the application finally issues a tpcommit() or a tpabort() request, but not until then. Although, if SVCTIMEOUT is hit, then killing the server should cause the database connection to be lot.
If you could describe the behavior you are seeing and the relevant portions of your ULOG we can try to make some sense of what is happening.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

How to find which user has killed a particular job in CPS?

Hi All,
I am new in CPS. I want to find the user who has killed a particular job in CPS?
Thanks in Advance.
Avdhesh

Hi Gerben,
Thanks for the reply.
But I noticed when I killed a job and checked in the last modified by option I didn't find my user name there. It was displaying the user who had modified that job definition last time.
Thank you
Avdhesh

Which version of iTunes 9 is killing iPods?

Hi Everyone: I've been reading the horror stories about the new version of iTunes that's ruining everyone's iPod and I have the very newest version...9.0.1 that I just downloaded. When I had 9.0, it recognized my iPod but wouldn't sync it...which I've also read about. Now I'm afraid to hook up my iPod with the 9.0.1. Does anyone know which version is killing the iPods? And should I go back to an earlier version? I'm scared to death to hook my iPod up to this newest version. I'm having enough problems with getting all of my music off of my iPod onto my new computer that I don't want to kill my iPod since that's the only place I have all of my music. Thanks SO much if there is anyone out there that can help

late response...like us mac user the problem exists. There is a problem with sync between itunes and ipod(s) - (classic for me). I went thru fraustrations of re-store, re-format, re-set and a host of recommended soluctions from apple or users to get my classic running well again. No solution yet, it is a conflict with sync on the ipod, it seems that it won't handle large transfers of files, maybe one or two before it freezes itself and iTunes,too. I was ready to abandon the classic but now I'll wait for an apple fix. Classic is a good ipod, but when sync conflict occurs it shut itself down or go into deep freeze...like here in the Arctic

How to kill Forms Runaway Process using 95% CPU and running for 2 hours.

We had a situation at E-Business Suite customer (using Oracle VM server) where some of Form processes were not being cleared by form timeout settings automatically.
Also when user exits the form session from front end, the linux form process (PID) and DB session did not exit properly, so they got hung.
They were spiking CPU and memory usage and causing e-business suite to perform slowely and ultimately causing VM host to reboot the production VM guest (running on Linux).
We could see the form processes (PIDs) using almost 100% cpu with "top" command and running for a long time.
Also we verified those Form Sessions did not exist in the application itself.
ie. Using from Grid Control -> OAM-> Site Map -> Monitoring (tab) -> "Form Sessions".
It means that we could safely kill that form process from Linux using "kill -9 <PID>" command.
But that required a continuous monitoring and manual DBA intervention as customer is 24x7 customer.
So, I wrote a shell script to do the following;
•     Cron job runs every half an hour 7 days a week which calls this shell script.
•     Shell script runs and tries to find "top two" f60webmx processes (form sessions) using over 95% cpu with 2 minutes interval.
•     If no process is found or CPU% is less than 95%, it exits and does nothing.
•     If top process is found, it searches for its DB session using apps login (with hidden apps password file - /home/applmgr/.pwd).
a.     If DB session is NOT found (which means form process is hung), it kills the process from unix and emails results to <[email protected]>
b.     If DB session is found, it waits for 2 hours so that form process times automatically via form session timeout setting.
It also emails the SQL to check the DB session for that form process.
c.     If DB session is found and it does not timeout after 2 hours,
it kills the process from unix (which in turn kills the DB session). Output is emailed.
This are the files required for this;
1. Cron job which calls the shell script looks like this;
# Kill form runaway process, using over 95% cpu having no DB session or DB session for > 2hrs
00,30 * * * * /home/applmgr/forms_runaway.sh 2>&1
2. SQL that this script calls is /home/applmgr/frm_runaway.sql and looks like;
set head off
set verify off
set feedback off
set pagesize 0
define form_client_PID = &1
select count(*) from v$session s , v$process p, FND_FORM_SESSIONS_V f where S.AUDSID=f.audsid and p.addr=s.paddr and s.process='&form_client_PID';
3. Actual shell script is /home/applmgr/forms_runaway.sh and looks like;
# Author : Amandeep Singh
# Description : Kills runaway form processes using more than 95% cpu
# and Form Session with no DB session or DB session > 2hrs
# Dated : 11-April-2012
#!/bin/bash
. /home/applmgr/.bash_profile
PWD=`cat ~/.pwd`
export PWD
echo "`date`">/tmp/runaway_forms.log
echo "----------------------------------">>/tmp/runaway_forms.log
VAR1=`top -b -u applmgr -n 1|grep f60webmx|grep -v sh|grep -v awk|grep -v top|sort -nrk9|head -2|sed 's/^[ \t]*//;s/[ \t]*$//'| awk '{ if ($9 > 95 && $12 = "f60webmx") print $1 " "$9 " "$11 " "$12; }'`
PID1=`echo $VAR1|awk '{print $1}'`
CPU1=`echo $VAR1|awk '{print $2}'`
TIME1=`echo $VAR1|awk '{print $3}'`
PROG1=`echo $VAR1|awk '{print $4}'`
PID_1=`echo $VAR1|awk '{print $5}'`
CPU_1=`echo $VAR1|awk '{print $6}'`
TIME_1=`echo $VAR1|awk '{print $7}'`
PROG_1=`echo $VAR1|awk '{print $8}'`
echo "PID1="$PID1", CPU%="$CPU1", Running Time="$TIME1", Program="$PROG1>>/tmp/runaway_forms.log
echo "PID_1="$PID_1", CPU%="$CPU_1", Running Time="$TIME_1", Program="$PROG_1>>/tmp/runaway_forms.log
echo " ">>/tmp/runaway_forms.log
sleep 120
echo "`date`">>/tmp/runaway_forms.log
echo "----------------------------------">>/tmp/runaway_forms.log
VAR2=`top -b -u applmgr -n 1|grep f60webmx|grep -v sh|grep -v awk|grep -v top|sort -nrk9|head -2|sed 's/^[ \t]*//;s/[ \t]*$//'| awk '{ if ($9 > 95 && $12 = "f60webmx") print $1 " "$9 " "$11 " "$12; }'`
PID2=`echo $VAR2|awk '{print $1}'`
CPU2=`echo $VAR2|awk '{print $2}'`
TIME2=`echo $VAR2|awk '{print $3}'`
PROG2=`echo $VAR2|awk '{print $4}'`
PID_2=`echo $VAR2|awk '{print $5}'`
CPU_2=`echo $VAR2|awk '{print $6}'`
TIME_2=`echo $VAR2|awk '{print $7}'`
PROG_2=`echo $VAR2|awk '{print $8}'`
HRS=`echo $TIME1|cut -d: -f1`
exprHRS=`expr "$HRS"`
echo "PID2="$PID2", CPU%="$CPU2", Running Time="$TIME2", Program="$PROG2>>/tmp/runaway_forms.log
echo "PID_2="$PID_2", CPU%="$CPU_2", Running Time="$TIME_2", Program="$PROG_2>>/tmp/runaway_forms.log
echo " ">>/tmp/runaway_forms.log
# If PID1 or PID2 is NULL
if [ -z ${PID1} ] || [ -z ${PID2} ]
then
echo "no top processes found. Either PID is NULL OR CPU% is less than 95%. Exiting...">>/tmp/runaway_forms.log
elif
# If PID1 is equal to PID2 or PID1=PID_2 or PID_1=PID2 or PID_1=PID_2
[ ${PID1} -eq ${PID2} ] || [ ${PID1} -eq ${PID_2} ] || [ ${PID_1} -eq ${PID2} ] || [ ${PID_1} -eq ${PID_2} ];
then
DB_SESSION=`$ORACLE_HOME/bin/sqlplus -S apps/$PWD @/home/applmgr/frm_runaway.sql $PID1 << EOF
EOF`
echo " ">>/tmp/runaway_forms.log
echo "DB_SESSION ="$DB_SESSION >>/tmp/runaway_forms.log
# if no DB session found for PID
if [ $DB_SESSION -eq 0 ] then
echo " ">>/tmp/runaway_forms.log
echo "Killed Following Runaway Forms Process:">>/tmp/runaway_forms.log
echo "-------------------------------------------------------------------">>/tmp/runaway_forms.log
echo "PID="$PID1", CPU%="$CPU1", Running Time="$TIME1", Program="$PROG1>>/tmp/runaway_forms.log
kill -9 $PID1
#Email the output
mailx -s "Killed: `hostname -a` Runaway Form Processes" [email protected] </tmp/runaway_forms.log
cat /tmp/runaway_forms.log
else
# If DB session exists for PID
if [ ${exprHRS} -gt 120 ]; then
echo $DB_SESSION "of Database sessions exist for this forms process-PID="$PID1". But its running for more than 2 hours. ">>/tmp/runaway_forms.log
echo "Process running time is "$exprHRS" minutes.">>/tmp/runaway_forms.log
echo "Killed Following Runaway Forms Process:">>/tmp/runaway_forms.log
echo "-------------------------------------------------------------------">>/tmp/runaway_forms.log
echo "PID="$PID1", CPU%="$CPU1", Running Time="$TIME1", Program="$PROG1>>/tmp/runaway_forms.log
kill -9 $PID1
#Email the output
mailx -s "`hostname -a`: Runaway Form Processes" [email protected] </tmp/runaway_forms.log
cat /tmp/runaway_forms.log
else
echo "Process running time is "$exprHRS" minutes.">>/tmp/runaway_forms.log
echo $DB_SESSION "of Database sessions exist for PID="$PID1" and is less than 2 hours old. Not killing...">>/tmp/runaway_forms.log
echo "For more details on this PID, run following SQL query;">>/tmp/runaway_forms.log
echo "-----------------------------------------------------------------------">>/tmp/runaway_forms.log
echo "set pages 9999 lines 150">>/tmp/runaway_forms.log
echo "select f.user_form_name, f.user_name, p.spid DB_OS_ID , s.process client_os_id,, s.audsid, f.PROCESS_SPID Forms_SPID,">>/tmp/runaway_forms.log
echo "to_char(s.logon_time,'DD-Mon-YY hh:mi:ss'), s.seconds_in_wait">>/tmp/runaway_forms.log
echo "from v\$session s , v\$process p, FND_FORM_SESSIONS_V f">>/tmp/runaway_forms.log
echo "where S.AUDSID=f.audsid and p.addr=s.paddr and s.process='"$PID1"' order by p.spid;">>/tmp/runaway_forms.log
mailx -s "`hostname -a`: Runaway Form Processes" [email protected] </tmp/runaway_forms.log
cat /tmp/runaway_forms.log
fi
fi
else
#if PID1 and PID2 are not equal or CPU% is less than 95%.
echo "No unique CPU hogging form processes found. Exiting...">>/tmp/runaway_forms.log
cat /tmp/runaway_forms.log
fi
If you have the same problem with some other unix and DB processes, the script can be easily modified and used.
But use this with thorough testing first (by commenting out <kill -9 $PID1> lines.
Good luck.
Edited by: R12_AppsDBA on 19/04/2012 13:10

Thanks for sharing the script!
Hussein

SP_WHO2 and KILL sessions

There is one app that opens a lot of sessions to a database and never closed for that app. At some point, there are 100 connections.
1) My question is, what happens when the user(s) closes out the application? Currently, it looks like the sessions remain open even after the user(s) exits the app. I executed
SP_WHO2 and the sessions are still there.
2) I am able to execute KILL spid to end the sessions. However, I was wondering if the server's Remote query timeout
settings will kill it? For now, it looks like it did; but, I just want to confirm that it is the
Remote query timeout that killed those sessions.
Thanks

There is one app that opens a lot of sessions to a database and never closed for that app. At some point, there are 100 connections.
1) My question is, what happens when the user(s) closes out the application? Currently, it looks like the sessions remain open even after the user(s) exits the app. I executed
SP_WHO2 and the sessions are still there.
2) I am able to execute KILL spid to end the sessions. However, I was wondering if the server's Remote query timeout
settings will kill it? For now, it looks like it did; but, I just want to confirm that it is the
Remote query timeout that killed those sessions.
Thanks
For point 1. My recomendation is to communication with application team to review the source code and close all database connection once the operation is completed or the application is closed. Or they use connection pooling method. Such sessions
are created due to poor programming standard at the application level.
For point 2. My recomendation here is not to kill a spid which are in Running/Background status without prior informing to application team. This may break the consistency of information stored in the database due to incomplete transaction. Remote
query timeout has nothing to do with incoming queries received by database engine.
http://technet.microsoft.com/en-us/library/ms177457(v=sql.105).aspx
Regards, RSingh

Setting Adapter Timeout

Hello
I am having a File/FTP Adapter at my receiving end.I have noted that if a async msg is sent with Exactly Once option and if FTP server is down the message does not gets delivered but as soon as its up it gets delivered.
I just wanted to know how long Adapter keeps polling to the target directory? Can we set some specific timeout for adapter e.g. if FTP server does not comeup within 15 mins the adapter should timeout and message should fail. The message can then be sent manually.
Thanks in advance.
Regards
Rajeev Patkie

Ashu,
It is not only the JTA timeout which may cause transaction rollback. If JDBC and BPEL are involved then following timeouts also does matter and ideally all of them will be less than the JTA timeout -
1. XA connection timeout configured in data-source
2. Statement timeout configured in data-source
3. BPEL timeout - set property SyncMaxWaitTime (value in seconds) in the EM console
4. SOA EJB's timeout
Now question here should not be that which timeout is actually causing the transaction rollback, rather question should be that why a JDBC call is taking 300 seconds? What processing are you doing which is taking this much time?
Regards,
Anuj

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

Urgent need to kill a process

Hi,
I have loaded the data through DTP to DSO. The load was successful and the activation was taking long time so i cancelled it manually. went to sm50 server and pid and cancelled without core and with core also
Job log is
Job started
Step 001 started (program RSODSACT1, variant &0000000000041, user ID .....
Activation is running: Data target USR_LOGN, from 974 to 974
Overlapping check with archived data areas for InfoProvider USR_LOGN
Data to be activated successfully checked against archiving objects
Status transition 2 / 2 to 7 / 7 completed successfully
Job was mannually set to cancelled
NOw when i am tryig to delete the req itsnot the deletion job is gng to released state and is not getting to active state for somany times. checked no locks for the DSO and a job for the same rpocess id isrunning
I am unable to kill a job in the sm37 is there any way through which i can kill that process. I tried sm66 and sm51 many times but no use
its urgent please
K Janardhan KUmar
Job status was manually set to 'cancelled'
Message was edited by: Janardhan
Janardhan Karmala

Hi,
you said job is in release state. follow the below steps:
1. Select the job in sm37.
2. Go to change mode.
3. change the priority to A.
4. Click on schedule and schedule it immediately.
your deletion job will start immediately and after deletion you can start your activation again.
Let me know if it helps?
Mayank

PT 8.46 / CRM 8.8 (ERMS) - Timeouts?

At my current client there are issues with emails having large attachments; those attachments are not stored on the server. We checked timeouts on app server / web server (profile) / process scheduler but this doesn't seem to be an issue, they should be large enough. The timeout configured in the Integration Broker also is set to an extremely large value.
Does someone know which timeout values Oracle uses internally in the java code for the actual email connection?
Thanks in advance.

We have PeopleTools 8.46, and we want to integrate it
to a customized application that we are building
using ADF, we are considering the option the above
option, of publishing the needed components
interfaces to web services and consuming them from
the ADF.
I did some research and I could find 8.48 materials
in OTN, but not 8.46.If you read the release notes for PT 8.46, 8.47 and 8.48 you might find some clues to that.
Afair the SOAPtoCI should be present since PT 8.47 at least, but I might be wrong.
ExceltoCI is there for a long time and that uses SOAPtoCI afaik.
So you might be on the wrong Tools for what you want, at least if it comes to OOTB WebServices using CIs.
Cheers & HTH
Peter

Solaris equivalent of kill -16 in linux

i am running a process in solaris 9(console) . i know its pid . To halt the process i have given "kill -16 pidvalue" . This halts the process . Later when i gave the same command (ie . kill -16 pidvalue )it resumes (continues)the process .
While giving the same command ( ie . kill -16 pidvalue ) in Linux the process corresponding to the pid value gets permanantly killed ( ie the process becomes nonexistant ) , so next time when i am giving the command (kill -16 pidvalue) in Linux i get an error message on console which says " process is nonexistant " .
So can u suggest the appropriate numeric value or alphabet which should follow kill to halt the process in Linux. In a way i am looking for "solaris equivalent of kill -16 in linux ".

kill -STOP
kill -CONT
should work on both.
I don't know why -16 (USR1) would work on Solaris 9.
Darren

Script to kill the locks

Hi all,
Good day..
DB version is 10.2.0.4 I need to write a script which has to kill any table locks in the DB which is more than 10 minutes.
thanks,
baskar.l

hi thanks saad for your valuable suggestions..
i modified the script accordingly and it executed.
SQL> DECLARE
2 CURSOR c IS
3 SELECT c.owner,
4        c.object_name,
5        c.object_type,
6        b.SID,
7        b.serial#,
8        b.status,
9        b.osuser,
10        b.machine
11   FROM v$locked_object a, v$session b, dba_objects c
12   WHERE b.SID = a.session_id AND a.object_id = c.object_id
13   and c.object_name in ('JSW_CRM_C_HR_COIL_INFO','T_SPCL_BARCODE_CRS2');
14 c_row c%ROWTYPE;
15 l_sql VARCHAR2(100);
16 BEGIN
17 OPEN c;
18 LOOP
19 FETCH c INTO c_row;
20 EXIT WHEN c%NOTFOUND;
21 l_sql := 'alter system kill session '''||c_row.SID||','||c_row.serial#||'''';
22 EXECUTE IMMEDIATE l_sql;
23 END LOOP;
24 CLOSE c;
25 END;
26 /
PL/SQL procedure successfully completed.thanks,
baskar.l

Killing table locks

Hi all,
Good day..
DB version is 10.2.0.4 I need to write a script which has to kill any table locks in the DB which is more than 10 minutes.
thanks,
baskar.l

hi sb,
DECLARE
CURSOR c IS
SELECT c.owner,
      c.object_name,
      c.object_type,
      b.SID,
      b.serial#,
      b.status,
      b.osuser,
      b.machine
FROM v$locked_object a, v$session b, dba_objects c
WHERE b.SID = a.session_id AND a.object_id = c.object_id
and c.object_name in (MES.JSW_CRM_C_HR_COIL_INFO,MES.JSW_CRM_C_HR_COIL_INFO);
c_row c%ROWTYPE;
1_sql VARCHAR2(100);
BEGIN
OPEN C;
LOOP
FETCH c INTO c_row;
EXIT WHEN c%NOTFOUND;
l_sql := 'alter system kill session '''||c_row.sessionid||','||c_row.serialid||'''';
EXECUTE IMMEDIATE l_sql;
END LOOP;
CLOSE c;
END;But when executing it i get
1_sql VARCHAR2(100);
ERROR at line 15:
ORA-06550: line 15, column 1:
PLS-00103: Encountered the symbol "1" when expecting one of the following:
begin function package pragma procedure subtype type use
<an identifier> <a double-quoted delimited-identifier> form
current cursorthanks,
baskar.l

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

Kill session priviliage

Hi every one,
could you please reply me that I want to create a user which explicity just kills the redundant sessions only. what kind of privilages i need to grant that user (i don't want to make that user as DBA).
regards

I believe you need ALTER SYSTEM privelage. Since one should use ALTER SYSTEM KILL SESSION... to kill the sessions.
Jaffar

Which timeout is killing me?

Similar Messages

Maybe you are looking for