Kill session in rac on other node

I need sql that kills all sessions at all nodes
version ORACLE 10gR2
what to do?

You could use the same approach as for enabling restricted session.
declare
job binary_integer;
inst_id number := '&inst_id';
sid number := '&sid';
serial number := '&serial';
begin
dbms_job.submit (
job=>job,
what=> 'begin execute immediate ''alter system kill session ''''' || sid || ',' || serial || '''''; end;',
instance=>inst_id
commit;
end;
or you can drive it from gv$session by some criteria, e.g.
for s in (select inst_id, sid, serial# from gv$session whre username = '&bad_user')
loop
dbms_job.submit (
job=>job,
what=> 'begin execute immediate ''alter system kill session ''''' || i.sid || ',' || i.serial# || '''''; end;',
instance=>i.inst_id
end loop;
...

Similar Messages

  • Kill session in RAC

    Hello, I have a RAC environment, and I need to kill a session, I user "alter kill session <SID> , <SERIAL>", but the session still appear in the database, so I tried to kill througn the OS (Unix), but the spid don´t match with the PID of SO.
    Any suggestion?
    clarification: I am connected in the same node, at database (11g R1) and the server.
    Thanks.

    I have been checked all nodes, and the spid of the session don´t appear in none.

  • Alter system kill session in RAC

    Hi,
    After identifying all inactive jdbc sessions or blocking sessions from gv$session or gv$lock respectively, should alter system kill session executed in both instances of RAC?, Can't we execute like alter system kill session ' inst_id,sid,serial#' from a single instance to kill all the session of RAC instances?
    So, above problem answered in 11g as:
    Alter system kill session ‘SID, serial#, @instance_id’;
    Eg: ALTER SYSTEM KILL SESSION ‘115,9779,@1';
    So, In our environment, most of the databases are in 10gR1 or 10g R2. Is there any patch for 10g Where instance_id can be recognized by alter system kill session?
    Thanks,
    Sunil.

    Hi Dan,
    Not sure what you mean by "instance specific kill session capability".
    To be clear, I'm speaking of a new feature, introduced in 11gR1, that provides for an optional third parameter to 'alter system kill session', which allows you to kill a session on a remote instance, in a RAC environment.
    Documentation is here:
    http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/statements_2013.htm#i2065117
    -Mark

  • Kill Session option is not rac aware?

    Connected to a RAC db, tried to kill session but SD kept complaining that session doesn't exist. It seems it shows sessions from gv$session but while issuing kill, it assumes session on local node.
    Would it not be possible to enhance the kill to use 'rac-aware' command ? alter system kill session 'sid,serial#@inst_id' ?

    Connected to a RAC db, tried to kill session but SD kept complaining that session doesn't exist. It seems it shows sessions from gv$session but while issuing kill, it assumes session on local node.
    Would it not be possible to enhance the kill to use 'rac-aware' command ? alter system kill session 'sid,serial#@inst_id' ?
    I can't address the Sql Dev specifics but the 'kill' statement itself is NOT rac-aware in versions prior to 11.1 (you did NOT provide your DB  version.
    And for 11.1 and later you have to provide the instance id for the third parameter.
    http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_2013.htm
      For the optional integer3, specify the ID of the instance where the target session to be killed exists. You can find the instance ID by querying the GV$ tables.
    I suggest you edit your post and provide more info so someone from the sql dev team can respond to how sql dev issues that particular statement. Depending on your sql dev version the actual sql issued would be shown in the log window if you have it open.
    1. full DB version - that 3rd parameter is NOT supported for versions prior to 11.1
    2. full Sql version

  • Killing oracle session in RAC

    Hi
    Some of the tables ot locked in my database(it is 4 node RAC) so i first identified the session id and serial has to kill the session using belo query
    col oracle_username for a10
    col os_user_name for a10
    set linesize 150
    select s.sid,s.serial#,s.inst_id,l.inst_id,l.session_id,l.oracle_username,l.XIDUSN,l.XIDSLOT,l.XIDSQN,l.OBJECT_ID,
    l.OS_USER_NAME,l.PROCESS,l.LOCKED_MODE
    from gv$session s,gv$locked_object l
    where s.sid=l.session_id
    and ORACLE_USERNAME='&USERNSME';
    it gaves me below result
           168        202          1          1        168 TEST123           72          0      34994      35239 test123   6652            3
    so i tried to kill it using below command
    alter system kill session '168,202,@1' immediate;
    but i m getting below error
    SQL> ALTER SYSTEM KILL SESSION '168,202,@1' IMMEDIATE;
    ALTER SYSTEM KILL SESSION '168,202,@1' IMMEDIATE
    ERROR at line 1:
    ORA-00030: User session ID does not exist.plz suggest how do i kill session in oracle rac

    yes it is there
    SQL> select sid,serial# from v$session where sid=168 and serial#=202;
           SID    SERIAL#
           168        202
    SQL>  select sid,serial#,inst_id from gv$session  where sid=168 and serial#=202;
           SID    SERIAL#    INST_ID
           168        202          1
    SQL> alter system kill session '168,202' immediate;
    alter system kill session '168,202' immediate
    ERROR at line 1:
    ORA-00030: User session ID does not exist.
    SQL> alter system kill session '168,202,@1' immediate;
    alter system kill session '168,202,@1' immediate
    ERROR at line 1:
    ORA-00030: User session ID does not exist.

  • One node RAC pause/hang/block on other node shutdown

    Hi,
    We have a Java application running on Linux servers connecting to a 10.2.0.1 RAC cluster, also Linux. When the application starts it opens up a pool of connections to the databsae, and these are used throughout the life time of the application. One server connects to one RAC node.
    AppA - DBA
    AppB - DBB
    When we shutdown one node, the application connecting to that node stops, which is what we would expect in this configuration.
    What is strange is that the other application blocks for 63 seconds and then continues. So it is like the database is blocking, or the database connections are blocking.
    We are not using TAF, FAN, FCN, LB, VIPs or any special features, just simple lightweight JDBC from one server to one database. In fact I do not thing we are unwittingly using any of these features, we have them switched off.
    john

    user1788323 wrote:
    What is strange is that the other application blocks for 63 seconds and then continues. So it is like the database is blocking, or the database connections are blocking.How have you determined/diagnosed the 63s blocking? (more details in this regard may shed some light on the problem)
    Assuming that the block is server side, then two basic reasons comes to mind.
    Networking issue - the CRS on the surviving node has to perform certain functions, like switching the VIP of the node that left the cluster to a surviving cluster node. The listener may need to re-register services. A local firewall may need to be dynamically reconfigured for supporting the new failed-over VIP. Etc.
    Thus these could result in some kind of delay or issue in the network layer that you are seeing from the client side.
    Infrastructure issue. If the actual client request via JDBC reaches the server process, and it is slow in responding, then that is not a network issue - instead some underlying service or s/w layer that the server process needs to use to perform the client request is busy for those 63s.
    This could be related to the Interconnect, the shared I/O storage layer or something along those lines. For example, how does the Interconnect and/or SAN switch re-act when a server node is powered down or rebooted?
    There's not really sufficient information to make anything but a guesses.. You will need to isolate the problem with further testing.
    I have seen similar problems with 10.1.0.3 CRS and RAC when a node is evicted from the cluster. In this case the "hung" period was in excess of 15 minutes and only for new connections (Listener unable to hand off to dedicated servers or dispatchers). Existing connections worked fine however and were unaware of any problems. But part of the issue in this case was a poor (outdated) driver layer - and also the last time we used proprietary binary drivers (kernel modules) from 3rd party vendors that results in a tainted (and very fixed and rigid) Linux kernel. Today we're sticking with an OpenSource driver layer only for Linux.

  • When one node reboot other node in RAC

    Hi Friends,
    I faced one situation where one node of RAC cluster had been rebooted by other node. This happen due to network interconnect link fluctuation.
    Sep 13 16:23:48 kkvs1a su: [ID 810491 auth.crit] 'su admin' failed for wipro1 on /dev/pts/3
    Sep 14 00:22:17 kkvs1a ixgbe: [ID 611667 kern.info] NOTICE: ixgbe3: link down
    Sep 14 00:22:21 kkvs1a ixgbe: [ID 611667 kern.info] NOTICE: ixgbe3: link up, , full duplex
    Sep 14 00:22:31 kkvs1a ixgbe: [ID 611667 kern.info] NOTICE: ixgbe1: link down
    Sep 14 00:22:31 kkvs1a ixgbe: [ID 611667 kern.info] NOTICE: ixgbe3: link down
    /opt/oracle/product/10.2.0/crs/log/node1/alertkk1a.log
    ==============================================
    2013-09-14 00:22:05.180
    [cssd(12561)]CRS-1612:node kk1b (2) at 50% heartbeat fatal, eviction in 14.251 seconds
    2013-09-14 00:22:12.180
    [cssd(12561)]CRS-1611:node kk1b (2) at 75% heartbeat fatal, eviction in 7.251 seconds
    2013-09-14 00:22:13.180
    [cssd(12561)]CRS-1611:node kk1b (2) at 75% heartbeat fatal, eviction in 6.251 seconds
    2013-09-14 00:22:17.179
    [cssd(12561)]CRS-1610:node kk1b (2) at 90% heartbeat fatal, eviction in 2.251 seconds
    2013-09-14 00:22:18.180
    [cssd(12561)]CRS-1610:node kkvs1b (2) at 90% heartbeat fatal, eviction in 1.251 seconds
    This clearly shows CSSD of node kkvs1a has given node eviction message to kkvs1b node.
    I got following messages on the instance which got rebooted:
    ASM alert log:
    Sat Sep 14 00:22:25 IST 2013
    Error: KGXGN aborts the instance (6)
    Sat Sep 14 00:22:25 IST 2013
    Errors in file /opt/oracle/admin/+ASM/bdump/+asm2_lmon_8527.trc:
    ORA-29702: error occurred in Cluster Group Service operation
    LMON: terminating instance due to error 29702
    A network fluctuation shouldn't give reboot like this. Then why oracle design like this way? Is this a bug? My oracle version is: 10.2.0.5.0
    Could you tell me the other possible situations when 1 RC instance reboots other RAC instacne.

    What you are describing is the expected behaviour: if your interconnect fails, you will have a node eviction. Releases < 11.2.0.2 evict a node by reboot, which can fix the problem: the NIC may come up correctly when the machine re-starts. Releases >= 11.2.0.2 can often evict without a re-boot. But either way, if your interconnect goes down, a node must be evicted to prevent uncoordinated disc writes.
    If you are interested, you can find some discussion and demos of this in a series of webcasts I've recorded,
    Free Oracle Database Tutorials for Administration and Developers
    If you really don't like this behaviour and the problems are transient, you can try 'raising the CSS MISSCOUNT parameter.
    John Watson
    Oracle Certified Master DBA

  • Strange issue in Oracle ASM on Two node RAC where in one ASM node shows all diskgroup while other node shows  missing node.

    We have Oracle datbase 11gR1 in RAC node with Oracle ASM.Recently our database server got crashed and we are trying to restore back services.
    Using Snapshot technologyBusiness copy we had synced all our disk on storage level. Post this when we are trying to start ASM instance on node 1 it is coming and showing all diskgroups but on other node it is throwing errot with missing e diskgroup.
    ORA-15032: not all alterations performed
    ORA-15040: diskgroup is incomplete
    ORA-15042: ASM disk "5" is missing
    Expert please share your views.
    Thanks,
    Tushar

    The I/O fabric layer on the other node failed to mount all storage LUNs - resulting in ASM being unable to mount a diskgroup as there are missing disks in that group.
    Rebooting is exactly what could be needed to reset the h/w and infrastructure used by that node, in order for it to see all the storage disks again. As node 1 sees all storage disks (and is working), the disk itself on the storage system is intact and usable.
    What is the o/s? What is the fabric layer? What is used on o/s for dealing with the I/O fabric layer?

  • Starting a node while you are in other node in RAC

    Hi,
    Any idea how to start a node while you are in other node in RAC?

    Hi,
    Not sure what is your database version. However, you can start/stop the instance via srvctl and/or sql*plus.
    Note: 753516.1 - The difference between using srvctl vs using sqlplus for start/stop one or more database nodes
    Oracle® Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide
    http://www.oracle.com/technology/documentation/database.html
    Regards,
    Hussein

  • Prevent VIP's from other nodes to start on 11gr2 RAC ??

    I have one node which is part of 3 node 11gr2 RAC.
    Other 2 nodes(rac1, rac2) a power down, and on this node(rac3), crs is down.
    Problem is, that, if I switch crs up, he will up all VIP addresses , from
    rac3-vip, but, also rac2-vip, rac1-vip..but, this (rac1-vip, rac2-vip) is
    already VIP address's in production on second RAC.
    1)Can I somehow disable this 2 VIP's BEFORE I start crs on rac3 to prevent
    this other VIP address to start on rac3???
    2) If no, can I start crs, and quick stop down this VIP's,
    crs_stop ora.rac2.vip
    crs_stop ora.rac3.vip
    3) and maybe somehow prevent from future start before I really migrate
    everything on new RAC??
    Tnx

    sauron666 wrote:
    I already do that, because this is preprod, we prepare to switch prod 10g rac to this 11gr2 rac.
    10g rac has 2 nodes. (prod)
    11gr2 rac has 3 nodes. (2 nodes have same VIP as prod).Huh? That's not what I would call a good idea. Using the same IP addresses? What for? Why not re-use the hostnames instead?
    Today the VIP hostnames resolve to the 10g RAC's VIPs. Tomorrow when the switchover to 11g happens, the DNS is updated and these VIP hostnames resolve to the 11g RAC's VIPs.
    So, I want on this third node from 11gr2 RAC to stop those VIP's, which is the same as prod VIP's..so I can have third node up, and first 2 node from 11gr2 rac down (which have same VIP's as 10g rac)Just the idea of purposefully creating duplicate IPs on a network.. Crazy...
    You can try and hide those 11g RAC duplicate IPs from the network. Routing table is perhaps an option. Using iptables is another Or as you want, preventing the VIPs from starting in the first place.
    But you should take this as a lesson in how NOT to configure networking. Duplicating IPs is simply a no-no. There is no reason I've ever seen, nor can think of, why IPs should be duplicated like this. Hostnames resolution exists for addressing such requirements.

  • RAC DB -Querying other nodes

    Provided one DB node in a cluster, how we can get the information (Host Name,Port Number) of other nodes in RAC? Is there some tables in each node which i can query ?

    "user will provide the DB Conn Info (Host,Port,User,Pass,SID) of one node , a query will fetch the remaining nodes DB Conn Info. "
    One thing not sure if your trying to deploy in your application you need not to worry which node is serving you and which node is down. you wiil have a load balencing TNS entry for your RAC environment which will take care of connection and retrieval of data.
    I am just pasitng a sapmple TNS entry of 2 node rac. it may be help full for you
    Service_name =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = HOST_NAME01-vip)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = HOST_NAME02-vip)(PORT = 1521))
    (LOAD_BALANCE = yes)
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = <SID)
    Regards,
    Anil Malkai

  • Immediate kill session in alert log file

    hi..
    i'm using db10.2.0 ,windows 2003 server
    we're having alot of "immediate kill session " in the alert log file ,what could be causing it?
    the log file looks lsomething ike that
    Sat Oct 11 10:55:33 2008
    Thread 1 advanced to log sequence 2390
    Current log# 1 seq# 2390 mem# 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\ABS\REDO01.LOG
    Current log# 1 seq# 2390 mem# 1: E:\DATABASE\ABS\REDO_LOGS\REDO01B.LOG
    Sat Oct 11 11:08:23 2008
    Immediate Kill Session#: 196, Serial#: 96
    Immediate Kill Session: sess: B7A4F764 OS pid: 2744
    Sat Oct 11 11:08:27 2008
    Immediate Kill Session#: 183, Serial#: 62
    Immediate Kill Session: sess: B823F4D0 OS pid: 2348
    Sat Oct 11 11:08:33 2008
    Immediate Kill Session#: 198, Serial#: 68
    Immediate Kill Session: sess: B7A50A2C OS pid: 2856
    Sat Oct 11 11:08:33 2008
    Immediate Kill Session#: 77, Serial#: 349
    Immediate Kill Session: sess: B8201168 OS pid: 5704
    Sat Oct 11 11:08:34 2008
    Immediate Kill Session#: 156, Serial#: 257
    Immediate Kill Session: sess: B7A37FC4 OS pid: 3428
    Sat Oct 11 11:08:41 2008
    Immediate Kill Session#: 92, Serial#: 104
    Immediate Kill Session: sess: B7A126C4 OS pid: 3500
    Sat Oct 11 11:08:45 2008
    Immediate Kill Session#: 178, Serial#: 17
    Immediate Kill Session: sess: B7A44E5C OS pid: 3408
    Sat Oct 11 11:08:51 2008
    Immediate Kill Session#: 180, Serial#: 43
    Immediate Kill Session: sess: B7A46124 OS pid: 1592
    Sat Oct 11 11:08:56 2008
    Immediate Kill Session#: 81, Serial#: 310
    Immediate Kill Session: sess: B82036F8 OS pid: 5088
    Sat Oct 11 11:08:57 2008
    Immediate Kill Session#: 114, Serial#: 290
    Immediate Kill Session: sess: B7A1F55C OS pid: 952
    Sat Oct 11 11:09:02 2008
    Immediate Kill Session#: 104, Serial#: 117
    Immediate Kill Session: sess: B7A19774 OS pid: 4068
    Sat Oct 11 11:09:11 2008
    Immediate Kill Session#: 177, Serial#: 20
    Immediate Kill Session: sess: B823BC78 OS pid: 2024
    Sat Oct 11 11:09:16 2008
    Immediate Kill Session#: 145, Serial#: 34
    Immediate Kill Session: sess: B8228FF8 OS pid: 4012
    Sat Oct 11 11:09:18 2008
    Immediate Kill Session#: 72, Serial#: 265
    Immediate Kill Session: sess: B7A06AF4 OS pid: 5592
    Sat Oct 11 11:09:28 2008
    Immediate Kill Session#: 176, Serial#: 9
    Immediate Kill Session: sess: B7A43B94 OS pid: 1988
    Sat Oct 11 11:09:37 2008
    Immediate Kill Session#: 148, Serial#: 118
    Immediate Kill Session: sess: B7A334A4 OS pid: 1216
    Sat Oct 11 11:09:41 2008
    Immediate Kill Session#: 110, Serial#: 1190
    Immediate Kill Session: sess: B7A1CFCC OS pid: 2152
    Sat Oct 11 11:09:46 2008
    Immediate Kill Session#: 141, Serial#: 488
    Immediate Kill Session: sess: B8226A68 OS pid: 5460
    Sat Oct 11 11:09:51 2008
    Immediate Kill Session#: 130, Serial#: 96
    Immediate Kill Session: sess: B7A28B9C OS pid: 1312
    Sat Oct 11 11:10:48 2008
    Immediate Kill Session#: 101, Serial#: 1592
    Immediate Kill Session: sess: B820F2C8 OS pid: 5936
    Sat Oct 11 11:10:57 2008
    Immediate Kill Session#: 170, Serial#: 5
    Immediate Kill Session: sess: B7A4033C OS pid: 3356
    Sat Oct 11 11:11:05 2008
    Immediate Kill Session#: 138, Serial#: 46
    Immediate Kill Session: sess: B7A2D6BC OS pid: 3156
    Sat Oct 11 11:11:06 2008
    Immediate Kill Session#: 111, Serial#: 1143
    Immediate Kill Session: sess: B82150B0 OS pid: 5056
    Sat Oct 11 11:11:09 2008
    Immediate Kill Session#: 132, Serial#: 228
    Immediate Kill Session: sess: B7A29E64 OS pid: 1628
    Sat Oct 11 11:11:10 2008
    Immediate Kill Session#: 150, Serial#: 560
    Immediate Kill Session: sess: B7A3476C OS pid: 2568
    Sat Oct 11 11:11:12 2008
    Immediate Kill Session#: 155, Serial#: 165
    Immediate Kill Session: sess: B822EDE0 OS pid: 3484
    Sat Oct 11 11:11:18 2008
    Immediate Kill Session#: 165, Serial#: 90
    Immediate Kill Session: sess: B8234BC8 OS pid: 1968
    Sat Oct 11 11:11:36 2008
    Immediate Kill Session#: 116, Serial#: 221
    Immediate Kill Session: sess: B7A20824 OS pid: 4848
    Sat Oct 11 11:11:37 2008
    Immediate Kill Session#: 192, Serial#: 54
    Immediate Kill Session: sess: B7A4D1D4 OS pid: 3972
    Sat Oct 11 11:11:45 2008
    Immediate Kill Session#: 164, Serial#: 98
    Immediate Kill Session: sess: B7A3CAE4 OS pid: 3888
    Sat Oct 11 11:11:45 2008
    Immediate Kill Session#: 121, Serial#: 17
    Immediate Kill Session: sess: B821AE98 OS pid: 1200
    Sat Oct 11 11:11:50 2008
    Immediate Kill Session#: 109, Serial#: 330
    Immediate Kill Session: sess: B8213DE8 OS pid: 3456
    Sat Oct 11 11:11:56 2008
    Immediate Kill Session#: 181, Serial#: 68
    Immediate Kill Session: sess: B823E208 OS pid: 3324
    Sat Oct 11 11:12:17 2008
    Immediate Kill Session#: 214, Serial#: 85
    Immediate Kill Session: sess: B7A5A06C OS pid: 2752
    Sat Oct 11 11:12:20 2008
    Immediate Kill Session#: 209, Serial#: 346
    Immediate Kill Session: sess: B824E8F8 OS pid: 3844
    Sat Oct 11 11:12:23 2008
    Immediate Kill Session#: 154, Serial#: 152
    Immediate Kill Session: sess: B7A36CFC OS pid: 3400
    Sat Oct 11 11:12:26 2008
    Immediate Kill Session#: 147, Serial#: 86
    Immediate Kill Session: sess: B822A2C0 OS pid: 2536
    Sat Oct 11 11:12:34 2008
    Immediate Kill Session#: 79, Serial#: 1504
    Immediate Kill Session: sess: B8202430 OS pid: 4052
    Sat Oct 11 11:12:47 2008
    Immediate Kill Session#: 189, Serial#: 234
    Immediate Kill Session: sess: B8242D28 OS pid: 2128
    Sat Oct 11 11:13:10 2008
    Immediate Kill Session#: 118, Serial#: 95
    Immediate Kill Session: sess: B7A21AEC OS pid: 3480
    Sat Oct 11 11:13:13 2008
    Immediate Kill Session#: 94, Serial#: 16
    Immediate Kill Session: sess: B7A1398C OS pid: 2140
    Sat Oct 11 11:14:24 2008
    ALTER SYSTEM SET service_names='aba10g' SCOPE=MEMORY SID='abs';
    Sat Oct 11 11:14:59 2008
    Immediate Kill Session#: 97, Serial#: 1197
    Immediate Kill Session: sess: B820CD38 OS pid: 4164
    Sat Oct 11 11:15:07 2008
    Immediate Kill Session#: 163, Serial#: 237
    Immediate Kill Session: sess: B8233900 OS pid: 3224
    Sat Oct 11 11:15:19 2008
    Immediate Kill Session#: 140, Serial#: 230
    Immediate Kill Session: sess: B7A2E984 OS pid: 1584
    Sat Oct 11 11:15:41 2008
    Thread 1 advanced to log sequence 2391
    Current log# 4 seq# 2391 mem# 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\ABS\REDO4.LOG
    Current log# 4 seq# 2391 mem# 1: E:\DATABASE\ABS\REDO_LOGS\REDO04B.LOG
    Sat Oct 11 11:15:51 2008
    Immediate Kill Session#: 88, Serial#: 541
    Immediate Kill Session: sess: B7A10134 OS pid: 4676
    Sat Oct 11 11:16:09 2008
    Immediate Kill Session#: 78, Serial#: 358
    Immediate Kill Session: sess: B7A0A34C OS pid: 6056

    2011-06-27 02:27:12.215: [    RACG][261091968] [24623][261091968][ora.rac.rac1.inst]: clsrcqryapi: crs_qstat error
    2011-06-27 02:27:12.215: [    RACG][261091968] [24623][261091968][ora.rac.rac1.inst]: clsrcpullupvip: Failed to get status of ora.srv01-025.vip
    2011-06-27 02:27:12.810: [    RACG][282473088] [24623][282473088][ora.rac.rac1.inst]: clscconnect failed with clsc ret 9
    2011-06-27 02:27:12.811: [    RACG][282473088] [24623][282473088][ora.rac.rac1.inst]: error connecting to CRSD at [(ADDRESS=(PROTOCOL=IPC)(KEY=CRSD_UI_SOCKET))] clsccon 184
    2011-06-27 02:27:12.811: [    RACG][261091968] [24623][261091968][ora.rac.rac1.inst]: clsrcqryapi: crs_qstat error
    2011-06-27 02:27:13.237: [    RACG][261091968] [24623][261091968][ora.rac.rac_srv.cs]: clsrcqryapi: crs_qstat error
    2011-06-27 02:27:13.625: [    RACG][261091968] [24623][261091968][ora.rac.rac_srv.rac1.srv]: clsrcqryapi: crs_qstat error
    2011-06-27 02:27:13.625: [    RACG][261091968] [24623][261091968][ora.rac.rac_srv.rac1.srv]: clsrcsmfread: cannot get status of resource 'ora.rac.rac_srv.rac1.srv'
    2011-06-27 02:27:15.829: [  OCRMSG][261091968]prom_rpc: CLSC send failure..ret code 11
    2011-06-27 02:27:15.829: [  OCRMSG][261091968]prom_rpc: possible OCR retry scenario
    2011-06-27 02:27:15.881: [  OCRAPI][261091968]procr_open: Node Failure. Attempting retry #0
    2011-06-27 02:27:16.096: [    RACG][261091968] [24623][261091968][ora.rac.rac_srv.rac1.srv]: clsrcqryapi: crs_qstat error
    Edited by: user13481820 on Jun 26, 2011 10:53 PM

  • Trace File Created Upon Execution of "alter system kill session sid, serial# immediate;"

    A problem within a third-party application is causing it to create and abandon Oracle sessions. At times three hundred or more abandoned sessions accumulated in the instance. The software company is working on the problem. Oracle's background processes will get rid of those sessions after several hours, but at times there were so many they caused the server to start using paging space. We wrote a SQL*Plus script to identify the abandoned sessions and kill them with command "alter system kill session <sid, serial#> immediate;". We automated the execution of the script a week ago. Today I noticed that in my udump directory an Oracle trace file has been created each time our script kills a session. A single trace file is created regardless of how many sessions are killed. No errors appear in the trace file.
    Is the creation of these trace files an indication that problems have occurred or are they there for information only?
    Since I know how and why the sessions are being killed, is it safe to ignore the trace files?
    Thank you,
    Bill

    The OS is AIX 5.2. The database server is 10.2.0.2. We are in the processing of upgrading to AIX 7.1 and database server 11.2.0.3.6.
    The script does not enable tracing for the SQL*Plus session.
    Below is the alert log message from a session killed at 11:22, and the corresponding trace file created at that same time:
    From alert_<sid>.log: 
    Wed Jul 31 11:22:01 2013
    Immediate Kill Session#: 1119, Serial#: 59885
    Immediate Kill Session: sess: 70000014dc4a7e0 OS pid: 267254
    /u02/admin/EXPRESS/udump $ ls -l express_ora_113358.trc
    -rw-r----- 1 oracle dba 2276 Jul 31 11:22 express_ora_113358.trc
    /u02/admin/EXPRESS/udump $ pg express_ora_113358.trc
    Dump file /u02/admin/EXPRESS/udump/express_ora_113358.trc
    Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    ORACLE_HOME = /u01/app/oracle/product/10.2.0
    System name: AIX
    Node name: navis
    Release: 2
    Version: 5
    Machine: 0005CD8C4C00
    Instance name: EXPRESS
    Redo thread mounted by this instance: 1
    Oracle process number: 225
    Unix process pid: 113358, image: oracleEXPRESS@navis
    *** ACTION NAME:() 2013-07-31 11:22:01.181
    *** MODULE NAME:(SQL*Plus) 2013-07-31 11:22:01.181
    *** SERVICE NAME:(EXPRESS.WORLD) 2013-07-31 11:22:01.181
    *** SESSION ID:(1723.61000) 2013-07-31 11:22:01.181
    SO: 70000014d44d278, type: 2, owner: 0, flag: INIT/-/-/0x00
    (process) Oracle pid=463, calls cur/top: 0/700000139166298, flag: (0) -
    int error: 0, call error: 0, sess error: 0, txn error 0
    (post info) last post received: 108 0 4
    last post received-location: kslpsr
    last process to post me: 70000014d36c398 1 6
    last post sent: 0 0 24
    last post sent-location: ksasnd
    last process posted by me: 70000014d36c398 1 6
    (latch info) wait_event=0 bits=0
    Process Group: DEFAULT, pseudo proc: 70000014d6aec00
    O/S info: user: oracle, term: UNKNOWN, ospid: 267254
    OSD pid info: Unix process pid: 267254, image: oracleEXPRESS@navis
    Short stack dump:
    ksdxfstk+002c<-ksdxcb+04e4<-sspuser+0074<-00004CB0<-nttrd+0120<-nsprecv+0750<-ns
    rdr+0114<-nsdo+1714<-nsbrecv+0040<-nioqrc+04a8<-opikndf2+0688<-opitsk+088c<-opii
    no+0990<-opiodr+0adc<-opidrv+0474<-sou2o+0090<-opimai_real+01bc<-main+0098<-__st
    art+0090
    Dump of memory from 0x070000014D2CC3B0 to 0x070000014D2CC5B8
    70000014D2CC3B0 00000004 00000000 07000001 39DA8D48 [............9..H]
    70000014D2CC3C0 00000010 0003139D 07000001 39166298 [............9.b.]
    70000014D2CC3D0 00000003 0003139D 07000001 4C73D508 [............Ls..]
    70000014D2CC3E0 0000000B 0003139D 07000001 4DC4A7E0 [............M...]
    70000014D2CC3F0 00000004 00031291 00000000 00000000 [................]
    70000014D2CC400 00000000 00000000 00000000 00000000 [................]
    Repeat 26 times
    70000014D2CC5B0 00000000 00000000 [........]
    Thanks,
    Bill

  • Regarding error in alert -- immediate kill session

    Dear Gurus
    os - linux4.5
    oracle -10.2.0.4
    i have an error in my alert log file for node 2 as below(i m posting here main text what i found)
    Immediate Kill Session#: 73, Serial#: 39455
    Immediate Kill Session: sess: 0x402337f0ca0 OS pid: 17058
    Immediate Kill Session#: 74, Serial#: 38391
    Immediate Kill Session: sess: 0x402337f2208 OS pid: 25083
    Immediate Kill Session#: 76, Serial#: 6725
    Immediate Kill Session: sess: 0x40233833af0 OS pid: 17018
    Immediate Kill Session#: 128, Serial#: 54171
    Immediate Kill Session: sess: 0x4023383a5f8 OS pid: 25861
    Sun Aug 14 14:25:31 2011
    Process OS id : 25861 alive after kill
    Errors in file /u01/app/oracle/admin/prod/udump/prod_ora_8179.trc
    Immediate Kill Session: sess: 0x40233a3c1f8 OS pid: 28900
    Immediate Kill Session#: 534, Serial#: 12002
    Immediate Kill Session: sess: 0x40233a598e8 OS pid: 16102
    Sun Aug 14 14:35:30 2011
    ALTER SYSTEM SET service_names='prod' SCOPE=MEMORY SID='prod2';
    Sun Aug 14 21:00:50 2011
    Thread 2 advanced to log sequence 3684 (LGWR switch)
    Current log# 3 seq# 3684 mem# 0: +RLOG_GROUP/prod/redo03.log
    Mon Aug 15 18:56:50 2011
    Thread 2 advanced to log sequence 3685 (LGWR switch)
    trace file text is as
    post info) last post received: 109 0 4
    last post received-location: kslpsr
    last process to post me: 40233693738 1 6
    last post sent: 0 0 24
    last post sent-location: ksasnd
    last process posted by me: 40233693738 1 6
    (latch info) wait_event=0 bits=0
    Process Group: DEFAULT, pseudo proc: 0x40233786f80
    O/S info: user: oracle, term: UNKNOWN, ospid: 21196 (DEAD)
    OSD pid info: Unix process pid: 21196, image: oracle@dbrac2
    Short stack dump: unable to dump stack due to error 72
    Dump of memory from 0x00000402336539E0 to 0x0000040233653BE8
    402336539E0 00000010 00000000 1DC35CE0 00000402 [.........\......]
    402336539F0 00000010 000313A7 1DC60660 00000402 [........`.......]
    40233653A00 00000003 000313A7 312D7370 00000402 [........ps-1....]
    40233653AE0 00000007 000313A7 00000000 00000000 [................]
    40233653AF0 00000000 00000000 00000000 00000000 [................]
    Repeat 14 times
    40233653BE0 00000000 00000000
    SO: 0x402336a9318, type: 2, owner: (nil), flag: INIT/-/-/0x00
    (process) Oracle pid=55, calls cur/top: (nil)/0x401fe14f1c8, flag: (0) -
    int error: 0, call error: 0, sess error: 0, txn error 0
    (post info) last post received: 109 0 4
    last post received-location: kslpsr
    last process to post me: 40233693738 1 6
    last post sent: 0 0 24
    last post sent-location: ksasnd
    last process posted by me: 40233693738 1 6
    (latch info) wait_event=0 bits=0
    Process Group: DEFAULT, pseudo proc: 0x40233786f80
    O/S info: user: oracle, term: UNKNOWN, ospid: 21597 (DEAD)
    OSD pid info: Unix process pid: 21597, image: oracle@dbrac2
    Short stack dump: unable to dump stack due to error 72
    Dump of memory from 0x0000040233655858 to 0x0000040233655A60
    40233655850 0000000C 00000000 [........]
    40233655860 1DD637A8 00000402 00000010 000313A7 [.7..............]
    40233655870 FE14F1C8 00000401 00000003 000313A7 [................]
    40233655880 312CC588 00000402 00000013 0003129B [..,1............]
    40233655890 33D61950 00000402 0000000B 000313A7 [P..3............]
    402336558A0 339F1338 00000402 00000004 0003129B [8..3............]
    402336558B0 28A937E8 00000402 00000007 000313A7 [.7.(............]
    402336558C0 6259D858 00000401 00000053 000313A7 [X.Yb....S.......]
    402336558D0 28A938C8 00000402 00000007 000313A7 [.8.(............]
    402336558E0 28A956B8 00000402 00000007 000313A7 [.V.(............]
    402336558F0 28A95798 00000402 00000007 000313A7 [.W.(............]
    40233655900 28A9F000 00000402 00000007 000313A7 [...(............]
    40233655910 28A9E9E0 00000402 00000007 000313A7 [...(............]
    40233655920 00000000 00000000 00000000 00000000 [................]
    Repeat 19 times
    (latch info) wait_event=0 bits=0
    Process Group: DEFAULT, pseudo proc: 0x40233786f80
    O/S info: user: oracle, term: UNKNOWN, ospid: 27060 (DEAD)
    OSD pid info: Unix process pid: 27060, image: oracle@dbrac2
    Short stack dump: unable to dump stack due to error 72
    Dump of memory from 0x0000040233653FF8 to 0x0000040233654200
    40233653FF0 0000000A 00000000 [........]
    40233654000 1DC35E78 00000402 00000010 000313A7 [x^..............]
    40233654010 1DCD4AF0 00000402 00000003 000313A7 [.J..............]
    Repeat 16 times
    please give some hint what actually is it and why
    also at the end in my alert what does it means
    ALTER SYSTEM SET service_names='prod' SCOPE=MEMORY SID='prod2'
    regards

    By any chance if you back in the alert log just a little more does an ORA-00600 error appear before the immediate kill session messages? I found a few problem reports on the Oracle support site that might be of interest if there is:
    ORA-00600 [1301] - Instance Terminated by PMON After Killing Sessions
    ORA-600 [4072] Is Possible After Killing A Session Or Cancelling a Operation [ID 1113829.1]
    Database Crash ORA-00600: [ksqcmi:res3], [], [], [], [], [], [], [] and ORA-00600: [1100], [ID 1327043.1]
    HTH -- Mark D Powell --

  • Forms session got disconnected during db node failure

    Hello All,
    Setup: Multi node configuration
    1 node appl tier - running all services except the database (2nd node will be setup soon)
    2 node db tier (10g RAC)
    During failover test, Invalid session error when shutdown of node where form session is connected. Is this normal
    behaviour? I suppose its not, any changes need to be done? I already changed "Tools OH TWO_TASK" to use <database_name>_806_balance alias and iAS OH TWO_TASK" and "Apps JDBC Connect Alias" to use <database_name>_balance then autoconfig.
    My tnsnames.ora is similar to this:
    DP1_806_BALANCE=
    (DESCRIPTION_LIST=
    (DESCRIPTION=
    (ADDRESS=(PROTOCOL=tcp)(HOST=dbp02-vip.xxx)(PORT=1521))
    (CONNECT_DATA=
    (SERVICE_NAME=DP1)
    (INSTANCE_NAME=DP12)
    (DESCRIPTION=
    (ADDRESS=(PROTOCOL=tcp)(HOST=dbp01-vip.xxx)(PORT=1521))
    (CONNECT_DATA=
    (SERVICE_NAME=DP1)
    (INSTANCE_NAME=DP11)
    DP1_BALANCE=
    (DESCRIPTION=
    (LOAD_BALANCE=YES)
    (FAILOVER=YES)
    (ADDRESS_LIST=
    (ADDRESS=(PROTOCOL=tcp)(HOST=dbp02-vip.xxx)(PORT=1521))
    (ADDRESS=(PROTOCOL=tcp)(HOST=dbp01-vip.xxx)(PORT=1521))
    (CONNECT_DATA=
    (SERVICE_NAME=DP1)
    Appreciate your response.
    Thanks a lot,
    Jeffrey

    Hello Hussein,
    Thanks for the documents.
    I already set s_tools_twotask and s_weboh_twotask with their respective values. But still form session is disconnected after failure of db node where the session is connected. Can you please help to verify if my tnsnames.ora is correct which is automatically generated by autoconfig.
    My tnsnames.ora is similar to this:
    DP1_806_BALANCE=
    (DESCRIPTION_LIST=
    (DESCRIPTION=
    (ADDRESS=(PROTOCOL=tcp)(HOST=dbp02-vip.xxx)(PORT=1521))
    (CONNECT_DATA=
    (SERVICE_NAME=DP1)
    (INSTANCE_NAME=DP12)
    (DESCRIPTION=
    (ADDRESS=(PROTOCOL=tcp)(HOST=dbp01-vip.xxx)(PORT=1521))
    (CONNECT_DATA=
    (SERVICE_NAME=DP1)
    (INSTANCE_NAME=DP11)
    DP1_BALANCE=
    (DESCRIPTION=
    (LOAD_BALANCE=YES)
    (FAILOVER=YES)
    (ADDRESS_LIST=
    (ADDRESS=(PROTOCOL=tcp)(HOST=dbp02-vip.xxx)(PORT=1521))
    (ADDRESS=(PROTOCOL=tcp)(HOST=dbp01-vip.xxx)(PORT=1521))
    (CONNECT_DATA=
    (SERVICE_NAME=DP1)
    Thank you so much,
    Jeffrey

Maybe you are looking for

  • XSLT Redirect extension in SAP PI

    Hi, We are trying to use XSLT redirect function PI 7.11 mapping. I can't find the actual class path name for Redirect class XSLT processor used in PI which I believe is XALAN. The XSLT syntax i am trying is: ?xml version="1.0" encoding="UTF-8"?> <xsl

  • Passing Invoice Payment in Consolidation Scenario

    Hello, I'm writing an scenario for consolidation more Business One Companies in one HQ Company. I'have no problem with BP, and Invoice but a question is: If I want pass Incoming/Outgoing Payment referring some AP or AR Invoivces, how can I close the

  • Maintenance windows applies only to task sequences doesn't work

    Problem: SCCM 2012 R2 CU4 Task sequence deployment run outside maintenance windows when the maintenance windows is set to apply only to task sequences. When the maintenance windows is set to apply to All deployments, the task sequence deployment run

  • Editing chart Axis label

    Hi. I have a report where one chart repeats one time, and in Preview, I am able to click on the Axis label and find an option to Edit the label, where I define 1 - 12 as Jan - Dec. However, another chart repeats for 80 or so pages, thus I can't use P

  • UTC Date Format

    Hi, I am facing the following problem. Say If I use the following select command select upd_date from table where id=123 I get as result => 22.08.07 I know that this result is in UTC Format. I would like to get the localformat with hour min and sec.