Monitoring oracle rman backup status and timing.

Backup is very important part of oracle database.Being Oracle DBA, Regularly we are doing backup of oracle database for recovery. To check the status of rman backup job we can use below script. We can use view v$rman_status, v$rman_backup_job_details and V$SESSION_LONGOPS to monitor the current executing RMAN jobs and the status of the previously completed backups.


Check RMAN Backup completion details.


SQL>select (select NAME from v$database) Instance, object_type,operation,status,session_stamp,
round((end_time - start_time) * 24 * 60, 2) Elapsed_Time,
decode(to_char(start_time, 'd'), 1, 'Sunday', 2, 'Monday',
                                     3, 'Tuesday', 4,'Wednesday',
                                     5, 'Thursday', 6, 'Friday',
                                     7, 'Saturday') dow,
to_char(start_time, 'mm/dd/yyyy hh:mi:ss') start_time,
to_char(end_time, 'mm/dd/yyyy hh:mi:ss') end_time,
round((input_bytes/(1024*1024*1024)),2) input_gb,
round((output_bytes/(1024*1024*1024)),2) output_gb
from v$rman_status
where start_time > trunc(sysdate-10) and operation = 'BACKUP';


Check Oracle Database RMAN Backup and Restore Operations progress.


SQL>select SID, START_TIME,TOTALWORK, sofar, (sofar/totalwork) * 100 done,sysdate + TIME_REMAINING/3600/24 end_at
from v$session_longops where totalwork > sofar
AND opname NOT LIKE '%aggregate%'
AND opname like 'RMAN%';



For rman backup  you may check at ⇒⇒ RMAN Backup scripts

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