Oracle Applications DBA APPSLab

Oracle APPSLab is a place where you get what you look for on Oracle’s Applications, Database, Fusion Middleware and many more.

		
		

Oracle Applications DBA APPSLab

CATEGORIES
  • Apps R12

    Start R12 in forms socket mode
    Changing Application tier Platforms
    Installation Of Apps R12
    Upgrade to Apps R12
    Get Current Patchset level
    Clone and Autoconfig logs
    Enable OEM in Release 12
    Collecting Config info for HTTP
    Regenerate forms in R12
    Downtime and Apache restrict mode

  • Apps 11i

    Prevent Conc request on new clone
    Queries - Concurrent Requests
    Personalizing the Login Page
    Versions of Apps techstack
    Replacing Jinitiator with JRE
    Reloading APPS Java Class Object
    Count total number of Users
    ICX: Session Timeout
    Generate Stack trace For Forms
    Configure Apache on ports < 1024
    Apps Hot backup Cloning
    Recover if Context file is lost
    Redirect Rapid Install Login
    How to Clean Non-existent Nodes
    Remove Portal Schema from 11i
    Clean Concurrent Manger Tables
    Creating custom Application
    Enable f60cgi direct login
    Downtime in restricted mode
    Maintenance Mode in Apps 11i
    Check if on Autoconfig latest Patch
    Patch Troubleshooting
    Apply Patch when adpatch is running
    Check Forms Patch Set Level
    Check AOL Table is Locked
    Java version Used by Jserv
    Verify opertion of reports server
    Relink Oracle Applications 11i
    Change IP Address in Applications

    Add to Technorati Favorites

  • Common Apps 11i and R12

    Scripts: monitor concurrent jobs
    Create User Event trace
    Apps Interview Qs-Part I
    Compile Invalid Objects in APPS
    Setup Password Security
    Create Web Link to Forms Menu
    Pinning Oracle Apps Objects
    Change IP in Oracle Apps
    Check if a Product is Installed
    Forms Runtime Diagnostics
    Access Apps from Linux client
    Recover if context file is lost
    Redirect Rapid Install Page
    Check if a patch was applied
    Check apps components version
    E-business Suite System survey
    Scripts to monitor jdbc conn
    Distribute Load of Conc Req
    Check if a product is installed
  • Database 9i-10g-11g

    Analyze Oracle Statspack
    SQL: Command line history
    How to recreate OraInventory
    Oracle DBA Cheat Sheet
    Formatted Explain Plan
    Recovery Catalog for RMAN
    RMAN Duplicate on new host
    RMAN Duplicate on same host
    Installation of 11G
    Background processes -11G
    Alert Logfiles in 11G
    Datapump:Specify a query
    Copy schemas to new db
    Flashback database in 10G
    Flashback Drop 10G
    Flashback table/query 10G
    Clone Database on same machine
    Move Database to diff Platform
    Sizing Undo tablespace
  • Oracle 10g AS

    Using Virtual Hostname with AS
    Relinking 10g Application server
  • Collaboration Suite

    Installation of OCS
  • Fusion Middleware
  • Unix / Linux

    Command Reference
  • Certifications
  • E-Mail Subscription

    Enter your email address:

    Delivered by FeedBurner

    Search
    Only search this Blog
    Add Ons

     Subscribe in a reader



    Add to Google Reader or Homepage

    How to Clean 11i Apps Concurrent Manager Tables
    Sunday, October 21, 2007
    Email this  |  Share on Facebook  |  Subscribe to this feed

    This can be used as a method to clear the errors upon bringing the internal manager back up.

    Use this method for 11.5.7+ instances provided the managers are down and no FNDLIBR processes are
    still running.
     
    FIRST
    Update process status codes to TERMINATED
    Updating invalid process status codes in FND_CONCURRENT_PROCESSES


    SELECT concurrent_queue_name manager,
    concurrent_process_id pid,
    process_status_code pscode
    FROM fnd_concurrent_queues fcq, fnd_concurrent_processes fcp
    WHERE process_status_code not in ('K', 'S')
    AND fcq.concurrent_queue_id = fcp.concurrent_queue_id
    AND fcq.application_id = fcp.queue_application_id;

    UPDATE  fnd_concurrent_processes
    SET process_status_code = 'K'
    WHERE process_status_code not in ('K', 'S');
    commit;
    SECOND
    Set all managers to 0 processes
    Updating running processes in FND_CONCURRENT_QUEUES
    Setting running_processes = 0 and max_processes = 0 for all managers


    UPDATE fnd_concurrent_queues
    SET running_processes = 0, max_processes = 0;
    commit;
    THIRD
    Reset control codes
    Updating invalid control_codes in FND_CONCURRENT_QUEUES

    SELECT  concurrent_queue_name manager,
    control_code ccode
    FROM fnd_concurrent_queues
    WHERE control_code not in ('E', 'R', 'X')
    AND control_code IS NOT NULL;

    UPDATE fnd_concurrent_queues
    SET control_code = NULL
    WHERE control_code not in ('E', 'R', 'X')
    AND control_code IS NOT NULL;
    commit;
    FOURTH
    Also null out target_node for all managers
    UPDATE  fnd_concurrent_queues
    SET target_node = null;
    commit;
    FIFTH

    Set all 'Terminating' requests to Completed/Error
    Also set Running requests to completed, since the managers are down
    Updating any Running or Terminating requests to Completed/Error

    SELECT  request_id request,
    phase_code pcode,
    status_code scode
    FROM fnd_concurrent_requests
    WHERE status_code = 'T' OR phase_code = 'R'
    ORDER BY request_id;

    UPDATE fnd_concurrent_requests
    SET phase_code = 'C', status_code = 'E'
    WHERE status_code ='T' OR phase_code = 'R';
    commit;
    SIXTH
    Set all Runalone flags to 'N'
    Updating any Runalone flags to 'N'
    set serveroutput on
    set feedback off
    declare
    c pls_integer := dbms_sql.open_cursor;
    upd_rows pls_integer;
    vers varchar2(50);
    tbl varchar2(50);
    col varchar2(50);
    statement varchar2(255);
    begin

    select substr(release_name, 1, 2)
    into vers
    from fnd_product_groups;

    if vers >= 11 then
    tbl := 'fnd_conflicts_domain';
    col := 'runalone_flag';
    else
    tbl := 'fnd_concurrent_conflict_sets';
    col := 'run_alone_flag';
    end if;


    statement := 'update ' || tbl || ' set ' || col || '=''N'' where ' || col || ' = ''Y''';
    dbms_sql.parse(c, statement, dbms_sql.native);
    upd_rows := dbms_sql.execute(c);
    dbms_sql.close_cursor(c);
    dbms_output.put_line('Updated ' || upd_rows || ' rows of ' || col || ' in ' || tbl || ' to ''N''');
    end;
    /
    commit;
    Now you can start with your Concurrent Managers...!!!!!!!!

    Labels:


    Read more!


    Translate 
    Posted by Famy Rasheed  
    2 Comments:
    • At January 25, 2008 2:46 AM, Blogger Murali said…

      Thanks. This article helped me with my TEST environment clean up.

       
    • At May 15, 2008 12:03 AM, Anonymous Anonymous said…

      Hi,

      I think this is good script.
      But I have one question for the oracle 11.5.9 concurrent manager tables cleanup.
      So Can we use the cmclean.sql for the concurrent manager tables cleanup?

      Thanks
      OKY

       
    Post a Comment
    << Home
     
    About Me

    Name: Famy Rasheed
    Home: Bangalore, India

    about me:

    I am working as Oracle Applications DBA specializing in E-Business Suite 11i/12i and Fusion Middleware.

    See my complete profile

    Recent Entries
    Archives
    Links
    Powered by



    BLOGGER