Website Design, Website Development, Shopping Carts, Content Management Systems, Custom Programming, Custom Applications Appsdba: Sniped Sessions Shadow Processes !!!!!!!

Oracle Applications, Middleware, Database, DB RAC & HA

It is place where anyone grab more knowledge about Oracle Applications, middleware etc.

 
APPS R12
  • File System
  • Tech Stack
  • Admin Scripts
  • Forms Mode
  • APPS 11i
  • Know more
  • Maintenance Mode
  • Maintenance Mode(New)
  • Patching
  • APPS Scripts
  • Database Scripts
  • Protect APPS Password
  • Concurrent Manager
  • Database Refersh
  • Patchset Utility
  • Forms Data Loader
  • Web Server
  • Space Required
  • Responsibilities Of APPSDBA
  • OAS 9i/10gR2
  • Software Load Balancer
  • OAS 10gR3
  • Components
  • HTTP Server as Port 80
  • Database
  • Enable Archive
  • Clear Temp Tablespace
  • Drop DB (New in 10g)
  • Database Performance
  • Oracle Process
  • Advanced Topic
  • Database RAC

  • Do you know
  • Clusterware
  • Manage RAC Environment
  • High Availability
  • Certifications
  • EBS R12 Beta Exam
  • APPS 11i - 1z0-233
  • RAC 10gR2 - 1z0-048
  • Oracle Certifications
  • DBA Tools
  • TOAD
  • KEEP TOOL
  • ORACLE's SQL DEVELOPER
  • Spotlight on Oracle E-Business
  • DBDiff For Oracle

  • Sniped Sessions Shadow Processes !!!!!!!
    Tuesday, June 10, 2008
    When idle_time exceeds, the session status becomes 'sniped' in v$session, but sniped sessions never get cleaned up.
    Using 'alter system kill session' to kill the session, session status becomes 'killed' in v$session, but still is never cleaned up.

    What happens is this:
    1) The user leaves their session idle
    2) Oracle sets the status to "sniped" (i.e. session is inactive, waiting on client)
    3) Once the message is displayed, the session is terminated and the user must reconnect
    It does not disconnect the session. It changes the status to from INACTIVE to SNIPED.

    Set Parameter
    Show parameter resource_limit
    SQL> show parameter resource_limit
    NAME TYPE VALUE
    ------------------------------------ ----------- ------------------------------
    resource_limit boolean FALSE

    If this parameter is false.I changed RESOURCE_LIMIT=TRUE make it true as following
    ALTER SYSTEM SET RESOURCE_LIMIT = TRUE SCOPE=BOTH

    Create New Profile
    CREATE PROFILE "INACT_SESS" LIMIT IDLE_TIME 10;
    Newly created profile assign to user
    ALTER USER apps PROFILE inact_sess;
    Query against Sniped status in v$session
    Select * from v$session where status=’SNIPED’;

    Shell Script to kill sniped processes from OS level :
    Suppose Script Name : snip_kill_proc.sh
    #!/bin/sh
    tmpfile=/tmp/tmp.$$
    su - testora -c /d01/oracle/product/10.2.0/bin/sqlplus /nolog < connect / as sysdba
    spool kill_sniped_sessions.lst
    select p.spid from v\$process p,v\$session s
    where s.paddr=p.addr
    nd s.status='SNIPED';
    spool off
    EOF
    for x in `cat /d01/testora/kill_sniped_sessions.lst | grep "^[0123456789]"`
    do
    kill -9 $x
    done
    rm /d01/testora/kill_sniped_sessions.lst
    Execute it by issue this command: sh snip_kill_proc.sh

    We can Schedule this shell script in crontab as follow :

    */30 * * * * /d01/backup/scripts/snip_kill_proc.sh > /d01/backup/scripts/snip_kill_proc.log 2>&1


    For Your Reference : Metalink Note id: 96170.1 Script for killing sniped sessions shadow processes
    posted by Jaswinder Singh @ 4:53 AM  
    0 Comments:
    Post a Comment
    << Home
     
    About Me

    Name: Jaswinder Singh
    Home: Bangalore, Karnataka, India
    Certifications: RAC Certified Expert, OCP 9i, 10g & 11i
    About Me: I am working as APPSDBA, have hands on experience on DB RAC, HA on OAS 10g and Oracle Applications.
    See my complete profile
    Previous Post
    Archives
    Links
    Powered by

    Free Blogger Templates

    BLOGGER

    ADVERTISEMENT
    click here
    © 2006 Appsdba .