Fixing OPP Concurrent Manager in System Hold Status

Oracle E-Business Suite R12.1.3 (Out-of-Support Environment)

While supporting an old customer still running Oracle E-Business Suite R12.1.3, an out-of-support release, I recently encountered an issue where the Output Post Processor (OPP) Concurrent Manager moved into a System Hold state.

Legacy EBS environments frequently surface such issues due to:

• Lack of vendor patches and security fixes

• Aging binaries and libraries

• Configuration drift over long operational periods

During routine monitoring of the Concurrent Manager Administer screen in the production environment, the following message was observed:

OPP Concurrent Manager status:
“System Hold, Fix Manager before resetting counters”

This issue had appeared multiple times previously and, if left unresolved, directly affects report output generation (PDF/XML) and business continuity.

This article documents the exact steps I followed to recover the OPP Concurrent Manager successfully, without any data impact.

Observation

In older, out-of-support Oracle EBS releases, the System Hold status for OPP typically indicates internal inconsistencies such as:

• Unclean or improper application shutdowns

• Orphaned or stuck Concurrent Manager processes

• Corrupted or outdated Concurrent Manager binaries

Given the nature of legacy environments, a controlled shutdown, relink, and cleanup approach is the safest and most reliable fix.

SOLUTION

Step 1: Cleanly Shut Down the Applications Tier

Ensure all application services are stopped and no Concurrent Manager processes remain active.

Verify that no related processes are running:

Step 2: Stop the Database

Log in as the database owner and shut down the database cleanly.

Step 3: Start the Database

Once the database is fully stopped, start it again.

Step 4: Relink Concurrent Manager Binaries

Navigate to the $FND_TOP/bin directory and relink the core Concurrent Manager executables.

This step rebuilds the binaries and resolves any corruption or linking inconsistencies.

Step 5: Run Concurrent Manager Cleanup Script

Execute the cleanup script and commit the changes.

This resets internal Concurrent Manager data and clears invalid counters.

Step 6: Validate FNDSM Concurrent Queue

Confirm that the FNDSM queue exists and is properly registered.

Step 7: Start the Applications Tier

Bring all application services back online.

Post-Fix Verification

After completing all steps:

• Navigate to Concurrent → Manager → Administer

• Confirm the OPP Concurrent Manager status is Running

• Submit a test request that generates PDF/XML output

Have you faced similar issues in legacy Oracle E-Business Suite environments?

Feel free to share your experience or reach out if you need help planning an upgrade or stabilization strategy.