Error in ADOP Cleanup phase

==================

Enter the APPS password:

Connected.

==============================================================

ADOP (C.Delta.12)

Session Id: 4

Command: status

Output: /apdascn7i/product/122/fs_ne/EBSapps/log/adop/4/20220217_232656/adzdshowstatus.out

===============================================================

Node Name       Node Type  Phase           Status          Started              Finished             Elapsed

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

shsebs7idb1     master     PREPARE         COMPLETED       2022/02/15 07:02:15  2022/02/15 12:52:39  5:50:24

                           APPLY           COMPLETED       2022/02/15 16:22:33  2022/02/15 21:06:33  4:43:00

                           FINALIZE        COMPLETED       2022/02/16 23:15:37  2022/02/16 23:49:17  0:33:40

                           CUTOVER         COMPLETED       2022/02/17 06:42:44  2022/02/17 07:24:30  0:41:46

                           CLEANUP         RUNNING

 

 

 

File System Synchronization Type: Full

 

SQL> select adop_session_id,status from ad_adop_sessions where status='F';

 

ADOP_SESSION_ID S

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

              4 F

 

SQL> update ad_adop_sessions set status='C' where status='F';

 

1 row updated.

 

SQL> commit;

 

Commit complete.

 

SQL> exit

Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

[apebs7i@shsebs7idb1 ~]$ adop -status

 

Enter the APPS password:

Connected.

==============================================================

ADOP (C.Delta.12)

Session Id: 4

Command: status

Output: /apdascn7i/product/122/fs_ne/EBSapps/log/adop/4/20220219_065432/adzdshowstatus.out

===============================================================

Node Name       Node Type  Phase           Status          Started              Finished             Elapsed

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

shsebs7idb1     master     PREPARE         COMPLETED       2022/02/15 07:02:15  2022/02/15 12:52:39  5:50:24

                           APPLY           COMPLETED       2022/02/15 16:22:33  2022/02/15 21:06:33  4:43:00

                           FINALIZE        COMPLETED       2022/02/16 23:15:37  2022/02/16 23:49:17  0:33:40

                           CUTOVER         COMPLETED       2022/02/17 06:42:44  2022/02/17 07:24:30  0:41:46

                           CLEANUP         NOT STARTED

 

 

 

File System Synchronization Type: Full

 

===========================================================================

ADOP (C.Delta.12)

Session ID: 4

Node: shsebs7idb1

Phase: cleanup

Log: /apdascn7i/product/122/fs_ne/EBSapps/log/adop/4/20220219_065527/adop.log

===========================================================================

 

Processing cleanup actions in parallel.

    Log: /apdascn7i/product/122/fs_ne/EBSapps/log/adop/4/20220219_065527/cleanup/shsebs7idb1/log/cleanup.log

 

Generating report of queued DDL actions.

    Output: /apdascn7i/product/122/fs_ne/EBSapps/log/adop/4/20220219_065527/cleanup/shsebs7idb1/adzdallddls.out

 

Running cleanup in STANDARD mode.

    Log: @ADZDSHOWLOG.sql "2022/02/19 06:57:35"

 

Generating log report.

    Output: /apdascn7i/product/122/fs_ne/EBSapps/log/adop/4/20220219_065527/cleanup/shsebs7idb1/adzdshowlog.out

 

The cleanup phase completed successfully.

 

 

adop exiting with status = 0 (Success)

 

Check ADOP status once again

 

[apebs7i@shsebs7idb1 ~]$ adop -status

 

Enter the APPS password:

Connected.

==============================================================

ADOP (C.Delta.12)

Session Id: 4

Command: status

Output: /apdascn7i/product/122/fs_ne/EBSapps/log/adop/4/20220219_065834/adzdshowstatus.out

===============================================================

Node Name       Node Type  Phase           Status          Started              Finished             Elapsed

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

