DOYENSYS Knowledge Portal




We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal




Monday, December 19, 2016

Adpreclone Fails in EBS 12.2.3 : There is already an ACTIVE ADOP CYCLE with session id


Adpreclone Fails in EBS 12.2.3 : There is already an ACTIVE ADOP CYCLE with session id

Issue:

The below failure while executing :

Running perl /DB01/app/PROD/fs2/prodapps/appl/ad/12.0.0/patch/115/bin/adProvisionEBS.pl ebs-get-serverstatus -contextfile=/DB01/app/PROD/inst/fs2/inst/apps/PROD_DB01PRODapp01/appl/admin/PROD_DB01PRODapp01.xml -servername=AdminServer -promptmsg=hide

The Oracle WebLogic Administration Server is up.

There is already an ACTIVE ADOP CYCLE with session id : SP2-0640: Not connected 
adpreclone cannot be run with pending ADOP session.


Details:

Looking at the error message, it seems like  there is an open ADOP session. Basically in  Oracle EBS R12.2, we need to have all ADOP sessions completed or aborted before any cloning can be executed. While An active ADOP session , If any clone is performed, both filesystems can be put into trouble: RUN and PATCH. Hence we need to clear all ADOP sessions before executing adpreclone.


However when checked the status using: adop -status -detail , there were no active sessions.


Solution:

Patch 22271970: ADPRECLONE.PL FAILS ON DELTA 7

adop phase=apply patches=22271970

No comments: