Adop Cutover Fails With Error PLS-00201: identifier 'SYS.AD_ZD_SYS' must be declared

Reference (Doc ID 2922410.1)

-------------------------------------------------------------------------- 

[oraprod@deverpdb01 19.3.0]$ . UPG_deverpdb01.env

[oraprod@deverpdb01 19.3.0]$ sqlplus system/manager@UPG

SQL*Plus: Release 19.0.0.0.0 - Production on Tue Dec 5 10:37:39 2023

Version 19.21.0.0.0

Copyright (c) 1982, 2022, Oracle.  All rights reserved.

Last Successful login time: Tue Dec 05 2023 09:59:37 +03:00

Connected to:

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

Version 19.21.0.0.0

SQL> alter trigger SYSTEM.EBS_LOGON disable;

Trigger altered.

SQL> commit;

[applprod@deverpapp01 scripts]$ adop phase=cutover

After completion of cutover phase again enable this trigger as below

SQL> alter trigger SYSTEM.EBS_LOGON enable;

Trigger altered.

SQL> commit;

 

Help:

1.   query to check cutover phase status

SQL>select NODE_NAME,ADOP_SESSION_ID, PREPARE_STATUS , APPLY_STATUS  ,CUTOVER_STATUS, CLEANUP_STATUS , ABORT_STATUS , STATUS

from AD_ADOP_SESSIONS where ADOP_SESSION_ID=79;

2.     Status meaning

cutover_status=’Y’ ‘COMPLETED’
cutover_status not in (‘N’,’Y’,’X’) and status=’F’ ‘FAILED’
cutover_status=’0′ ‘CUTOVER STARTED’
cutover_status=’1′ ‘SERVICES SHUTDOWN COMPLETED’
cutover_status=’3′ ‘DB CUTOVER COMPLETED’
cutover_status=’D’ ‘FLIP SNAPSHOTS COMPLETED’
cutover_status=’4′ ‘FS CUTOVER COMPLETED’
cutover_status=’5′ ‘ADMIN STARTUP COMPLETED’
cutover_status=’6′ ‘SERVICES STARTUP COMPLETED’
cutover_status=’N’ ‘NOT STARTED’
cutover_status=’X’ ‘NOT APPLICABLE’



Comments

Popular posts from this blog

adop phase=prepare failed with error "data dictionary corrupted"

Apply Latest CPU Patch of April 2024 on Oracle EBS R12.2.7 Application and Database 19c

upgrade the AD/TXK Delta Patch to 14 in Oracle EBS R12.2.7