OracleFree checklistPDF, Excel, Word exportOracle E-Business SuiteAll Oracle E-Business Suite tools

Oracle EBS Concurrent Manager Not Starting: Troubleshooting Checklist

This checklist walks an EBS 12.1 or 12.2 apps DBA through a concurrent manager that will not start, from confirming the state to reading the ICM log, checking FND tables and node definitions, and recovering safely. Critical items are the ones that can corrupt or lose request history if skipped.

0%

0 of 33 items complete

7 critical items still open - these are the highest-risk gaps.

Download checklist:

1. Confirm it is really down

2. Read the logs

3. Database side

4. Node configuration

5. Network and listeners

6. Recovery

7. After start

Work top to bottom. Do not run cmclean.sql or any FND table cleanup with an open critical item in the Recovery group; backups and a confirmed full stop come first.

Send us your ICM log

Share the ICM log excerpt from the failed start and we will tell you which item in this checklist it points to.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

What the concurrent manager is

In Oracle E-Business Suite, concurrent processing runs batch programs (reports, interfaces, purges) in the background. The Internal Concurrent Manager (ICM) controls all other managers; it reads FND_CONCURRENT_QUEUES to know the target processes for each manager and asks the Service Manager (FNDSM) on each node to start them. The Standard Manager runs most requests, the Conflict Resolution Manager releases requests whose incompatibilities are clear, and service components such as the Output Post Processor and Workflow Mailer run under the same framework. If the ICM cannot start, nothing else does, which is why the ICM log is the first place to look.

Where to look in the system

The control script is adcmctl.sh in $ADMIN_SCRIPTS_HOME; on 12.2 it is in the run edition. Logs are in $APPLCSF/$APPLLOG: the ICM log is named after the database SID and date, and each manager writes its own log. In the forms interface, Administer Concurrent Managers under the System Administrator responsibility shows actual and target processes and lets you verify, restart or deactivate managers. In the database, FND_CONCURRENT_QUEUES holds manager definitions and state, FND_CONCURRENT_PROCESSES holds one row per manager process, and FND_NODES lists the nodes known to the instance.

  • FND_CONCURRENT_QUEUES: CONTROL_CODE, RUNNING_PROCESSES, MAX_PROCESSES, TARGET_NODE
  • FND_CONCURRENT_PROCESSES: PROCESS_STATUS_CODE, OS_PROCESS_ID, CONCURRENT_QUEUE_ID
  • FND_NODES: NODE_NAME, SUPPORT_CP

The usual causes

After a clone, the most common cause is FND_NODES still holding the source hostnames, so the ICM tries to start managers on a node that does not exist; clean it with FND_CONC_CLONE.SETUP_CLEAN and rerun AutoConfig. After a crash or kill, stale rows in FND_CONCURRENT_PROCESSES and nonzero RUNNING_PROCESSES make the ICM think managers are already up; Oracle's cmclean.sql (Doc ID 134007.1) resets them, but only with every manager stopped. Other causes: a full log file system, a changed APPS password not used in the start command, wrong TNS entries, and a stopped database listener.

Common mistakes

Running cmclean.sql while some FNDLIBR processes are still alive leaves orphan processes that keep processing requests outside the ICM's control. Deleting rows from FND_CONCURRENT_REQUESTS to clear a backlog destroys audit history; cancel requests instead. Restarting the whole application tier when only the concurrent tier is affected wastes time. Finally, do not change MAX_PROCESSES directly in the table; use Define Concurrent Manager work shifts so the change is recorded.

Frequently Asked Questions

What is the concurrent manager in Oracle EBS?

It is the framework that runs background programs. The Internal Concurrent Manager controls the others, Service Managers start processes on each node, the Standard Manager runs most requests and the Conflict Resolution Manager handles incompatibilities. Requests are stored in FND_CONCURRENT_REQUESTS and queued to managers by specialization rules.

How do I check concurrent manager status from the command line?

Run adcmctl.sh status apps/<password> from $ADMIN_SCRIPTS_HOME. It reports whether the Internal Concurrent Manager is running. Combine it with ps -ef | grep FNDLIBR on each node and the Administer Concurrent Managers form to see actual and target processes.

Is it safe to run cmclean.sql?

It is Oracle's non-destructive script for resetting concurrent manager tables, documented in Doc ID 134007.1, but only when all managers are stopped and no FNDLIBR processes remain. Back up the FND concurrent tables first and use the version from the current note.

How do I start the applications listener in EBS 12.2?

Use adalnctl.sh start from $ADMIN_SCRIPTS_HOME of the run edition, or adstrtal.sh to start all application tier services. The applications listener serves FNDFS, which you need to view concurrent request logs and output from the browser.

If you want your support team to ask EBS what is stuck in concurrent processing in plain English, on your own servers and read-only, we can set that up.

ArchRay builder
Design the on-prem AI stack for Oracle E-Business Suite: model, GPUs, RAG pipeline, guardrails
See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.
Open the builder

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

AI on your ERP

Integrations

Software