Davis Apps DBA

 When applying CPU (Critical Patch Update) patches or standard patch sets in Oracle E-Business Suite (EBS) R12.2, the Online Patching Utility (adop) relies on a strict sequence of execution phases: prepare, apply, finalize, cutover, and cleanup. Among these, the cutover phase is the most critical operational event. It performs the actual switchover between the RUN and PATCH file systems (fs1 and fs2), bringing down the application services, swapping the dual file system mount points/environment variables, and bringing the new application services back online. A common real-world issue DBAs face during cutover is an unexpected hang where adop appears stuck while shutting down internal managers or service controllers. In this post, we will walk through a live diagnostic scenario during a July 2026 CPU Patching cycle, analyze why orphaned Mobile Supply Chain Applications / Mobile Web Applications (MSCA/MWA) processes block adop, dive deep into Linux process hierarchies (PPID=1), ...

Understanding OEM 13c Agent Out-of-Sync Errors In Oracle Enterprise Manager (OEM) 13c, the Management Agent acts as the vital communication bridge between target host systems and the Management Repository (OMR). When an agent status throws the error "Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered," it signifies a mismatch in sequence numbers or timestamp tokens between the agent state and the Management Server (OMS). This situation usually occurs during: Host-level server recovery or disaster recovery tests. Unscheduled agent re-installations without clearing old target metadata. Long periods of network disconnection between the host and OMS. Abrupt server shutdowns causing local state corruptions in the agent's filesystem. Prerequisites & Initial Checks Before starting the resynchronization process, log in to the affected target node via SSH as the Oracle installation owner and run an initial status check: $ ...

Overview of AutoConfig RC-50014 Error During Oracle E-Business Suite (EBS) cloning, environment patching, or system configuration updates, running adconfig.sh (AutoConfig) is mandatory to synchronize context files with system templates. A common failure during the ApplyApplTop execution phase triggers the error: ERROR: RC-50014: Fatal: Execution of AutoConfig failed This error indicates that the underlying deployment script was unable to execute terminal commands or write XML driver properties to the application file system, bringing the clone or patching process to a complete halt. Root Causes The RC-50014 exception usually points to one of three underlying system issues: Permission Mismatches: The Linux account running AutoConfig lacks read/write/execute permissions on APPL_TOP or sub-directories (e.g., inst/apps/$CONTEXT_NAME/admin/log ). Environment Variable Corruption: Missing or incorrectly set PATH , LD_LIBRARY_PATH , or ORACLE_HOME variables in the APPS tier environment f...