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

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

Read more...

6
Jan

ADOP Prepare Phase Fails With Error "runSyncFS sub-routine is called"

Symptoms:

ADOP Prepare phase fails while applying a patch.

Error:

[PROCEDURE] [END 2018/11/12 18:21:48] Acquiring lock on AD_ADOP_SESSION_PATCHES table
[PROCEDURE] [START 2018/11/12 18:21:48] Sync FS of RUN and PATCH
[PROCEDURE] Calling: /u02/oracle/ERPPROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl
[EVENT] Log: /u02/oracle/ERPPROD/fs_ne/EBSapps/log/adop/42/20181112_175050/prepare/erpisup
[UNEXPECTED]Error occurred running "perl /u02/oracle/ERPPROD/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl -contextfile=/u01/oracle/ERPPROD/fs1/inst/apps/erpprod_erpisup/appl/admin/erpprod_erpisup.xml -patchcontextfile=/u01/oracle/ERPPROD/fs2/inst/apps/erpprod_erpisup/appl/admin/erpprod_erpisup.xml -promptmsg=hide -console=off -patchtop=/u02/oracle/ERPPROD/fs_ne/EBSapps/patch -mode=update -sync_mode=patch -sessionid=42 -timestamp=20181112_175050 -workercount=8 -outdir=/u02/oracle/ERPPROD/fs_ne/EBSapps/log/adop/42/20181112_175050/prepare/erpisup -autoskip=No"
[PROCEDURE] [START 2018/11/12 18:22:29] Unlocking AD_ADOP_SESSION_PATCHES table
[STATEMENT] Unlocking AD_ADOP_SESSION_PATCHES table for erpisup having lock name ADPATCH

[PROCEDURE] [END 2018/11/12 18:22:29] Unlocking AD_ADOP_SESSION_PATCHES table
[UNEXPECTED]Error calling runSyncFS subroutine.
[ERROR] Prepare phase has failed.

Read more...

3
Jul

With AD-TXK Delta.9 and higher, Autoconfig Fails On PatchFS with error "ORA-12514: TNS:listener does not currently know of service requested

Symptoms:

 

When attempting to run autoconfig on patch fs the following error occurs.


ERROR
-----------------------
Enter value for 1: Enter value for 2: Enter value for 3: ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor

ERRORCODE = 1 ERRORCODE_END
.end std out.

.end err out.

 
Read more...

5
Jun

Change APPS password in EBS R12.2.x Delta 7 or above

Important: These steps must be carried out on the run file system. The FND_USER and FND_ORACLE_USERID tables should be backed up before any passwords are changed. Remove the backups after you have confirmed that the changes are successfully completed. Passwords for all the 3 schemas, APPS, APPLSYS and APPS_NE will be changed together while changing APPLSYS password.

1. Shut down the application tier services using the below script:

$INST_TOP/admin/scripts/adstpall.sh

2. Change the APPLSYS password using

 
There are 2 ways to change the APPLSYS password:
Read more...

7
Mar

Change Weblogic admin password in Oracle E-Business Suite R12.2.x

The steps mentioned in this document can be used to change the Oracle WebLogic Server Administration User Password in R12.2.x when the weblogic password is known.

Pre-requisite:

R12.AD.C.Delta.7 and R12.TXK.C.Delta.7 or later.
 

The release of R12.AD.C.Delta.7and R12.TXK.C.Delta.7 has brought in a lot of new features, one of them is a script to automate Changing Oracle WebLogic Server Administration User Password (Conditional to be on patch set level R12.AD.C.Delta.7 and R12.TXK.C.Delta.7 ).

The procedure used to change the Oracle WebLogic Server Administration User Password has been simplified and largely automated by the introduction of a new utility that performs what were previously manual steps.

The option to set the Oracle WebLogic Server Administration User password to a non-default value is available during Oracle E-Business Suite installation. This section describes the procedure to use (on the run file system) if you need to change the password at a later time.
 
The EBS WebLogic Domain uses Node Manager to control the Administration Server and the managed servers. For the EBS WebLogic Domain, the Node Manager and WebLogic Server Administration User passwords must be same, otherwise the AD control scripts will not work properly.
 
Important:
If you need to change the Administration User password, you must change the Node Manager password first. If you do not do this, the WebLogic Server configuration change will not be detected and the next online patching cycle may fail.
 
The instructions that follow should be performed on the run file system. The password change will be automatically propagated to the patch file system during the next adop prepare phase or fs_clone operation.
 
Read more...

Back to Top