Skip to main content

Concurrent Processing References


    Note 1160285.1 - Application Technology Group (ATG) Product Information Center (PIC)
    Note 1304305.1 - Concurrent Processing - Product Information Center (PIC)
    Note 1411723.1 - Concurrent Processing Analyzer for E-Business Suite
    Note 1499538.1 - Concurrent Processing Sample SQL Statements

    Note 1057802.1 - Concurrent Processing - Best Practices for Performance for Concurrent Managers in E-Business Suite
    Note 1399454.1 - Tuning Output Post Processor (OPP) to Improve Performance
    Note 104452.1 - Concurrent Processing - Troubleshooting Concurrent Manager Issues (Unix specific)
    Note 225165.1 - Patching Best Practices and Reducing Downtime
    Note 957426.1 - Health Check Alert: Invalid objects exist for one or more of your EBS applications
    Note 104457.1 - Invalid Objects In Oracle Applications FAQs
    Note 261693.1 - Concurrent Processing - Troubleshooting Concurrent Request ORA-20100 errors in the request logs
    Note 822368.1 - Concurrent Processing - How To Run the Purge Concurrent Request FNDCPPUR, Which Tables Are Purged, And Other Known Issues
    Note 762024.1 - Concurrent Processing - How To Ensure Load Balancing Of Concurrent Manager Processes In PCP-RAC Configuration
    Note 134007.1 - Concurrent Processing - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables
    Note 760386.1 - 749748.1 - Concurrent Processing - How to Cancel a Concurrent Request Stuck in the Queue?
    Note 559996.1 - 1066332.1 - Concurrent Processing - One Concurrent Manager SQL statement shows excessive executions
    Note 104282.1 - Concurrent Processing - Purge Concurrent Request and/or Manager Data Program (FNDCPPUR)
    Note 1312632.1 - Concurrent Processing - ICM log file shows 'CONC-SM TNS FAIL', 'Call to PingProcess failed', and/or 'Call to StopProcess              failed' for

    FNDCPGSC/FNDOPP
    Note 1086013.1 - Concurrent Processing - How to run the Purge Concurrent Request and/or Manager Data program, and which tables does it             purge?   
    Note 134035.1 - ANALYZEREQ.SQL - Detailed Analysis of One Concurrent Request (Release 11 and up)
    Note 171855.1 - CCM.sql Diagnostic Script for Concurrent Manager
    Note 134033.1 - ANALYZEPENDING.SQL - Analyze all Pending Requests
    Note 164978.1 - REQCHECK.sql - Diagnostic Script for Concurrent Requests
    Note 213021.1 - Concurrent Processing (CP) / APPS Reporting Scripts
    Note 216205.1 - Database Initialization Parameters for Oracle Applications Release 11i
    Note 396009.1 - Database Initialization Parameters for Oracle E-Business Suite Release 12   

Comments

Post a Comment

Popular posts from this blog

CLSRSC-430: Failed to start rolling patch mode

############################################################ GRID PSU Failed on Node2: =========================== [root@server1 tmp]# /oracrs/oracle/product/12102/OPatch/opatchauto apply /path1/patches/23273629 -oh /oracrs/oracle/product/12102 -ocmrf /tmp/ocm.rsp OPatch Automation Tool Copyright (c)2014, Oracle Corporation. All rights reserved. OPatchauto Version : 12.1.0.1.10 OUI Version        : 12.1.0.2.0 Running from       : /oracrs/oracle/product/12102 opatchauto log file: /oracrs/oracle/product/12102/cfgtoollogs/opatchauto/23273629/opatch_gi_2016-11-25_06-13-44_deploy.log Parameter Validation: Successful Configuration Validation: Successful Patch Location: /path1/patches/23273629 Grid Infrastructure Patch(es): 21436941 23054246 23054327 23054341 DB Patch(es): 23054246 23054327 The following patch(es) are duplicate patches with patches installed in the Oracle Home.  [ 20299023] You hav...
2 comments
Read more

ORA-27102: out of memory Linux-X86_64 Error: 28: No space left on device

Upon startup of Linux database get ORA-27102: out of memory Linux-X86_64 Error: 28: No space left on device (Doc ID 301830.1) Issue: ====== ORA-27102: out of memory Linux-x86_64 Error: 28: No space left on device Solution: ========= 1. Ask SA to increase "kernel.shmall" in /etc/sysctl.conf     Formula:     RAM * 1024 * 1024 * 1024 / page_size     Ex:-     RAM = 50GB     $getconf PAGE_SIZE ==> 4096     50*1024*1024*1024/4096 = 13107200 ==> kernel.shmall 2. After updating kernel.shmall, ask SA to do "sysctl -p" to activate changes. 3. Start the DB Note: ==== Kernel values will be set in below files 1. Updating below files doesn't require system reboot.     /proc/sys/kernel/shmmax     /proc/sys/kernel/shmall     /proc/sys/kernel/shmmni     Usage:  # echo "536870912" > /proc/sys/kernel/shmmax       ...
Post a Comment
Read more