Adop Phase Cutover Failing with AutoPatch AidafoGetFileDbVersion INFO ORA-01403 No Data Found

Adop Phase Cutover Failing with AutoPatch| Oracle E-Business Suite (EBS) Release 12.2 introduces Online Patching, a mechanism that enables you to apply patches to your EBS environment while it remains available for end-users. The key tool used during the patching process is the AD Online Patching Utility (adop). However, there are instances when the Adop Phase=Cutover fails, and you encounter the error message “AidafoGetFileDbVersion: INFO: ORA-01403: No Data Found.” In this blog, we will delve into the common causes of this error and provide troubleshooting steps to resolve it effectively.

  1. Understanding the Error:

The error “AidafoGetFileDbVersion: INFO: ORA-01403: No Data Found” typically occurs during the Cutover phase of the AD Online Patching process. This error suggests that ADOP is unable to retrieve the version information for a specific file from the database tables.

  1. Possible Causes:

There are several reasons why this error might occur:

a. Corrupted Data: The data in the database tables related to the file version may be corrupted or missing.

b. Incorrect Patching: It’s possible that the patching process didn’t apply correctly to the file in question.

c. Concurrent Processes: Concurrent execution of ADOP or other database-related activities might interfere with the data retrieval process.

d. Environment Issues: Environmental factors such as resource constraints, database performance, or network connectivity problems can also contribute to the error.

  1. Troubleshooting Steps:

To resolve the “AidafoGetFileDbVersion: INFO: ORA-01403: No Data Found” error during the Adop Phase=Cutover, follow these steps:

a. Review ADOP Log Files: Examine the ADOP log files to identify any specific file or database table causing the error. Understanding which file is encountering the issue can narrow down the troubleshooting process.

b. Check Database Objects: Verify the integrity of the database objects related to the problematic file. Run relevant SQL queries to check for the existence and validity of the data in the concerned tables.

c. Ensure Proper Patching: Ensure that the patching process completed successfully without errors for all relevant files. If there were any errors during patch application, address them and rerun the patching process.

d. Check Concurrent Processes: Identify any concurrent processes that might be running during the Cutover phase. If possible, reschedule or temporarily halt concurrent processes to avoid interference.

e. Verify Environment Settings: Check your environment settings, including database parameters and resource availability, to ensure optimal performance during the patching process.

f. Apply Required Patches: In some cases, you may need to apply specific patches or bug fixes related to the ORA-01403 error. Check Oracle Support for any relevant patches.

  1. Seek Expert Assistance:

If the troubleshooting steps mentioned above do not resolve the issue, or if you encounter complex scenarios, it’s best to seek expert assistance from Oracle Support or experienced EBS consultants. They can perform in-depth diagnostics and provide tailored solutions based on your specific environment.


Encountering the “AidafoGetFileDbVersion: INFO: ORA-01403: No Data Found” error during the Adop Phase=Cutover can be frustrating, but it’s crucial to address the issue promptly to ensure a successful patching process. By following the troubleshooting steps outlined in this blog, you can identify the root cause of the error and take appropriate measures to resolve it. Always remember to perform adequate testing in a non-production environment before applying any fixes to your live EBS environment.

Leave a Comment