How to Fix adop -validate Failure on the Admin Node in Oracle E-Business Suite
Table of Contents
When running adop -validate in Oracle E-Business Suite, validation can fail on the Admin node even when SSH connectivity between the application nodes is working correctly. One common scenario is an AdopValidate failure after patch file system AutoConfig activity.
This article explains how to troubleshoot and resolve an adop -validate failure on the Admin node, using an example where validation fails on ebs301u while another node, ebs302u, is available.
Understanding the adop -validate Failure
Typical errors in the ADOP log may look like this:
[ERROR] Node: “DEV01u” Status: “failed”
[ERROR] AdopValidate failed on Node: “DEV02u”
[ERROR] AdopValidate failed or is incomplete on Admin node: DEV01u
[ERROR] Unable to continue processing on other available nodes: DEV02u
[UNEXPECTED] Error running “AdopValidate” on node(s): DEV01u.
[UNEXPECTED] Remote action failed.
In this situation, SSH connectivity may be successful and there may be no existing patching cycle. The failure occurs specifically when AdopValidate runs on the Admin node.
If the failure occurs immediately after AutoConfig on the patch file system, verify AutoConfig on the patch file systems of all relevant nodes before rerunning validation.
Symptoms
The environment may show the following conditions:
- Admin node: DEV01u
- Additional application node: DEV02u
- SSH connectivity: Successful
- No existing ADOP patching cycle
- AdopValidate fails on DEV01u
- Processing does not continue on DEV02u
- Failure occurs around patch file system AutoConfig activity
These symptoms can indicate that the patch file system configuration is not consistent or that AutoConfig did not complete successfully on one of the nodes.
Resolution: Fix adop -validate AutoConfig Issues
1. Disable the Online Patching Logon Trigger
Before running AutoConfig, connect to the Oracle E-Business Suite database as the APPS user:
sqlplus apps/<apps_password>
Then disable the online patching logon trigger:
EXEC ad_zd.alter_logon_trigger(‘DISABLE’);
Confirm that the procedure completes successfully before continuing.
Important: Use the appropriate database credentials and follow your organization’s change-management procedures when modifying the trigger.
2. Run AutoConfig on the Patch File System
Run AutoConfig on the patch file system of both application nodes.
Start with DEV02u:
source <PATCH_FS_ENV_FILE>
adautocfg.sh
Wait for AutoConfig to finish and verify that it reports:
AutoConfig completed successfully.
Next, perform the same operation on DEV01u:
source <PATCH_FS_ENV_FILE>
adautocfg.sh
Again, verify that AutoConfig completes successfully.
Checking both nodes is important because an incomplete or inconsistent patch file system configuration can cause subsequent ADOP validation to fail.
3. Re-Enable the Online Patching Logon Trigger
After AutoConfig successfully completes on both nodes, reconnect to the database as the APPS user:
sqlplus apps/<apps_password>
Enable the trigger:
EXEC ad_zd.alter_logon_trigger(‘ENABLE’);
COMMIT;
Verify the trigger status:
SELECT status
FROM user_triggers
WHERE trigger_name = ‘AD_ZD_LOGON_TRIGGER’;
The expected result is:
STATUS
——–
ENABLED
Do not proceed with the validation until the trigger status has been confirmed as ENABLED.
4. Run adop -validate Again
Once AutoConfig has completed successfully on both patch file systems and the online patching logon trigger has been re-enabled, run:
adop -validate
Review the ADOP log and confirm that validation completes without errors.
Why Does adop -validate Fail After AutoConfig?
adop -validate checks important aspects of the Oracle E-Business Suite online patching environment. If AutoConfig has not completed correctly on a patch file system, configuration files or environment settings may not be synchronized as expected.
In a multi-node environment, it is therefore important to verify the patch file system configuration on all participating application nodes, not just the node where the error was initially reported.
Troubleshooting Checklist
Before rerunning adop -validate, confirm:
- SSH connectivity works between the application nodes.
- There is no conflicting or existing ADOP patching cycle.
- The online patching logon trigger was disabled before AutoConfig.
- AutoConfig was run on the patch file system of ebs302u.
- AutoConfig was run on the patch file system of ebs301u.
- Both AutoConfig executions completed successfully.
- AD_ZD_LOGON_TRIGGER was re-enabled.
- The trigger status is ENABLED.
- adop -validate was rerun after completing the above steps.
Frequently Asked Questions
What causes adop -validate to fail on the Admin node?
One possible cause is an incomplete or inconsistent patch file system configuration, particularly when the failure occurs around patch file system AutoConfig processing. AutoConfig should be checked on all relevant application nodes.
Should AutoConfig be run on both nodes?
Yes. In a multi-node Oracle E-Business Suite environment, verify AutoConfig on the patch file system of each participating node when troubleshooting this type of validation failure.
What should the AD_ZD_LOGON_TRIGGER status be before running adop -validate?
The trigger should be enabled after AutoConfig completes successfully:
AD_ZD_LOGON_TRIGGER = ENABLED
Is successful SSH connectivity enough to resolve the problem?
No. SSH connectivity only confirms that the nodes can communicate remotely. AdopValidate can still fail because of application, database, patch file system, or configuration issues.
Conclusion
An adop -validate failure on the Admin node does not necessarily indicate an SSH or node-connectivity problem. When the failure occurs after patch file system AutoConfig activity, verify AutoConfig on both application nodes, ensure the online patching logon trigger is correctly disabled and re-enabled, and then rerun adop -validate.
For the example environment, the key sequence is:
Disable AD_ZD_LOGON_TRIGGER
↓
AutoConfig on DEV02u patch file system
↓
AutoConfig on DEV01u patch file system
↓
Enable AD_ZD_LOGON_TRIGGER
↓
Verify trigger status = ENABLED
↓
Run adop -validate
This procedure provides a structured approach to troubleshooting Oracle E-Business Suite ADOP validation failures related to patch file system AutoConfig.
