ERROR: Patching cycle in progress - run this utility from patch file system

AD Administration error:.

ERROR:  Patching cycle in progress - run this utility from patch file system.

You can only run it from run file system when not patching.


Check the any active adop cycle by running the script ADZDSHOWED.sql:-

SQL> @ADZDSHOWED.sql
=========================================================================
= Editions
=========================================================================

Edition Name Type Status Current?
--------------- -------- -------- --------
EDITION1 PATCH ACTIVE
ORA$BASE ACTIVE
V_20000001_2001 ACTIVE



Solution:-

To resolve the issue test the following steps in a development/test instance and then migrate accordingly:

👉 Complete or abort any open patching cycles using adop phase=abort.

👉 Any remaining database editions (for example 'EDITION1') will need      to be addressed by the DBA.

👉 Run ADZDSHOWED.sql to confirm the editions are corrected.

👉 Run adadmin and and confirm it proceeds without error.

adgentns.pl exiting with status 2 after Clone

This article is very useful for those who encountered issue while cloning EBS adgentns.pl exiting with status ****.

On application Release 12 When attempting to run autoconfig on APPS Tier, the following error occurs:

[CVM Error Report]

The following report lists errors encountered during CVM Phase
     
/u01/oracle/apps/apps_st/appl/ad/12.0.0/bin/adgentns.pl  2

No of scripts failed in CVM phase: 1


AutoConfig is exiting with status 1

AutoConfig execution completed on Mon Aug 26 03:26:41 2019


adgentns.pl exiting with status 2 after Clone/Refresh

Autoconfig Error: adgentns.pl exiting with status 2 after Clone/Refresh


Error:-

[CVM Error Report]
            The following report lists errors encountered during CVM Phase
            /u01/oracle/apps/apps_st/appl/ad/12.0.0/bin/adgentns.pl  2
            No of scripts failed in CVM phase: 1
            AutoConfig is exiting with status 1


Solution:-

Open a new shell and source the APPS Environment. 

($APPL_TOP/APPS_.env)

$sqlplus apps/apps

SQL> exec fnd_conc_clone.setup_clean;

SQL>commit;


Open a new terminal or shell and source the DB Tier Environment.

Execute Autoconfig on the DB Tier. 

($ORACLE_HOME/appsutil/bin/adconfig.sh)
 
Switch back to the APPS environment or start a new shell and source the


APPS Tier:-

Execute Autoconfig at the Apps Tier. ($AD_TOP/bin/adconfig.sh)
 
Check the Autoconfig log for any errors and ensure that the services start correctly.

$sh adstrtal.sh

Clearing redo logfile in oracle database.

Sometimes redo log file become corrupted while database open the database may "lock up" and we are unable to do anything because archiving can't continue this case you may execute 'ALTER DATABASE CLEAR LOGFILE' statement to reinitialize the redo log file and database continue processing.


SQL> select GROUP#,SEQUENCE#,MEMBERS,ARCHIVED,STATUS from v$log;

    GROUP#  SEQUENCE#    MEMBERS ARC STATUS
---------- ---------- ---------- --- ----------------
         3      69151          2 YES UNUSED
         5      69150          2 YES INACTIVE
         4      69152          2 NO  CURRENT



Note:- Specifying UNARCHIVED makes backups unusable if the redo log is needed for recovery. Do not use CLEAR LOGFILE to clear a log needed for media recovery.

If the corrupted redo log file has not been archived, use the unarchived keywordin the alter database clear logfile statemnent.

SQL> ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 5;


The unarchived option clears the corrupt online redo log and avoids archiving it.