Applying an Oracle datapatch/CPU installation fails specifically in Production (not in Test or Training) with 'start_processes: failed to open (Resource temporarily unavailable) pipe to SQL*Plus' and 'catconInit failed, exiting' — what's the actual cause, given the same patch installs fine elsewhere?

All FAQ questions / Platform, Aurena, and customization

Answer

This is a known Oracle-side issue where the datapatch tool's underlying Catcon.pm utility defaults its parallel worker-process count to cpu_count*2 — on a server with a notably higher CPU_COUNT than your other environments (which Production commonly has compared to Test/Training), this default can be high enough to exhaust available process/resource limits on that specific server, causing exactly this failure. Check the current value with SHOW PARAMETER cpu;, temporarily lower it (e.g. ALTER SYSTEM SET CPU_COUNT = 4;), run datapatch again, and once it completes successfully, restore CPU_COUNT back to its original value.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Platform, Aurena, and customization questions