Skip to main content

CLEARING an ADOP patching session

In some case adop prepare phase fails due to some issues and if you wish to apply any patch in hotpatch mode, it will fail with below errors

 [STATEMENT] There is already a session which is incomplete. Details are:
[STATEMENT]     Session Id: 2
[STATEMENT]     Prepare phase status: R
[STATEMENT]     Apply phase status: N
[STATEMENT]     Cutover  phase status: N
[STATEMENT]     Abort phase status: N

[STATEMENT]     Session status: F
[ERROR]     Cannot apply hotpatch as another online patching cycle is going on
[ERROR]     Unrecoverable error occured. Exiting the current session.
[STATEMENT] [START 2019/10/22 16:13:00] Unlocking sessions table
[STATEMENT] [END   2019/10/22 16:13:00] Unlocking sessions table
[STATEMENT] Log file: /adop_20191022_161221.log
[STATEMENT] [START 2019/10/22 16:13:02] Unlocking sessions table
[STATEMENT] [END   2019/10/22 16:13:03] Unlocking sessions table
Can't call method "close" on an undefined value at /u01/apps/TEST/fs1/EBSapps/appl/au/12.0.0/perl/ADOP/Phase.pm line 239.


Now, if you try to cleanup the previous session using below

$ adop phase=cleanup

  [ERROR]     Error: Pending session of prepare/apply/cutover exists
  [ERROR]     Hint: Before trying cleanup complete the pending session
  [STATEMENT] [START 2019/10/22 16:18:36] Unlocking sessions table
  [STATEMENT] [END   2019/10/22 16:18:36] Unlocking sessions table
  [STATEMENT] Log file: /u01/apps/TEST/fs_ne/EBSapps/log/adop/2/adop_20191022_161746.log

adop exiting with status = 2 (Fail)


The solution is to abort the patching cycle as shown below:
Type Y when prompted 

$ adop phase=abort

...

[STATEMENT]           one patch is already applied for the session id
The above session would be aborted/rolled back. Do you want to continue [Y/N]? Y



[STATEMENT] adop phase=abort - Completed Successfully


$ adop -status

Node Name       Node Type       Phase       Status          Started                        Finished                       Elapsed
--------------- --------------- ----------- --------------- ------------------------------ ------------------------------ ------------
oel7            master          PREPARE     SESSION ABORTED 22-OCT-19 02:33:06 +03:00      22-OCT-19 02:54:06 +03:00      0:20:00
                                APPLY       SESSION ABORTED
                                CUTOVER     SESSION ABORTED
                                CLEANUP     SESSION ABORTED




File System Synchronization Used in this Patching Cycle: None

For more information, see the full ADOP Status Report.
Generating full ADOP Status Report at location: /u01/apps/TEST/fs_ne/EBSapps/log/status_20191022_162759/adzdshowstatus.out
Please wait...
Done...!

adop exiting with status = 0 (Success)












Comments

  1. Billcarson12 December 2020 at 06:55

    This comment has been removed by a blog administrator.

    ReplyDelete
  2. Unknown15 July 2021 at 14:06

    Thanks for sharing this blog. The content is beneficial and useful. Very informative post. Visit here to learn more about Data Warehousing companies and Data analytics Companies. I am impressed by the information that you have on this blog. Thanks once more for all the details.Visit here for Top Big Data Companies.

    ReplyDelete
  3. Expert_service8 February 2022 at 01:39

    Some truly wonderful work on behalf of the owner of this internet site , perfectly great articles . Entrümpelung Berlin

    ReplyDelete
  4. Muhammed Ali12 August 2022 at 13:05

    Thanks

    ReplyDelete

Post a Comment

Popular posts from this blog

12.1.0 Grid Installation on Solaris 11.3 fails with ASM failed to start

Issue Description  We faced one issue, while installing the GI 12.1.0.1.0 on Solaris 11.3  ASM failed to start. Check /u01/app/grid/cfgtoollogs/asmca/asmca-201202PM061908.log for details. 2020/12/02 18:19:17 CLSRSC-184: Configuration of ASM failed 2020/12/02 18:19:17 CLSRSC-258: Failed to configure and start ASM Died at /u01/app/12.1.0/grid_1/crs/install/crsinstall.pm line 1976. The command '/u01/app/12.1.0/grid_1/perl/bin/perl -I/u01/app/12.1.0/grid_1/perl/lib -I/u01/app/12.1.0/grid_1/crs/install /u01/app/12.1.0/grid_1/crs/install/rootcrs.pl ' execution failed This error is coming during root.sh execution on primary node. After checking the asmca logs, the error seen is as below: ========================== [main] [ 2020-12-02 17:00:49.575 AST ] [UsmcaLogger.logException:156] SEVERE:method oracle.sysman.assistants.usmca.backend.USMInstance:configureLocalASM [main] [ 2020-12-02 17:00:49.575 AST ] [UsmcaLogger.logException:157] ORA-27122: unable to protect memory [main] [ 2020-1...
Post a Comment
Read more

Health Check Script

Oracle Database Health Check Script Run this script has sysdba user or any user having DBA Role Change the spool file patch to correct directory. In this example it is set to  /export/home/oraprod/ $ cat Health_Check_Script.sql set pagesize 1100 SET MARKUP HTML ON SPOOL ON spool /export/home/oraprod/health_check_new.html set feedback off set linesize 200; set pages 50 set lines 1000 set pages 70 set heading on PROMPT================================================================ prompt PROMPT PROMPT Daily_Monitoring Checkup Report prompt ================================================================================================================================================= PROMPT REPORT DATE select to_char(sysdate,'DD-MON-YYYY:HH:MI:SS') "Report Run Date" from dual; prompt DATABASE NAME PROMPT ============== select instance_name,host_name,version,status from gv$instance ,v$database a; PROMPT DATABASE INFO PROMPT =============...
1 comment
Read more

12.2 Stage area creation fails with startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java: No such file or directory

 12.2 Stage area creation fails with startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java: No such file or directory While creating the stage area for 12.2 Installation, we face issue while running the buildstage.sh ....startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java: No such file or directory Solution:  Please go to the path provided in the error log and check if the java is working fine with below command: java -version Generally this java is having some issues.   Install the jre 7 or jre 8 and copy the the jre at the same path by renaming old folder. It should work fine.  Now if your run the build command again, it should succeed.  Running command: /u01/soft/ebs/startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java -classpath /u01/soft/ebs/startCD/Disk1/rapidwiz/bin/../jlib/emocmutl.jar:/u01/soft/ebs/startCD/Disk1/rapidwiz/bin/../jlib/ewt-3_4_22.jar:/u01/soft/ebs/startCD/Disk1/rapidwiz/bin/../jlib/share-1_1_18.jar:/u01/soft/ebs/star...
Post a Comment
Read more