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

Warning Message When Creating A Keystore

  Warning Message When Creating A Keystore When we try to list the contents of the keystore, using the below command, keytool -list -v -keystore adkeystore.dat Enter keystore password: Keystore type: JKS Keystore provider: SUN Your keystore contains 1 entry Alias name: prod_apps002 Creation date: Jan 26, 2012 Entry type: PrivateKeyEntry Certificate chain length: 1 Certificate[1]: Owner: CN=PROD_apps002, OU=apps, O=apps002, C=US Issuer: CN=PROD_apps002, OU=apps, O=apps002, C=US Serial number: 4f208085 Valid from: Thu Jan 26 01:21:57 AST 2012 until: Tue Jan 16 01:21:57 AST 2052 Certificate fingerprints:          MD5:  XX: XX XX XX          SHA1:  XX: XX XX XX          SHA256:  XX: XX XX XX Signature algorithm name: SHA1withDSA Subject Public Key Algorithm: 1024-bit DSA key Version: 3 ******************************************* ******************************************* Warning: The JKS keystore...
Post a Comment
Read more

XX_XXXXXXX is not a valid responsibility for the current user. Please contact your System Administrator.

  XX_XXXXXXX is not a valid responsibility for the current user. Please contact your System Administrator. Issue : When user logs into EBS, he gets the following Error :  xx_XXXXX  is not a valid responsibility for the current user. Please contact your System Administrator. Solution: 1. Check if the responsibility is end dated.  Extend the end-date if required and try to login again.  2. Check the profile option  Applications Start Page for the user ( User Level). If there is any value defined, remove it and save it. Try to login again and it worked in our case.  Before: After:
Post a Comment
Read more