shsebs7idb1     master     PREPARE         COMPLETED       2022/02/15 07:02:15  2022/02/15 12:52:39  5:50:24

                           APPLY           COMPLETED       2022/02/15 16:22:33  2022/02/15 21:06:33  4:43:00

                           FINALIZE        COMPLETED       2022/02/16 23:15:37  2022/02/16 23:49:17  0:33:40

                           CUTOVER         COMPLETED       2022/02/17 06:42:44  2022/02/17 07:24:30  0:41:46

                           CLEANUP         COMPLETED       2022/02/19 06:56:17  2022/02/19 06:57:43  0:01:26

 

 

 

File System Synchronization Type: Full 

Comments

Post a Comment

Popular posts from this blog

How to fix Oracle SQL Developer connection issue "Got minus one from a read call"

Image
 During connection from SQL Developer to EBS database got below error message: Status : Failure - Test failed: IO Error: Got minus one from a read call Following solution can be done : 1. Go to directory $ORACLE_HOME / network / admin 2. Modify sqlnet.ora file with following parameter : tcp.validnode_checking = no 3. If you don 't want to disable this, you can put the machine names as follows: tcp.invited_nodes=(machine1, machine2) 3. Bounce the listener. Due to security enhancements it is not good to put tcp.validnode_checking = no or comment out will through error when we start listener like below: Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=shsebs7idb1.appsolworld.com)(PORT=1522))) TNS-00584: Valid node checking configuration error TNS-12560: TNS:protocol adapter error Better plan is to add localhost or IP address of client (Local Computer) in the sqlnet.ora file That will solve the problem NAMES.DIRECTORY_PATH=(TNSNAMES, ONAMES, HOSTNAME) SQLNET.EXPI
Read more

How to troubleshoot Long Running Concurrent Request in EBS 12.2

 The following points need to answer before jumping into troubleshooting: Are there any recent code changes done in the concurrent program?           Check long_running_sid and verify the recent code change of last_ddl_timestamp after a             discussion with the developer. Was this running long in the last few run as well, or was this time only?            ==> Check the program history. How much time does it take to complete?           Once again program history can give us some idea. Are these jobs fetching higher data compared to the last run           ===> Confirm on data change . Query Plan change will indicate this issue. Does this job runs at any specific time or it can be run anytime           ===> The nature of the job can help to understand the job's nature. Does this job fetch data using DB Link          ====> Check whether the DB link is involved or not. The below-given approach would help to conclude the gray areas. Check the load of the server using t
Read more

Few Important steps of Oracle Database Clone

 Make Sure oraInst.loc location is correct and accessble. [demantra@dsiddem ~]$ cat /etc/oraInst.loc inventory_loc=/orastage/oraInventory inst_group=dba [demantra@dsiddem ~]$ cd /orastage/oraInventory [demantra@dsiddem oraInventory]$ ls -ltr total 16 drwxrwx---. 5 demantra dba 4096 Jul 22 19:37 backup drwxrwx---. 2 demantra dba 4096 Jul 22 19:37 ContentsXML drwxrwx---. 2 demantra dba 4096 Jul 22 19:37 locks drwxrwx---. 3 demantra dba 4096 Jul 23 10:08 logs Remove Oracle Home from Inventory [demantra@dsiddem oraInventory]$ cd $ORACLE_HOME/oui/bin [demantra@dsiddem bin]$ ./runInstaller -detachHome ORACLE_HOME=$ORACLE_HOME Starting Oracle Universal Installer... Checking swap space: must be greater than 500 MB.   Actual 3039 MB    Passed The inventory pointer is located at /etc/oraInst.loc Run Clone.pl [demantra@dsiddem bin]$ echo $ORACLE_HOME /dnbsid/demantra/oracle/19.0.0 [demantra@dsiddem bin]$ echo $ORACLE_BASE /dnbsid/demantra [demantra@dsiddem bin]$ E01=ORACLE_HOME=$ORACLE_HOME [dema
Read more