Install, Upgrade, Clone, Patch - EBS (MOSC)

MOSC Banner

ADOP Abort failed with ORA-21700: object does not exist or is marked for delete

edited Nov 2, 2016 5:00AM in Install, Upgrade, Clone, Patch - EBS (MOSC) 8 commentsAnswered

I was test applying 12.2.6 patch to my audit environment and it errored out due to several "Crossedition triggers "FND_EID_TriggerName_T1" does not exist"

So i abort the curect failed adop session, however it kept erroring out  with the following

Log: /u02/appaudit/fs_ne/EBSapps/log/adop/97/20161024_160307/adop.log
===========================================================================

Running abort phase.
    Log: @ADZDSHOWLOG.sql "2016/10/24 16:04:02"
    [ERROR]     Failed to execute sql statement:
        alter session set events='10624 trace name context forever, level 1';
        declare
        begin
          ad_zd_adop.abort(x_mode=>'ADOP',x_session_id=>97);
        exception
          when others then
            ad_zd_adop.update_session_status_failed(97);
            commit;
            raise_application_error(-20001,'Error while calling ad_zd_adop.abort' || sqlerrm);

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center