Thursday, May 12, 2022

Cutover failed on 12.2

 

                                      

 adop phase=cutover restart=no

Statement handler reference is invalid.

Session killed.

 Note that this is normal in the online patching cutover phase.

 DB-Handle Error Code: 28

 DB-Handle Error Message: ORA-00028: your session has been killed (DBD ERROR: OCIStmtExecute/Describe)

 Reconnecting to the database.    [ERROR]     adop phase=cutover failed on Node: "sridev1"

    [ERROR]     adop phase=cutover failed on Node: "sridev2"

    [UNEXPECTED]adop phase=cutover on all the nodes returned failure.

    [UNEXPECTED]Unable to continue processing.

    [UNEXPECTED]Error running "adop phase=cutover" on node(s): sridev1 and sridev2.


Summary report for current adop session: 

    Node sridev1: Failed

       - Cutover status:    FS_CUTOVER_COMPLETED

    Node sridev2: Failed

       - Cutover status:    FORCE_STARTUP_COMPLETED

    For more details, run the command: adop -status -detail

[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 = 2 (Fail)



Solution:-

Please check the adop.log under cutover directory like below
vi /app/<dbname>/fs_ne/EBSapps/log/adop/35/12345_67890/cutover/sridev1/adop.log

[UNEXPECTED]Error occured submittimg compile_invalid_objects job.
[UNEXPECTED]Cutover phase has failed.

if you see above error please execute below steps

1. Check to see if the job is already scheduled:SELECT JOB_NAME, STATE FROM DBA_SCHEDULER_JOBS WHERE JOB_NAME = 'AD_COMPILE_INVALID_OBJECTS';If it returns:JOB_NAME STATE
-------------------------------------- ------------------------------------------
AD_COMPILE_INVALID_OBJECTS SCHEDULED2. Drop the job as apps user.BEGIN
dbms_scheduler.drop_job(job_name => 'AD_COMPILE_INVALID_OBJECTS');
END;3.Rerun the cutover:adop phase= cutover



No comments:

Post a Comment