22
Jan

ADOP Fails with message " [ERROR]: Domain might be locked by some other WLS user process" and "[UNEXPECTED]Error 1 occurred while Executing txkADOPValidation script

Author: Shakeeb Petkar | Category: EBS 12.2.x, TroubleshootingComments Off on ADOP Fails with message " [ERROR]: Domain might be locked by some other WLS user process" and "[UNEXPECTED]Error 1 occurred while Executing txkADOPValidation script | Tags: , , , , , , , , , ,

Symptoms:


While running an ADOP session it fails due to the Weblogic domain being locked by another process.

 

[applprod@erpapp1 ~]$ adop phase=fs_clone force=yes

Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:

Validating credentials.

Initializing.
Run Edition context : /u01/oracle/EBSPROD/fs2/inst/apps/EBSPROD_erpapp1/appl/admin/EBSPROD_erpapp1.xml
Patch edition context: /u01/oracle/EBSPROD/fs1/inst/apps/EBSPROD_erpapp1/appl/admin/EBSPROD_erpapp1.xml
Patch file system free space: 273.40 GB

Validating system setup.
Node registry is valid.
[WARNING] SYS.DUAL table has incorrect privileges
Shut down the application tier services and then run the following commands in the order shown
sqlplus apps/ @ $AD_TOP/patch/115/sql/ADFIXUSER.sql
sqlplus apps/ @ $AD_TOP/sql/adutlrcmp.sql

Checking for existing adop sessions.
No pending session exists.
Starting new adop session.

===========================================================================
ADOP (C.Delta.11)
Session ID: 48
Node: erpapp1
Phase: fs_clone
Log: /u02/oracle/EBSPROD/fs_ne/EBSapps/log/adop/48/20190902_123003/adop.log
===========================================================================

Validating configuration on node: [erpapp1].
Log: /u02/oracle/EBSPROD/fs_ne/EBSapps/log/adop/48/20190902_123003/fs_clone/validate/erpapp1
[WARNING]: There could be issues while validating the ports used for E-Business Suite instance against ports used in /etc/services. Refer the log file for more details.
[ERROR]: Domain might be locked by some other WLS user process
[UNEXPECTED]Error occurred running "perl /u02/oracle/EBSPROD/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl -contextfile=/u01/oracle/EBSPROD/fs2/inst/apps/EBSPROD_erpapp1/appl/admin/EBSPROD_erpapp1.xml -patchctxfile=/u01/oracle/EBSPROD/fs1/inst/apps/EBSPROD_erpapp1/appl/admin/EBSPROD_erpapp1.xml -phase=fs_clone -logloc=/u02/oracle/EBSPROD/fs_ne/EBSapps/log/adop/48/20190902_123003/fs_clone/validate/erpapp1 -promptmsg=hide"
[UNEXPECTED]Error 1 occurred while Executing txkADOPValidation script on erpapp1

[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.

adop exiting with status = 1 (Fail)

 

Cause:

If the EBS Weblogic domain is in EDIT mode, it can cause adop to fail.

Someone with administrator privileges on WLS Admin Console may have locked the Weblogic domain for making changes, and has not released the checkout.

This leaves the domain in edit mode, resulting in the issue.
 

Solution:

1. Start the admin server on the run file system (if not started already).

2. Login in to WLS Admin Console (http(s)://hostname.domain:/console)

3. Click on the "Activate Changes" or the "Release Configuration" button (depending on the version) in the "Change Center" region on the top left corner.

4. Logout of the WLS console.

5. Rerun the adop command and confirm if it completes successfully.

Back to Top